Experiencing an error

Good luck, man! Also, if you need anything from logs, just let me know, I’m super familiar with Google Developer tools so can get that information for ya.

Cole,

Yesterday after refreshing my cache a bunch I found an error in my installation where I couldn’t upload image files. After much playing around with WordPress to get it working again, I did a completely fresh install and moved my wp-config.php back into my wordpress root folder. This fixed my image upload issue as well as the login modal!

I imagine, all along, that my wp-config.php being outside of my root folder has been the problem. I just didn’t know it, because I was using a cached version of it.

I’m not sure how that would affect anything like this, but apparently it did, and I am now able to log in just fine using your plugin.

Laura, you might check the same thing with your installation.

Unfortunately, my wp-config.php file IS in the root folder, so I’m not sure where to take it from here. Cole – I noticed there was an update, so I went ahead and installed it, but I’m still having the same error. I went into Chrome and did the ‘inspect element’ … It DOES have the ‘200 ok’. Here’s a screen shot:

https://tinyurl.com/kz4aton

oops… try this instead…
https://www.cjisadvancedauthentication.com/chrome-sample.jpg

Very interesting, thanks for the update onorok and Laura!

I’ve been strapped on time but really want to get this fixed for you guys, so my apologies in the time this is taking ?? I’ll try moving some files around in my install and see if that will help me replicate, but I can’t see why that would ’cause issues…

Laura, thanks for the screenshot, however the files returning 200 OK are JavaScript files. The file in question is the wp-ajax.php, if you scroll down in the window for “network” you should see that file near the bottom. If that says 200 ok, click on the file and you should get a window like this screen shot which will help me figure out if the data is being sent back. https://cl.ly/image/292e2j0Y2i1R

Thanks again for the help everyone! Really appreciate it ?? I’ll try and squeeze in some time soon to take another stab at this!

It appears to be a conflict with your login and using WooCommerce. Can you see what might be the issue there?

If I enable WooCommerce (even turning off the ‘Force SSL’ options), it won’t update (it hangs on checking credentials forever). However, if I disable WC, your plugin waits a little bit and then works.

Please let me know if there is an update that will work with WC.

ah awesome, thanks! I will be sure to test it with WooCommerce!

I’m using WooCommerce version 2.0.10
Using WordPress version 3.5.1

Thanks, I’m getting the same result with WooCommerce 2.0.10 and WP 3.6-beta3. Working on fixing right now ??

This appears to be an issue also when s2Member is installed.

In s2Member, the problem lies in the class ‘c_ws_plugin__s2member_login_redirects’, which is defined in \s2member\includes\classes\login-redirects.inc.php. The specific function causing the problem is at line 67 of my installed version:
public static function login_redirect ($username = FALSE, $user = FALSE)
To remove the issue temporarily, I added:
if(defined ("DOING_AJAX") || DOING_AJAX) return;
to the top of that function, which resolved the issue for the time being.

I am thinking that s2Member is probably using a bad filter; they are definitely not return the WP_User object correctly using the filter they are using currently.

Correction: it’s not a filter, it’s an action…so it shouldn’t have to return the user object.

Okay so here is my deduction of what is going on…
Modal Login calls wp_signon with the POSTed data.
Modal Login expects to retrieve a WP_User object in return.

Meanwhile….
s2Member adds an action to wp_login – their redirect logic.
The wp_login hook is fired by Modal Login’s wp_signon call.
s2Member performs it’s wp_redirect (the success of which can be seen by watching the Network panel of Chrome’s developer toolbar).

Back to Modal Login…
Modal Login expects to retrieve the WP_User object, but by this time, we’ve already moved on to the redirected page. So No WP_User for Modal Login. Hence, Modal Login just sits.

For a fix…I believe it is on the end of s2Member – maybe using the login_redirect filter INSTEAD of the wp_login hook.

Thanks joshlevinson, it is still a possibility your issue is something on my end. I haven’t had a ton of experience with ajax so I’m sure there’s something I’m missing here causing these issues.

I really appreciate the help and I’m still trying to get the time to sit down and debug further.

Good news! Found a fix!

I tested this and got things working when WooCommerce is installed, however, s2Member has many issues in it. The second I activated it, WordPress tossed a massive array of warnings and other miscellaneous stuff (this is all evident when Debug mode is on). It became very difficult to use just a vanilla install of WordPress without my plugin even activated. At this point, I am calling fault on s2Member in this instance.

I’m rolling in a few other bug fixes and updates and should have 2.0.2 out tonight or tomorrow at some point.

Thanks everyone for all your feedback, hopefully this next release we can resolve this tickets ^_^

Cole, I noticed that your plugin redirects to the same page unconditionally, instead of allowing the redirect to be changed. I suggest that you modify this block:

if ( ! is_user_logged_in() ) {
	wp_localize_script( 'wpml-script', 'wpml_script', array(
		'ajaxurl' => admin_url( 'admin-ajax.php' ),
		'redirecturl' =>$_SERVER['REQUEST_URI',
		'loadingmessage' => __( 'checking credentials...' ),
	) );
}

to

if ( ! is_user_logged_in() ) {
	wp_localize_script( 'wpml-script', 'wpml_script', array(
		'ajaxurl' => admin_url( 'admin-ajax.php' ),
		'redirecturl' =>                 apply_filters('wpml_redirect_to',$_SERVER['REQUEST_URI']),
		'loadingmessage' => __( 'checking credentials...' ),
	) );
}

so that we can have control over what page WP Modal Login redirects to.

On the topic of s2Member, I do agree that the fault is s2Members. I have modified s2Member for now to filter the login_redirect instead of wp_redirect’ing on the wp_login hook, as I feel this is a more appropriate place to redirect. This, in combination with the filter I added to your plugin’s redirecturl, solved my problems for the time being.