Chat and several icons on 5.3.1 are missing

[Wayne Luke]

When stored as files, the CSS files will end up in /core/clientscript/vbulletin_css. vBulletin uses a variable to reference the image properly. {vb:stylevar imgdir_spriteiconsvb}. This should be images/css and it should reference /images/css built off the basepath and Frontend URL.

Did you change that style variable? If you did, then you need to make sure the images are stored in the location specified.

You might try updating the style variable so it uses your CDN directly.

[discoverxs3]

Wayne Luke
so yeah by changing just Store CSS Stylesheets as Files? from yes to no
it changes the path.


right now we switched to Store CSS Stylesheets as Files? NO
so you can check the paths at discoverxs.com

[discoverxs3]

so yeah by changing just Store CSS Stylesheets as Files? from yes to no
it changes the path

[discoverxs3]

What is the computed path to the sprites according to Chrome's Developer Tools?

when using the cdn settings:
Store CSS Stylesheets as Files? NO

images/css/sprite_icons_vb_ltr.png?v=531
or check the links that are pulled with the test
https://www.webpagetest.org/result/1...37a/1/details/

when using the cdn settings with export cdd to file

Store CSS Stylesheets as Files? YES

https://discoverxs-440990.c.cdn77.or..._ltr.png?v=531

and a link with this
https://www.webpagetest.org/result/1...5cd/1/details/





so by using a simple diff compare in the Request Headers section

[Wayne Luke]

What is the computed path to the sprites according to Chrome's Developer Tools?

[discoverxs3]

We reference css.php as css.php not /core/css.php. The sprites and images used in CSS are located in /images not /core/images. /core/images contains smilies and posticons.

If you're using a CDN and the path changes, you would have to manually adjust the URLs for images and backgrounds in the CSS as needed to reflect where you're storing the images.

we are using cdn77
so the path is the same..

first hit caches the file next one serves it from the cdn

so
xxxxxxx.com/something/
is the same as
cdnxxxxxx.com/something

also
i just found out
that the sprites are served from different location if they are exported as a file instead of https://************/css.php?styleid=1&td=ltr&sheet=css_imgareaselect-animated.css,css_jquery-ui-1_11_4_custom.css,css_jquery_qtip_min.css,css_jquery_selectBox.css,css_global.css&ts=1 503586184
for example

So using a CDN of cache on first hit with same path :

https://discoverxs.com/images/tmp/discoverxs_messenger.jpg
https://discoverxs-440990.c.cdn77.org/images/tmp/discoverxs_messenger.jpg

its messing the sprites path too.am i going crazy or what ?


and again Wayne thanks for the outstanding support over the past years

[Wayne Luke]

We reference css.php as css.php not /core/css.php. The sprites and images used in CSS are located in /images not /core/images. /core/images contains smilies and posticons.

If you're using a CDN and the path changes, you would have to manually adjust the URLs for images and backgrounds in the CSS as needed to reflect where you're storing the images.

[discoverxs3]

You're storing your CSS on a different server. This can cause problems referencing images properly. Since css.php is actually in the /core/ directory it can be using that as the relative URL base.

Thanks for the reply,
actually the css is on the CDN.
so yes different place.

thanks for clearing it up


but that means that everyone that uses the CDN option should

replace to core/images/css/

not /images/css/

[Wayne Luke]

You're storing your CSS on a different server. This can cause problems referencing images properly. Since css.php is actually in the /core/ directory it can be using that as the relative URL base.

[discoverxs3]

After upgrade
some of the icons ware missing (the chat bubble... the like icon on mobile/. the calendar ... etc)


To fix this we just had to re-upload manually
sprite_icons_vb_ltr.png and
sprite_icons_vb_rtl.png


BUT
not to /images/css/

but to core/images/css/

and it will work.

yeasy enough right .. duh....




but it took me a week to figure something so simple out.



The question is .. why does it want the core path and not the the original path (as in the installation package) in which all initial files are stored...

bug during the last upgrade ?