Posted 1 year ago #
I am the admin and I have two other users that are classified as contributors: Contributor A and Contributor B. When I, as admin, go to write a post/page the author defaults to Contributor B and my only other option is to choose Contributor A. There is no option to choose the Admin as the author.
In posts that I'd written prior to bringing on Contributor B, admin was an option.
Also, all posts and pages written by the admin are still showing as such.
Posted 1 year ago #
Same problem EXACTLY for me. I added my self as an author (so I have me as admin and me as author). Then I write the post as Author and delete it. When deleting it asks, "Do you want to replace this name with Admin?" and I reply YES and it puts me on the post. Still, I read it was a bug in the new wordpress. Maybe someone will see these posts.
Sometimes it helps if you give yourself a "nickname" in the Users > Your profile subpanel.
Posted 1 year ago #
I think you need to make sure you have a display name field set. I tried deleting mine, and I had the same problem where admin was not listed as an author choice. Actually, I think the author choice is still there, but since there's no display name, it just looks like a blank choice. Anyway, you can probably fix this by making sure the admin user has all the information filled out in the Name section of the user profile. You can double check this in your database by making sure the display_name field in the wp_users table has a value.
Posted 1 year ago #
Yeah, my whole admin profile is filled out (nickname as well), so it's not that.
@markhuss - you mean you delete the author every time? Then re-create it again?
Another solution for this in the past has been to create a new user with adminstrator role (e.g. 'newadmin'), delete the 'admin' user and assign all posts to the 'newadmin' user. Then if necessary create 'admin' again and then delete the 'newadmin' user you created before, and assign the posts again to 'admin'
Posted 1 year ago #
This is definitely a bug. I am exactly in the same situation. I use my blog kind of like a forum, where everyone can post (we are a translation team). Then this bug appears. I went to Wordpress Codex and I got this:
Post Author
A list of all blog authors you can select from to attribute as the post author. This section only shows if you have multiple users with authoring rights in your blog.
At first I thought this was unreasonable of the coders to "force" the admin not be able to write anymore in this case. But now I think this may be a mistake.
Really want a way to fix this. Creating another account to "pour" the later posts into it is not a solution!!!
Posted 1 year ago #
I'm having the same problem as well. I'm the admin and one of the major contributors to my blog (along with 2 other editors), but all my posts are showing up as authored by one of the editors. I could and probably in the interim WILL create a separate "editor" account for myself, but am hoping the good WordPress folks can get a fix for this soon. Thanks!
Posted 1 year ago #
Try this solution:
Create another profile for yourself with a name that shows up first alphabetically (e.g., 1admin). When you create a post, authorship will default to this user.
Posted 1 year ago #
but will Wordpress fix this in future versions? No word from the admin in this topic.
Posted 1 year ago #
It still seems to be a bug in 2.6.1, but there is a pretty easy fix.
1. Create a new user and give them admin rights.
2. Log-in as that new user.
3. While logged in with them, change your main admin account to "subscriber" and save it.
4. Now change your main admin account back to "administrator".
That should do it!
Posted 1 year ago #
I think coders should find a way to fix this instead of making their 1000000... users do this manually (as they are quite tedious, esp when you have more than 1 blog). IT IS A BUG, so I don't see why it shouldn't be fixed for so long, rather than applying temporary solutions.
Posted 1 year ago #
Here is what i do.
I have the myphpmyadmin plugin.
Use the myphpmyadmin or myphp to change post author fields to 1.
Only a temp untill 2.6.2 comes out
Posted 1 year ago #
Oh, do you know it for sure? Great!
Posted 1 year ago #
mickmel's solution worked for me.
Basically, created second admin account, then change original admin to a subscriber and back to admin. Now it works.
Would love to see this bug fixed.
Posted 12 months ago #
Thank you mickmel, that did it. Weird bug.
Posted 11 months ago #
Hi
I somehow signed up for my blog not as the admin, now I can't access areas of my blog. Any ideas on how to fix this>
Posted 11 months ago #
I had this same issue in version 2.7. Mickmel's fix worked for me, though.
This bug seems pretty old. How would we notify the developers of it?
Posted 11 months ago #
It's so irritating this bug, even when we have solved it. How can the new blog owners aware of this fix? They would be totally confused as I once was...
Posted 11 months ago #
I too had the same problem in 2.7. Luckily, mickmel's idea also worked for me. Hopefully new blog owners will be lucky and smart enough to use this forum. The Wordpress codex has also been incredibly helpful also.
Posted 11 months ago #
@mickmel
Thanks a lot! You saved me a HUGE headache!
Posted 11 months ago #
Had the same weird problem for some time. Adding a new administrator and changing the old to subscriber and back to admin again does the trick for me too. Great, thanks.
Posted 11 months ago #
@mickmel
You saved me too, thanks a lot!
Posted 10 months ago #
@mickmel trick worked for me... Thank you so much!
I noticed that before, and never found a solution. The most weird thing is that I run three WP 2.7 on the same domain name (www.mydomain.com, and two subdomains) and only have had the problem on one of them.
WP guyz, please fix it? =)
Posted 10 months ago #
@mickmel
I had already created a new user and reassigned my posts to it. However, this worked like a charm.
Posted 8 months ago #
Looks like this bug has still NOT been fixed.
Posted 7 months ago #
I have this problem, bugs happen, but this really should have been fixed by now! I've spent ages trying to get a solution and was lucky enough to find this thread eventually.
Thankfully this fix solved the problem, but come on devs... this was a bug reported ages ago. Why has a fix not been added to the core yet?
This topic has been closed to new replies.
