Make WordPress Core

Opened 8 years ago

Last modified 5 years ago

#36179 new defect (bug)

Password protected post with force_ssl_admin() and domain mapping not working

Reported by: tcdeskwolf's profile tcdeskwolf Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.3.1
Component: Login and Registration Keywords: https dev-feedback
Focuses: multisite Cc:



I'm running a WordPress multisite with "define(FORCE_SSL_ADMIN, true)" and domain mapping.

Our network site is using ssl (where users login to administrate their site). But a domain mapped site is not using ssl, which is working fine.

So, I have a post that is password protected. When I'm on the mapped domain and submit the password protect form, I then get redirected to "wp-login.php?action=postpass" over https and get a security warning.

It should not redirect me to https when I'm on a non-ssl mapped domain.


Change History (7)

#1 @johnbillion
8 years ago

  • Component changed from General to Login and Registration
  • Focuses multisite added
  • Keywords reporter-feedback https added

Thanks for the report, @tcdeskwolf .

  • Which plugin are you using for domain mapping?
  • What exactly is the security warning that you're seeing? Is it due to the site's mapped domain name being requested over HTTPS?
  • If you add the Meta widget to your site's sidebar, do the log in / log out / admin links in the widget work as expected?

#2 @johnbillion
8 years ago

Partially related: #29641

#3 @tcdeskwolf
8 years ago

Thanks for the reply.

  • I'm using the "WordPress MU Domain Mapping" plugin.
  • Yes, it's a web browser security error, due to the site's mapped domain name being requested over HTTPS.
  • I get the same error with the login link in the meta widget - but we don't use remote domain login, so that's not an issue for us.

This ticket was mentioned in Slack in #core-multisite by flixos90. View the logs.

8 years ago

#5 @flixos90
8 years ago

  • Keywords dev-feedback added; reporter-feedback removed

#6 @iamfriendly
8 years ago

Yeah, I can confirm this is an issue, too (same setup here). However, I think it's more of a WPMU Domain Mapping issue than it is a WP Core issue. We have a work-around in place using several filters available in core and in the WPMU plugin to get around this.

It may be possible for core to "do better" here, though, but just want to give a heads up that there are ways around it currently.

#7 @pento
8 years ago

Hi @iamfriendly! Would you mind posting the code you've used to get around it? That may help us get it working correctly in Core. :-)

Note: See TracTickets for help on using tickets.