Yes, @viktor mentioned this a few replies ago.
All seems fine on that end, and the same settings (.htaccess) on a different VPS with CP work fine.
But yes, I did find a few posts about that. Wholly unfamiliar with CORS and what that’s supposed to do and stuff though.
These directives look a bit different - I’ll give it a read, maybe I’ll learn something.
Still, to my mind, these tweaks shouldn’t be nessesary to save a post when everything else works fine.
Especially since saving anything also worked fine a few weeks ago. I made the site after-all
If I click save on a page it does it instantly. Same for a Classic Commerce product.
Of-course as an automatism I picked the top (newest) post to save and resave. And that does NOT work.
However, other (older) and new posts, also save.
So ONE post does not save. Fine, idiosyncrasy of the browser right?
I copy the contents, which is just a bunch of text and a shortcode.
Put it in a new post, delete the original. And now the new post doesn’t work.
I’ve tried this in Safari and Firefox.
Firefox is a bit more informative. I did find out that if I let it run for a while that after 5 seconds the post does save through load-scripts.php invoking admin-ajax. Fine. But the response is broken. If I leave it running it tries 3 times 15 seconds apart according to Firefox.
Then It fails on a internal server error.
Which shows this:
[09-Jul-2022 00:03:02 UTC] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /path/to/domains/mototravel.net/wp-includes/cache.php on line 536
I don’t use any caching on the site, no plugins. This is the built-in object cache.
stumped
During this road of discovery I did figure out that ENABLE_CACHE in wp-config.php doesn’t work anymore aparently. So I removed that. I also found a thing that caches into APCu, which I added.
Seems to work - No errors, but that one f*cking post still won’t safe.
Oh, and yes, I did delete all history and cached data from Firefox during all this too. No change.
It’s not necessary, as CP will just add -2 (or -3, or whatever) to the URL if that happens. On news sites, lots of posts have the same title. It’s not an issue at all.
Hmm - Never thought of that.
But, it doesn’t solve the issue.
Logically it’s not a server issue nor a CP issue as the same code works for other posts/pages to save and respond.
Other than perhaps a stupid firewall or some adaptive policy thing for security. But I can’t find such a thing.
Several browsers with or without cached pages doing this also (mostly) rule out a browser issue…
I think you have to do the disable plugins trick and see what happens then. As you site’s live, ideally you’d want to do this on a staging or localhost site. I’d start with the SSL plugin.
I’ve tried all that today. Also dug through the database, meta data, stuff like that looking for weird stuff.
Nothing.
I also don’t really have the patience/energy to continue looking for now. Maybe one day I’ll figure it out… Stupid internet…
Thanks for everyone their input and thoughtful responses. If I learn something new I’ll update the topic.
@timkaye I did change the permalinks as you suggested, looks a lot cleaner
The 403 page you see on the non working urls is a custom redirect I made for other stuff, protecting the login pages and such. I’m not sure how it applies to /uploads/ I never made that, nor can I find where it comes from - Perhaps a server directive?
Several hours more… I finally succumbed to switching themes and plugins.
Turned everything off - Default theme, no plugins, no htaccess… And it worked fine.
Turns out that the plugin “Lightswipe Masonry” (Some gallery thing) caused a conflict with galleries or something when saving posts - Because why would it…
Didn’t even look at the code to figure it out - Immediately deleted it after confirming the issue came back when the plugin was active and now the site seems fine.
Wtf!
