Is this happening routinely or was it just a one off.
If it’s happened just once, it could well have been an issue with the server at that split second and not an issue.
If it’s continued and it sounds like it has, then it maybe that your host is limiting or can’t support the amount of work it has to do when posting content.
Does the content get posted and show on the front end?
A few things to do and some of these may have been discussed before:
You might want to check for plugins which do things when you post, like syndicating your post to Facebook for example and specifically disable them.
Switch on WP_DEBUG by going into your wp-config.php file and setting WP_DEBUG to true, then try posting content it may show additional error messages, which can help debugging, if you don’t understand the message don’t worry you can post it back here.
Limit revisions in the DB, by default WordPress stores lot’s of versions of your post and pages and these build up.
You can limit how many revisions are stored by going to wp-config.php and adding
define('WP_POST_REVISIONS', 4);
This limits the number of revisions stored per post to 4, so only the last 4 revisions are stored. Bare in mind, if you make lots of small changes by limiting revisions you won’t be able to access old ones.
It’s also worth talking to your host and they maybe able to give you some advice as well.
Thanks for your answer, Tim.
This has occurred only once. After updating the content, it showed up on the frontend, then the site went down.
I’m unable to see the website on the frontend or backend, so I’m unsure as to how I can few the bug log. I looked it up, but couldn’t find the proper information. Or didn’t know how to make it work.
I also tried the revisions, but the site is still down. I’ll attempt to talk to the host.
Sorry, I misunderstood and assumed the error had subsequently gone.
If you have access to your error logs which you should be able to access via your control panel then you can look to see if there is an error there.
Otherwise do as your currently doing and contact your host, who should be able to see the issue and fix it for you.
