Martin Robbins

ACF plugin stores data either as WordPress post-meta(= custom field) or WordPress options. A lot of folks do say, compared to some super-robust data structures, they are less than optimum. But this is the WordPress way, options, posts and post-meta , users and user-meta, are the primary data structures.

The way I understand, some acf query functions are resource heavy, mostly just wrappers around the underlying native WordPress functions for simplicity to non-programmers. I typically use instead the native functions.

You are welcome. Although I don’t understand completely your English, I would suggest the following references:

https://codex.wordpress.org/Moving_WordPress

http://codex.wordpress.org/Changing_The_Site_URL

Good Luck

You are welcome, It seemed to load fairly fast for me. Often the load speed is more about the host and the browser’s connection to the host than it is about the WordPress.

You are welcome, seems to be a question for bluehost. Have you asked them?

You are welcome, no apology needed, accepted nonetheless. To be as clear as possible:

I had used the /wp-login earlier in the process of previous work and it had worked.

This is highly unlikely.

my admin page had to be accessed by: http://im.mikediane.com/wp/wp-admin

Yes, because the install is in /wp/ the admin must be addressed there, either as /wp/wp-admin/ or /wp/wp-login.php

I didn’t understand was why my site could be addressed at: http://im.mikediane.com

This is possible because we put /index.php in the root and properly edited it. EDITED after I wrote to the end: I take that back it appears you have deleted the /index.php @pwdiane YOU ARE ON THE WRONG TRACK AS OF 22:09 EDT You better stop messing with it right now. Or are you just messing with me?

However, because we could not modify the site_url option without breaking everything, any further clicks into the site first addressed at the root would necessarily include the /wp/ installation path. It’s no big deal, that’s the url previously you have published, right?

Further the site is addressable at /wp/ because that is where we rebuilt it and is present /wp/index.php

I got really frightened when you said “The caveat would be that your site likely will break if you ever switch themes or allow update theme twentyfifteen to a new version.”

This is really no big deal. You like TwentyFifteen? don’t switch! Want to upgrade its version? First keep a copy of the functions.php and put lines 2 and 3 into the new functions.php after the upgrade is done. Better yet, save a local copy of functions.php right now, just in case it auto-upgrades without your knowledge or consent.

see if I can get it all back and running on the /wp subdirectory

As far as I know, your site is up and running at /wp/ just as it always was before you started the other topic.

When you mark it resolved (the other topic) you acknowledge no unresolved issues. So by mentioning unresolved issues here you have gotten off to a really bad start.

I can only access my admin page by using, http:im.mikediane.com/wp/wp-admin. (/wp/wp-login returns a 404 error)

This is the only well-defined issue you stated here. And the reply by @claytonjames is spot on. Vaild dashboard login url is http://im.mikediane.com/wp/wp-login.php or http://im.mikediane.com/wp/wp-admin/ and NOT the one you tried that returned a 404. He solved the problem you stated, you should mark this topic resolved.

Perhaps my suggestion for you to start this topic was in error. Everything we did is there in the other topic, and more, including the answer to your last previous question here, which indicates limited understanding of what all we did throughout almost 200 posts in that topic. Bottom line over there, we solved the problem you stated in the very first post, hence it is resolved.

If you want to attempt again whatever your objective that caused your problem there in the first place, I’m going to suggest at this time for you to spend some time and study that topic carefully all the way through yourself, instead of expecting someone else to do it.

Good Luck

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');

___

Ok try it without the 2 leading forward slashes on line 3

<?php
update_option('siteurl','http://im.mikediane.com');
update_option('home','http://im.mikediane.com/wp');