Following! I have similar issues after upgrading to 4.2.
Ok so some more details. I ruled out any networked activated plugin. It’s not them or at least, I have other multisite with the same core (akismet/akismet.php, jetpack/jetpack.php, wordpress-mu-domain-mapping/domain_mapping.php) installed which are not having issues. Most of the installs are redirect looping between the main network address and subsite 2. I thought I was on to something until I discovered one looping between the main network address and subsite 12. So no commonalities there. I checked the database all of the following are clean and correct.
- wp_options: options named “siteurl” and “home”
- wp_site
- wp_sitemeta: the option named “siteurl”
- wp_blogs: any entries in the “domains” column that have the old domain name
- wp_#_options: Each sub-site will have sets of tables that correspond to the blog_id in the wp_blogs table. You need to go to the wp_#_options table, where # corresponds to the blog_id, and update the “siteurl” and “home” settings in that table.
Anyone have any other ideas? I’m started to think this might be a bug in core.
I’m experiencing this and am not using ACF Pro, so there may be something else involved here too.
Also having the redirect loop problem after updating to 4.2, and I’m not using ACF Pro.
I discovered that it was happening on one multi-site install, but not another, on the same server. And then even on the problematic installation, it was not happening with every domain. Although it made no sense, and was perhaps just coincidence, deleting the domain mapping record for the problematic domain, and re-creating it, solved the issue. Cookies were also cleared locally.
So, not much troubleshooting help, but it worked for my particular instance.
I tried deleting and re-adding the domain mapping record, but it didn’t help.
Having the same issues – all domain mapping stopped and in my case redirects to cgi apache page.
Anyone? 🙂
I’m having the same problem with WP 4.2.1, even with ACF plugin disabled.
I can confirm that 0.5.4.4 with WP 4.2.1 is compatible. I’ve upgraded and everything went as planned, so I’d suggest a local or dev install and testing to look at your specific domain mapping settings etc
I have the same problem. WordPress 4.2.1 MU and ACF pro.
Please update the ticket. Is not resolved!
Thanks,
Lorenzo
Have you tried checking for Debug errors? On a multi-site installation, you want to have WordPress debugging On for only your IP address. It can be invaluable for tracking down problems like this!
The domain mapping plugin works fine on my sites with WP4.2.1 and WP4.2.2.
@austin Ginder: WPEngine is managed hosting with higher attention to anti-malware security than most hosts. You could have words (partial words) in some URLs that trigger their security system to block the URL. This would be a 403 error but before it ever gets to your account.
Sucuri and iThemes Security and related security plugins might also block some URLs, for the same reasons. Learn how to make exceptions for their security rules, or disable the specific rule.
I first ran into these problems with SiteGround blocking bad User-Agents, such as semalt, archive.org, Baiduspider, MJ12bot (all triggering 403 Forbidden errors); if I remember right I was writing a post comparing zip/tar/7zip etc archive formats and “-archive” was blocked in the URL. Then I had my .htaccess script blocking words like “update” (a SQL command hackers use) and had to make an exception for WordPress URLs such as /wp-admin/network/site-new.php?update=added or /wp-admin/network/update-core.php and the list goes on…
