Latest BPS version multi-site issue?

Just another issue (which may be of my own making?).

Noticed the subsite of my multi-site network (there are only 2 sites) – images were not displaying either on the front-end or back-end (in posts or media gallery).

Upon going through htaccess file (seems to be the main place to look for these types of issues) – and comparing files from 51.4 and 51.6, I noticed that these two lines were missing from the new 51.6 root htaccess file:

# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

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

I’m not sure if this is by design – or if they should have been in Custom Code? (they weren’t) but after adding these back in, it seemed to fix the image problem.

I’ve now added these two lines to Custom Code WP Rewrite Loop Start in case they are lost again. (hoping this would be the correct place to put them?)

Does this make sense? Thanks

The WP Toolbar menu items (nodes) display in BPS plugin pages is a new BPS option setting that you can control on the UI|UX|Theme Skin | Processing Spinner | WP Toolbar page.

BPS Whats New tab page info:

New Feature|Option: WP Toolbar Functionality In BPS Plugin Pages

This option affects the WP Toolbar in BPS plugin pages ONLY and does not affect the WP Toolbar anywhere else on your site. WP Toolbar additional menu items (nodes) added by other plugins and themes can cause problems for BPS when the WP Toolbar is loaded in BPS plugin pages. This option allows you to load only the default WP Toolbar without any additional menu items (nodes) loading/displayed on BPS plugin pages or to load the WP Toolbar with any/all other menu items (nodes) that have been added by other plugins and themes.

UI Theme Skin|Processing Spinner|WP Toolbar Read Me help button info:

WP Toolbar Functionality In BPS Plugin Pages:
This option affects the WP Toolbar in BPS plugin pages ONLY and does not affect the WP Toolbar anywhere else on your site. WP Toolbar additional menu items (nodes) added by other plugins and themes can cause problems for BPS when the WP Toolbar is loaded in BPS plugin pages. This option allows you to load only the default WP Toolbar without any additional menu items (nodes) loading/displayed on BPS plugin pages or to load the WP Toolbar with any/all other menu items (nodes) that have been added by other plugins and themes. The default setting is: Load Only The Default WP Toolbar (without loading any additional menu items (nodes) from other plugins or themes). If the BPS Processing Spinner is not working/displaying correctly then set this option to the default setting: Load Only The Default WP Toolbar.

BPS literally uses WordPress’ code that creates Network/Multisite htaccess code. We have “borrowed” it and are using it in BPS. ?? This ensures that the htaccess code created for your site is the correct htaccess code.

Go to your Network Admin panel >>> Settings >>> Network Setup and post the code that you see under: “2. Add the following to your .htaccess file in /home/xxxxx/, replacing other WordPress rules:”

I do see some additional WP Toolbar Default nodes for Network/Multisite sites that need to be added. These will be added in the next BPS version.

The Default WP Toolbar nodes have been added and tested in BPS .51.7 for these Network/Multisite site types: standard: subdirectory and subdomain and GWIOD: subdirectory and subdomain. We have a few more things to complete so BPS .51.7 will probably be released in 6 days.

Hi

Thanks for looking into this. Clearly, my mistake – should have read about the extra feature (UI Theme skin….). Sorry.

As for your suggestion to look in Network Admin panel >>> Settings >>> Network Setup – I don’t have this option? I thought that this was only during initial network setup? I have Network>>>settings which displays operational settings – but not the rules for htaccess file?

I have to admit that as each new version of BPS comes out with more features..I’m starting to get a little concerned. Extra features can mean extra problems…and a larger plugin footprint.

I find that maintenance mode doesn’t work for me already (kills my site and I have to restore previous index files – so I don’t use it).

Actually thanks for pointing out the missing Network Toolbar nodes which definitely needed to be added. ??

To get the Network Setup page to display add this code with your other Network code in your wp-config.php file: define('WP_ALLOW_MULTISITE', true);

Actually one of the primary focuses in a recent BPS version was to reduce the overall footprint|impact, but BPS was already a very light resource usage plugin so there was not too much optimization and footprint reduction work needed in BPS free. So no need to be concerned. Anything that we create focuses on the most important things: security, performance, resource usage, ease of use.

Maintenance Mode can be tricky on some Network/Multisite sites and if you are using a non-conventional folder structure or doing something that is not standard then MMode may not work right out of the box.

We have a whacky Network/Multisite test site setup that we use to test to break BPS. That Network test site is a subdirectory Network/Multisite site installed in a true subdomain folder with DNS pointing to the subdomain installed in a subdirectory of another unrelated single site WordPress installation. Lots of whacky problems occur on that test site and that test site requires different root htaccess code then the code that WordPress creates or that BPS creates, which are the same thing since BPS uses the exact WordPress code for creating the Network/Multisite root htaccess code.

subdomain.example.com
folder structure: /example.com/subdomain
DNS A record pointing to /subdomain

That may also be what is occurring with your particular Network/Multisite. I believe WordPress used to have a disclaimer for Network/Multisite htaccess code to the effect of “works in most cases, but may not work in all cases”.

You may need to have both of these constants in your wp-config.php file to get the Network Setup page to display:

define('WP_ALLOW_MULTISITE', true);
define('MULTISITE', true);

My network config is not whacky – root folder install – subdirectory – nothing special (I don’t think). Your test set-up sounds bizarre (and worse case scenario!)

You were correct – adding the extra define(‘WP_ALLOW_MULTISITE’, true); enabled the network setup option. Here is my htaccess code presented in network setup:

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]

# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [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).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]

I was missing everything after RewriteRule ^index\.php$ – [L] for some reason after updating from 51.4 to 51.6? I think it must have been a copy/paste issue in custom code when adding the non-www to www entry to the loop.

Anyway, it’s all sorted now – and I have created a new entry in custom code (I’ve added the below entry to the loop after RewriteBase /)
RewriteCond %{HTTP_HOST} ^mydomain\.co.uk$ [NC]
RewriteRule ^(.*)$ https://www.mydomain.co.uk/$1 [R=301,L]
and created a new secure htaccess file. It all looks correct now.

Perhaps maintenance mode might work now?…but I’m too scared to try it!
If there is no other input then please mark this thread as resolved.

Thanks again for your efforts.

Your test set-up sounds bizarre (and worse case scenario!)

Exactly. Prepare for the worst case scenario so that when it happens you are already prepared for it. ??

I think it must have been a copy/paste issue in custom code when adding the non-www to www entry to the loop.

DOH! Mystery solved. I should have asked you that question first – if you had added any custom code in the CUSTOM CODE WP REWRITE LOOP START: www/non-www http/https Rewrite code here text box. The way BPS Custom Code works is BPS will create standard htaccess code UNLESS you have added custom code to a Custom Code text box and then that code will be used|created instead of the default standard code.

All working well now – thanks for your patience.