-
Posts
-
Dear support,
On this website, background images and color areas no longer load properly. In the background you should see pictures and/or color areas but they are not there. This is the case on all pages.
We see that Enfold saves the css for each page separately. Something seems to have changed and because of this the css of the page can no longer be found. I see a 404 on (see link 2).
And it can only be solved by saving that specific page (you don’t have to change anything on the page). However, there needs to be a global fix to avoid having to save/update all pages.
Hey bonsaimedia,
Please send us a temporary WordPress admin login and login URL so that we can have a closer look. You can post the details in the Private Content section of your reply.
Best regards,
RikardHi,
Thanks for the update. Background images and backgrounds seems to be loading as they should now, did you manage to find a solution?
Best regards,
RikardHi,
Thanks for the update. The second site you posted looks fine on my end, images are loading and there are no missing files. The first one doesn’t anymore though, since it’s returning a 404 error on a style sheet (in private). Please try to check the file permissions of the containing folder on your server, or disable the post CSS creation using this filter in functions.php:
/** * Filter to skip css file generation. * You can add logic to skip for certain pages/posts only. * * @since 4.8.6.1 * @param boolean $create * @return boolean true | false or anything else to skip generation of css file */ function custom_avf_post_css_create_file( $create ) { return false; } add_filter( 'avf_post_css_create_file', 'custom_avf_post_css_create_file', 10, 1 );Best regards,
RikardThe file permissions on the folder are fine. I think the problem is that the css files are created in the the wrong folder. All the css files are located in “/wp-content/uploads/avia_posts_css”, but the folder requested is “/wp-content/uploads/dynamic_avia/avia_posts_css”.
Hi,
Thank you for your patience, when I check your example page in the back end I don’t see any background colors or background images set in the color sections on the page.
As I understood your posts above I thought you had background colors and images set in the color sections that were not showing on the frontend, am I understanding this correctly?
/wp-content/uploads/avia_posts_css was used prior to 5.3 and was only kept for cache backward compatibility, it is no longer used.
Saving the Theme Setting after the update should have copied the css files to /wp-content/uploads/dynamic_avia/avia_posts_css after the update, but it would not change the element settings and when the Enfold Theme Options ▸ Performance ▸ JS & CSS file merging and compression is disabled those css files would not be called and the element settings would take over.
I see your Enfold Theme Options ▸ Performance ▸ JS & CSS file merging and compression is disabled now.
Can you identify which elements on that page don’t show the expected background colors or background images, perhaps I missed it.
The Grid element at the top of the page shows a background color and image and it shows on the frontend, is this the only element?
If this is true and the issue is when you enable the Enfold Theme Options ▸ Performance ▸ JS & CSS file merging and compression because the css is calling the wrong path, I recommend copying the /wp-content/uploads/avia_posts_css files via FTP and adding them to the /wp-content/uploads/dynamic_avia/avia_posts_css folder manually.
Perhaps a security plugin or file permissions are not allowing the move automatically.Best regards,
MikeHi,
Thanks for your feedback, and I have checked your page /aanbevelingen/ but I don’t see any failed requests for css, such as post-10755.css, so I’m not sure what occurred but it seems to be sorted out now?Best regards,
MikeHi,
Can you create a staging site with the function disabled and an admin login so we can see the error? We have not experienced this on our sites so I wonder if it is related to a server setting, can you tell us about your server is it using object-oriented cache? Have you tried disabling your server cache or any CDN cache?
Once we can see the error I will ask the rest of the team for ideas, The Dev Team states that
/wp-content/uploads/avia_posts_css was used prior to 5.3 and was only kept for cache backward compatibility, it is no longer used.
Saving the Theme Setting after the update should have copied the css files to /wp-content/uploads/dynamic_avia/avia_posts_css after the update and used going forward.
It sounds like a cache, either a plugin, server, or CDN, etc, is still calling the old location, since we can’t recreate the issue it is hard to say.Best regards,
Mike
- You must be logged in to reply to this topic.