Block changes not showing after save
Permalink 1 user found helpful
I've just installed 5.7.5.2 and not done anything else to configure it. I added a content block to the Main area on the home page. The content is simply "aaa".
Now I edit the same content block and change it so that it reads "aaa bbb". When I save this, the page just shows the content as "aaa". And if I again edit the block, the Redactor editor just shows "aaa".
However, if I refresh the page then I get "aaa bbb". I can see that the changes are being saved to the database, but are not showing up after saving the block.
The same behaviour can be seen with different block types - it's not limited to Content.
There's no errors coming up in the console or the C5 logs. I've been using this server for C5 5.6 versions. I'm at a loss as to how to work out what's happening.
Now I edit the same content block and change it so that it reads "aaa bbb". When I save this, the page just shows the content as "aaa". And if I again edit the block, the Redactor editor just shows "aaa".
However, if I refresh the page then I get "aaa bbb". I can see that the changes are being saved to the database, but are not showing up after saving the block.
The same behaviour can be seen with different block types - it's not limited to Content.
There's no errors coming up in the console or the C5 logs. I've been using this server for C5 5.6 versions. I'm at a loss as to how to work out what's happening.
This is a caching issue, have you turned off all C5 caching through the dashboard? 5.7 has really aggressive caching and even with those off sometimes you have to refresh the page to see your changes.
Thanks, yes, I've disabled all the C5 caching. I've installed this version of C5 elsewhere and have never had this kind of problem - it makes updating content pretty much impossible.
I've just established that Varnish caching is active on this server. I don't know whether that might have any impact.
I've just established that Varnish caching is active on this server. I don't know whether that might have any impact.
Yes, the Varnish cache will also cause the problems you are experiencing.
Thanks so much! That appears to be the problem. I've disabled Varnish cache with the following in .htaccess:
Header set Cache-Control "max-age=0, private, no-cache, no-store, must-revalidate"
And now I can edit content again!
Header set Cache-Control "max-age=0, private, no-cache, no-store, must-revalidate"
And now I can edit content again!
I am having a very similar issue but only under IE 11. I've posted my own topic about it but had no response yet.
Were you using IE 11 when you had your issues nthorpe?
I checked with my host and they don't have the Varnish caching plugin on our server.
Were you using IE 11 when you had your issues nthorpe?
I checked with my host and they don't have the Varnish caching plugin on our server.
Even tho my host said they didn't have the Varnish Cache addon I still put:
in the .htaccess file anyway to see if it did anything and it fixed my problem too!
I wonder if this a bug that might need addressing?
Header set Cache-Control "max-age=0, private, no-cache, no-store, must-revalidate"
in the .htaccess file anyway to see if it did anything and it fixed my problem too!
I wonder if this a bug that might need addressing?
