Can't log on to mapped domain dashboard anymore since 4.1.1 update

Have you been able to resolve this issue? If so, can you please respond with the solution.

That’s great. I’m facing the same issue. Do respond if you have been able to get past the issue.

Have you enabled cookies for both the unmapped and mapped domains? Login won’t work with cookies blocked, like that message says.

You should also delete the existing login cookie. (Don’t delete all cookies for the domain(s) which sometimes triggers the browser to block cookies for the domain.) Old cookies may no longer be valid.

Log in to the domain WordPress is installed in (not a mapped domain).

Go to the Domain Mapping Settings page /wp-admin/network/settings.php?page=dm_admin_page , and set them. (If they look right, click and unclick one so there “is a change”) and Save them.

Then do an Upgrade Network (just like you should do for every update of the WordPress core files).

You also have to follow this if you update the version of the Domain Mapping plugin; the list of settings themselves sometimes change.

If you’ve been messing with your web.config, you’ve probably messed it up. This is from a functioning Multi-Site installation, in Subdomain mode. But be very careful; syntax errors or putting this in the wrong place will crash your account; if quotation marks get mangled in this board, you will crash your account. You can not, for example, have two system.webServer tags, so paste the rules inside that section.

<system.webServer>
    <rewrite>
	<rules>
		<clear />

<!-- security stuff taken out -->

<!-- Start of WORDPRESS Rules -->
		<rule name="WordPress Rule 1" stopProcessing="true">
			<match url="^index\.php$" ignoreCase="false" />
			<action type="None" />
		</rule>
		<rule name="WordPress Rule 2" stopProcessing="true">
			<match url="^wp-admin$" ignoreCase="false" />
			<action type="Redirect" url="wp-admin/" redirectType="Permanent" />
		</rule>
		<rule name="WordPress Rule 3" stopProcessing="true">
			<match url="^" ignoreCase="false" />
			<conditions logicalGrouping="MatchAny">
				<add input="{REQUEST_FILENAME}" matchType="IsFile" ignoreCase="false" />
				<add input="{REQUEST_FILENAME}" matchType="IsDirectory" ignoreCase="false" />
			</conditions>
			<action type="None" />
		</rule>
		<rule name="WordPress Rule 4" stopProcessing="true">
			<match url="^(wp-(content|admin|includes).*)" ignoreCase="false" />
			<action type="Rewrite" url="{R:1}" />
		</rule>
		<rule name="WordPress Rule 5" stopProcessing="true">
			<match url="^([_0-9a-zA-Z-]+/)?(.*\.php)$" ignoreCase="false" />
			<action type="Rewrite" url="{R:2}" />
		</rule>
		<rule name="WordPress Rule 6" stopProcessing="true">
			<match url="." ignoreCase="false" />
			<action type="Rewrite" url="index.php" />
		</rule>

<!-- End of WordPress Rules -->

		</rules>

	</rewrite>

<!-- custom error page stuff and MIME Type stuff removed -->

   </system.webServer>

@janr — “installed the WordPress MU Domain Mapping plugin through the WordPress Dashboard, as where I used the “mu-plugin” method the previous time.”

No, you can’t do that. The files have to go in specific locations, that the Dashboard Install Plugin won’t do. Follow my Domain Mapping Plugin installation instructions. (Since the plugin Must be used for your domain mapping to work, I put the appropriate file in the “must use plugin” folder, where it won’t show up in the list of plugins that can be disabled or deleted.)

“after setting up my sites ( http://www.saotn.org as ID 1, and http://www.itfaq.nl as ID 3, after deleting the site once ), I couldn’t log in”

Two errors here.

1) You don’t get to pick the ID of a site when you create it; the ID is assigned. So I guess you are talking about what ID you specify in the Domain Mapping. But you don’t get to pick a number there, either. You specify the actual Site ID of the site you want to map. How do you get the ID? Read my instructions, I cover it step by step. (It’s visible in several URLs.)

2) Mapping “Site ID 1” Does Not Work, and you will get locked out of your entire network. The main site Can Not be mapped; you need the domain name steady to be able to then find out how other sites should get mapped.

“Don’t know why the tables stayed empty though”
That is because you don’t have the mapping plugin installed and/or configured properly. All your database manipulation was unnecessary, and since you were trying to map Site ID 1 it should have gotten you locked out.