WordPress Changes Not Showing? Here’s How to Fix It!
WordPress Changes Not Showing? Here’s How to Fix It!
Are you running into the WordPress Changes Not Showing issue? 👀 Learn how to fix this common problem with help from this tutorial!
👉 Subscribe: https://www.youtube.com/c/Kinsta?sub_…
Changes not showing on your WordPress site is a widespread issue for WordPress users. In almost all cases, the issue stems from caching problems, either in your own web browser, your WordPress site’s cache, or your content delivery network’s cache (CDN).
In this video, we’ll dig into what those reasons are and why caching can cause problems with WordPress changes not showing. Then, we’ll show you several troubleshooting steps to figure out the problem and make it so that you and your site’s visitors can see your site’s updates! ▶️
ℹ️ About Kinsta
Kinsta is an award-winning Cloud Platform designed to host and manage your WordPress sites, Applications, and Databases faster and more efficiently. Trusted by 25,000+ companies worldwide, from developers, startups, and agencies, to multinational brands, we guarantee lighting-fast performance, enterprise-level security, ease of use, and exceptional support.
🚀 Try our flagship Managed WordPress Hosting plans and get $240/month worth of premium features included in every plan. That’s free unlimited migrations, 20% faster load times thanks to Google’s fastest servers and Premium Tier network backed by Cloudflare’s 275+ CDN locations worldwide, and 24/7/365 multilingual technical support from humans in less than 2 minutes.
👉 Try risk-free with our 30-day money-back guarantee Powerful Managed WordPress Hosting
👤Follow us:
► https://kinsta.com/blog/
► https://kinsta.com/newsletter/
► https://twitter.com/kinsta
► https://instagram.com/kinstahosting
► https://facebook.com/kinstahosting
💡Discover all of our hosting solutions ► https://kinsta.com/
🕘Timestamps
0:00 Intro
0:56 Why Is My WordPress Site Not Updating?
2:19 How to Fix Problems With Browser Caching
4:32 How to Fix Problems With WordPress Caching
7:53 How to Fix Problems With CDN Caching
9:05 How to Fix Problem With User Roles/Capabilities
📚Resources
📙 Full Guide on WordPress Changes Not Showing
► https://kinsta.com/blog/wordpress-cha…
🔌 User Switching plugin
► https://wordpress.org/plugins/user-sw…
#WordPressChangesNotShowing #WordPressNotUpdating
Content
0.15 -> Hi, I'm Alisha
1.61 -> and today we're gonna show you how to fix the problem
4.81 -> of changes not showing up on your WordPress site.
7.327 -> (upbeat music)
13.31 -> Generally speaking, your WordPress site
15.73 -> should update immediately after you hit the Save button.
19.02 -> That is, you should be able to hit the Save button,
22.56 -> open the page in question and instantly see those changes.
26.51 -> More importantly, the same should also apply
29.1 -> to your site's visitors.
30.61 -> That's what should happen.
32.42 -> But since you're watching this video,
34.36 -> you've probably figured out
35.92 -> that things don't always go according to plan.
38.69 -> But before we get too far,
40.3 -> I wanna let you know that there will be links
42.51 -> to more resources in this video's description.
45.14 -> And remember, subscribe and ring that bell
47.81 -> to get notifications for future helpful content.
51.4 -> All right, let's get your site updated.
57.15 -> Your WordPress site's most common cause
59.68 -> for not updating is caching issues.
62.61 -> There are different types of caching
64.04 -> that may be preventing you from seeing changes
66.52 -> on your WordPress site.
67.78 -> Browser caching stores certain static files
70.82 -> on visitors' local computers in the web browser cache.
74.1 -> Page caching stores the static HTML version of your site,
77.8 -> rather than the PHP
79.64 -> to generate it on the fly for each visit.
82.62 -> CDN caching speeds up global load times
86.37 -> by caching your site's static content
88.64 -> on a network of servers around the world.
90.64 -> So even though you've updated the version
92.61 -> of your WordPress server,
94.06 -> visitors and you might still be seeing the older
97.41 -> and cached version of your site,
99.66 -> hiding the changes that you pushed live recently.
102.37 -> Beyond caching issues,
104.01 -> another reason why you might not see changes
106.31 -> on your WordPress site might have to do with permissions
109.36 -> on your site.
110.38 -> In this scenario,
111.32 -> even if changes might be successfully saved,
114.35 -> you might not have permission to see the updated content
118.08 -> and it might cause you to see the older content still.
121.66 -> This is unlikely to cause the problem on simple sites,
124.82 -> such as blogs or portfolios,
127.33 -> but it could be an issue with dynamic sites.
132.96 -> Browser caching works by storing certain site assets
136.28 -> in your computer's browser cache.
138.38 -> It avoids repeatedly downloading these assets
140.95 -> directly from your WordPress site server.
143.15 -> To fix the problem, you can force your browser
145.42 -> to download the freshest versions of all files
148.33 -> from your server, instead of loading them from the cache.
151.35 -> Here are a few ways to accomplish that.
153.51 -> The simplest solution to fix browser caching issues
156.47 -> on a single page is to hard refresh your web browser.
159.83 -> When you force a hard refresh,
161.32 -> your browser will skip the cache
162.94 -> and download all web server assets.
165.07 -> To begin, open a tab with the page on your site
167.78 -> where you expect to see changes.
169.69 -> Then, hit the following keyboard combinations,
172.87 -> Control and F5 on windows, Command and R on Mac.
177.23 -> If the hard refresh didn't work,
178.97 -> you might need to clear your browser's cache completely.
181.67 -> This will wipe out all of the cached files,
183.85 -> ensuring that you download new versions of all files
187.05 -> across your site.
188.14 -> You might be able to fix the problem for your own computer,
190.91 -> but your visitors still might not see the changes
193.32 -> right away, because they didn't clear their browser caches.
196.66 -> One slightly more advanced tactic to get around this
199.83 -> and make sure your visitors always see the latest version
203.08 -> is to use a cache busting tactic.
205.42 -> For example, let's say your site's logo is logo.png.
210.23 -> If you update your logo
211.72 -> and upload a new file with an identical name,
214.85 -> that change might not show up right away
217.69 -> because people's browsers will still load
219.68 -> the original logo.png file from their cache.
223.56 -> To fix this with cache busting,
225.91 -> all you need to do is change the file name.
228.8 -> For example, instead of uploading logo.png
231.75 -> and overriding the old file,
233.76 -> you could upload logo-v2.png.
237.35 -> Because it's a new file name,
238.76 -> you'll be able to bypass issues
239.593 -> with your site's changes not showing
242.4 -> because of browser caching.
244.23 -> This tactic can also be useful for scripts,
246.91 -> such as CSS style sheets.
249.31 -> So if your CSS changes are not showing up in WordPress,
252.93 -> this is one tactic that might be able to fix that.
256.79 -> Other cache busting tactics include
258.7 -> changing the file path or adding query strings
261.77 -> in addition to changing the file name.
264.07 -> Here are some examples.
268.42 -> While there are different types of WordPress caching,
270.98 -> the most likely culprit is page caching.
273.93 -> Normally your server builds your site's finished HTML
277.38 -> from scratch for each visit using PHP.
280.64 -> Then, your server sends off the finished HTML
283.67 -> to a visitor's browser to render your webpage.
286.69 -> To speed things up,
287.77 -> page caching lets you store the finished HTML in the cache,
291.5 -> eliminating the need for your server
293.07 -> to process the PHP and query the database on every visit.
297.52 -> This means that if you update something on your site,
300.28 -> that change won't be available right away
302.47 -> because your server is still serving the cached HTML
305.21 -> from before you made the change.
307.24 -> Most web hosts and caching plugins get around this
310.14 -> by automatically clearing the cache
312.58 -> whenever you publish or update a new piece of content.
315.55 -> However, your caching solution
317.22 -> might not be configured to do this
319.55 -> or it might just not be working properly for some reason.
323.15 -> Many caching solutions also exclude WordPress admin users
326.66 -> from seeing cached content.
328.71 -> This is why you might run into a problem
331.06 -> with WordPress changes not showing up when logged out.
334.81 -> In other words, when you're logged into your admin account,
338.03 -> you don't see any cached content,
340.04 -> which means you can see the changes right away.
342.69 -> But when you log out,
343.73 -> you're seeing the older cached version,
345.97 -> as are all your site's visitors.
347.9 -> The fix here is to clear your site's cache manually.
351.35 -> This will flush out all the stored HTML versions
354.19 -> of your pages and have your site create
356.31 -> a new version from scratch.
358.11 -> It will then store that new version in the cache
360.55 -> to get all the caching's performance benefits.
363.41 -> How you clear your WordPress cache
365.06 -> depends on what caching solution you're using.
368.09 -> We'll show you two solutions.
369.75 -> Kinsta implements page caching for you
372.42 -> so that you don't need to use a WordPress caching plugin.
375.68 -> There are two ways to clear your site's cache at Kinsta.
379.05 -> First, you can do it from your WordPress site's dashboard
382.77 -> via the Kinsta Cache tab in the left sidebar
385.77 -> and the Clear Cache button.
387.37 -> Second, you can also clear your site's cache
390.14 -> via your MyKinsta dashboard.
392.69 -> Open your site in MyKinsta,
394.93 -> then go to the Tools tab and click the Clear Cache button
398.47 -> under site cache.
399.64 -> If you're not hosting at Kinsta,
401.49 -> you might be using a WordPress caching plugin
403.89 -> to handle page caching.
405.75 -> All caching plugins include options
407.99 -> to clear your site's entire cache
410.03 -> and sometimes just the cache
411.97 -> for individual pieces of content,
413.62 -> where you're having issues.
415.04 -> We can't show you how it works in all caching plugins,
417.88 -> but we will show you some of the most popular plugins.
420.83 -> Most caching plugins behave similarly
423.41 -> so that you can use the same idea in other plugins.
426.28 -> In WP Super Cache, you can click the Delete Cache option
430.89 -> on the WordPress toolbar or in the plugin's settings.
434.69 -> To delete the entire cache with WP Fastest Cache,
438.67 -> you can click the Delete Cache option
440.57 -> on the WordPress toolbar.
442.58 -> You can also only clear the cache for the piece of content
445.54 -> that you're experiencing issues with.
447.6 -> Open the Post page custom post type list,
451.12 -> hover over the piece of content that's not showing changes
454.15 -> and click the Clear Cache link.
456.13 -> To clear your entire site's cache while using WP Rocket,
460.47 -> hover over the WP Rocket option in the WordPress toolbar
464.12 -> and select Clear Cache.
465.92 -> To clear a single piece of content,
467.92 -> hover over it in the content list
469.84 -> and click Clear This Cache.
471.52 -> If you're using a content delivery network, CDN,
474.94 -> to speed up your WordPress site's global load times,
478.4 -> that could be another reason
479.8 -> why your WordPress site's changes aren't showing.
482.9 -> A CDN works by caching your site's static content
486.08 -> on its network of servers around the world.
488.64 -> Then it serves up those files
490.51 -> from the location that's nearest to each visitor.
493.09 -> However, if your CDN has cached
495.04 -> an old version of an image file or CSS style sheet,
498.53 -> that could lead to a problem
499.84 -> with WordPress changes not showing.
502.1 -> This is unlikely to happen with your content itself,
505.35 -> but it can be a common problem with static files
507.8 -> that you might be hosting on the CDN,
510.26 -> such as images and scripts.
512.36 -> As with other caching problems,
514.36 -> you can fix this by clearing the cache at your CDN.
517.64 -> The exact steps to accomplish this will depend on your CDN.
521.26 -> If you're using a different CDN,
522.79 -> you can consult your CDN's documentation for help.
525.69 -> Kinsta includes a built-in CDN at no extra cost.
529.83 -> You can clear your CDN's cache from your MyKinsta dashboard.
533.83 -> In MyKinsta, open the dashboard area for the WordPress site
537.5 -> where you're having issues.
539.06 -> Then, go to the Kinsta CDN tab
541.79 -> and click the Clear CDN Cache button.
543.94 -> Finally, your site might be working totally fine,
547.1 -> but you still might not see the changes you make
549.37 -> because of some WordPress role or capability problem.
552.75 -> Your site is updated correctly,
554.64 -> but your user account doesn't have permission
556.5 -> to see the changes.
557.63 -> For example, maybe you have a membership site
560.16 -> where registered members see one set of content
562.51 -> and anonymous visitors see a different content.
565.11 -> If you change the content for registered members
567.46 -> and then open your site in incognito mode,
570.13 -> you won't see those changes
571.37 -> because your anonymous guest account doesn't have permission
574 -> to view the content you changed and vice versa.
577.47 -> This can get even more complicated
579.59 -> if you have a membership site
581.29 -> with multiple different membership levels.
583.8 -> To fix this, make sure
585.34 -> that you're logged into a WordPress account
587.2 -> with the proper permissions to see the content in question
590.49 -> or that you're not logged into an account
592.18 -> for some situations.
595.11 -> Kinsta's WordPress hosting can speed up your website
597.91 -> by up to 200% and you'll get 24/7 support
602.5 -> from our expert WordPress engineers.
605.04 -> Let us show you the Kinsta difference.
607.31 -> Try a free demo of our MyKinsta dashboard
609.71 -> at demo.kinsta.com.
612.29 -> Thank you for watching.
613.67 -> Don't forget to subscribe for more tutorials,
616.1 -> explainers and helpful content like this.
618.504 -> (upbeat music)
Source: https://www.youtube.com/watch?v=C4317cQfZwA