WP eMember and Javascript Issues with WordPress Upgrade

[amin007]

WordPress 3.0 have upgraded JQuery to 1.4.2 so on some servers users are having some issues with WP eMember’s forgot password, registration submission etc. We have updated eMember to handle this issue. If you are facing a similar problem please request an update to get the updated version of eMember then install the new version and it should fix the problem.

Don’t forget to clear your browser cache after you do the update so it’s not using the old script.

[socialvideolabs]

Where do I request the update?

[Ivy]

Hi, Please see the following post as it will explain how updates work:

https://support.tipsandtricks-hq.com/forums/topic/how-and-when-do-you-get-an-update

[neilsunset]

Hello, Ivy and Amin. First off, I am IN LOVE WITH YOUR PLUGINS, which is crazy because I haven’t even tapped into their full power just yet. Just wanted to get the congrats out of the way.

So… I just received the latest updates for all three plugins (WP Affiliate – v4.1.5; WP eMember – v5.4.5; WP eStore – v4.0.1; and even just purchased WP PDF Stamper v1.5), today, and I have the same above problem with my buttons, for example the “Register” button on my free registration page doesn’t go through, even though I see something runs down in the task bar when I click it. I tried to troubleshoot the problem as much as I could without having to contact you because I know you are very busy, but I’m stuck.

A few things I noticed:

1. The buttons seem to work on the default WP 3.0 “Twenty Ten” theme, but not my premium theme.

2. Using Firebug and inspecting the button element while in both themes, the Register button is shown in a < button > tag in my premium theme, but in an < input > tag in the default WP theme, which leads me to

3. In the eMember_misc_functions.php , the button DOES in fact start off in an < input > tag but somehow gets spit out into a < button > tag once the page loads using the premium theme, not to mention that this pHp file is “inactive” (amongst others).

I feel like I’ve been literally playing CLUE for the last six hours and I’m burned out. Your help is definitely appreciated!

[neilsunset]

Oh, and I almost forgot..When I load up my site in the premium theme and go into Firebug and replace that wrongfully/automatically populated < button > code of:

<button type="submit" class="eMember_button btn" id="eMember_Register"><span style="margin-top: -1px;">Register</span></button>

with this, which is what it has while in the default WP theme:

<input type="submit" value="Register" id="eMember_Register" name="eMember_Register" class="eMember_button">

it works just like it’s supposed to. And one more final thing, the button itself was automatically loading under the styles of the premium theme’s css, which I commented out to get it to look the the normal way…don’t know if that helps…

[amin007]

This usually happens when you are using a theme that’s not properly code. This article will explain this issue a bit more:

When Themes Go Wild – Importance of Using a Properly Coded WordPress Theme

The default WordPress theme is properly coded which is why the plugin works fine. I would recommend you try few other free themes just to confirm the theory and let me know your findings.

[neilsunset]

You’re right, but this was not a free theme at all that I was using, which of course doesn’t mean it can’t be mis-coded in some spots, but all works well so far with the exception of that < input > submission button. Could javascript turn it from a < input > to a < button > ? I didn’t think CSS could do something like that, although I did find that the eMember button shared the same class name of .loginForm with the theme’s class style for it’s login button, of which I just went ahead and commented out.

That de-confliction made the eMember button look the way it was supposed, but there’s something still conflicting with the way the submission button loads…it loads as a < button > instead of a < input >. It originates in the eMember plugin as an < input >, but somehow gets told to be a < button >. Where would that command be issued? I’m suspecting in one of the theme’s files, but I don’t know if it might be a .js or a .php file. I cant even troubleshoot the eMember_misc_function file by changing the < input > to a < button > just to see what happens because it’s “Inactive”. How does one “activate” it?

[neilsunset]

The plugin’s < input > tag, extracted from the plugin’s “wp-eMember/reg_member_view.php” file in the plugin editor, reads:

<input type="submit" value="Register" id="eMember_Register" name="eMember_Register" class="eMember_button">

And the button’s < button > tag, extracted from Firebug once the webpage is rendered reads:

<button type="submit" class="eMember_button btn" id="eMember_Register"><span style="margin-top: -1px;">Register</span></button>

Could that type="submit" be causing the conflict, since it’s shared by both the plugin and the theme?

[amin007]

This would be the work of a javascript file. I am pretty sure your theme is using some JQuery library which needs the input to be a button so it’s replacing the “input” submit fields to a “button”. Obviously the theme author forgot that the users will use other plugins which can also use a submit button.

[neilsunset]

You are the greatest, I mean effing awesome. It was a jQuery script in the header.php that was the culprit. Once I commented it out, problem solved!

[Author]

Posts