Title: Chris M.'s Replies | WordPress.org --- # Chris M. [ ](https://wordpress.org/support/users/inxilpro/) * [Profile](https://wordpress.org/support/users/inxilpro/) * [Topics Started](https://wordpress.org/support/users/inxilpro/topics/) * [Replies Created](https://wordpress.org/support/users/inxilpro/replies/) * [Reviews Written](https://wordpress.org/support/users/inxilpro/reviews/) * [Topics Replied To](https://wordpress.org/support/users/inxilpro/replied-to/) * [Engagements](https://wordpress.org/support/users/inxilpro/engagements/) * [Favorites](https://wordpress.org/support/users/inxilpro/favorites/) Search replies: ## Forum Replies Created Viewing 8 replies - 1 through 8 (of 8 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WordPress MU Domain Mapping] [Plugin: WordPress MU Domain Mapping] Suggestion: better compatibility with FORCE_SSL_ADMIN](https://wordpress.org/support/topic/plugin-wordpress-mu-domain-mapping-suggestion-better-compatibility-with-force_ssl_admin/) * Thread Starter [Chris M.](https://wordpress.org/support/users/inxilpro/) * (@inxilpro) * [14 years, 12 months ago](https://wordpress.org/support/topic/plugin-wordpress-mu-domain-mapping-suggestion-better-compatibility-with-force_ssl_admin/#post-2296040) * I’ve updated the gist to fix that bug: [https://gist.github.com/1215001](https://gist.github.com/1215001) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WordPress MU Domain Mapping] [Plugin: WordPress MU Domain Mapping] Suggestion: better compatibility with FORCE_SSL_ADMIN](https://wordpress.org/support/topic/plugin-wordpress-mu-domain-mapping-suggestion-better-compatibility-with-force_ssl_admin/) * Thread Starter [Chris M.](https://wordpress.org/support/users/inxilpro/) * (@inxilpro) * [14 years, 12 months ago](https://wordpress.org/support/topic/plugin-wordpress-mu-domain-mapping-suggestion-better-compatibility-with-force_ssl_admin/#post-2296037) * Oops! It seems that in it’s current form, my code messes with all site URLs, not just the current one. Let me see if I can fix that real quick. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WordPress MU Domain Mapping] [Plugin: WordPress MU Domain Mapping] Suggestion: better compatibility with FORCE_SSL_ADMIN](https://wordpress.org/support/topic/plugin-wordpress-mu-domain-mapping-suggestion-better-compatibility-with-force_ssl_admin/) * Thread Starter [Chris M.](https://wordpress.org/support/users/inxilpro/) * (@inxilpro) * [14 years, 12 months ago](https://wordpress.org/support/topic/plugin-wordpress-mu-domain-mapping-suggestion-better-compatibility-with-force_ssl_admin/#post-2296036) * Hmm… here’s a gist of the plugin I’m using to test my code, since the forums don’t handle large blocks of code very well. * [https://gist.github.com/1215001](https://gist.github.com/1215001) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WordPress MU Domain Mapping] [Plugin: WordPress MU Domain Mapping] Domain mapping treats domains as case sensitive](https://wordpress.org/support/topic/plugin-wordpress-mu-domain-mapping-domain-mapping-treats-domains-as-case-sensitive/) * Thread Starter [Chris M.](https://wordpress.org/support/users/inxilpro/) * (@inxilpro) * [15 years ago](https://wordpress.org/support/topic/plugin-wordpress-mu-domain-mapping-domain-mapping-treats-domains-as-case-sensitive/#post-2283439) * It’s worth noting that the second change does not fix the issue for anyone who already has a domain name in the system that’s not all lower case—it might make sense to make both changes for the time-being (both `strtolower()` when inserting into the database, and `strcasecmp()` when comparing the domains). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WordPress MU Domain Mapping] [Plugin: WordPress MU Domain Mapping] Domain mapping treats domains as case sensitive](https://wordpress.org/support/topic/plugin-wordpress-mu-domain-mapping-domain-mapping-treats-domains-as-case-sensitive/) * Thread Starter [Chris M.](https://wordpress.org/support/users/inxilpro/) * (@inxilpro) * [15 years ago](https://wordpress.org/support/topic/plugin-wordpress-mu-domain-mapping-domain-mapping-treats-domains-as-case-sensitive/#post-2283437) * That’s the issue—the domain mapping plugin doesn’t treat domains in a case insensitive way. If you look at the function `domain_mapping_siteurl()` (lines 529 and 536) you can see that it simply pulls the domain from the database as is, and in ` dm_domains_admin()` it inserts the domain directly as it is sent from `$_POST`( lines 163 and 166). So if I enter “MyDomain.com” on the domain mapping admin page, it gets saved in the database as “MyDomain.com” — not “mydomain.com”. Finally, if you look at `redirect_to_mapped_domain()` (line 707), you’ll see that it simply checks if the domain in the database matches the domain in the `$current_blog` global variable. `$current_blog->domain` should always be lower case, but `domain_mapping_siteurl()` does not always return a lower case domain, so that check will **always** return false if the domain is not entered as all lower case in the admin panel. * A better fix might be changing the `dm_domains_admin()` function so that it performs` strtolower()` on `$_POST['domain']` before inserting it into the database. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [Fixes to make OpenID work on PHP 5.3](https://wordpress.org/support/topic/fixes-to-make-openid-work-on-php-53/) * [Chris M.](https://wordpress.org/support/users/inxilpro/) * (@inxilpro) * [16 years, 6 months ago](https://wordpress.org/support/topic/fixes-to-make-openid-work-on-php-53/#post-1384537) * Yep—changing those two lines got it working for me! * Thanks! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [Fixes to make OpenID work on PHP 5.3](https://wordpress.org/support/topic/fixes-to-make-openid-work-on-php-53/) * [Chris M.](https://wordpress.org/support/users/inxilpro/) * (@inxilpro) * [16 years, 6 months ago](https://wordpress.org/support/topic/fixes-to-make-openid-work-on-php-53/#post-1384536) * The file is openid/Auth/OpenID/Server.php — I haven’t tested whether those changes work yet, but that’s the file he’s referring to. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Redirecting URL hack](https://wordpress.org/support/topic/redirecting-url-hack/) * Thread Starter [Chris M.](https://wordpress.org/support/users/inxilpro/) * (@inxilpro) * [16 years, 6 months ago](https://wordpress.org/support/topic/redirecting-url-hack/#post-1407431) * They’re fixed on my site, and I know that Google will eventually get the right links, but until that happens every visitor from a Google search is just going to get a HTTP 400 error, which is less than ideal. It seems like there must be a way to redirect those old URLs to working ones, but Apache doesn’t like them one bit. * Chris Viewing 8 replies - 1 through 8 (of 8 total)