Page 1 of 1

BUG!! - generation of PayPal buttons does not work anymore

PostPosted: August 19th, 2011, 5:22 pm
by candy
Hi,

I think it must be because of one of the latest updates, fact is the code for the PayPal button is not updated when one clicks on the "Generate now" button.

I needto switch to a live version today, now I am stuck because of this, as I need a new button to switch from sandbox to normal account, update domain, etc.

Tried in IE, Chrome and Firefox, it is simply NOT working anymore!!!!

Please help!

PS: following error shown in IE when clicking on those paypal buttons:

Code: Select all
';' expected
Line: 2
Code: 0
URI: http://www.domain.com/?ws_plugin__s2member_menu_pages_js=1508323841&ver=110815-1511037330



PPS: I don't know what changed in those last updates, but it messed a lot of stuff up! Messed my site on many corners!!!!

Re: BUG!! - generation of PayPal buttons does not work anymo

PostPosted: August 19th, 2011, 10:31 pm
by Cristián Lávaque
Hi Candy.

What updates were they? What versions do you have of WordPress, s2Member and s2Member Pro (if you have it)?

The generator problem can be a conflict with your theme or another plugin. Try the TwentyTen or TwentyEleven themes and see if the generator works. If not, disable other plugins and try the generator after each, when it works you'd have found the plugin that was conflicting.

The JavaScript problem with the generator may be causing trouble in other places where JavaScript is also used.

This video may help too: http://www.s2member.com/options-page-di ... ing-video/

Re: BUG!! - generation of PayPal buttons does not work anymo

PostPosted: August 20th, 2011, 7:03 am
by candy
Hi Christian,

I CANNOT try other themes now, it's a finished project! And everything worked fine till the last 1 or 2 updates (didn't need the paypal changes till yesterday)
I have the latest versions of WP, S2 and buddypress.

As I did not install other plugins since, only updated S2, it cannot be it's suddenly because of the other plugins.

Besides, all errors are pointing out to a S2 problem as far as I can see (see also bellow)

Code: Select all
Warning: 'important' expected, but 'ie' found.  ';' or '}' to close declaration expected, but 'ie' found.  Declaration ignored. Source: http://www.site.com/?ws_plugin__s2member_menu_pages_css=347944584&ver=110815-549123789
Line: 1

Unknown property 'box-sizing'.  Declaration ignored. Source: http://www.site.com/?ws_plugin__s2member_menu_pages_css=347944584&ver=110815-549123789
Line: 1

Re: BUG!! - generation of PayPal buttons does not work anymo

PostPosted: August 20th, 2011, 4:47 pm
by Jason Caldwell
Thanks for the heads up on this thread Cristián.
~ and thanks for reporting this important issue.

I CANNOT try other themes now, it's a finished project!
I think what Cristián means is that if you can test this with another theme temporarily, it may help to narrow down the conflict that is occurring. In the mean time, we're going to investigate this issue, but right now this appears to be an isolated incident, perhaps a conflict or server-specific issue.

You posted these warning/notices.
Code: Select all
Warning: 'important' expected, but 'ie' found.  ';' or '}' to close declaration expected, but 'ie' found.  Declaration ignored. Source: http://www.site.com/?ws_plugin__s2member_menu_pages_css=347944584&ver=110815-549123789
Line: 1

Unknown property 'box-sizing'.  Declaration ignored. Source: http://www.site.com/?ws_plugin__s2member_menu_pages_css=347944584&ver=110815-549123789
Line: 1
These are in fact quite common, related to CSS specifications to address cross-browser incompatibilities. Firefox is known to display issues like this in it's Error Console, but they are harmless, and really intended for developer debugging purposes. In the two cases that you've posted here, these are harmless warnings about declarations that Firefox does not understand, but other browsers, in specific versions, do understand. Thus, the reason for their inclusion. No need to worry about these.

You posted this bug report:
I think it must be because of one of the latest updates, fact is the code for the PayPal button is not updated when one clicks on the "Generate now" button.
OK. Yea, this sounds like a conflict with another plugin and/or your theme. We've seen this happen before, whenever another plugin introduces an error in your Dashboard somewhere, which like all JavaScript apps, can cause all JavaScript functionality in the Dashboard to become faulty. I would suggest disabling one other plugin at a time, until you find the plugin combination that is causing this faulty behavior.

Even better, the Firefox Error Console can also help you narrow this down. On the PayPal Buttons page in your Dashboard, go up to Tools -> Error Console in Firefox, and please post a copy of the "Errors" tab output for us. This video tutorial may help you in that regard:
http://www.s2member.com/options-page-di ... ing-video/

Once we see the JavaScript errors that are occurring, we might be able to help you out. Also, if you'd like to post a list of the other plugins/themes that you're running in concert with s2Member, that may also help. Screenshots are also welcomed.

[Solved!]Re: BUG!! - generation of PayPal buttons not workin

PostPosted: August 27th, 2011, 9:52 am
by candy
Hiiii,

Thank you both of you for looking into it!
However, it was indeed not an other plugin, but a little issue in S2 itself.

I happend to have one of the membership levels called smth like "Grannie's Club" - well was exactely that
" ' " inside the memberhip label name that caused all the trouble as the javascript could not handle it properly ... :-(

I have now changed the label name not to contain any " ' " characters and the buttons are back!

Please consider in a future update to include a short "how to" in the membership label names section, telling people they should never use unusual characters when defining their memberhip names.

Thanks!

Re: BUG!! - generation of PayPal buttons does not work anymo

PostPosted: August 27th, 2011, 12:48 pm
by Jason Caldwell
Ah.. Thank you VERY much for reporting this.
We'll have this corrected in the next release of s2Member.

Thanks also for your patience.