authentication issue when site is in 'coming soon mode'

I have a coming soon page activated, the plugin works when i deactivate it however when in use it doesn't authenticate. Maybe it could request the authentication function in a different way? instead from the root directory?

modstudio,

Thanks for reporting in. Are you using a plugin for the coming soon page - if so, which one is it? I'd like to troubleshoot this issue from my end later.

I've been able to use the custom login form from various pages and URLs, for example:

http://glassocean.net/login <-- custom Page with [wpoa_login_form] http://glassocean.net/wp-login <-- default Login screen

So I am not sure I fully understand your problem. Maybe you could clarify further.

Perhaps larsschenk's recent commits will fix your issue. You'll find his changes here in the repository, but they haven't been released as a new plugin version yet.

At first, this plugin did auth with dedicated URLs instead of the root (site_url), but I also had to include wp-load.php as a way to hook back into WordPress core during the auth callback. This was considered bad practice and prevented the plugin from passing review, so I researched how other login plugins do this (turns out they all do it differently) or a standard way to work without using wp-load.php. Otto's blog article here is what I went with - "Right Way the Second". It turns out if we have it call back to the main site_url, WordPress core will load and can use an action to check for the OAuth querystring parameters, then do some handling after the callbacks within WordPress context.

Hope that helps...

Woops, sorry didn't see this until now. I was using Ultimate Coming Soon. I no longer use it, the site is live so it's OK now and WP-OAuth functions correctly. I copied it over to a test environment again, and activated it, sure enough the problem returned. I've not really had chance to look into it being christmas etc. I'm sure it's trivial!

Very useful, I'll test that plugin later on to see if I can reproduce the compatibility issue so I can get it fixed for other users that might run into it. Thanks!