BradTheGeek

I found a solution. The site had been moved, breaking urls. Per moving the moving a WP site doc, I found a couple lines that I added to wp-login that fixed the paths in the DB.

Thanks all

wp-config.php is correct. I have even gone so far (see first post) to create, in another folder, a new install of wp and the theme used, with a new database. This works. If I take the new working (albiet with no content) test site and point the wp-config to the old database, it also has the same problems. It is not an authentication error, it is reading some data from the db, eg, the text of the front page is correct, but all links and urls to other resources are incorrect.

This also tests the version problem, as I have tested with the newest version of the theme.

As far as deleting the old db and bringing the tables back.. I tried that too.. I pointed the fresh install to its empty db, made sure it was working with the default content. It was. Then I imported the tables from the DB backup to its db, and viola, broken.

Thanks for the feedback. I don’t think it is htaccess. I never moved the site, but I think it was moved at some point and it is a path issue.

Basic setup is as follows:

Domain 1 (drupal site, working) path = /

Domain 2 (hhbailenforcement) path to site = /bail/wordpress

If you look at the path of a failed image from the resultant HTML in a browser you see something like:
https://hhbailenforcement.com/wordpress/wp-content/themes/business-lite/images/social/default/facebook.png

other resources in the page source have similar paths, IE domain/wordpress

however, the server config already points the site to bail/wordpress so in my mind that means when the HTTP request comes in it is looking for /bail/wordpress/wordpress which is of course incorrect. Not having worked with godaddy hosting before, it seems error logs are turned off, but I have turned them on and will dig through as soon as I can, I expect to see 404’s with incorrect paths like that.

If I am correct, how do I fix that? Can I run some sort of an update SQL to fix the paths or is there a better fix?

Thanks again for all the assistance.