Opened 3 weeks ago
Last modified 2 weeks ago
#62826 new defect (bug)
New post editing times out...
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Awaiting Review | Priority: | normal |
Severity: | normal | Version: | 6.7.1 |
Component: | Editor | Keywords: | reporter-feedback |
Focuses: | Cc: |
Description
Trying to edit a new post and it times out and displays the time out error page when clicking update, occurs in less than 5 minutes.
Restoring to the latest post revision leads back to where I started editing. Back arrow does the same. Took 3 hours to complete the editing of a new single page Post (chaos.goblinbox.com/2024-2/). Did not use to do this, but has always been problematic.
The time out timer seems to be triggering fast recently with the latest revisions but I only create this type of page once per year (so action is memory related) which means many WP updates have occurred. I do not mess with my settings very often and haven't for a few years. All I do is add new posts and occasionally new pages.
The auto time out seems to be set the way comments are set instead of allowing a full editing session (in my case just a few minutes is needed for creating the new post...30 minutes perhaps), now it seems to error out in under 5 minutes. Occurs fast enough that the auto-save of revisions don't even record my quickly inserted line items when I try to post.
Change History (3)
#1
@
3 weeks ago
- Focuses accessibility removed
- Keywords reporter-feedback added; changes-requested removed
#2
@
3 weeks ago
Have not asked BlueHost to check on this yet as it so much seems to be a WP issue.
I don't have any other WP installations. If there's a way to deactivate all the default themes without ruining my setup, like some way to save my current setup for restoration later, I'll try that. I'll have to do some serious google searching to find out how to save my current setup.
WP FAQs mention a 5 minute timeout for Comments several times...I'm just wondering if a coder didn't set up the posting timer for that 5 minutes too? Or perhaps it's a global inactivity timer that's gone nuts?
I will try later to post a step-by-step of the problem.
I should mention that I'm a novice WP user. I've had the blog for 20 years and have only changed a few things over those years. Even the plugins and theme I use haven't been changed in years. Edit: I have done the upgrades required as they appear.
Edit: Wind in my area is screwing up the internet reception so I won't be able to add any info today. Drops out too often for work. Be back tomorrow.
#3
@
2 weeks ago
Well now...it seems to have fixed itself. The page I was working on that was giving me so much trouble, the one where even calling for a restore of a revision didn't restore an older revision? It seems to have fixed itself. That linked page now shows my last revision which had disappeared on me after the system had given a timed out error message.
Which implies it was actually a BlueHost drive issue. Failing drive perhaps? Restored by their raid system? Which then recognized that I had clicked on a revision? (Clicked on restore several times in frustration because the only revisions shown were where I'd started editing).
BTW, I did close the editing page, leave the site, return, even rebooted while these issues remained during a several hour editing session that should have taken 30 minutes. It frustrated me to no end.
Anyway, it seems to have resolved itself, adding that last set of revisions to the page, I guess from the restored RAID setup at Bluehost. If that was what the problem was.
I'll try to edit another page and see what happens. If I don't return, the issue has been resolved magically.
Hi @jimhitek and welcome to WordPress Trac.
It is difficult to troubleshoot these kind of issues as they may be server related. Did you already ask for support from your host?
Can you reproduce it on other WordPress installations, such as on a local test setup, with plugins deactivated and with a default theme? If so, please provide detailed step-by-step instructions for how to reproduce the issue so that others can help test it.