Thread Starter
ronams
(@ronams)
Here’s what’s in it.
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /blog/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /blog/index.php [L]
</IfModule>
# END WordPress
I’ve re-created it many times, but not sure what renaming it would do, so haven’t tried anything like that.
Thks for the help.
Rename it to .htaccess.bak just for grins. WP won’t see it and may act a bit differently.
Sure, I’m grasping, but it’ll only take a minute to try. 🙂
Thread Starter
ronams
(@ronams)
No change when renaming .htaccess to .htaccess.bak.
But did find something interesting. At the bottom right of the wp-admin there is blog stats. I can’t look at the posts (cannot display page), but I can look at the comments. On that page that shows all the comments, you can choose to edit comments. When I bring that up edit-comments.php I get a good Manage Page (created by edit-comments.php) I can again select edit-pages.php and get a good page, but if I select edit posts (edit.php) again I get the page cannot be displayed.
Hope this helps. Does this not mean in both the index and the edit.php they are both trying to display all the posts at once and fail.
Thread Starter
ronams
(@ronams)
FYI, having seen that edit.php is always failing, I’ve uploaded it from fresh upgrade versions a couple of times in case it was corrupted. No luck on that fixing it.
Apologies for jumping in on your problem but I have been following this thread and am also experiencing upgrade problems from 1.5 to latest and I didn’t want to duplicate another thread. I’m stuck.
I have read and reread the instructions and tried twice to delete old and upload new files. I have checked DB is intact but for some reason I cannot access the upgreade.php page or any other.
My Blog has gone BLANK through the browser and yet all the files are there with the correct dir and file permissions
I would appreciate and help or guidance anyone can give. I have trawled the site but to no avail. Many thanks rus (the blog resides in root at http://www.04gh.com)
Kay – well, I’m at a loss.
If it were me, I’d just FTP into my area, delete all wordpress files and just fresh-install 2.04.
Of course, knowing me, that’s probably not the right way to do it. This flabbergasts me.
Sorry I couldn’t help more!
Doodlebee, that’d be spot-on the thing to do I think.
Get a fresh zip and start over.
Save wp-config.php and anything under themes that you’re in love with first, I reckon.
I too am at a loss.
Thread Starter
ronams
(@ronams)
I have done this countless times. Cleared all out of my site and reuploaded a fresh upgrade set of files. I then upload a new wp-config.php and .htaccess. No change.
I don’t know what else to do.
Ronams – I know this is crazy, but how would you feel if someone else gave it a try?
If you email me (you can go through my form at http://www.anekostudios.com/contact.php) let me know if you’d be interested in having me give it a go.
And hawkins…
1.5 to 2.04? Have you upgraded to versions in between? I can’t remember which ones first – but you can’t just go straight from 1.5 to s.04 – you have to upgrade slowly with other versions first. You didn’t say if you had gone that route or not, so I’m just putting it out there, just in case!
Anything interesting showing up in apache error logs?
For some reason either WordPress or Apache is sending a redirect header (I would guess it is in Apache). It could be coming from your parent directory, but here is a raw dump of the packets going to your blog site:
GET /blog HTTP/1.1
Accept: */*
Accept-Language: en-us
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; Maxthon; .NET CLR 2.0.50727; .NET CLR 1.1.4322; InfoPath.1)
Host: http://www.strategy2execution.com
Connection: Keep-Alive
HTTP/1.1 301 Moved Permanently
Date: Wed, 30 Aug 2006 18:40:58 GMT
Server: Apache/1.3.33 (Unix) ApacheJServ/1.1.2 PHP/4.3.10 FrontPage/5.0.2.2635 Rewrit/1.1a
Location: http://h2roadmap.com/blog/
Keep-Alive: timeout=15, max=96
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html; charset=iso-8859-1
e6
<!DOCTYPE HTML PUBLIC “-//IETF//DTD HTML 2.0//EN”>
<HTML><HEAD>
<TITLE>301 Moved Permanently</TITLE>
</HEAD><BODY>
<H1>Moved Permanently</H1>
The document has moved <A HREF=”http://h2roadmap.com/blog/”>here</A>.<P>
</BODY></HTML>
0
Thread Starter
ronams
(@ronams)
I don’t think the re-direct is the problem, but I’m desparate and hope that it could be.
I have more than one url pointing at the same site.
During my 2.0.3 blog days, either http://www.strategy2execution.com/blog or http://www.h2roadmap.com/blog would go to the blog correctly and all would work. http://www.h2roadmap.com is the base url, but the name http://www.strategy2execution.com is the actual focus of the blog’s material.
I continue to try both when I try to get to the blog and both fail. Today I changed the entry in the wp-admin options to http://www.h2roadmap.com/blog to ensure no potential confusion. But it hasn’t had any impact.
Just out of curiosity, have you tried to disable your gzip compression in WordPress? There is a possibility something screwy is happening in there (I have seen it happen on other platforms before).
Something else to try is go into wp-blog-header.php and start working down and add the following in the file:
die(“test point”);
See if when you go to the site you get the test point. If you do then move it down further in the code and see where you stop getting it at. It could be something causing the crash when wp() is initialized, but this will give a better idea of where the problem is occuring.
Thread Starter
ronams
(@ronams)
Tried you die(“Test Point”) in wp-blog-header.php . I’ll mark with **** where it showed up and #### where it just went to page cannot be displayed. In some cases it was in the middle of an if statement and gave a different error as some unexpected stuff. Does this help?
<?php
****
if (! isset($wp_did_header)):
if ( !file_exists( dirname(__FILE__) . ‘/wp-config.php’) ) {
if ( strstr( $_SERVER[‘PHP_SELF’], ‘wp-admin’) ) $path = ”;
****
else $path = ‘wp-admin/’;
#####
die(“There doesn’t seem to be a wp-config.php file. I need this before we can get started. Need more help? We got it. You can create a wp-config.php file through a web interface, but this doesn’t work for all server setups. The safest way is to manually create the file.”);
Thread Starter
ronams
(@ronams)
I dont’ know how to look at or what is “apache error logs”. I don’t know where any error logs are that could help.
I also don’t know how to do any gzip compression changes. Please point where / how to change.
Thanks again for the help.
