Updating Failed, ver 3.8

I found the problem was, it was the permalinks, you may need to redo the permalinks that, fixes the problem. I just did that after a while trying to figure the problem was.

I should also add that the “Classic” editor works just fine.

Thanks Benjamin,
Unfortunately I have reset the permalinks a few times and it still does not work.

Strange little thing, before i was having the same issue and when i try and click on my previous articles/posts, it give me an 404 error, so i re-apply the permalinks and it worked fine for me, so maybe it could be something else too.

Yea re-applying permalinks didn’t solve this one unfortunately.
I also can’t publish new posts, it says Publish failed.

all I can think is downgrade to 3.7.0 for Gutenberg and re-apply permalink and update to 3.8.0. that’s one step i did to just in case.

so at least I’m not the only one that’s having issue :).

I actually had 3.7.something first installed (def reset permalinks then too) and upgraded to 3.8 hoping it’d fix the issue!

So what I just learned is that Gutenberg uses REST API and if a plugin that you may use that is turning off REST API, may cause this problem. This can be plugin that deals with security (maybe) or something that’s causing it.

Also, since Gutenberg uses REST API, and it uses rewrite rules in place for the REST API to work. so pretty permalink is needed.

but this wouldn’t be something that people would check when it comes permalink but is definitely a weird one.

One possible way you can try is to disabled all plugins and leave Gutenberg and change permalink, and see if that works.

Yup as I stated in my original post I disabled ALL plugins AND installed the default wordpress theme and get the same issue. Thanks so much Benjamin for responding!

Hiya,

So I’ve seen the 403 error a few times now, and it’s been relating to security rules implemented by hosts. You should be able to open your sites logs (it usually has its own button for viewing in your hosts control panel if they offer one) and it should give you a bit more information about what blocked the request and why.

that’s very interesting. security rules, my problem was permalink so I had to re-apply pretty permalink and it fixed that, but I have my own dedicated server so I have full control, so that’s one thing is different.

Marius, Thanks for the info, I’ve relayed that to Siteground and they are looking into it. On my cpanel there are no errors in the error logs so it may be that the logs are beyond what my cpanel account can access.

UPDATE:
Issue is resolved. Wordfence was installed and removed but the php variable was left in the directory. This was causing the 403.

that’s awesome, always something very simple. glad everything worked out.