WebPrezence

Just go to your WordPress administration, and go to Settings >> Permalinks and click save, so your permalinks are updated.

Thanks Mika.

I’m having the 404 / page not found issues for wp-signup.php, but I’m sure that’s related to some wildcard issue or CloudFlare … will figure it out.

Appears to be fixed. I’ll post a fix in here once I figure out what I did to fix things.

But I can say for sure here are some of the things I needed to do:

1. Change all my A records to CNAMEs — in CloudFlare as well as BlueHost’s DNS records.
2. Deactivate WordPress HTTPS plugin (rename it in your host’s file manager of via your FTP client)
3. Change your site URL from https to http (go into your database via phpmyadmin and search in your _options table for it)
4. Go into my WHM (ask your host if you’re not on a VPS), and find the SSL certificate that was creating clashes with another SSL cert. Click Make Primary, so the multisite SSL is the primary SSL
5. Change the name of your WordPress HTTPS plugin back to normal
6. Log into your Multisite and go to your network plugins. Activate WordPress HTTPS.
7. Make sure your WordPress HTTPS is properly configured; for me, personally, I wanted everything SSL’d site-wide, so I just put a / in the textbox where it says Secure Filters >> URL Filters. See the screenshot for the rest of my WordPress HTTPS settings that worked.
8. Change your site name and all that back to https (I had to do it via phpmyadmin, since it doesn’t show up in my General Settings.
9. Forget about all that “mapping” stuff — at least in my case; none of it really applied to what I’m doing.
10. You might need to use the Search and Replace plugin after everything is done to tie up any loose ends. I just did a https://nationalcdp.org and replaced with https://nationalcdp.org and that fixed all the broken images within my WordPress admin.
11. My admin images are still broken for the subdomains, but it’s still easy enough to navigate for now. It’s nothing in my database, so I suppose I’ll just need a reboot or something to figure it out … might be an .htaccess thing; not sure.

That’s about what worked for me. The main thing was that the SSL certificate was clashing with another certificate on a completely separate domain; making the multisite domain the primary SSL domain in my Web Hosting Manager (WHM) was the main thing.

Then it’s just about configuring that WordPress HTTPS issue.

If anyone runs into a similar issue, hit me up and I’ll see if I can share things I learned.
Anyway, that’s what worked for me.

After switching to CNAMEs instead of A-records, and deactivating https (and the WordPress HTTPS: plugin altogether), I’m finally able to see how Multisite is supposed to work, and I’m able to access all of my subdomain dashboards.

I should note that my objective is to have several subdomains — forums.nationalcdp.org, discuss.nationalcdp.org, cases.nationalcdp.org, etc., etc. …. but I’m thinking down the road, and I’d like for defense attorneys to want to list themselves in our directory. But I’d also like for visitors to be able to create their own blog, such as johndoe-lawfirm.nationalcdp.org. Based on this, is it (recommended) to use CNAMEs instead of A-records?

I did purchase a Wildcard SSL certificate, however, and there will be payments, contact forms, etc., so I’d like really the entire site to be SSL’d.

So I’m sure it has something to do with htaccess or the way things are set up in the WordPress HTTPS plugin. So now it’s all about trying to figure out how to get this SSL working properly.

Still working on it!

I guess I’ll delete the A-records and start adding CNAMEs and see if that works better.

I purchased a Wildcard SSL certificate for $100, installed it, and deleted the subdomains, per the BlueHost tech’s suggestion, and added this to my .htacess, per his suggestion:

# .htaccess WildCard SSL + wordpress + subdomain
RewriteEngine on
RewriteCond %{HTTP_HOST} ^forums.nationalcdp.org$
RewriteCond %{REQUEST_URI} !^/
RewriteRule ^(.*)$ /$1
RewriteCond %{HTTP_HOST} ^forums.nationalcdp.org$
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(/)?$ forums/index.php [L]

# .htaccess WildCard SSL + wordpress + subdomain
RewriteEngine on
RewriteCond %{HTTP_HOST} ^dicuss.nationalcdp.org$
RewriteCond %{REQUEST_URI} !^/
RewriteRule ^(.*)$ /$1
RewriteCond %{HTTP_HOST} ^discuss.nationalcdp.org$
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(/)?$ discuss/index.php [L]

# .htaccess WildCard SSL + wordpress + subdomain
RewriteEngine on
RewriteCond %{HTTP_HOST} ^directory.nationalcdp.org$
RewriteCond %{REQUEST_URI} !^/
RewriteRule ^(.*)$ /$1
RewriteCond %{HTTP_HOST} ^directory.nationalcdp.org$
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(/)?$ directory/index.php [L]

# .htaccess WildCard SSL + wordpress + subdomain
RewriteEngine on
RewriteCond %{HTTP_HOST} ^cases.nationalcdp.org$
RewriteCond %{REQUEST_URI} !^/
RewriteRule ^(.*)$ /$1
RewriteCond %{HTTP_HOST} ^cases.nationalcdp.org$
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(/)?$ cases/index.php [L]

# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]

# add a trailing slash to /wp-admin
RewriteRule ^wp-admin$ wp-admin/ [R=301,L]	

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^(wp-(content|admin|includes).*) $1 [L]
RewriteRule ^(.*\.php)$ $1 [L]
RewriteRule . index.php [L]

# END WordPress

Yes I’m at the same crossroads. No Tools >> Network Setup, and when I try to go to the dashboard of any subdomain (“fake subdomain”?), it returns a 404 page not found error.

Any ideas would be greatly appreciated!

I just got off live chat with a BlueHost VPS technician … he basically said as follows:

1. Having 2 IP addresses is appropriate when you’re using CloudFlare; the A-records should still point to 192.163.194.201, which is my Server IP.
2. He told me to ditch all of the subdomains I created (directory, forums, discuss, etc.) and told me to just create the * (wildcard) subdomain in the directory where my WordPress installation is located (/public_html/nationalcdp/). I’m not sure if this is good information, however.
3. He then told me to scrap the separate SSLs, and just purchase a wildcard SSL instead; he said this was his recommendation, although it would require a few extra compexities.

So I’m doing all of those things right now, on the horn with namecheap.com and getting that wildcard SSL.

• I deleted the domain mapping plugin — which included the files sunrise.php and domain-mapping.php, since I don’t think I’m “mapping” any domains, but rather just creating a few subdomains.

Just one question — is there a reason I still don’t have Tools >> Network Setup on my dashboard? Did I do something wrong in setting this up?

Thank you for taking the time to reply, Ipstenu! We’re an anti death-penalty 501(c)(3) coporation and we supply services to indigent prisoners in need of such (as an FYI), but I did read all of your ideas.

I’ll make the changes you’ve hinted at and report back ASAP. I also e-mailed you from your about.com/ page, and on FB, with a different message, although I didn’t see the caveat on your personal page until just now, so perhaps that e-mail/msg should be disregarded.

Yes, https://nationalcdp.org/wp-signup.php?new=sdsdsvcases gives me a 404 not found. I think I need to SSL discuss, directory, and forums … if you’re referring to them as fake subdomains.

I would like the URL to look like directory.nationalcdp.org, discuss.nationalcdp.org, etc. …

Again, thanks, and I’ll report back when I figure out why I’m having two separate IP addresses, and make all the other changes.

I should note that with CloudFlare, you always have 2 separate IP addresses; it’s just the way they operate.

I don’t know this plugin, Karen, but I would assume you just download the image(s) in the plugin, open them up in some image editor (e.g., Photoshop), and change the color of the image(s) in there, then re-upload to your server.

I think a lot of my problem had to do with the installation of the Root Relative URLs plugin.

I went to WordPress general settings, and changed my WordPress Address & Site Address from https:// to https://.

I then just saved my WordPress general permalinks 3 or 4 times, then went into Plugin Organizer’s settings and recreated those permalinks from https://www.example.com to https://www.example.com.

Then, I changed the Ignore URL Protocol to enable, which is I believe how you intended for this function to operate.

From there, I just tested, and disabled a plugin globally that I only want enabled on one page. I went to that page, and things worked.

So I believe all issues are resolved, and working as you intended PO to work with SSL sites.

Thanks, Jeff, and if I can be of any assistance in helping you with anything, just let me know!

Okay, well I’ve finally fixed everything on my end — again, this is an SSL domain. I’m not sure what precisely fixed things, but I’ll explain things I did.

1. Removed the plugin Root Relative URLs.
2. Changed my Settings >> General >> WordPress Address and Site Address from https:// to https://
3. Went to Settings >> Permalinks and resaved my permalinks 3 times (just an arbitrary number, but from working with WordPress over the years, sometimes you have to resave your permalinks more than once)
4. Went to Plugin Organizer >> Settings. Recreated the permalinks — in my case, from https://www.example.com to https://www.example.com
5. Within Plugin Organizer >> Settings, I enabled Ignore URL Protocol. This goes against what had worked for me earlier, but I believe it’s what Jeff had in mind when creating this function in his plugin.
6. Since you’re using it too, here are my WordPress HTTPS settings. Screen Capture 1. Screen Capture 2 (notice, under URL Filters, I have just a / and that’s it). That makes your entire WordPress (and admin) SSL’d, as does having https in your WordPress settings >> General WordPress address & Site address, but this ensures consistency.

From there, I globally disabled a plugin that I wanted globally disabled. I went to the 1 page where I wanted it enabled, cleared my browser cache, and things just worked.

Again, there might be a lot of resaving your permalinks — both in your WordPress settings >> Permalinks and your Plugin Organizer >> Settings >> Recreate Permalinks. You might have to do this more than once or twice.

That’s what worked for me. Let me know how things work out if you try those steps.

Well, certainly that’s why Jeff created this plugin — to boost performance and speed up page load times, avoid conflicts, etc. …

Use phpmyadmin or something in your host’s cPanel, and check to make sure the PO_plugins table exists in your database.

It will be wp_PO_plugins, unless you renamed your database table prefix (recommended), wp_ will be whatever you changed it to.

When in the database, you can use the browse function in phpmyadmin and look for the particular page. There, you can see which plugins are enabled/disabled and perhaps — as a temporary hack — just manually remove / add a plugin within the database table.

Also, go to the settings page and see if there are any messages in red at the top of the screen. If so, follow the instructions in that message.

Lastly, make sure you didn’t disable the Plugin Organizer itself on the page.

I’ll try to think of more solutions while I attempt to fix my own SSL issues.

Jos, when you say it’s “not working on some pages”, do you mean the options aren’t listed on some pages to turn a plugin on or off?

Or do you mean the CSS / Javascript is still loading on other pages when you have a plugin turned off for that particular page?

Or, conversely, certain plugins are not loading on a page where you would like them to load, and have them turned on?

I’ve used Jeff’s plugin for a while now on just about every domain I have, so I might be able to help with some more details.

Hey Jeff.

Yes, I use W3 Total Cache on domains hosted on a VPS, most of the time. Additionally, on some domains, I use CloudFlare … I try to be cautious not to “over-cache”, so to speak, or cache too aggressively.

Strange, though … for some reason, I’m still having issues on this SSL domain. Plugin Organizer is working better than it was w/ the Ignore URL Protocol set to disabled, but with some plugins, it seems to resort to the global settings.

Still haven’t completely figured this one out!

Check that … for whatever reason, when I have Ignore URL Protocol set to disable, that seems to work for now (after doing the steps in he above thread).

However, I had to go to pages and resave the page / purge website cache to get the changes to display properly on the front-end.

This might be because I use the WordPress HTTPS plugin, and there might be some type of thing with that — not a conflict, but some type of reason I should have Enable URL Protocol set to disable.

This is kind of the opposite of what I think you intended for your plugin, Jeff, but perhaps there’s an issue if you’re using WordPress HTTPS.

I’ll follow up in this thread if I figure anything more out, and maybe you can note it in the FAQs or documentation for future reference, as WordPress HTTPS is a pretty popular plugin for SSL’d sites.