Page 1 of 1
creating new standard editor keeps chief editor info
Posted: Tue Aug 02, 2005 4:19 am
by kevin v
First: I upgraded from 0.7.1 to 0.8.2. For some reason that killed my "administrator" account, but left my chief editor account. I cannot create a new admin account while logged in as chief ed, so how do I create a new administrator? I don't see a "users" file that I can edit in the file structure. Is this a sql edit?
Second: as chief editor, I added a new user (let's call him 'Joe') with standard editor perms. When I then log in as Joe and click Personal Settings, the displayed username and password are those of the chief editor, not Joe. If I change username and password and save, they revert back to the values for chief editor. Everything else, such as email and real name, are as entered for Joe.
Re: creating new standard editor keeps chief editor info
Posted: Wed Aug 03, 2005 4:45 pm
by garvinhicking
That is strange. The upgrading facility does not delete author rows. Which database are you using?
The only thing that affected the authors table is this SQL:
Code: Select all
ALTER TABLE {PREFIX}authors ADD realname VARCHAR( 255 ) NOT NULL FIRST;
UPDATE {PREFIX}authors SET realname = username;
Can you check your serendipity_authors table and look if your administrator account is maybe still there and you're just using the wrong loginname or password?
The authors table is also the place to insert new accounts manually.
Your second issue can happen if you are using Firefox with some extensions that save your last form input. If you look in the HTML code you will see the right values; just Firefox/Mozilla displays it wrong because it stored other profile's info. You can only fix this by disabling the evil extension (I forgot the name, but if you tell me all your extensions I can tell you the one to remove). This extension BTW is troubling more than just Serendipity; I've had issues with many other webapps as well.
Regards,
Garvin
Posted: Fri Aug 12, 2005 9:13 am
by kevin v
thanks Gavin. when I went into MySQL I found two serendipity_author rows with the <i>same</i> username - one with 255 and the other with 1 permissions. This was definitely changed sometime during the upgrade, but it is possible there was a weird interaction between my s9y install and my hosting site's APIs. I haven't played with SQL in a long time, but I can see how the lines you cite below may have created this problem. Doesn't the second line set username to realname? So if I had the <i>realname</i> of my admin account set the same as the <i>username</i> of my cheif ed account, then that line would give my admin account a new <i>username</i>? And isn't it <i>username</i> that is being checked when I log into the admin/authoring suite?
You are correct on firefox's password field handling. mozilla needs to deal with that! changing the info in IE did the trick.