Skip to:
Content
Pages
Categories
Search
Top
Bottom

Great new version!! But New user email password "still" does not work : (


  • dlittle800
    Participant

    @dlittle800

    LOVE new version 1.2, but….

    Login password “still” does not work in 1.2 – just like it didn’t in the previous version 1.1.3.

    No point in reporting it as a bug since I already did so for the previous version

    Here’s the sign-up email…


    Dear User,

    Your new <domainname.com> blog has been successfully set up:

    <domainname.com/blog>

    You can log in to the administrator account with the following information:

    Username: xxxxxxxx

    Password: fbff9b74 <<<


    What is this? Where does it come from? It does not work! (Just like 1.1.3)

    LOGINLINK <<<


    There’s no login link

    We hope you enjoy your new blog.

    Thanks!


Viewing 11 replies - 26 through 36 (of 36 total)

  • Mike Pratt
    Participant

    @mikepratt

    @jfigura being a dick is probably not going to get you all the help you need and we are all attempting to give. DJPaul is fond of playiing moderator :-)

    There are only 2 people with commit autorization and if you think @apeatling and @jjj are the only ones contributing and helping people, you are sorely mistaken.

    I just re-read all of your posts and nowhere did you mention info like @hnla did above…for example, everything works well in the no blog creation scenario but breaks when blogs are allowed to be created. Now we have something to help us try and re-create the problem. You said “IF” it does. We have repeatedly told you that it is NOT supposed to (nor has it in any of my installs) Now, I believe you when you state that it’s happening to you. So we’re trying to get your install to the point where you DON’T get the email from WP with the password. Given the overwhelming majority of users do not get the email, wouldn’t it be easier to get to the root of your problem, than to create a hack for just your case? Odds are you have a setting wrong or something we are not aware of (either that or there’s a massive bug and the rest of us are just plain lucky we don’t get the confusing email!)

    If you’d rather, we can stop pouring over the code base to see what might be causing your issue (since we’re not on the dev team and all)


    jfigura
    Participant

    @jfigura

    “@jfigura being a dick is probably not going to get you all the help you need and we are all attempting to give. DJPaul is fond of playing moderator :-)

    Excuse me? You have given no help other than to misread my posts, accuse me of debating something I am not, and now you your professional attitude is to call me a “dick”? – who is “we all” – Who has given something to troubleshoot or to look at? What HAS been stated here is how to make it go away but that it doesn’t help to solve testing issues. Yet no one has come back asking anyone here to do anything to test, especially you.

    People who use names like that are usually representing how they ultimately see themselves, and it’s real apparent that the only “dick” on the thread right now is yourself.


    Mike Pratt
    Participant

    @mikepratt

    Let’s move on to solving your problem, shall we? Everyone here is trying to help you. We are not misreading your posts (as evidenced by jjj’s reply – he’s part of “we”) We have given you things to look at but continue to have to ask questions to nail down your specific case. The bandaid solutions are not what we’re after but we are trying to figure out what combinations of settings might be tripping this behavior on your install. Yes, asking all these questions is a part of “helping” It’s not merely the eureka solution you expect (which also counts as “helping”)

    Are you experiencing this on a clean 1.2, wpmu 2.9.1 (if not, that’s a suggestion to test) install with no plugins (esp the email related ones out there?) Are you experiencing it with blog creation on? off? Is this a sub-directory or sub-domain install? After this we might be able to reproduce. But if we can’t, then we have to continue to ask questions to see what it is you might have set differently.

    Oh, and I promise to work on my self-image projection issues. :-)

    Relax people, please. Let’s get a little perspective here.

    Where is the ticket for this issue in trac? Can someone please link it on this thread. I need a ticket to reference.


    peterverkooijen
    Participant

    @peterverkooijen


    jfigura
    Participant

    @jfigura

    Andy – Being a new user to BP, I was unaware you had a ticket tracking process. I found Trac and created a ticket. Ticket #2043.

    Mike – I would appreciate it at this point if you just backed off.

    And I have demonstrated the test conditions of a clean install of 2.9.1.1 and BP 1.2 with NO additional plugins.

    However I will qualify ‘clean install’ by adding that BP 1.1.3 was originally installed activated once deactivated and not used on this particular install other to test once only that it was functioning. BP was upgraded to 1.2 for purposes of this test and activated.


    jfigura
    Participant

    @jfigura

    This has apparently been set to fixed in 1.2.1 — Hope that it indeed is. Thanks.

    The emails will now say [user set] next to the password, unless you change the welcome email.


    jfigura
    Participant

    @jfigura

    Confirmed… works as advertised. THANK YOU ANDY!

    No problem, glad to get that one worked out.

Viewing 11 replies - 26 through 36 (of 36 total)
  • The topic ‘Great new version!! But New user email password "still" does not work : (’ is closed to new replies.
Skip to toolbar