1.1.1 version issue

I completely forgot to test the recent changes on a subdirectory setup; the sites I’ve sandboxed this on were subdomain only.

I’ve been able to do some testing now and found the issue; at some point while modifying the redirect handling, the path prefix wasn’t getting stripped out when it created the new URL to redirect to. This should be fixed now, look for 1.1.2.

Dear Wollison
Thanks for your update, but the issue is still not fixed in 1.1.2.
Can you check more?

I still get same error:
https://abc.com/xyz => https://xyz.com/xyz then 404 error, it should be only https://xyz.com/

Thank you very much.

Damn, I forgot to account for the trailing slash missing; it would’ve worked on abc.com/xyz/ but it doesn’t recognize the /xyz as the same. Should be fixed now.

I’ll have the patch published in the morning; noticed a few other details I needed to fix. However, if you want to install the fix now, you can download the updated code here: https://github.com/dougwollison/domainer/archive/5635aa75cdbf0a75ac5cd2b04f5bad2a7e21e7d0.zip

Or if you’re comfortable just replacing the affected file: https://raw.githubusercontent.com/dougwollison/domainer/master/includes/class-domainer-system.php

Hi
Thanks for answer.
But I has update to 1.1.3, then all website is 500 error.
So I back to 1.0.1 again, then everything is fine.

• This reply was modified 6 years, 3 months ago by Neo.

Sorry about that, I thought I tested the changes before publishing the release but there was one little tweak I made that I apparently didn’t test.

Try 1.1.3.1

Dear Wolison
1.1.3.1 has no any issue, it’s running well.
Thank you very much.

Awesome. Sorry about the hiccups on that.