Forums

site htaccess disables log to blog (5 posts)

  1. saltoboss
    Member
    Posted 7 months ago #

    Dear Friends,
    I am going around in circles now for hours. I have a godaddy hosting and successfully installed WP. I could log in changed themes, plugins everything was working fine. Until I must have caught a plug in that wasn't compatible - after activating it I could no longer log in to WP - it kept bouncing back to the log in screen.

    After some fiddling around and deleting the plugin - still not possible to log in. Was searching the post in the forum tried all kind of things without success. Now I have a small breakthrough - I can control if I can log in or not !
    My mainpage has a htaccess file - when I rename it I can log into the blog as admin like it should be - problem - the main website doesn't work any more !
    when I rename it again to its original htaccess- the site works but cannot log into WP anymore

    My guess there must be some conflict or other corrupt file - please help me out on this as it is driving me crazy

    Thanks

  2. HostMantis
    Member
    Posted 7 months ago #

    It sounds like you still have a plugin that is trying to load that is having issues. You'll need to find out which one it is and delete it.

    Check your PHP error log to see which plugin is causing the error (filename: error_log).

  3. saltoboss
    Member
    Posted 7 months ago #

    Dear mantis,
    thanks for your advice - it was really strange. Each time I disabled my htaccess of the main page I could log in to WP without problem. But of course the navigation of my website didn't work.
    Remark - I have deleted the complete folder of the ping.fm custom URL 2.0.1 plugin
    After I enabled the htaccess file again - the website navigation was ok but the log in to WP failed.
    I changed the htaccess file in several ways (whatever I could find in here and tried again. Results were mixed - at some point I came to a level in which I could log in and the website worked almost - except the links to subpages didn't work any more.

    Finally I gave up - and removed the whole WP application via the godaddy site. Then I disabled the original htaccess file and the php5.ini file and re-installed WP again.
    and tataa - it was working - some of the setting were still there but of course all the hours of work into customizing the template were gone.
    After this I activated the two files again and it is still working fine.

    I guess there must have been some file in the blog sub directory that has been altered by the plugin and messed up the WP log in with the existing htaccess.

    Thank you anyway for the tip with the "error.log" file - was just searching for it in the new istallation but all I found was a filed named "class-wp-error.php" located in /blog/wp-inludes. for the futuree is this the same file you are talking about?

    Thanks

  4. HostMantis
    Member
    Posted 7 months ago #

    No, that's not the file I was referring to. PHP errors are typically logged to error_log by default, but Godaddy logs differently. With them you have to activate logging to begin with. Here is an article that explains more: http://help.godaddy.com/article/1197

  5. saltoboss
    Member
    Posted 7 months ago #

    found the log file on the server - to me does give very much
    I can only guess what the entries mean
    [error] [client 207.204.229.249] File does not exist: /var/chroot/home/content/t/m/a/myusername/html/blog/missing.html"
    This must be the event when I couldn't log in any more, another message was
    "[error] [client 95.108.241.250] File does not exist: /var/chroot/home/content/t/m/a/myusername/html/homepage/addpopup/103/"
    ..this means that the website could not jump to product 103 (addpopup/...I have seen on my normal website.
    Then a bunch of messages, which I assume came from my different experiments with modified htaccess files, looking like this
    [error] [client 66.249.68.200] mod_rewrite: maximum number of internal redirects reached. Assuming configuration error. Use 'RewriteOptions MaxRedirects' to increase the limit if neccessary.
    ] /var/chroot/home/content/t/m/a/tmarinelli/html/.htaccess: RewriteCond: bad argument line '%{REQUEST_FILENAME}!-f'\n
    [Sun Oct 9 03:22:41 2011] [alert] [client 207.204.229.249] /var/chroot/home/content/t/m/a/tmarinelli/html/.htaccess: RewriteCond: bad argument line '%{REQUEST_FILENAME}!-f'\n
    [Sun Oct 9 03:22:59 2011] [alert] [client 207.204.229.249] /var/chroot/home/content/t/m/a/tmarinelli/html/.htaccess: RewriteCond: bad argument line '%{REQUEST_FILENAME}!-f'\n
    [alert] [client 207.204.229.249] /var/chroot/home/content/t/m/a/tmarinelli/html/.htaccess: RewriteCond: bad flag delimiters
    after that nothing left - not sure if this can give any indication what actually went wrong..
    I am just a little worried that all I could do to fix it was a re-install and loosing pretty much everything.
    So if I load a new plugin - I risk again loosing everything if the plugin in not working! Any suggestions how to prevent this? (except from not trying new plugins)

Reply

You must log in to post.

About this Topic