WordPress.org

Make WordPress Core

Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#4432 closed defect (bug) (worksforme)

After a couple of new users register as AUTHORS, after that ADMIN can't write as himself

Reported by: lelion Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.2
Component: Administration Keywords:
Focuses: Cc:

Description

OK,

here it is in two words:

I install a fresh copy of WP 2.2. I let user register themselves for the blog. I make default users to be AUTHORS when they register.

After one or two users register, ADMIN (me) can't write a post or a page as HIMSELF, only as one of the newly registered users...

Workaround? Yes. After the first 1-2 users register and the bug happens, go to OPTIONS and change the role of ADMIN to be ADMINISTRATOR. He *is* already an administrator, but only *after* updating his profile as ADMIN you can start writing pages/posts as yourself...

Happened to me more than once, so it should be a bug...

Do you need PHP/MySQL versions?

All details are explained here: http://wordpress.org/support/topic/121520?replies=4

MichaelH advised me to file a trac ticket, so here I am, duly reporting this bug:)

Thx:)

Change History (8)

#1 @rob1n
12 years ago

  • Milestone set to 2.4 (future)

#2 in reply to: ↑ description @pishmishy
12 years ago

Replying to lelion:

Happened to me more than once, so it should be a bug...

I tried to replicate this using the trunk version of WordPress. Here's what I've done.

  1. Completed install and allowed new users to register as authors. Logged out.
  1. Registered user 1
  1. Registered user 2
  1. Logged in as admin and created a new post. This appeared as written by me.

I've been unable to replicate what you've seen. Can you provide any further information that might help?

#3 @lelion
12 years ago

OK, I may give you versions of PHP, MySQL, etc. (will try as soon as possible - it's on another server).

I've seen the bug at least twice (or more even) - when I replicate these steps, it appears on THIS server always. Then I can fix it with the workaround...

Thx, I'll be back with more details:)

#4 follow-up: @lelion
12 years ago

OK, here it is:

MySQL 4.1.22, PHP 4.4.6

Blog is installed in subdomain (blog.ourdomain.net)

Does this help?...

I might try to replicate it again, if needed, and just ask what other details you might need to see the problem better? :-)

#5 in reply to: ↑ 4 @pishmishy
12 years ago

Replying to lelion:

Does this help?...

I might try to replicate it again, if needed, and just ask what other details you might need to see the problem better? :-)

I can't think what it might be. Could you contact me at james@… - there's some things I'd like to try but don't want to fill up the ticket with minutiae.

Thanks,

James

#6 @lelion
12 years ago

OK, I'll contact you:)

#7 @pishmishy
12 years ago

  • Resolution set to worksforme
  • Status changed from new to closed

Both myself and the reporter have been unable to replicate this problem with trunk code in two different server environments. I can only presume that this is an issue that's already been resolved.

#8 @Nazgul
12 years ago

  • Milestone 2.4 (future) deleted
Note: See TracTickets for help on using tickets.