#43399 closed defect (bug) (worksforme)
Non-admin roles get error 500 when creating new post
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | 4.9.4 |
| Component: | Posts, Post Types | Keywords: | |
| Focuses: | administration | Cc: |
Description
I didn't notice this issue until my client pointed this out to me when she couldn't create new posts.
I have an admin account and can create posts, but when she creates a new post or goes to /wp-admin/post-new.php she gets a white screen. To be clear: the ditor doesn't show up. this is before even saving anything.
When investigating this I found out that admin accounts do not have this problem, but her account, an editor role, does. I also created a new editor account, to see if it was perhaps something only related to her specific account, but the results were the same, no creation possible. internal server error 500
I fiddled around with post-new.php for a bit and commenting line 70 ($post = get_default_post_to_edit( $post_type, true );) allows her account to see and be able to create a new post again. I put it back as it was, because I'm sure it serves its purpose, but perhaps this tidbit of info will help others to find out what's going on here.
I have used health check and the core files seem to be the same as provided by wordpress.org
I haven't found any similar tickets, but if there are please direct me to them!
Change History (4)
#1
follow-up:
↓ 2
@
7 years ago
- Focuses administration added; accessibility removed
- Keywords reporter-feedback added
#2
in reply to:
↑ 1
@
7 years ago
- Resolution set to worksforme
- Status changed from new to closed
Thank you for your quick reply. I thought I'd disabled all plugins this week for this exact check, since it's one of the first things you do when something is awry. Apparently this was imaginary.
Disabling sucuri and gtmls.net did the trick. Strangely enough, enabling them again didn't seem to recreate the problem, making it solved.
Thank you so much for your effort on something I really should have double checked. If anyone stumbles on a similar issue, perhaps this helps for them though.
Replying to SergeyBiryukov:
Hi @ninke, welcome to WordPress Trac! Thanks for the report.
Does the issue still happen with all plugins disabled and a default theme (Twenty Seventeen) activated?
This sounds like a problem with a particular environment rather than a bug in WordPress core, I'd suggest trying the
support forums for troubleshooting.
Hi @ninke, welcome to WordPress Trac! Thanks for the report.
Does the issue still happen with all plugins disabled and a default theme (Twenty Seventeen) activated?
This sounds like a problem with a particular environment rather than a bug in WordPress core, I'd suggest trying the
support forums for troubleshooting.