Landing Location has no effect

I can sometimes figure it out just from testing your site, so a URL would a good place to start.

I will probably need it at some point, so you may also want to provide:

1. Your Theme Name
2. If you are not using one of the WordPress Twenty themes, a URL to the Theme’s WordPress Theme Directory entry, or its home page, if not in the Theme Directory
3. A list of Plugins — only the Activated ones. I’ll try to work with a list of names, and ask for clarification if there are any with similar names to other plugins

Thanks for being so helpful. I’ll do my best to get this figured out quickly.

Sorry for the initial delay in responding. In my time zone, it was sleeping time.

No, at this point, I’d like to explore a few of those plugins on my own test system where I have everything I need to debug really quickly. I already see some names that “look interesting”.

Be back ASAP.

After looking through your plugin settings, I now have re-created your problem on my test system, and can work on a solution.

A temporary workaround, until I fix my plugin, is to adjust settings on the Better WP Security plugin. The Hide tab takes you to Hide WordPress Backend. If the Enable Hide Backend checkbox is selected, my plugin’s Landing Location fails. If the checkbox is empty, my plugin works.

I was not able to make that change on your site as my Admin authority did not allow it. Nor did I know what you wanted to do.

I have run into similar problems with other plugins and themes, and have added code in my plugin to handle those specific plugins and themes. I will expand that to include support for the Better WP Security plugin, which I have not been asked about before.

I’ll report back to this thread when I’m done. Thanks for your patience, once again.

Much to my surprise, Better WP Security does not use WordPress hooks to do the final processing of the URL, where it adds the Secret Key with a ? before it, making it a Query parameter. Instead, it generates a number of ReWrite rules in the .htaccess file to handle this.

ReWrite, both within WordPress and using .htaccess, is an area I have almost no experience with, and it will be a steep learning curve.

As a result, I am going to offer a Workaround for now, and create an automatic solution in Version 3, as part of some major new features already being developed. Obviously, if this won’t work for you or anyone else reading this, I am willing to do something more immediate.

Here is the Workaround: in .htaccess in the root of your WordPress site (i.e. – wherever WordPress is installed, either in the root of a domain or in a folder or subdomain), you will see “# BEGIN Better WP Security”. The third non-blank line that follows will begin “RewriteRule ^login/?$”. Near the end of the line, just before “[R,L]” and immediately after (with no blanks) a question mark and your Better WP Security Secret Key that is already there, insert “&redirect_to=http://domain.ext/wp/sample-page”, where “http://domain.ext/wp/sample-page” is the URL of the desired Landing Location. Be sure there is still a blank before the “[R,L]” at the end of the line. The line should look like this:

RewriteRule ^login/?$ /wpfolder/wp-login.php?dp0amamafnxnlun4gdsyu&redirect_to=http://domain.ext/wp/sample-page [R,L]

If you alter the Enable Hide Backend checkbox of Better WP Security, you will lose the changes you made in the Workaround, and have to apply them again the next time that the Enable Hide Backend checkbox is selected (has a checkmark in it).

I don’t like Workarounds either.

Your suggestion to work with the author of Better WP Security is a good one. At first glance, they really should be retaining the &redirect_to= query whenever present in the URL, regardless of my plugin’s presence.

I’ll keep this thread updated with my progress.