joecwhite
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: moving servers and upgrading versions breaks permalinksOK, finally found it. After rereading Using Permalinks, I found this relevant section:
Requirements:
Apache web server with the mod_rewrite module installed
In WordPress’s home directory,
The FollowSymLinks option enabled
FileInfo directives allowed (e.g. AllowOverride FileInfo, AllowOverride All)
An .htaccess file (if this file is missing, WordPress will try to create it when you activate “pretty” permalinks)
If you want WordPress to update the .htaccess file automatically, WordPress will need write access to the file.I went in and checked the httpd.conf file, and, lo and behold, FileInfo directives were not allowed. I changed it to
AllowOverride FileInfo
, and now my permalinks are back to pretty!Thanks for all the help!
Forum: Fixing WordPress
In reply to: moving servers and upgrading versions breaks permalinksmust be some PHP config issue somewhere; tried creating a brand-new 2.5 install, and got the same problem when I switch it to pretty permalinks.
Forum: Fixing WordPress
In reply to: moving servers and upgrading versions breaks permalinksthe mbscript extension of php was not installed; got them to install it, but still having the same issue.
Forum: Installing WordPress
In reply to: Fresh Install of WP 2.5 gives Blank Page of domainor maybe the index.php file has an incorrect entry for the location of wp-blog-header.php?
Forum: Fixing WordPress
In reply to: moving servers and upgrading versions breaks permalinksExported old 2.0.9 DB, backed up and deleted current DB, imported the 2.0.9 and ran the upgrade script, get the same result. (BTW, it appears the upgrade script changes the structure of the DB. The 2.0.9 db before upgrade has the following tables:
wp_categories
wp_comments
wp_linkcategories
wp_links
wp_options
wp_post2cat
wp_postmeta
wp_posts
wp_usermeta
wp_userswhereas the upgraded version of the same DB has these:
wp_comments
wp_links
wp_options
wp_postmeta
wp_posts
wp_terms
wp_term_relationships
wp_term_taxonomy
wp_usermeta
wp_userswhich explains why those errors appeared on the forced upgrade…they had already been converted.
Again, permalinks work fine using the default permalink structure of, but if I try to change to Day and Name
to maintain compatibility with external links to my posts, it fails.
Forum: Fixing WordPress
In reply to: moving servers and upgrading versions breaks permalinksForced the upgrade; got this result:
WordPress database error: [Table ‘joeblog.wp_categories’ doesn’t exist]
SELECT * FROM wp_categories ORDER BY cat_IDWordPress database error: [Table ‘joeblog.wp_post2cat’ doesn’t exist]
SELECT post_id, category_id FROM wp_post2cat GROUP BY post_id, category_idWordPress database error: [Table ‘joeblog.wp_linkcategories’ doesn’t exist]
SELECT cat_id, cat_name FROM wp_linkcategoriesUpgrade Complete
Your WordPress database has been successfully upgraded!
all three did exist in the version I brought over. I can try to re-export from the old blog and re-import it on the new server.
Forum: Fixing WordPress
In reply to: moving servers and upgrading versions breaks permalinksPartial success: I had switched permalink types before, but saved it and then went back to the ‘month and day’ version (which is what I had been using). If I leave it at default, it works! But then all the old links to posts on my blog, both internal and external, will be broken.
It seems like there must be one place where I’ve got a munged setting, but no clue where it is.
Gentlemen, I greatly appreciate y’all helping me with this…thank you!
Forum: Fixing WordPress
In reply to: moving servers and upgrading versions breaks permalinkstried moving it up a level, so that it resides at at [my www directory]/wordpress
no change.
Forum: Fixing WordPress
In reply to: moving servers and upgrading versions breaks permalinksit is
Forum: Fixing WordPress
In reply to: moving servers and upgrading versions breaks permalinksEverything appears in order; located at the home directory of the blog (whereas wordpress itself is in cgi/wordpress):
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule># END WordPress