Conversation
supportThe BODY content in the backend does NOT match the body content on the frontend, see below Backend: https://snipboard.io/oHxy7u.jpg Frontend: https://snipboard.io/0Wz4fM.jpg
Hey @mohobook , thanks for opening a support request. I tested this on a local install and on a live site. The body content matched in the backend and frontend on both, so I cannot reproduce it here. This points to a caching issue rather than a problem with the content. When a page is cached, the frontend can keep serving an old version of the body text even after you update it in the backend. A couple of things to try: Open the preview link in the top corner of the settings page. It adds a URL parameter to the page, which bypasses the cache and loads a fresh version. This is a quick way to check whether your latest content renders. Clear your site cache, plus any server or CDN cache, then reload the frontend. If the content looks right through the preview link but wrong on the live page, the cache is holding the old version, and clearing it should fix the problem. Can you also share a link to the website? That way I can take a closer look if the steps above do not sort it.
Hello, It’s not cache, let me explain why… I have repeated this on 3 websites, here’s how you can do the same Install WP Extended on a brand new site Enable the maintenance mode module Look at the default content in the body area (don’t change anything) Click the Preview link, you will see different content Or, open the live frontend, again, you will see different content I stopped there when I saw the problem, I never tried to change the default content
Hey @mohobook , okay I think I found the issue. It was to do with the default fallback that was set. If you had made a change to the default body content, then it would have rendered the correct body text message. I have fixed this issue in the dev branch which will be released this week. Thanks for the report.
That’s great, glad it was an easy fix, thanks for letting me know, I’ll go ahead and use this feature now
Hey @mohobook , thanks for opening a support request. I tested this on a local install and on a live site. The body content matched in the backend and frontend on both, so I cannot reproduce it here. This points to a caching issue rather than a problem with the content. When a page is cached, the frontend can keep serving an old version of the body text even after you update it in the backend. A couple of things to try: Open the preview link in the top corner of the settings page. It adds a URL parameter to the page, which bypasses the cache and loads a fresh version. This is a quick way to check whether your latest content renders. Clear your site cache, plus any server or CDN cache, then reload the frontend. If the content looks right through the preview link but wrong on the live page, the cache is holding the old version, and clearing it should fix the problem. Can you also share a link to the website? That way I can take a closer look if the steps above do not sort it.
Hello, It’s not cache, let me explain why… I have repeated this on 3 websites, here’s how you can do the same Install WP Extended on a brand new site Enable the maintenance mode module Look at the default content in the body area (don’t change anything) Click the Preview link, you will see different content Or, open the live frontend, again, you will see different content I stopped there when I saw the problem, I never tried to change the default content
Hey @mohobook , okay I think I found the issue. It was to do with the default fallback that was set. If you had made a change to the default body content, then it would have rendered the correct body text message. I have fixed this issue in the dev branch which will be released this week. Thanks for the report.
That’s great, glad it was an easy fix, thanks for letting me know, I’ll go ahead and use this feature now