mkaresh
Forum Replies Created
-
Okay, found this. The first one would have done it.
For table wp_new_options
wp_user_roles becomes wp_new_user_rolesFor table wp_new_usermeta
wp_capabilities becomes wp_new_capabilitieswp_user_level becomes wp_new_user_level
wp_autosave_draft_ids becomes wp_new_autosave_draft_ids
In my case the problem was that I had renamed my tables and changed the prefix in wp_config. Apparently I needed to change something else in addition to these things.
Forum: Fixing WordPress
In reply to: Getting WP to run on my development machineWell, I gave up trying to get WordPress to work on my notebook. Transferred the files to the server, and 2.8.4 works fine there.
Something is not adapting well to running on “localhost.”
Forum: Fixing WordPress
In reply to: Getting WP to run on my development machineNot using anything like XAMP. Just a standard Apache install on a Windows machine.
The directoryindex isn’t the problem. Even if I directly type http://localhost/blog/index.php it defaults to the directory. And yet the entire admin area works perfectly, so the problem is only when trying to view the blog itself. When this happens, it appears that a file like blog?p=4 is not being found.
Forum: Fixing WordPress
In reply to: Getting WP to run on my development machineThe bit that was unclear:
I’m trying to install WP on my laptop, to get all of the formatting correct before I upgrade WP on the server.
So Apache is defaulting to index.html when a file isn’t found.
So real question: why aren’t these files being found? What could cause WP files to not be found, when they are on the hard drive in the blog directory?
Forum: Fixing WordPress
In reply to: Getting WP to run on my development machineNo suggestions?
Some additional info: no plug-ins except akismet, and the problem is the same even if I switch to a default theme.
Forum: Fixing WordPress
In reply to: Getting WP to run on my development machineUpdate: the admin area is now functional. The blog itself, still not.