I am learning WordPress on localhost. I am using the Divi theme to create a demo site. whenever I edit a landing page, the changes don't show up on the site after publishing. What is the problem? Kindly help me as I am a newbie to WordPress.
Are you properly saving the changes? You must click on Save button in Divi builder (sometimes you must save twice), because Divi builder has a cache method for the builder that throws this kind of problems in some cases.
The most common cause of a WordPress site not updating right away is caching. Try these two steps to resolve the issue.
You’ll start by first clearing the browser cache. For most users, this should fix the issue.
The second and most likely cause of this issue is poorly configured WordPress caching plugin. Most caching plugins make it super easy to clear your cache with the click of a button.
Related
currently I'm running into this issue, where external links are automatically set to no-follow by WordPress. As of now I wasn't able to detect the source of this behaviour.
The page uses the Classic Editor (v1.6.2) Plugin - however, the problem still occurs without the use of this Plugin.
There are a bunch of other plugins installed but those are not directly involved with the post editin feature of WordPress. Are there any clues which might cause this issue?
If you need any information I can provide.
Which other Plugins are you using?
Are you maybe using RankMath or another SEO Plugin?
These have a setting to make all external links with "rel=nofollow". You would need to deactivate this or add an exceptions for specific domains.
Check the settings.
I am building a website and I am always having issues with development because of caching.
We are using Siteground with the SG Optimizer plugin active, we are using Elementor as page builder, we are using Sucuri who is also caching.
Does anyone knows what do I need to do to be able to see my website as it is, instead of the caching versions ? Many times I click on purge cache on Wordpress, or I go to Siteground to remove Memcache but is like I can't never see the changes i made on elementor in live.
Any help about how to avoir this kind of issues would be great !
Thanks!
Turn off the cache while developing.
Caching is only beneficial once in production.
Cheers,
My responsive website just shows the word Menu for the navigation on mobile. When you click it's supposed to show the primary navigation, and it did for years. I just noticed it does not work anymore and I'm not familiar with responsive code.
MacInspires.com
based on Twenty Eleven Theme
Wordpress
Thank you for any assistance or point in the right direction!
This is usually done via Javascript. Disable the minification, compression/optiomization plugins you’re using. They may be breaking the javascript used to manage that menu.
This may be a plugin or theme conflict. Please attempt to disable all plugins. If the problem goes away, enable them one by one to identify the source of your troubles.
If you can install plugins, install “Health Check” (https://wordpress.org/plugins/health-check). On the troubleshooting tab, you can click the button to disable all plugins and change the theme for you, while you’re still logged in, without affecting normal visitors to your site. This may be a faster option. Let me know how things go and I will try to help further if required.
GoDaddy Fixed it!
site had a mixed content issue, where resources were being pulled both from HTTP and HTTPS sources. I have installed and activated the plugin Really Simple SSL. This resolved the mixed content issue, and also the mobile menu issue.
We use a plugin that creates a content type and dynamically generates pages for that type. It works fine except that when when we upgrade plugins (especially The Event Calendar, which also creates a content type, but doesn't experience this problem), this sometimes (but not reliably) causes all of the page URLs generated by the plugin to stop existing. When you go to those URLs, you get a 404 error.
This problem can be fixed by going to the site's permalinks page and (without making any changes) saving the settings.
I looked for a solution that would prevent the problem from happening, but have not been able to find one. I wasn't able to figure out a way to mimic what happens when you save the permalinks settings for each site, and I haven't been able to figure out what might be triggering the problem. I currently "solve" the problem by using a Selenium script to go through each permalinks page in our multisite and click the save button on each automatically after I update plugins.
How can I:
Track down the source of the problem.
Set up a content type that will not unset itself in the wrong circumstances.
Failing either of those things, implement a backend solution that will do what I am currently doing on the frontend, but in a fully automatic way.
I have the same problem on different WordPress based websites.
I developed some of them, while others are made by someone else.
They don't have that much in common: completely different websites, different themes/plugins and so on.
Recently in these websites, I've been experiencing this problem: WordPress is caching the backend in a really tough way and, after saving any edits, I have to force a refresh with ctrl+f5 to actually see the edits I made before.
After some digging I can assure that:
it doesn't seem to depend on the webserver (same problem on nginx and on apache)
it doesn't depend on varnish or wp caching plugins (it happens also on website without any cache solutions)
it happens just in some new wp releases, I'm not experiencing this problem on older websites
it doesn't depend on my pc/browser configuration because my colleagues are experiencing the exact same problem on their pc
Anyone who had the same problem and was able to find a solution?
EDIT: It actually happened also on a fresh WordPress installation. Once I created a page, I went back to the page list by clicking on the menu item and I couldn't see the page in the list. After forcing a page refresh the newly created page was there as it was supposed to be before.