There’s maybe some leftover junk in the root:
How many .php files in the root?
Is one of them /wp-config.php ?
List the files not .php each on its own line please.
___
Or maybe some extra lines in /wp/wp-config.php
Show me the bottom part starting on about line 64 like below. Be sure not to show me(everybody) any database credentials usually but not necessarily near the top and down to line 62.
here is typical starting at line 64:
/**
* For developers: WordPress debugging mode.
*
* Change this to true to enable the display of notices during development.
* It is strongly recommended that plugin and theme developers use WP_DEBUG
* in their development environments.
*/
define('WP_DEBUG', false);
/* That's all, stop editing! Happy blogging. */
/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
define('ABSPATH', dirname(__FILE__) . '/');
/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');
___
I’m going to have to go for lunch again. My husband is a good cook and thrilled that I’m working on this site and problem, but he doesn’t want to eat his delicious cooking alone.
If you have some suggestions, I’ll check back in a while. If not, I’ll try to contact you again tomorrow about the same time as today.
Thank you,
Diane
In the root, there are 14 .php files.
There is no wp-config.php, only wp-config-sample.php
The files that are not php are:
.htaccess
error log
index.html
license.txt
readme.html
Then, wp/wp-config.php, from line 64:
/**
* For developers: WordPress debugging mode.
*
* Change this to true to enable the display of notices during development.
* It is strongly recommended that plugin and theme developers use WP_DEBUG
* in their development environments.
*/
define('WP_DEBUG', false);
/* That's all, stop editing! Happy blogging. */
/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
define('ABSPATH', dirname(__FILE__) . '/');
/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');
In post 181 you wrote:
Everything is back up and running.
You reasonably should at this point mark the topic resolved and put it to rest. The caveat would be that your site likely will break if you ever switch themes or allow update theme twentyfifteen to a new version.
To clear the caveat and attempt get rid of the /wp/ url suffix, you might create a new topic in the how-to forum. And reference this topic. And accept no generic responses that obviously have not read this topic.
If you do mark this topic resolved, I might post here some further ideas how to proceed. If I do post here again it will be my last post in the topic. I need to move on and attempt help some others.
You are welcome for the many thanks throughout. And I thank you for a valuable learning/teaching experience for myself. There is a website listed under my member profile.
I will proceed as you suggested. You have been a tremendous help and I’d be so pleased to have you more available to the many others who are needing your expertise.
God bless!