narratorben

Thanks, it wasn’t actually late replies. I thought the speed was in line with what I would expect from this type of support. The main problem was the lack of info in the replies, many were just a single sentence along the lines of “this is fixed”. This may feed into the support team being overloaded and rushing still but for me I’d rather wait a little longer and get a well thought out reply, explaining what has been done and anything I might need to do differently.

In the specific case of my original call that would have been that you had modified the files on my site to fix the issue and that meant that I couldn’t update the plugin. It took 5 or 6 emails back and forth to extract that info from the support team which actually ended up taking more time for both of us than if that info had been included in the original reply.

Hope this clarifies things and I know how easy it is to rush and neglect the explanations when you’re busy so just making that point that doing so actually increases your workload by multiplying the amount of replies back and forth.

OK.. I performed 2 tests:

Test 1 (there was no issue after performing this test):

– Clear server cache by deleting contents of /usr/local/lsws/cachedata (I used this method instead of the purge all button in wordpress admin to be 100% sure the cache was clean)
– Starting with a clean browser cache in chrome I clicked around various pages on the site, at no point did I add anything to the basket.
– Pages were cached publically according to the headers.
– I hit the “purge all” button in the Litespeed cache settings.
– Everything looked fine after refreshing the page

Test 2 (this is the one that breaks it)

– Clear server cache by deleting contents of /usr/local/lsws/cachedata.
– Starting with a clean browser cache in chrome I clicked around various pages on the site, I browsed the shop and added some items to the basket, visited the checkout / basket removed some items etc.
– Pages were cached privately according to the headers.
– I hit the “purge all” button in the Litespeed cache settings.
– At this point on refreshing the page and got 404 errors on the CSS and JS files created by litespeed cache.. The 404’s were on files like https://www.twobirdsspirits.co.uk/wp-content/litespeed/cssjs/e7d66.css?d2cff and https://www.twobirdsspirits.co.uk/wp-content/litespeed/cssjs/da6d0.js?0f112 on checking the litespeed/ccss folder in wp-content (ccss was the only folder now present in litespeed) the only files in there are archive.css, front.css and page.css

Let me know if you need more info, the problem appears to be if pages at any point have been privately cached once I add even one item to the basket and purge the cache I see the issue.

If I click around the site without any items in the cart then purging the cache seems to work fine.

If however I have ever had any items in the cart weather they are still there or not then the issue happens so it seems to be an issue with the private caching. But that is just a guess based on my testing!

Thanks qtwrk,

I gave that a go (it was set to 200 before) and then restarted lsws to be sure.

The problem is still happening, it seems to happen if I have products in the cart, or if I had products in the cart.. I have the cache cart privately option enabled.. My first test was to just put some pages in the cache with nothing in the the cart then do a “purge all” from the wordpress admin. That seemed to work fine, on the next page load the site loaded properly.

Then I tested by clicking around first to put some non private pages in the cache, verifying cache hits by inspecting the headers.. Then I put some items in the cart and clicked around verifying the private cache hits again by looking at the headers.. Then I removed the items from the cart and tested to check I was now seeing the public cache which I was. This time when doing a purge all the site broke giving 404 errors on the litespeed cache files.. I gave it 30 seconds or so in case something was happening in the background but it stayed broken.

Hi qtwrk,

Apologies I had meant to mention that in my original post.. Serve stale has always been set to off.

thanks

Thanks Peter,

The file mode constant sounds like exactly what I need.

Thanks for the swift and knowledgeable help, very much appreciated.

Hi Peter,

Unfortunately it still doesn’t work, I’ve tried the permissions both ways around so either:

rw-rw— ftpuser:www-data

or

rw-rw— www-data:ftpuser

permissions on the folder are the same but 0770 rather than 0660

Neither works, I always either get wordfence complaining that it can’t write the files (even though the permission setup means it can) that happens with the second one, or I get it changing the permissions to 600 with the first option which locks out my FTP user and leads to the same error.

I think it is because with my setup when logged in to WordPress PHP has the permissions of FTP user and when logged out it has www-data so WF is getting confused.. Ideally I just need it to stop changing the permissions as I have already set them to something that works, is this possible?

Hi Peter,

Thanks for the reply, I think that I was setting it up the wrong way around, I was setting permissions of 660 with the FTP user as the owner and www-data as the group but Wordfence was then taking ownership and setting 600 effectively locking out the FTP user.

I’ve now set www-data as the owner with the FTP user as the group and 660 permissions so I’ll see how that goes.

Appreciate the help.

Hi there,

I have the same issue, I’m using Divi and after updating to Top Bar 2.0 the tpbr_front.js file throws an error, something about an unexpected identifier in the Chrome Console.

“Uncaught SyntaxError: Unexpected identifier
at HTMLDocument.<anonymous> (tpbr_front.js?ver=5.5:62)
at i (jquery.js?ver=1.12.4-wp:2)
at Object.fireWith [as resolveWith] (jquery.js?ver=1.12.4-wp:2)
at Function.ready (jquery.js?ver=1.12.4-wp:2)
at HTMLDocument.J (jquery.js?ver=1.12.4-wp:2)”

That error also breaks all javascript on the page so my contact forms and carousels stop working. If I downgrade to Top Bar 1.2 it doesn’t have the same issue so I’ve done that for now.