ronnicholls

Resolved

All sorted. Needed to put the wordpress directory in the statements for WP_HOME and WP_SITEURL e.g.

define(‘WP_HOME’,’https://localhost:8888/YourProjectDirectory’);

Thanks @threadi for responding, and giving me the inspiration to continue debugging. Was getting close to jacking it in.

From another forum, I found that by adding the following to the foot of wp-config, that I now get a connection, but it is not formatted. More of an outline. Also I get 404 error when trying to access wp-admin ????

What WP subdirectories should I keep from production site, and which from a clean WP install (if any). I think this is what I am struggling with

/** Sets up WordPress vars and included files. */ define(‘WP_CACHE’, true); $currenthost = $_SERVER[‘HTTP_HOST’]; $mypos = strpos($currenthost, ‘localhost’); if ($mypos === false) { define(‘WP_HOME’,’https://YOURSITE.com’); define(‘WP_SITEURL’,’https://YOURSITE.com’); } else { define(‘WP_HOME’,’https://localhost:8888′); define(‘WP_SITEURL’,’https://localhost:8888′); }

Thanks. Will give it a go tomorrow

root has global prieveledges on all databases but I agree that this seems to be the issue . . . . .

Do you have to perform a WP install for a new database? I was rather thinking that you could just use your production directories (and change wp-config). I ask this becasue if I do perform a WP install, it creates a database as part of the install (with nothing in it so to speak).

$table_prefix = ‘wp_’;

Thanks for response. This is how it is in production config. It is also how it is in dummy wordpress install on localhost so I left it alone. Seems that it just doesn’t want to recognise my imported database. I am using root/root as user credentials as production creds don’t work anyway