New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Updating Failed" / "Publishing Failed" on latest Update (temp conflict with an unknown theme or solved by deactivating and reactivating WP Cerber) #7652

Closed
tvledesign opened this Issue Jul 1, 2018 · 20 comments

Comments

Projects
None yet
@tvledesign
Copy link

tvledesign commented Jul 1, 2018

Description:

Upon updating to the recent version of Gutenberg, I haven't been able to save or publish posts. I keep getting an "Updating Failed" or "Publishing Failed" error. Tried this on a fresh install of WordPress as well as deactivating all plugins on the site I'm experiencing this on.

To Reproduce

  1. With Gutenberg installed and updated, create a new post.
  2. Try to save the new post as a Draft or Publish it.

Expected behavior

I've expected the post to save like it normally does.

Screenshots

Screenshot of post not saving.

2018-06-30_21-13-01

Screenshot of the inspector.

2018-06-30_21-07-22

Desktop:

  • OS: Windows 10
  • Browser: Chrome (67.0.3396.99 (Official Build) (64-bit))
@designsimply

This comment has been minimized.

Copy link
Contributor

designsimply commented Jul 3, 2018

Error in plain text for reference:

The hook name can only contain numbers, letters, dashes, periods and underscores.
index.js?ver=153025076:1

Noting a few other mentions of that same error message in past issues:

I believe #6091 addresses the underlying problem, which appears to be that if another installed plugin uses wp.hooks.addAction() (such as Advanced Custom Fields) then editing will break.

@tvledesign, thank you for the report! If you'd like to reply here to note whether you are currently using the Advanced Custom Fields plugin (and the version), that'd be great to document! Past that, please subscribe to #6091 if you'd like to follow progress on this issue.

@tvledesign

This comment has been minimized.

Copy link

tvledesign commented Jul 3, 2018

@designsimply I have this running on a site without Advanced Custom Fields and it produced the same errors (as well as on a site that has ACF). Disabling all plugins with only Gutenburg activate yield the same results.

@designsimply

This comment has been minimized.

Copy link
Contributor

designsimply commented Jul 3, 2018

🤔 For good measure, may I ask if you have tested with the default theme? I will also try testing from Chrome on Windows…

@tvledesign

This comment has been minimized.

Copy link

tvledesign commented Jul 3, 2018

Actually, interestingly enough I deactivated everything just now and set it to the default theme and had an error the first time but it saved the second time. Then I switched back to my theme and turned all my plugins back on and it oddly worked.

@designsimply designsimply changed the title "Updating Failed" / "Publishing Failed" on latest Update "Updating Failed" / "Publishing Failed" on latest Update (temp conflict with an unknown theme) Aug 31, 2018

@mattions

This comment has been minimized.

Copy link

mattions commented Sep 4, 2018

For me the problem was because I had started serving the site using HTTPS, with a SSL certificate from lets encrypt, however I didn't update the urls on the Settings in the General Dashboard (Dashboard --> Settings). That was making Chrome not load a jetpack pluging, breaking the JS execution.

HIH

@markolbert

This comment has been minimized.

Copy link

markolbert commented Sep 18, 2018

I just ran into the same problem. Can someone explain how to diagnose what might be causing the problem? Things like "turn everything off" are not what I want to be doing with my time.

@sakyachen3

This comment has been minimized.

Copy link

sakyachen3 commented Sep 20, 2018

I solved this problem
Just stop WP Cerber Security version 7.2, and update to version 7.6,
then restart WP Cerber Security,everything is worked fine

@markolbert

This comment has been minimized.

Copy link

markolbert commented Sep 20, 2018

@sakyachen3

This comment has been minimized.

Copy link

sakyachen3 commented Sep 20, 2018

Sorry, it is version 7.6

@markolbert

This comment has been minimized.

Copy link

markolbert commented Sep 20, 2018

No worries.

For the benefit of anyone else running into this problem: I had already updated WP Cerber to 7.6 before encountering this issue. Deactivating Cerber and re-activating it seems to have fixed things. Please note that in the course of doing this I had to re-install Gutenberg (I forgot that I had deleted it at one point after running into the problem), so deleting and reinstalling Gutenberg may have played a role in solving the problem, too.

@designsimply designsimply changed the title "Updating Failed" / "Publishing Failed" on latest Update (temp conflict with an unknown theme) "Updating Failed" / "Publishing Failed" on latest Update (temp conflict with an unknown theme or solved by deactivating and reactivating WP Cerber) Sep 24, 2018

@sumitsuboink

This comment has been minimized.

Copy link

sumitsuboink commented Oct 28, 2018

I just ran into the same problem too.
ON MY FIRST TEST RUN
just after my install and guide over.
because I'm never install "WP Cerber Security"...and I'm a WP newbie
so I have no idea what going on
anyone can help?

@noumanabbas

This comment has been minimized.

Copy link

noumanabbas commented Nov 5, 2018

I am having the same issue on my company website, https://www.DigitalBrandingCraftship.com. I found the issue is into my settings tab with the url. I changed it from http to https and the issue is resolved, Thanks to @mattions :-) who guided here.

@diveyez

This comment has been minimized.

Copy link

diveyez commented Nov 10, 2018

I can confirm SSL/HTTPS is breaking this if, in General the URL's are not updated to https://

@jutta-livingmiracles

This comment has been minimized.

Copy link

jutta-livingmiracles commented Nov 19, 2018

I have the same issue. "Updating failed" with latest version of Gutenberg plugin. I do not use WP Cerber. My site uses https:// and the settings in General (WordPress Address, Site Address) use https:// as well.

What can I do to troubleshoot?

@JGuiselin

This comment has been minimized.

Copy link

JGuiselin commented Dec 7, 2018

Hi everyone ! I got the same prohlem and solved it thanks to the method explained on this article
I installed the cloudfare Wordpress plugin
It still didn't work so then I installed the SSL Insecure Content Fixer
And finally, as it didn't work, I installed this one instead and it finally worked

I have to mention that i also whitelisted my ip address on cloudfare, as explained above.
And this article helped me a lot too
hope it could help someone
good luck

@decpress

This comment has been minimized.

Copy link

decpress commented Dec 19, 2018

Check your domain registrar DNS settings and make sure there are no unfamiliar A records that could deny permission to publish. I had a SUCURII entry that was interfering with my ability to update and publish.

@JudahGabriel

This comment has been minimized.

Copy link

JudahGabriel commented Jan 4, 2019

My WordPress site updated automatically today with the new Gutenberg editor and now everything is broke, I'm getting the "Updating Failed" for every post.

It's unrelated to HTTPS. I don't have WP Cerber installed. I don't know if my theme uses Advanced Fields or not.

Very frustrated with WordPress' breaking the world.

@Kokoss666

This comment has been minimized.

Copy link

Kokoss666 commented Jan 4, 2019

Hello i have installed 5.02 wordpress update and cant edit the posts same problem Updating failed. I have cloudfare HTTPS and its sitll working fine, i hade no problem since i didnt install that update. i also have the https set up in general settings. pls how can i solve it, i also updated all plugins. im desperate.

@Kokoss666

This comment has been minimized.

Copy link

Kokoss666 commented Jan 4, 2019

okay solution is instaling classic editor plugin to deactivate that new sh*t and you are fine no more errors. thank you for updates that makes things harder

@anormore

This comment has been minimized.

Copy link

anormore commented Jan 11, 2019

CAN CONFIRM that installing classic editor works -- but I had to revert a post back and forth to fix. Could have been browser cache too.

This new editor looks like a bit of a blunder... yikes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment