![]() If you’re a Cloudflare user, your firewall may be inadvertently blocking legitimate requests. ![]() Checking to see if Cloudflare is blocking the REST API.Ideally, the Site Health tool will provide some indication as to how you can re-enable the REST API on your WordPress site. ![]() Step 2: Re-Enable the REST API by Resolving the Specified Error How you should go about resolving this problem and enabling the REST API again will depend somewhat on the error you see listed here. This could be a “ 401 Not Authorized” response, an operation timeout, a “ 403 Cookie Nonce Is Invalid” message, or another error. The Site Health tool will also display a specific error that is producing the ‘unexpected result’. One example is the block editor screen, which relies on this to display and save your posts and pages.” The REST API is one way WordPress and other applications communicate with the server. “The REST API encountered an unexpected result. If the REST API is being blocked, you’ll see the following message: Under the Status tab, WordPress will list any existing problems with your installation. To access it, navigate to Tools > Site Health: Accessing the Site Health tool in WordPress. You can do this directly in WordPress using the Site Health tool. If you’re seeing this message, a wise place to start troubleshooting is by testing the REST API to make sure it’s working. Step 1: Determine Whether the REST API Is Being BlockedĪ common cause of the “Publishing Failed” error in WordPress (since the Block Editor was launched) is that the REST API is being blocked or disabled. Here are four steps you can take to go about fixing this problem on your site. Once you understand why your WordPress content is failing to update or publish, resolving the problem becomes easier. How to Fix the WordPress Updating Failed and Publishing Failed Errors (In 4 Steps) If that is what’s causing the error on your site, you’ll need to get the REST API working again in order to fix it. When this communication is broken or disabled, the Block Editor’s publishing functionality breaks. However, in this case, there’s no need to worry.Īll you need to understand for the purposes of resolving the “Publishing Failed” error is that the REST API is how the Block Editor communicates with WordPress. If you’re a beginner or just a less-technical user, any mention of the REST API can seem intimidating. In the event that something is blocking or disabling this process on your site, you won’t be able to launch new content. The new WordPress editing interface relies on the REST API to create, save, and publish posts. There are a few different causes of the “Publishing Failed” error, but one in particular is linked to the Block Editor. Learn More Updating Failed error in the Block EditorĪs you can imagine, this problem can be an especially frustrating one for bloggers, as well as any site owner who finds themselves needing to update key information on their web pages. Maybe that is what Matt means with “fresh run”.Optimize your admin tasks and budget with $275+ enterprise-level features included free in all WordPress plans. It does look like this is part of something which Google decided to do two years ago, but maybe that never really got off the ground. Upgrading WordPress and the plugins within is the best way of keeping secure, next to making sure you have decent backups of your database and files.” I deal with hacked blogs on a regular basis, often because I’ve been hired in a “hey, we’ve lost all our search traffic!!” panic. “I think it’s awesome that Google is sending out these messages and urging people to upgrade. WordPress expert Joost de Valk is happy with the new policy: If you are thinking: “how does Google know I am not running the latest version?” the answer is simple: it is in your code, which anybody can see by using “view source”. Not-upgraded WordPress sites are fairly easily hackable and therefore a possible danger for Webspam in the SERPS. The fact that Google is ‘pushing’ the updates is remarkable but also makes sense. When asked through Twitter about the messages Matt Cutts responded it was in fact a new policy from Google. The e-mail or message in WMT tells you your site appears to be running an older version of WordPress and that you should update because otherwise your site may be vulnerable to hacking or malware. I myself today got an e-mail from GWT saying one of my sites needs an update. Last week the first people started noticing that Google had sent them a message within Google Webmaster Tools saying they should update their WordPress versions. ![]() And no, this is not the warning you get when you open the WordPress CMS, it is a warning from Google. If you own a WordPress website and you haven’t updated your WordPress version lately you might be getting a warning soon. ![]()
0 Comments
Leave a Reply. |