Have you looked into any error logs being generated?
This is happening to me too. =(. Out of curiosity, who’s your webhost? I use Dot5Hosting.
Let me describe my problem, and let’s see if anyone else has this exact same issue. First of all, I didn’t tamper with anything. I posted a blog entry last night, several friends viewed it (including myself), and I woke up this morning with a broken WordPress. =(.
I can access all the admin pages (even managing particular posts/pages). However, I cannot access the dashboard, and therefore, cannot access the /wp-admin directory (as it takes you directly to the dashboard). I’m unable to access my main website (http://www.rishi-kumar.com) as it times out. I’ve tried disabling all the plugins, but this problem persists.
rishk789, Seems to me that something in your index.php has changed – suggested route would be to check what is in the index.php file – if it doesnt match the default index.php from wordpress then replace it with the default. And maybe post the contents as they are now on this forum.
And also seems to me that you may have set up or edited your .htaccess file so check what that is doing.
Hello hotkee, I’ve checked both and they’re identical. I “upgraded” to beta 3 of the WP 2.6, so the index.php is the same as the install default. My FTP server said that my htaccess was modified yesterday, but I don’t see any glaring differences.
.htaccess contents:
DirectoryIndex index.php
AuthName rishi-kumar.com
# BEGIN WPSuperCache
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
AddDefaultCharset UTF-8
RewriteCond %{REQUEST_METHOD} !=POST
RewriteCond %{QUERY_STRING} !.*s=.*
RewriteCond %{QUERY_STRING} !.*attachment_id=.*
RewriteCond %{HTTP_COOKIE} !^.*(comment_author_|wordpress|wp-postpass_).*$
RewriteCond %{HTTP:Accept-Encoding} gzip
RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html.gz -f
RewriteRule ^(.*) /wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html.gz [L]
RewriteCond %{REQUEST_METHOD} !=POST
RewriteCond %{QUERY_STRING} !.*s=.*
RewriteCond %{QUERY_STRING} !.*attachment_id=.*
RewriteCond %{HTTP_COOKIE} !^.*(comment_author_|wordpress|wp-postpass_).*$
RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html -f
RewriteRule ^(.*) /wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html [L]
</IfModule>
# END WPSuperCache
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
index.php
<?php
/**
* Front to the WordPress application. This file doesn't do anything, but loads
* wp-blog-header.php which does and tells WordPress to load the theme.
*
* @package WordPress
*/
/**
* Tells WordPress to load the WordPress theme and output it.
*
* @var bool
*/
define('WP_USE_THEMES', true);
/** Loads the WordPress Environment and Template */
require('./wp-blog-header.php');
?>
I would try disabling super-cache plugin in then – and if you cant access admin, then at least reset your .htaccess to the default setting.
I’ve disabled all the plugins, heh. And tried reuploading my .htaccess file without the Super-Cache parameters.
Well upgrading to a beta version might be the cause – I never do that myself.
When you say you re-uploaded .htaccess then does it contain the supercache as you have described above – I would expect just
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
You’re right. What I meant was that I tried just uploading the basic WP .htaccess parameters, but that didn’t work. So I replaced it with my original .htaccess (containing the Super-Cache parameters). I suppose I’ll upload another copy of WP 2.5.1 and overwrite the files?
Before doing that is there error log file being generated?
My webhost is sort of… weird. I found an “accesslog” document from my webhost, but is there anywhere else I could search for an error log?
In your wordpress directory, maybe a file called error_log
Well in that case I dont know – The beta version might be broken or your database is messed up. If you try to downgrade to 2.5.1 I wouldnt know if it would work.
You might try replacing all your existing files with fresh copy from the beta install.
I’ll try that hotkee! Thanks for spending the time to help! I hope this works.
