itsnotrocketsurgery

@wph4 can you explain what you were trying to achieve and what you figured out to make it work?

There are lots of similar questions on here from multisite Super Admins asking for the Super Admin and the sub-site Administrator roles to be separated in Adminimize, and I don’t think Frank has the capacity to develop everything people request as well as support the current features.

It would be useful if you can share your experience – it might help lighten Frank’s load a little if we can all get some workarounds working for now.

Thanks!

Hi

Thanks for moving it to the right place, I wasnt sure where it should go.

I have tried it, or a vacation of it and the site deploys how I need it to but it cant be accessed from the dashboard or front end.

It is set up to work to have sub folders inside a subdomain. I basically want to have the url have a trailing /s/

So it would look like weddings.popupsites.com/s/sitename

Hope that makes sense?

Thanks.

Thanks, sounds good – do you think it’ll be on the cards? ??

If you’ve got any other conceptual hurdles, post them here and I’ll be happy to spitball some possible solutions with you.

• This reply was modified 7 years, 10 months ago by itsnotrocketsurgery.

Thanks Rogier!

I’m just taking a look – is there a license upgrade path from Pro to Multisite Pro?

Many thanks!

All sounds fantastic. Great updates. Can’t wait for the official 2.5.12 ??

Yep, messages appear to be gone now for customers. Thank you!

Yep, no error now. Managed to network activate it and test on both dev and now live server. Working nicely – thanks for the update and fixing those issues!

I see in the network level settings there are still some other settings available in the per-site SSL. Will those be able to be set at the network level at any point, or will they always be reserved for per-site?

Super. Will try and reply.

That sounds like it should do the trick nicely, thanks Rogier. I’ll let you know.

Same with this message:

ALMOST READY TO MIGRATE TO SSL!
NO SCAN COMPLETED YET. BEFORE MIGRATING TO SSL, YOU SHOULD DO A SCAN

Excellent, thanks for the info. I think it would be useful to update the WordPress plugin repository changelog so this is easily visible for all users, but this works.

Thanks!

Ah, I’ve downloaded 2.5.12 from Git Hub and tried installing it on the machine without deactivating first and got a white screen of death when returning to any page on WordPress.

So I reverted, network deactivated the old version of the plugin, replaced it with 2.5.12 and tried network activating again:

Plugin could not be activated because it triggered a fatal error.

Parse error: syntax error, unexpected ‘public’ (T_PUBLIC) in domain.com/wp-content/plugins/really-simple-ssl/class-multisite.php on line 133

Good thinking. The server is PHP 5.4.13.

Hi Rogier,

I’m not particularly familiar with Git Hub, but I’ve downloaded the master as a zip and replaced RSSSL on a dev multisite with this.

The version number appears the same (2.5.11), but I do now have a network SSL config page.

On that page, when I first loaded it, it had “per site” already selected. I changed that to “networkwide” and saved. It took me to the following URL but it’s just a white page:

/wp-admin/network/edit.php?action=rsssl_update_network_settings

I don’t know if it’s done anything, or whether there’s anything I should test, but please let me know if there is anything you recommend. When I return to the network SSL config page, it’s shows “per site” again so I guess it didn’t save the setting successfully. That’s all the feedback I have for now I think.

One question: If this setting did save, and I visited one of the sites on the network and went to Settings > SSL – would it tell me that the setting is enabled network-wide and prevent me from making any tweaks to the settings for that site?

Many thanks!

I’m going Pro!

??