Home › Forums › Community Forum › Pro Form "Buy Now" button not working in IE9
This topic contains 9 replies, has 5 voices. Last updated by Jason (Lead Developer) 3 years, 12 months ago.
Topic Author | Topic |
---|---|
Posted: Sunday Dec 30th, 2012 at 10:49 am #35798 | |
|
|
Just to let you guys know, the before mentioned button does not work independently (theme independent). I had to hack my funtions.php to disable the auto paragraph function, and afterwards edit 9 pages and 169 posts with inserting coded breaks and paragraphs just to make the buy now button working with IE9 This wasnt one of my good days! You need to correct this!
|
List Of Topic Replies
Author | Replies |
---|---|
Author | Replies |
Posted: Tuesday Jan 1st, 2013 at 7:56 am #35884 | |
|
|
Hi Ronnie. I’m sorry you went through that but, although we’ve had someone report from time to time a problem with IE9, it’s normally a problem introduced by the custom theme or another plugin. A default installation of WP with s2Member only, doesn’t have that problem in our tests, so it’s being introduced by something else. To find what, you’d test the theme and other plugins. Knowledge Base » Common Troubleshooting Tips Once you find what is causing the problem, you can find a replacement, or ask the developer to fix it. I hope that helps. |
|
Posted: Tuesday Jan 1st, 2013 at 9:26 am #35887 | |
|
|
I would like to chime in for IE9. I used the Pro-form for billing modification and one member could not get it to work. When i suggested she tries a different browser, she did and it worked. She emailed me back saying that it was with IE9 that it would not work. |
|
Posted: Wednesday Jan 2nd, 2013 at 9:35 pm #36045 | |
![]() |
|
Hi there, There’s a bug with IE9 that we found a few weeks back that might be the issue. Try editing the page in HTML mode, and put the following right before the start of the Pro Form (before the new line, or anything): The error is caused by IE9s HTML parsing techniques. It closes the form before anything is put into it and that means that the submit buttons don’t work because there’s nothing to submit. |
|
Posted: Thursday Jan 3rd, 2013 at 2:31 am #36059 | |
|
|
Ill re-enable the wordpress autoparagraph function and try it. |
|
Posted: Thursday Jan 3rd, 2013 at 2:46 am #36060 | |
|
|
@ Bruce Unfortunately I cannot confirm that your solution works effectively. This is how a payment page looks like in HTML:
You can view the page with IE here: https://www.movielocker.dk/?page_id=507 The solution is to add this code to your custom theme functions.php:
And regarding the buy now button, I am allowed by paypal to use a custom Buy Now button image (we are not using PayPal Pro but PayPal express checkout), and it would be great if you or someone in the support team would tell me how I can either a) change the button image, or 2) atleast have it in our native language (danish). |
|
Posted: Thursday Jan 3rd, 2013 at 2:38 pm #36125 | |
![]() |
|
Hi Ronnie,
Thanks for that info. We had found that the issue was arising because of the paragraph tags but did not find the root cause of it. This should work perfectly in the future.
Are you talking about the PayPal button image, or the button that’s generated by s2Member? The PayPal image can be changed with the image attribute. See: Knowledge Base » Custom Image in PayPal Button. If you’re looking to change the way that the Buttons look, you’ll need to write a little hack. Try this:
|
|
Posted: Saturday Jan 5th, 2013 at 5:25 pm #36336 | |
|
|
Will there be an update to s2 to work around this IE9 but or will everyone have to edit their pro-forms like that in the future? |
|
Posted: Tuesday Jan 8th, 2013 at 5:12 pm #36618 | |
![]() |
|
Hi Cassel, There really isn’t a way to get this patched from within s2Member. I’ll let Jason know about the issue with wpautop, but I do not think that there is a way for this to be fixed within s2Member. This issue is more of an incompatibility between IE9 and wpautop than IE9 and s2Member. |
|
Posted: Saturday Jan 12th, 2013 at 1:01 am #37079 | |
![]() |
|
Thanks for the heads up on this thread.To clarify what Bruce is talking about here…We researched a bug report related to IE9 several weeks ago, which we ultimately tracked back to the WordPress Editor, and WordPress content filters. While the issue causing this problem in IE9, can be caused in part by the wpautop filter, it’s really NOT the true problem. The wpautop filter is just doing it’s job.
The real issue is related to an invalid HTML nesting order, and how IE9 in particular will respond when your HTML tags are out of balance (e.g. when you have an invalid HTML document).
So what is an invalid HTML nesting order (aka: unbalanced tags)?For example, if you look at the source code for your site, you might discover something like this.
See how there is a matching open/close tag for the div element, but there is no matching open tag for the p element? That’s an invalid nesting order. Or, some might refer to this as unbalanced HTML code. IE9 (more so, than other browsers) attempts to correct unbalanced tags in ways that can lead to some problems in JavaScript, which will effectively break some functionality with elements on your page, such as an s2Member Pro Form. You can’t really blame IE9 for this either, because really, your site contains unbalanced tags when this occurs, and that’s what really needs to be fixed. This problem just shows up more in IE9, because… well Microsoft. Need I say more :-) Anyway, here are some things that can cause unbalanced tags.
In conclusion, this is NOT a bug with s2Member specifically (not that I’m aware of at this time). It’s also NOT a bug with WordPress (that I’m aware of at this time). It’s really just caused by unbalanced HTML tags, and that can happen for any number of reasons.
Always run your site through the W3C Markup Validation Service, to ensure that your site (or specific pages on your site) are coded properly. I can’t really provide a one-size fits all solution here. The solution to this problem is to balance your HTML tags. Depending on what’s causing unbalanced tags on your installation, the solution might be slightly different from one case to the next. |
This topic is closed to new replies. Topics with no replies for 2 weeks are closed automatically.