Azurite

Hi there,
Thanks for getting back to me so quickly!
So the way I tested it was having a user create an account with sub-site A. Then, when they visit sub-site B, they can simply log-in, but not (per the usual WordPress Multisite behavior) be redirected back to sub-site A. The problem is that though they can login, they don’t show up as a Member or User of sub-site B.

Perhaps the issue is with the fact that I’m using another plugin for handling membership and complex registration forms (UserPro) which has front-end registration? This means that when the user logs in, they’re not actually going to the admin dashboard.

So it’s not a matter of visibility– the user has no problem seeing any of the content I want them to on sub-sites A or B, but I want them to show up as a User (backend) and a Member (front-end). The process of logging in is what I would like to trigger them showing up as “having subscriber access” to sub-sites A and B, vs. just “view access” of any other sites on the network (e.g. C, D, etc).

It doesn’t look like this has been fixed yet. I just downloaded the latest version (after having to deactivate the plugin from FTP because it added PHP output to my login screen and wouldn’t allow me to log in to the admin panel) and it’s still giving output on every page, frontend and back. ??

Well, I tried it– I was able to find the Disable Caching for Logged In Users for W3TC’s Performance for the Network (Performance > Page Cache). I also emptied all the caches, but nothing has changed. I verified the widgets are still listed as being in the right place in Appearances > Widget. I also checked the Settings > Reading to verify my front page was set up as the Posts page.

I also checked in another browser (that I don’t use often), but still no luck.

Yes! I actually didn’t think of that. I have W3 Total Cache and WP Hummingbird. However, I have Minify turned off for W3 Total Cache since Hummingbird takes care of that.

Any suggestions for how I can use them and still get my plugin’s widgets to show up?

• This reply was modified 8 years, 4 months ago by Azurite.

That’s the thing– I didn’t create these aliases myself! (At least, not that I remember.) When I go to the cPanel for Email Forwarders, I can create a new Email Forwarder, but my options are limited to my existing subdomains and the aliases– so I imagine if I delete one or more of these aliases, I won’t be able to create the email for them.

I had told my hosting support when I contacted them that I didn’t need the email addresses to be “real,” just exist as forwarders, but I suppose it might be a limitation that aliases have to be created for them to exist as forwarders, too.

I will look into a third-party SMTP plugin to see if it can do what I need… honestly, it was all to make sure Contact Form 7 worked properly. I was concerned that deleting the aliases would make the site completely inaccessible, but if it’s just a matter of waiting for the 72 hours to pass, I might just try it.

The main reason why I wanted to get rid of the aliases is because my hosting plan limits me to 4 , and I don’t see any reason to be using those two if I don’t want to. I have other things pointed to my hosting using up the other two, but I’d like at least one of those two freed up if I can!

I didn’t manually create blueeyes.seventh-star.net or sailormoon.seventh-star.net as subdomains; that’s why neither of them are listed under “subdomains,” but the wildcard is (along with a few other, non-WordPress subdomains).

Yes, I’m pretty sure I have wildcard subdomains set up, because it was the only option for me when setting up multisite since I already had existing subdomains and such (I think). When I go to my cPanel, I have the *.seventh-star.net set up as a “subdomain,” and it’s not redirected.

As previously mentioned, the two sites are the only ones that have aliases in cPanel, but removing them makes them inaccessible. Neither of them redirect anywhere.

They also show up as available to edit for DNS Zone Editing, and I wonder if it’s because I needed them to “exist” so that I could invent the fake email addresses [email protected] (as an example) for Contact Form 7’s validation.

The reason why I have Domain Mapping and Multi-Domains (both by WPMU Dev) is because my multisite install is also home to two other domains (not seventh-star.net). Just based off the descriptions, I don’t think their functions overlap, but that’s hardly a professional opinion.

Neither domain shows up under Tools > Domain Mapping for the individual site or under Settings > Domain Mapping for the Network; they didn’t exist on other sites before the WordPress install.

Any help would be appreciated, because I feel like all I can do is delete the aliases and then not be able to access the site(s) again.

Fanworks in general can cover a lot of ground:

• Fanart (could include regular art, but also specific kinds, like wallpaper, icons/avatars, signatures, banners, buttons, etc.) <– Fanart is a kind of graphic though, so it could feasibly be covered in that.
• Podfic
• Videos (including AMVs, edits, etc.)

There can also be things like quizzes and articles.

Okay, I’m pretty sure it works on multisite, because the errors I am seeing match up with the sort in the instructions for common troubleshooting, about a line being “eval’d” on a certain line. I’ll troubleshoot the PHP part elsewhere…but is there anything useful to know about how the plugin can include files from elsewhere?

Oh, I know. I’ve been using the shortcode. I’m trying your “test” method first, to see if the issue I am having is with the PHP I’m trying to insert by putting it into an independent test.php file, and I’m trying to debug that.

Right now it’s saying

Parse error: syntax error, unexpected T_ENCAPSED_AND_WHITESPACE, expecting T_STRING or T_VARIABLE or T_NUM_STRING in /home/username/public_html/wp-content/themes/twentythirteen/test.php on line 4

and I’m trying to figure out what’s wrong with that (since there doesn’t appear to be any whitespace)….

Hi,
Yes, I mean a WordPress installation that runs on more than one site. Or, a WordPress Network, if that’s the more “official” term (I see them both used in the Codex).

From what I can tell, it SEEMS to be working, in the sense that it’s replacing my <?php and ?> code properly, but I’m still working on some errors to see what’s going on–if it’s my PHP or something else.

I did have the following line in my .htaccess

RewriteRule ^indigo$ "http\:\/\/www\.meredithsweet\.com\/" [R=301,L]

which I tried removing, since I used to utilize a subdomain with a redirect (indigo.seventh-star.net to meredithsweet.com), and since I was able to get this plugin and change meredithsweet.com to be a parked domain, I didn’t do that anymore…

But it doesn’t work.

And someone accessing the website from a non-allowed IP address should see my 403 Forbidden error page.

How do I figure out where the error is coming from? My host seems to think it originates with this plugin somehow.

Okay, I noticed something odd:

My normal browser, Safari, started working again without the infinite redirects even with the domain-mapping.php in the regular plugins folder. But I started using a different browser today, Chrome, and now I get the infinite redirects again.

I have my .htaccess file set so that only certain IP ranges will be allowed to access wp-login.php, but it hasn’t changed since long before I installed the Domain Mapping plugin. How can I get it so it won’t infinitely redirect…or else figure out WHERE the redirect is coming from?

I removed the code that the Tom McFarlin solution suggested. The redirect isn’t happening anymore, so I’m wondering if it’s just because I moved the domain-mapping.php file from mu-plugins and into the normal plugins folder.

Is that safe?

I may have fixed the issue with a workaround that I am not sure is a good idea. I removed the plugin domain-mapping.php from the mu-plugins folder and put it into the normal plugins folder and activated it.

Now that I’m able to get into the Dashboard, I can see my settings, which say:

• https://meredithsweet.com
• https://www.meredithsweet.com
• https://meredithsweet.com

Where the one with the www is selected as the Primary. None of them have the delete option.

I contacted my host about this and they supplied me with this link: https://tommcfarlin.com/resolving-the-wordpress-multisite-redirect-loop/

It basically says to add:

define('ADMIN_COOKIE_PATH', '/');
define('COOKIE_DOMAIN', '');
define('COOKIEPATH', '');
define('SITECOOKIEPATH', '');

to wp-config.php, but when I did that, the define(‘COOKIE_DOMAIN’, ”); line gave me an error, so I removed it.

Not sure how necessary the other lines are or if I should keep them.