ver. 5.45.0 breaks the site

I also had major style issues with 5.45.0 and had to rollback to the previous version. Interestingly, most of my style issues only showed up for guest users, not logged in users.

Thanks for using our plugin and reporting a problem!

Could you please share URL of a page where we could check the problem?

I cannot share a URL because I had to rollback to a previous version of the plugin to avoid presenting an ugly mess to my customers. In my testing, though (which including disabling all caching and performance optimizations on my site), it appeared that some CSS files for the plugin (frontend.css and maybe others) were not being loaded for users who were not logged in.

Thanks for providing additional information.

We’ve checked visual appearance of reviews for non-logged-in uses on our test website but could not see any issues. Unfortunately, it will be very difficult to troubleshoot the problem further without being able to see it on some sample page.

Yep. Front end is broken for non-logged in users in 5.45. Displays fine when logged in as an admin. Had to downgrade to 5.44 too.

• This reply was modified 1 year ago by meniscus1.

Still awaiting for someone to share a page with an example of this problem…

Well, you might be waiting for a while because we are all rolling back to a version of your plugin that doesn’t break our sites.Here are a couple of screenshots from my staging site, though.

From single product page:

From reviews grid:

I’m not seeing any console errors, but it is clear that frontend.css (and maybe other stylesheets) are not loading for guest users for some reason. Everything looks fine when logged in.

Thanks for sharing the screenshots and providing additional information.

We double checked it on our test website but unfortunately still cannot reproduce this problem.

If the issue is only impacting guests, it sounds like it might be caused by a “performance optimization plugin” because these plugins usually disable caching for logged-in users. That would explain why you don’t experience this problem when logged-in.

As I mentioned previously, I already tested this with all caching and performance optimization plugins disabled and the problem remained. Also, this problem doesn’t exist with version 5.44.0?of the plugin (even with all my caching and optimization plugins enabled) . Thus, it seems clear that there was a change made between 5.44.0 and 5.45.0 that contributes to this problem.

Perhaps there is a conflict with version 5.45.0 and some other plugin that I and the other posters all have in common. I tried disabling a lot of my plugins to determine any possible conflicts but was not able to find anything.

On my site, the pages containing the reviews were broken. I immediately reverted to the previous version of the plugin. If you wait a few hours, day and I’ll take screenshots. I need to find a time when the site has no visitors.

• This reply was modified 1 year ago by vinicius23.

/wp-content/plugins/customer-reviews-woocommerce/css/frontend.css not found if not logged in.

I took two screenshots. The first, with the “review slider”, the second with “all review” on another page. They are only broken when I am not logged in as admin. However, it is not a problem with the cashe plugin (wp fastest cache), which I disabled for testing.

Ops, I can’t attach the images, can use wetransfer.

click to wetransfer link:

https://we.tl/t-zkfjdwQ9GN

• This reply was modified 1 year ago by vinicius23.

Looks like frontend.css is not loaded for logged out users in 5.45.0. Thought it was WP Rocket at first, but the problem persisted despite disabling all caching and minifying settings. Incidentally, don’t you have a test environment with all the popular plugins that are used by most sites? I think this would help you mitigate the risks associated with other plugins.

Same problem here, please correct this bug. I use pro version.

thanks

Thanks for sharing screenshots and providing additional information. Unfortunately, it is still very difficult to understand the root cause of the problem because nobody has shared a URL of an actual page with the issue. The next version of the plugin (5.46.0) might resolve the problem but we cannot know for sure because we didn’t have this CSS problem on our test sites in the first place. Please install the latest update and share your observations.