Fix request for case sensitivity problem

  • David Burkhart

    (@dlburkhart)


    9 years, 8 months ago

    If an uppercase letter is inadvertently used in a domain name with this plugin, it will cause an error in resolution of the domain. I have wasted time on multiple occasions tracking down domain/DNS issues only to discover the problem lies in the inability of either this plug-in or WordPress to properly handle uppercase letters in a domain name.

    I typically prefer the use of mixed case in domain names as it often makes them easier to read. So, I use them wherever possible. And, this plugin allows it. However, if used with this plug-in, it will cause misleading errors.

    If even possible, I would prefer this plug-in be altered to fix the case-sensitivity issue. However, if this is not possible, please correct it to either disallow uppercase letters in domain names or automatically translate uppercase letters to lowercase.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Ron Rennick

    (@wpmuguru)

    9 years, 8 months ago

    This plugin is in maintenance for legacy support. As of WP 4.4, domains can be mapped natively following https://ww.wp.xz.cn/support/topic/howto-domain-mapping-without-a-plugin-instructions/ .

    Thread Starter David Burkhart

    (@dlburkhart)

    9 years, 7 months ago

    Ron, thanks for the response. However, I’m unsure what you mean by “in maintenance for legacy support.”

    I had already stumbled across the thread for natively mapping custom domains. But, it brought about too many concerns.

    First, and foremost, the native method for mapping requires a dedicated IP address. This will cost most multi-site owners extra money and not just a one-time fee. For those like me with more than one multi-site, this recurring fee would be multiplied.

    Second, the side-effects, especially the one of disabling the structured URI path, seems troubling. What happens when the domain or DNS servers have a problem? Would that block my access to the site also?

    Third (and possibly a summary concern including the first two), using the native method for mapping seems like more of a hack. Using the plugin is more intuitive (except for having to remember to use only lower-case letters in the domain name).

    I suspect it’s only a matter of time before the native support for domain mapping matures and becomes as easy-to-use and intuitive as this plugin. But, for now, it seems like a no-brainer to use the plugin instead.

    Plugin Author Ron Rennick

    (@wpmuguru)

    9 years, 7 months ago

    First, and foremost, the native method for mapping requires a dedicated IP address.

    The server side requirements for any form of domain mapping are the same.

    What happens when the domain or DNS servers have a problem?

    I expect the concern for most people would be that the front end of the site was effectively down. Again, the domain method used doesn’t alter that.

    If you had a situation where the owner of the domain let it expire & doesn’t plan to renew you can edit the site URL and change it back to a subsite URL.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Fix request for case sensitivity problem’ is closed to new replies.