Hi,
After some design fixes our designer moved all the css files into their own folder as a child of the major designs folder.
Now the associated files referenced in the css aren't appearing on the front end, it's just blank. The URLs in the css are using the mysource_files/icon_pdf.gif style URL, which used to work fine.
The files related to a different site are working fine. The difference seems to be that the ones that work with the other site have a URL like __data/assets/image/0015/3750/logo_left.jpg while the ones for my first site that isn't working have the URL _designs/css/foldername/common.css/icon_pdf.gif.
The _designs webpath is applying to both newly uploaded associated files and ones that used to work.
After trying to get my head around similar problems on this board I guess my files aren't saved in that mysource_files folder anymore, but I don't understand why or how to get them back in there.
If I can change the webpath to a __data one, will it start working? If so, how do I do this?
The css files are linked to the parse file via a linked_css customisation.
The mysource_files folder doesn't actually exist -- as long as the images are children of the CSS File asset, Matrix should still be able to see them. I suspect the CSS File has either lost its Public Read Permission or Live status (or the child image assets have). That would explain the non-Live URLs for your image assets.
It might be quicker to open a Support request so that one of our helpful support people can take a peek and work out what's happened! :)
faceplant
Permissions.
I need to make myself a problem workflow. Check live, check permissions, then go and examine all the other bits.
Thank you!
[quote]faceplant
Permissions.
I need to make myself a problem workflow. Check live, check permissions, then go and examine all the other bits.
Thank you![/quote]
Hi Rachel,
If all files/images are in Matrix, you can always use id numbers in css files “./?a=7896” where “7896” is asset (image) ID number. this works for me.
Or you could place images under paths you want, set them “under construction” and give them write permission for public user so images will keep normal paths. Example:
http://www.image.com/images/pdf_files.gif
Both of these are bad ideas for performance reasons: It means Matrix has to serve each CSS/Image and cannot cache it. The browser is also unable to cache files delivered in this way. If you are having performance-related issues, this could be a key contributor.