More Capitalization Woes

  • Resolved l0gan0

    (@l0gan0)


    10 years, 7 months ago

    I am having a strange problem where the directory for the new site is automatically capitalized. I am 200% sure that I didn’t use capital letters when cloning the site. Furthermore, I have cloned a dozen sites before this, but I have never had an issue like this.

    To better explain, I’ve created a template site where I can quickly clone and change the necessary info/theme/etc. I’ve used this template site to clone at least a dozen sites. Starting yesterday, I noticed that unless I am logged into WordPress, I can’t view the site unless I capitalize the first letter of the sub folder.

    example.com/test (doesn’t work unless I’m logged in)
    example.com/Test (works)
    example.com/tESt(works)

    It seems like an htaccess thing, but I don’t see anything that would cause that and all my other sites are fine. I am not sure that the cloner plugin is causing this, but it was my most recent plugin update, and it seemed to work fine before that. Anyone have a theory as to what is going on?

    Thanks in advance,
    Logan

    http://wordpress.org/plugins/ns-cloner-site-copier/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter l0gan0

    (@l0gan0)

    10 years, 7 months ago

    Bit more info here… I just created a site from scratch and did not have the same problem. So I am assuming that the Cloner is indeed responsible for this glitch.

    Thread Starter l0gan0

    (@l0gan0)

    10 years, 7 months ago

    Okay got it figured out in case anyone else has this issue. Still not sure if this was caused by the plugin, but here’s the solution.

    Go into your database and edit the wp_blogs table of the sites that you are having issues with. The function dropdown should be blank, but you want to select “LOWER” and save. I’m no SQL expert, but I believe this forces the database to format the subfolder in lower case letter format.

    Not sure why this started happening all the sudden, but I hope this saves you some time if you run into similar issues.

    Cheers,
    Logan

    Plugin Author Never Settle

    (@neversettle)

    10 years, 7 months ago

    Thanks for posting that work around, Logan. Just catching up on the day’s activity. That is very strange indeed, and I’m thinking shouldn’t have been necessary. The only thing I can think of that would even be somewhat related, is that in a recent update we added checking specifically to prevent that scenario. So like you said – even if you had accidentally typed an uppercase character, the Cloner SHOULD filter it all to lower case for the site name.

    Did you happen to check your logs from that clone operation to see if anything stood out? Making that change in MySQL shouldn’t be necessary, and if there is a weird bug lurking we want to catch and smash it.

    Did it happen with multiple clones or just that one? Very odd indeed. Would you mind putting your MySQL column setting back to default and trying again to see if you can recreate the issue? If not no problem. I’m just wondering if we can capture any more data about the conditions that led to that result.

    Marking this resolved for now, but please add any new info that you think of especially if something similar happens again.

    Thanks!
    NS

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘More Capitalization Woes’ is closed to new replies.