Does this plugin seamlessly deal with this, either:
1) in the FREE version, creating:
siteurl: https://example.com/staging/wp
home: https://example.com/staging
or
2) in the PRO version, creating:
siteurl: https://staging.example.com/wp
home: https://staging.example.com/

Thanks.

I have no idea why or how this is happening and no idea where to start. Does anyone have an ideas?

I’m getting a bit confused over whether my urls in links etc have changed or not!

This is the scenario:
1. I have a pre-existing install in it’s own folder/directory with the site url and wp home url the same = https://mysite.com/myblog
2. I’ve just changed it using the guidelines for GWIOD “Using a pre-existing subdirectory install’; so now my settings are site url = https://mysite.com and wp home url = https://mysite.com/myblog
3. All seems to be working properly.
4. ?? need to change/update urls??

So now do I need to run the Velvet Blues url updater to change all my urls from the old url to the new one? Or are they the same, just appear different in a browser url?

Appreciate any help on this.

Many thanks, j

The second time i enabled the multisite it skipped the part where asks for the network name and other things, i think the restore of the backup didn’t erased this informations, and god knows what else…

The exact moment when it brokes it’s when i paste the provided lines in the wp-config.php and .htaccess files and click on “login”.

suggestions on where to investigate?

here is my .htaccess (in the root dir):

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) wordpress/$2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ wordpress/$2 [L]
RewriteRule . index.php [L]
</IfModule>

# END WordPress

wp-config.php(just the relevant part, after the db connection configuration, which is 100% correct):

define('WP_DEBUG', false);

define('WP_HOME','https://mysite.com/wordpress');
define('WP_SITEURL','https://mysite.com/');

define( 'WP_ALLOW_MULTISITE', true );

define('MULTISITE', true);
define('SUBDOMAIN_INSTALL', false);
define('DOMAIN_CURRENT_SITE', 'mysite.com');
define('PATH_CURRENT_SITE', '/');
define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);

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

define ('FS_METHOD', 'direct');

//--- disable auto upgrade
define( 'AUTOMATIC_UPDATER_DISABLED', true );

index.php (in the root dir):

<?php
/**
 * Front to the WordPress application. This file doesn't do anything, but loads
 * wp-blog-header.php which does and tells WordPress to load the theme.
 *
 * @package WordPress
 */

/**
 * Tells WordPress to load the WordPress theme and output it.
 *
 * @var bool
 */
define('WP_USE_THEMES', true);

/** Loads the WordPress Environment and Template */
require( dirname( __FILE__ ) . '/wordpress/wp-blog-header.php' );

and this are the first lines of functions.php:

<?php
update_option('siteurl','https://mysite.com/');
update_option('home','https://mysite.com/wordpress');

I already have WordPress installed in its own folder with a running site : www.sagl.net/2016

I used this thread to solve my problem without sucess : https://codex.www.ads-software.com/Giving_WordPress_Its_Own_Directory
I copied both index.php and change the /… + copy the .htaccess

I tried to upload the wordpress files into the root under www.
it doesn’t work neither because some wpinclude/pomo/entry.php doesn’t load on line 61 : public function Translation_Entry( $args = array() ) {

I don’t know what to do anymore to redirect this folder to point out to the root.

Can some one help ?

Marc

Siteworks well in subdirectory.

Now all pages except “Home” work with the root url.
I re-wrote the index.php and htaccess as per instructions.

I’d like it to open with the home page!

https://www.drjanisenzenbacher.com/biography/

https://www.drjanisenzenbacher.com

The blog currently exists with the index.php and htaccess files in the root, while the rest resides in a sub-directory as per the instructions for Using a pre-existing subdirectory install.

But now I need to have the whole thing reside in the root, so moving all the files into the root along with index.php and htaccess.

I’m sure it’s not as simple as just moving all the files into the root (where index.php and htaccess already reside) and changing the “WordPress address (URL)” to reflect the root directory.

Are there any step-by-step instructions on how to do this? I’ve searched but can’t see this particular scenario presented anywhere in the Forums …

On most of my projects I’m using subdirectory install. Basically that means that my website home_url is https://www.example.com, but site_url is https://www.example.com/wordpress.

Recently, I discovered that some of the rules written by AIOWPS plugin into .htaccess file seem not to expect such setup. Namely, all rules that employs %{HTTP_REFERER} have their value set to site_url.

For example, firewall rule that prevents image hotlinking is following: RewriteCond %{HTTP_REFERER} !^https://www.example.com/wordpress [NC]
But as such it evaluates to true also for legitimate visitors of the site, because their referer starts with https://www.example.com, but rarely with https://www.example.com/wordpress (this holds only when they come from admin dashboard).

Can you confirm the issue? I’m using the recent version of the AIOWPS plugin. Would be nice to have it fixed, now I have to remember to manually edit .htaccess file whenever I make changes to AIOWPS or remember which features not to use I think just using home_url instead of site_url for referer check should solve this problem.

Best regards,
?eslav

https://www.ads-software.com/plugins/all-in-one-wp-security-and-firewall/

As the old/original installation resides in the root, would it be best to create the new install in a subfolder or subdomain? Does it matter? In the long run, my Multisite installation will be a subDIRECTORY install.

I have learned my fair-share through Google as most of you and am worried this will be a daunting task, or at least take more time and effort than I originally thought.

What’s the best way to go about this? Is there anything I should be aware of? Are there any sites with resources that I may have missed and would be a good guide? All thoughts are welcome.

https://algiersurgentcare.com/wp/

So what I did was change the site address to https://algiersurgentcare.com, copy the .htaccess file and index.php file into the root directory. Change the line in the index.php file that says: require( dirname(_FILE_ ) – ‘/wp-blog-header.php’ );
to require( dirname(_FILE_ ) – ‘/wp/wp-blog-header.php’ );, update my permalinks.

So after doing the above, absolutely nothing happened. So I contacted the host provider who said I need to change the domain path to point to the wp directory. When I do that I get the white page and I can no longer log into wp admin. I had to place the following 2 lines of code in my theme’s functions.php file to get back to wp-admin:
update_option(‘siteurl’,’https://algiersurgentcare.com/wp’);
update_option(‘home’,’https://algiersurgentcare.com/wp’);
Then remove those 2 lines of code once back in.

So I’m back to square one. The host provider doesn’t have any other suggestions. Does anyone know what I might be doing wrong or anything else I can try?