Doug Wollison

Totally understand, the plugin is semi-defunct anyway since WordPress 4.5 added built in domain mapping.

Sorry for the delay, been juggling rush jobs for weeks on end.

I’ve found and fixed the issue and will be publishing an update shortly. The issue had to do with the system thinking that the localized sidebars were no longer enabled, causing it to perform unnecessary cleanup.

None of the sites I’ve prototype/test this plugin on use sidebars so I never caught it.

I apparently didn’t have a functioning safety check in place to make sure the sunrise.php file was properly installed before adding the SUNRISE line to wp-config.php, which caused the error. I’ve patched this in the new 1.2.1 update and further added checks about where it can write to before even offering the “give it a shot” option.

You’re still getting the loopback request failure with the 1.2.0 update? What setup/configuration do you have?

This has now been fixed in 1.2.0; it was due to the remote login feature initializing a session regardless of if the feature was enabled or not, which was causing ajax requests to hang.

I replied to your previous post about the sunrise file.

If the issues persist, I should point out that a few releases back, WordPress allows you to set the full domain/url of each site on your network, basically rendering my plugin obsolete (aside from alias/secondary domains but in 99% of use cases that’s better done with cPanel/Plesk/whatever UI your hosting provider gives you).

The file is located in the plugin’s folder (wp-content/plugins/domainer/sunrise.php), however the plugin should be able to auto-install it for you provided WordPress has full write permissions to it’s install folder.

Okay, same steps should apply though.

Are you getting a 404 that looks like it’s on your site (compare with example.com/site1/404)? If not then it’s pointed to a shared hosting system and not pointing to your account.

You’re talking about setting up a redirect domain, correct? And is it a 404 page from your site or a generic error?

Let’s say I have a site at example.com, and I want to add example.net as a redirect; visiting it will immediately change to the .com version.

1) Ensure that example.net is set to point to the same server as example.com via DNS settings; make sure the IP address is the same.

2) Ensure your server is setup to accept traffic from that domain. With a simple redirect domain you technically don’t even need this plugin, just configure it in cPanel/Plesk instead.

At this point, see if the domain redirects to your network’s main site. It should be routing to the wordpress install, and WordPress is redirecting to the official domain the site uses.

3) In WordPress go to My Sites > Network Admin > Domains and click Add New

4) Fill out the form and hit Save Changes. This is mostly needed if example.com isn’t the default site on your network.

Alrighty, that ended up being really simple. Long story short Piklist was doing something I didn’t account for (nothing wrong just… odd) and that’s what caused the redirect loop and prefix stacking. I’ve made a simple fix by having nLingual always “delocalize” the URL before localizing it, rather than only some of the time.

You should see an update for 2.8.4 shortly.

Okay, I’ve setup a dev site using the themes/plugins you sent and was able to recreate the issue. I’ve thus far narrowed the cause down to the Piklist plugin. I’m attempting to find the exact cause and should have a patch figured out tonight.

Honestly, in order to debug this thoroughly, I’d need to mess around with the plugin code to test where it’s getting the double-localized URL from.

Are you comfortable sending over a ZIP of your themes and plugins so I can sort of recreate the site? I don’t *think* I’d need any database related stuff as I can just use dummy pages and manually recreate the settings.

You can send it privately to me at [email protected]

Sorry about the delay; been slammed at work.

I’ve recreated your settings on another test site but still can’t recreate the issue. Are you using any plugins that might affect URLs?

I’ve had a chance to test stuff and right now I can’t seem to recreate the issue on a sample dev site. Can you send me a screenshot or summary of what your translation settings are and how the languages are configured?

Hello,

I’ll see about debugging this later this evening; it should be a simple overlooked glitch caused by the recent subdirectory handling patch.

In the mean time, perhaps try replacing the plugin with an older version? You can download them here: https://github.com/dougwollison/nlingual/releases (I suggest trying 2.8.1)

Please note: do not uninstall/delete the plugin as this will delete it’s settings and translations data with it. If you have FTP access you should be able to replace it outright.

Otherwise I should have a fix in place in a couple days tops; I need to see if I can recreate the issue first. Will keep you posted.