WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] [closed] Help for your Sign-in issues - other than case sensitive username (24 posts)

  1. SocialBlogsite
    Member
    Posted 2 years ago #

    As many of you, I fell by the "we changed passwords in June…" message but there are other things to consider when you can't login:

    1) Although help says everywhere "your plugin login is the same than the forums" they don't clarify that OTHER wordpress.org passwords, like for Codex / Documentation sections won't work. The first notification seems to spread positivity, but the negative answer needs to be given too, because it's the solution for lots of frustrations.

    2) You might have different accounts, e.g. personal and busines's, and both could be sharing the same gravatar's email. Don't know exactly whether that caused the following error, but double check and help me to figure it out.

    3) I haven't solved this one yet, and I'd appreciate your feedback.
    When trying to upload one of my plugins by SocialBlogsite I tried out logging in from several locations, logout, login again…because it was clear the my user IS SocialBlogsite, and my password was allowing me access the CODEX pages, so "it must be the same", I thought.

    During those trials, at some point THE SAME account (same ID#) shown different email addresses. Nothing to do with cookies, because as you can see I mispelled my own name in one of them (don't know how i managed to setup two accounts with same user ID) so it's a new page, not cached nor populated by cookies.

    Well, here are the screenshots, seconds apart from each other.
    http://socialblogsitewebdesign.com/social_downloads/Wordpress-login-1.png
    http://socialblogsitewebdesign.com/social_downloads/Wordpress-login-2.png

    That's a bug? that affected every login in the last months BIG time, because one of the things you try when user and pass seem correct, is that you are logging in to the right account, retrieve passwords… so you TRUST the info at wordpress.org pages to base your next trials.

    Also, the screen capature thing was to show (not resolved yet) that…

    4) Usernames are NOT always case-sensitive (yes, I know it's impossible, but the previous screen-capture are not either, but it happened!, so, considering that…)

    When logging in with SergioZambrano, the "username" appeared as Sergiozambrano (lowercase Z). Regardless of the account I was accessing to, it shown one thing in the profile when signing in with a different thing. NOT helpful when you are trying to figure out why your password won't work and you really trust "Your username is case-sensitive"

  2. SocialBlogsite
    Member
    Posted 2 years ago #

    I can't commit changes to a plugin I developed, and I'm wondering whether the "Author" name in the info at the top should be the "username" instead.

    It could be denying me access to the plugin, rather than a login failure, because the "Author" name appears like "Sergio Zambrano" rather than "SergioZambrano".

    I'll make a few tests with gravatar now to track and replicate the different usernames and emails I saw.

  3. Zambrano Sergio
    Member
    Posted 2 years ago #

    [UPDATE}
    Here are a few tests I screencasted. The video was edited since I repeated the same test many times, but I cut at the logouts, so it doesn't affect the tests.

    http://www.youtube.com/watch?v=Srm8LXKraNU

    I use Chrome. in the video you can see me deleting the cookies before. My apologies for the watermarks.

    It shows:

    1) WordPress says "logins are unified", "no spaces allowed" and "case sensitive" but
    I can log-in to forums using spaces, and no caps for codex.

    2) Codex user is not to the same, though. Codex accepts Sergiozambrano and forum doesn't.
    No option to edit Codex's user info nor create a new user. It says "Go to Forum", BUT logging-in to forums WONT log me in to Codex. So there's an account I can't change nor verify (Codex's)

    3) The broken link in my plugin's page (graphic sitemap) means the "Author:" line in readme.txt (and plugin's comments?) means "Username". Using "Full Name" will break the link to the author.

    Still not able to commit my plugin. WP says everything is ok in their side, but my side keeps showing inconsistencies from WP DB.

  4. SocialBlogsite - If you're still having problems, email plugins [at] wordpress.org

  5. SocialBlogsite
    Member
    Posted 2 years ago #

    They are the ones who don't reply anymore.
    Since they can commit with my username from their end, it's assumed nothing wrong is in "their" side.

    My screenshots and videos show the opposite, though.

  6. The code used for unified logins between codex, plugins and SVN is mostly consistant. The profiles are also mostly consistant, and you really shouldn't be messing around with your profile in the codex. Either change it at http://wordpress.org/support/profile/socialblogsite or http://profiles.wordpress.org/users/SocialBlogsite/

    Looking at your info, you SHOULD be logging in with SergioZambrano and SocialBlogsite camel-cased. Everywhere. That should work all the time with forums, Codex and SVN.

    If you look at my profile, you'll see my userID shows as Ipstenu, capital I. I have to login to the forums and SVN as Ipstenu, with the capital, but the codex (being an older version of MediaWiki and kind of weird) accepts I and i. Don't get hung up on the Codex, it's the odd man out and everyone knows it's odd.

    By the way, notice how the profiles.wordpress URL has your ID camelcased? THAT is how I always know what the ID should be :) if that's camel'd you should be camel'd. And YES, it totally matters when you add users to have SVN commit access, and even author listing for a plugin.

    Leave your Codex profile alone. It's useless.

  7. Zambrano Sergio
    Member
    Posted 2 years ago #

    Ipstenu:

    Thanks for your helpful answers.
    Let me ask you some things anybody would check themselves but since my issues seem to happen only to me, I'd like to know how it goes in YOUR end.

    1) Can you login to forums with "Name Lastname"? (yes, with the space) If you watched my video, you'll see I CAN.

    And… just to free me up from the doubt:
    2) For codex: If your "real name" has not been updated yet (Seems like before there was no realname fields because I found my username here last week) Can you login with your "real name"? (just change it to "somename" no spaces and try.

    3) As per what you said, do both readme.txt and myplugin.php need to show "YourLogin" as "Author" in order to be allowed to commit?

    Otto told me:

    This doesn't make any sense. The plugin's comments have nothing whatsoever to do with "committers". The allowed committers are set on the plugin's individual administration pages.

  8. Samuel Wood (Otto)
    Tech Ninja
    Posted 2 years ago #

    You're making very little sense here, in much the same way that you made almost no sense via our earlier emails.

    - Your username is "SergioZambrano" or "SocialBlogsite". Period. You don't *have* any other username.

    - No, you can't use spaces, because there's no spaces in your username.

    - The codex has the exact same username and passwords as this forum does. They're unified. What you set your "Real Name" to is completely and totally irrelevant. You cannot change your login username, at all, ever, period.

    - What is in the readme.txt and the plugin.php file has absolutely nothing to do with who can commit to a plugin. Committers are set on the Plugin's administration screen. Login, go visit your plugin in /extend/plugins, click the Admin link. You can add committers there.

  9. Samuel Wood (Otto)
    Tech Ninja
    Posted 2 years ago #

    Watched your video. What you're seeing is that the support forums are smart enough to authenticate you regardless of your added space. My username is "Otto42", but I can also log in as "Otto 42" or "O t t o 4 2" if I want. That doesn't change what my username is, and that won't make it magically work elsewhere, especially not in SVN (which is *very* picky.. name and case matter there).

    Stop trying to use weird usernames. Your username is "SergioZambrano". Use that. As I just typed it in.

    There's nothing wrong with your account that I can find and there's nothing wrong with our system. When you gave me your password, I tried it, and it worked fine.

    Do a re-checkout of your plugin if you have to. Maybe something is wrong with your working copy.

  10. bbPress strips the spaces, Otto. That's kind of awesome in a weird way. o.O

    (The readme and plugin.php only matters in terms of who gets listed as an author on the plugin page. They're also case sensitive, but as Otto said, putting in the wrong name will note revoke your access.)

  11. Zambrano Sergio
    Member
    Posted 2 years ago #

    Yes, I don't make much sense because my first language is not english.

    Ok, you have answered most of the screencast.
    Still not answered where the different email came from in the original screenshots. cuentanumerouno@… was not used in codex until I created it last week to test existence. It was used years ago, so I assume some backup came up to life for a few seconds when I was testing it.

    support forums are smart enough to authenticate you regardless of your added space

    Yeah… that magic should be translated to the "Author" link in each plugin footer or otherwise noted to us Plugin creators so we don't use "Our Name" instead, or the link gets broken.

    Stop trying to use weird usernames. Your username is "SergioZambrano". Use that. As I just typed it in.

    If I had had an answer to my first two screenshots (same user ID#, different email) and had been able to commit in first place, I wouldn't be "trying weird usernames". I call it "tracking an issue nobody found".

    There's nothing wrong with your account that I can find and there's nothing wrong with our system. When you gave me your password, I tried it, and it worked fine.

    For me, to be told logins are unified and then finding all these inconsistencies, how do you want me to call it other than "something wrong". Anyway, no tests no answers.
    I understand you don't find anything wrong in your side, but everything in my side is subject to what your side allows me and how much I trusted or misunderstood your documentation.

    Do a re-checkout of your plugin if you have to. Maybe something is wrong with your working copy.

    I made so many tests with my plugin that now that I added a new user (Otto offered to do it but seems didn't have the time) and am able to commit, I found the "tags" directory was scheduled to be removed. I fixed that "updating" the dir, but now SVN throws:

    xecute: Commit
    Error: Error while performing action: Commit failed (details follow):
    MKACTIVITY of '/!svn/act/******-****-****': Could not read status line: Connection reset by peer (http://plugins.svn.wordpress.org)
    Ready
    
    Execute: Commit
    Added: /Users/sergio/Documents/WP_Plugins/graphic-wp-sitemap/tags/1.1.0
    Error: Error while performing action: Commit failed (details follow):
    Server sent unexpected return value (405 Method Not Allowed) in response to MKCOL request for '/!svn/wrk/****-****-****-****/graphic-wp-sitemap/tags/1.1.0'
    Ready

    I used rapid SVN and DreamWeaver. DreamWeaver unlike rapidSVN notifies me the login was successful, but still a throws 403 for the main user.

    So, as you can see, I'm stuck again, and the original user permissions is not fixed.

  12. Zambrano Sergio
    Member
    Posted 2 years ago #

    Thanks Mark. My original username commits fine now.

    I don't know what you did, but if you didn't do a thing, let's keep this open so others can contribute with their input until it gets fixed or the word on how to fixe it is spread.

    If you did, let us know what! or how to avoid it next time.

    Removing the whole local copy fixed the last errors. That was one of my first tests but it didn't work, so you must have done something.

  13. Samuel Wood (Otto)
    Tech Ninja
    Posted 2 years ago #

    FYI: The codex is wholly irrelevant. Whatever you have set in there has no meaning anywhere outside of there. It has integrated logins, not integrated profiles or anything else. You can put any email you like there and it won't affect anything else anywhere.

    The "(405 Method Not Allowed) in response to MKCOL" message is what happens when you are trying to add a directory that already exists in the SVN. Most likely, Mark deleted that directory, allowing you to add it.

    See, you're trying to commit a change (adding the /tags/1.1.0 directory), but that change conflicts with what is already in there. That's why I suggested creating a new checkout and starting your working copy fresh from that checkout. Whatever you've did locally borked up your working copy.

    You can modify committers to your particular plugin by going to this page and putting in the proper usernames:
    http://wordpress.org/extend/plugins/graphic-wp-sitemap/admin/

    Note, the plugin is currently owned by the "SocialBlogsite" account. You'll have to be logged in as that to modify the committers.

    What is in the plugin's readme.txt file doesn't change who is allowed to commit to a plugin, it just changes the display of the plugin in the directory.

  14. SocialBlogsite
    Member
    Posted 2 years ago #

    Note, the plugin is currently owned by the "SocialBlogsite" account. You'll have to be logged in as that to modify the committers.

    Yes, I removed the original user as another way of fixing a nonsense error with nonsense tests. That's the way new cures are discovered :) (and the same way they are banned by FDA in name of "science" hehe)

    I hope you guys can tell me what you did, because the occurred shouldn't fix a user but a plugin local copy at most.

    1. The original committer was throwing errors for ANOTHER plugin as well, in TWO different SVN clients, so…
    2. The commiting issue was oddly fixed by committing from a new account,
    3. then I was able to see the corruptness of files,
    4. then I deleted the whole thing and started from new checkout,
    5. proofs so far shown me the error was "tags" directory "scheduled for deletion" affecting OWNER only, I went ahead and removed the original commiter from the list and changed the commiters and "Author" from the plugin code.
    6. Oddier, the OTHER plugin started working

    The only thing I can think of is user/plugin combinations needing manual "approval", like a flag or something, only gotten at some early stage, and when changing the line "Author" in the plugin the checksum doesn't work anymore, nor the approval is requested to WP.org admins.

  15. No, there's no manual approval. Once you get the repo access, you're good to go.

    It's possible your SVN setup on your PC was goobered because of the corrupt files.

  16. SocialBlogsite
    Member
    Posted 2 years ago #

    No, there's no manual approval. Once you get the repo access, you're good to go.

    Well, any other approval, even automated, done around the initial stages of a plugin creation which could be not re-done when changing the only commiter's "Author" would explain it.

    It's possible your SVN setup on your PC was goobered because of the corrupt files.

    It's true, but the only thing that changed in the local copy of that plugin when became corrupt was the profile update and the "Author" name, which I reverted as soon as I got the first error, no success.

    So the error must be on the server, which is the one who gives or denies privileges. My local copy doesn't decides the access. The client just sends the credentials I entered when "logged in". I just looked for my username in the current (theoretically working) .svn files and there's no mention of the username.

    AND even if this is not so, both users should work or fail the same. Instead, a new user worked while another didn't.

  17. No you misunderstood. There is but one moment of approval.

    You ask for the plugin. Approved. The folder is made, the access is granted. DONE. Nothing else happens. As soon as you have, once, uploaded code, and everything's fine, we know the approval/creation process was done correctly. After that, if something gets screwey, you must have done it.

    No one approves/denies privs after that first moment! The simple fact that you are checking out code you checked in means the privileges were set up just fine.

    My local copy doesn't decides the access

    Yes it does. Your local copy tells the server who you are. If THAT info got corrupted, you'd see a problem like this.

  18. SocialBlogsite
    Member
    Posted 2 years ago #

    Yes it does. Your local copy tells the server who you are. If THAT info got corrupted, you'd see a problem like this.

    No, my local copy doesn't contain the username in any .svn file, and it doesn't say a thing to nobody. It's just data in my disk, which worked FINE for another user. It's the client who sends the login info, in this case rapidSVN, which is a software. This software agrees with DreamWeaver that my login is fine, and that your insinuations that there's no error on the server side is wrong.

    If it's not wrong in the DB, it's wrong in some other place you'll find soon.
    I just hope somebody is honest enough to admit it when you/they fix it.

    Again, by changing something in my profile, or "Author" name in my plugin, by themselves SHOULD NOT affect that user's access to TWO plugins, through TWO different clients, while other user CAN access it using the SAME local info. Not if everything were working as you describe it should.

    When the description of "how it should be" and "how it actually works" mistmatch, there's a bug. Even if it's the description what is wrong, it's called a bug, since it's not performing as it is expected (or taken as given it should)

    Now, let's forget you confused local copy with client and move on:
    Given:

    1. DreamWeaver and rapidSVN tells me WP SERVER throws a 403 error, and
    2. DreamWeaver even confirms "You have been successfully accessed the server", and
    3. ANOTHER user and another client use both the same local files, and
    4. one of my first tests to fix the 403 issue was actually to create a new local folder and starting from scratch, and didn't work
    5. A new user gained access fine
    6. committing was tested and failed right before to grant access to the new user, which means the error didn't fix itself between 1 and 5

    Do you still suggest there's something wrong with my local copy?

  19. Not your local copy of the plugin, your local install of the SVN client (in your case, RapidSVN).

    It's the client who sends the login info, in this case rapidSVN, which is a software. This software agrees with DreamWeaver that my login is fine, and that your insinuations that there's no error on the server side is wrong.

    Yes, that's what I think is corrupted.

    I use svn via command line, but I have the ability to save my username and password so I don't enter it every time. Should my password change I get one error, and should the file that stores that info get corrupted, I get a 403. It's happened before.

    RapidSVN takes your username and password to the WordPress SVN repo to commit files. Should it's information as to who YOU are get corrupted, you'd likely see the same error.

    I'd uninstall RapidSVN or wipe out it's prefs and start over.

  20. SocialBlogsite
    Member
    Posted 2 years ago #

    I have the ability to save my username and password so I don't enter it every time

    As I said before, the username WAS in the .svn files, but it was just in the url, as you said to use it. That was not causing the issue, since I tested it too. With and without it the error kept going. (I made other tests with and without other usernames as well)

    The theory of a corrupt software makes no sense. I DIDN'T install any software when it finally worked from a different user. Again, other plugins were commiting fine. Nothing changed and what did I tested it, reverted it, and tried to replicate it.

    RapidSVN takes your username and password to the WordPress SVN repo to commit files

    No. The password is not saved in the .svn files. I HAVE to manually log-in/out before to connect and I DID test many usernames, passwords, saved, not saved, etc. No success. Other plugins committed fine with a different user.

    The info for each plugin is stored in the files inside .svn and .tmp directories. The ones inside .tmp are deleted in each app restart and the ones inside .svn only affect the directory it is in. I tried other directories etc etc. no success. Forget it. My local files were tested for ANYTHING you can think of, many times, many days.

    Yes, a mouse bitting my internet cable under the rain also would explain an error. But that doesn't explain all the other points I'm repeating in every post.

    Should it's information as to who YOU are get corrupted, you'd likely see the same error.

    The information as to who I am is saved in the .svn files, in the url. Nowhere else. AND those files don't affect other plugins. Anyway I removed, re-created, duplciated, edited, etc all the bookmarks, created new local directories, etc. Nothing worked.

    Only logging in from a different user worked, AND fixed another plugin (or matched with the date the block in the server was removed/fixed)

  21. SocialBlogsite
    Member
    Posted 2 years ago #

    UPDATE:

    The plugin graphic-wp-sitemap appears as missing in the plugins directory.
    I got an email saying "your plugin is ok" (I was questioned about a back-link in it) and I though someone would eventually put it back live, but it's been 7 days and the plugin is still not found I can commit, though.

    If the normal process is NOT taking it off-line while the doubts are resolved, then it definitely stopped working since I REMOVED the original user from the list of committers.

    Why did I remove the original user?
    Once I got it back working with the new user and committed all files and made sure the plugin was properly working, I removed the original user to test wether re-adding it would fix it (the user) how precise was the statement of

    No one approves/denies privs after that first moment! The simple fact that you are checking out code you checked in means the privileges were set up just fine.
    and other similar statements about how nonsense was my questions about the relation between the "Author" line in a plugin or the readme.txt file, the committing privileges and the plugin's approval process.

    As per the happened (the plugin is missing now) It seems the plugin is approved for the ORIGINAL user. That means exactly was I suggested: A change in the "Author:" line in the plugin comments or readme.txt file or, in this case, the committers, would make the plugin-user validation to fail.

    Right Now I can commit, but the plugin does NOT appear in wp plugins website. No answer from WP in the last 7 days about that.

  22. Samuel Wood (Otto)
    Tech Ninja
    Posted 2 years ago #

    No, this is not an SVN issue, nor does it have anything to do with the readme or any other thing like that. There is no 'validation' like you're speaking of. I do know how this thing works, you know. I have the source code.

    The plugin appears to have been manually removed from the listings. No idea why, I'll put in a request for the reasoning.

  23. SocialBlogsite
    Member
    Posted 2 years ago #

    Thanks Otto.

    Well, manual intervention was always one of the possibilities, and even makes more sense for the initial issue. (My user was definitely blocked)

    Now that you guess that, I'll guess something too: My plugin was flagged for moderation but since nobody had the time to take a look at it, some random block was put in place, and when I found the way around it the whole plugin was taken out of the listing.

    That would explain why I've got questioned about the back-link MONTHS after it was approved (right after I re-gained committing access through the new user)

    Good news, it's not a bug :)
    Bad news, when a hand is involved it becomes discrimination, retaliation, personal interest, hidden agendas, or many other nasty words.

  24. Samuel Wood (Otto)
    Tech Ninja
    Posted 2 years ago #

    The user was not blocked. We don't even have a way to do that.

    The plugin itself "graphic-wp-sitemap" was manually delisted. It's been re-listed now, and is visible in the plugins repository.

Topic Closed

This topic has been closed to new replies.

About this Topic