There is no icon_search_adv.gif file anywhere. The only place it exists, is as a path in the colours css file.
I suggest finding an icon for this path or removing the _adv from the path name to use the simple mag icon until you can find the right icon..

Also, i never understood why arent the prosilver icons made to fit any background.
The white border on icons makes them look terrible on black or coloured backgrounds. Same for the smilies.

icons are managed in sets and the large like styled icons were merged into sprites so all button icons are one sprite, all contact related icons are another set.

Since the rest of the icons are not like styled and created by several different individuals over several years its not possible to create a single sprite without recreating all the icons.

I actually put a lot of work into accomplishing this but it was to late in the development timeline to make such a big change and their are still some minor icons that require backend changes in order to get it all to work properly.

this has since died as with 3.2 we will be utilizing font-awsome for all of our icons.

hanakin wrote:this has since died as with 3.2 we will be utilizing font-awsome for all of our icons.

will these icons be called from within the phpbb forum software? or will it depend on the external site to provide them?

reason i ask is when phpbb.com went down, logging into the ACP was lagging as it had to connect to phpbb.com for version information. if for some reason font awesome icon location goes down for any reason, will there be some kind of icon set to fall back on?

otherwise, if the connection to the font awesome server fails, there will be no icons to see

spaceace wrote:so the icons will not rely on an external site? can someone confirm this?

Yes and no. There will be an option to rely on a cdn, like we do with jQuery now, but this won't be enabled by default.

That's if we go with something like LESS where one can specify variables and we can then use those to specify where the images are coming from. Otherwise it's just going to be local. So far things are pointing at a LESS-type parser so the former is likely going to be the end result.