Loading...
 
Architecture / Installation

Architecture / Installation

Forum List Topic List

Forums » Architecture / Installation » Invalid username or password
 
Thread actions
PDF Print this page
  • Print all pages

    • Invalid username or password

    Posted by cords posts: 6 Cyprus

    hi gang!

    i was running v1.7 with no problems until my hosting service made some changes to their system at the end of last year. i decided to bite the bullet and installed v1.8.1 from the ground up. i renamed the old directory, installed to a new directory and cleared the database.

    after struggling with permissions, i got the install running. got the thumbs up that it went okay and tried to access my site. got another permissions problem because all cached pages seemed to be owned by a new apache user and group (it's what broke v1.7) but got *that* resolved by my hosting service.

    now everything appears fine. i can access TikiWiki, but when i try to log in as admin/admin, i get an "Invalid username or password" error message. i don't know what to try anymore and am feeling a little frustrated. confused

    can anyone suggest a starting point for me to find a solution. i am using a hosted redhat/apache system with FTP & SSH access, and asaik safe-mode is enabled. i've added the basedir and smarty use_sub_dirs tweaks, and browsed the forums for help. now i'm at my wits end! should i try re-install now that all the permissions are fixed?

    regards
    cord

    Reads: 1498
    Link
    Posted by Damian Parker posts: 2881 United Kingdom


    Looks like the admin password was changed

    Login to your database with phpMyAdmin or something
    find in users_users the admin record
    and give it a valid email address

    now if you have remind passwords enabled you can simply to I forget my password and get it emailed
    if you dont simply enable it in tiki_preferences table

    Hope it helps

    Link
    Posted by cords posts: 6 Cyprus

    hi Damian,

    > Looks like the admin password was changed

    nope... i checked that already. the password field is still "admin".

    now here's the bizzare thing: i did as you suggested (added a valid email address to the user record) and went through the motions of "I forgot my password". i was sent an email with a new password - i think that's how TikiWiki works by default; it resets the password. anyway, long story short, i logged in with the new password and i'm in!

    i'm still scratching my head of this but anyway... i seem to be up and running now.

    > Hope it helps

    indeed! thanks for the suggestion.

    regards,
    cord

    Link

    Posted by cords posts: 6 Cyprus

    hi Damian,

    > Looks like the admin password was changed

    nope... i checked that already. the password field is still "admin".

    now here's the bizzare thing: i did as you suggested (added a valid email address to the user record) and went through the motions of "I forgot my password". i was sent an email with a new password - i think that's how TikiWiki works by default; it resets the password. anyway, long story short, i logged in with the new password and i'm in!

    i'm still scratching my head of this but anyway... i seem to be up and running now.

    > Hope it helps

    indeed! thanks for the suggestion.

    regards,
    cord

    Link

    Posted by cords posts: 6 Cyprus

    further to my original post, i am definitely experiencing problems with the way TikiWiki is managing users. i allow a user to register on my wiki and send a validation email to confirm that everything is ok (standard practice in my book).

    the validation email was sent along with a URL which when clicked on generates the following:

    The XML page cannot be displayed
    Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.

    Only one top level element is allowed in an XML document. Error processing resource 'http://xxxx.co.uk/wiki/tiki-login...

    Warning: ob_start(): output handler 'ob_gzhandler' cannot be used after 'URL-Rewriter' in /home...

    try as i might, i cannot get the user to log in from this point. i have tried the original password and also "I forgot my password" to reset the oringal password.. no go. TikiWiki won't allow the user to log in at all even though Admin'ing the user account shows that it's valid and active!

    any ideas what next?

    Link

    Posted by Philippe Cloutier posts: 1001 Canada

    Hi cords,
    the strage password you get when asking for a new password is indeed normal.
    The XML error usually depends the browser and is generally associated with IE use, try with Mozilla. It can give you a PHP error message instead, more helpful.
    I suggest disabling the Gzip compression from Admin General, if it's activated, although I'm not sure this will help.

    Link
    Posted by cords posts: 6 Cyprus

    hi Chealer9,

    > The XML error usually depends the browser and is generally associated
    > with IE use, try with Mozilla. It can give you a PHP error message instead,
    > more helpful.

    oddly enough i had the error with Opera 7 and IE.

    > I suggest disabling the Gzip compression from Admin General, if it's
    > activated, although I'm not sure this will help.

    this seemed to fix the problem. tried a number of different options - in desperation - on the same day i made the post and turning off the gzip compression seemed to do the trick.

    sorry for not posting my findings sooner!

    and, thanks for the suggestions...

    Link

    Posted by cords posts: 6 Cyprus

    hi Chealer9,

    > The XML error usually depends the browser and is generally associated
    > with IE use, try with Mozilla. It can give you a PHP error message instead,
    > more helpful.

    oddly enough i had the error with Opera 7 and IE.

    > I suggest disabling the Gzip compression from Admin General, if it's
    > activated, although I'm not sure this will help.

    this seemed to fix the problem. tried a number of different options - in desperation - on the same day i made the post and turning off the gzip compression seemed to do the trick.

    sorry for not posting my findings sooner!

    and, thanks for the suggestions...

    Link