#24603 breaks 3.9 updates for Multisite blog networks with mixed case pathnames/subdirectories

[AnthonyJKenn]

This is my first ticket using Trac, so please be gentle with me.

This relates to #24603, which converted path and domain names to lowercase.

Unfortunately, I have two blog networks which use mixed case in their pathnames, and the result of #24603 was that when I updated to 3.9, I lost access to all but the root network blog in both networks. I can now only access the first blog listed on my root network, but attempts to access any other blog in my network get a 404 Not Found page. In addition, if I attempt to access the admin page for any blog in my network other than the root blog, I get redirected to the admin page of my root blog, even though the URL gives me the intended blog page.

I'm also worried that in the process of the update, my databases may have been altered so that more recent posts might have been erased.

I'm aware that a fix for this is being worked on for 3.9.1, via #27866, but what will that do for the present time, while my network is inaccessible? Is there any way to reverse this prior to an update?

Also..some of us users use mixed case names for their subdomains for a legitimate reason; it would be a swell idea to think of them before making a potentially hazardous change to their sites.

If this is the wrong venue, I apologize....any help or answers would be appreciated.

[nacin]

Hi AnthonyJKenn, this should be kept on #27866. I recognize you're having difficulty but the support forums are the best place to seek general assistance. As indicated on #27866 we're working on a solution that involves removing an strtolower() call. Could you elaborate on #27866 what your reason is for using case-sensitive subdomains? I am not familiar with the use case and that could help.

[AnthonyJKenn]

Thanks...and I will transfer my comments over there.