CiviCRM Community Forums (archive)

@Krypto- you are probably right on the money- but, the registration code is much more complex than the donation code, since there are options for multiple registrations etc.
I had a theme ninja look at the pinboard theme vs twenty twelve- he didn't find any theme related differences.
But- if he switched to twenty twelve it worked- going to Paypal.
So - it's something to do with the child theme-
and- it also does this oddly- it works the first time- then, it stops. Once it's returned - no more. So, is it a cookie issue?

The biggest beauty of wordpress is it's simplicity in theming. If Civi can only work with the default theme- what do we have.
Seriously, Don, the two most important functions are donations and registrations- we need a reliable, bulletproof loop here.
Paypal is by far the most used payment processor.

I'd pay someone to fix this- do we need to have a MIH fund for a bug fix?

Hey Guys.  I've run into this issue with a Wordpress 3.5.1 and Civi 4.2.8. 

Bottom line: Any jQuery error on an event registration page or contribution page will likely break CiviCRM's 'billing info block' functionality which causes errors for Paypal Standard.  Use Firefox's Error Console or Firebug or other debug tool to view a list of jQuery errors on webpages.

More details:
1. CiviCRM relies on jquery to remove the billing block will thus an error in jQuery will cause the block to be included in the post incorrectly (as if it were paypal pro or authorize) this results in the processor error on the thank you page

2. Notice in the attached screenshots how the billing block is included incorrectly on our custom theme, but not on a default theme.

It's not just theme related, it's also plugin related.  In fact, there are a LOT of reasons a jQuery error could occur on a CiviCRM page.    My case was a plugin problem.

In our particular case, the inclusion of the Multi Level Plugin in header.php (as the plugin instructs to do so) includes this code on the page:

<!-- Multi-level Navigation Plugin v2.3.5 by PixoPoint Web Development ... http://pixopoint.com/multi-level-navigation/ -->
<!--[if lte IE 7]><script type="text/javascript" src="http://www.capitolpagealumni.org/wp-content/plugins/multi-level-navigation-plugin/scripts/suckerfish_ie.js"></script><![endif]--><script>jQuery(document).ready(function() {
jQuery("ul.sf-menu").superfish({
animation:     {opacity:"show",height:"show"},  // fade-in and slide-down animation
delay:        50,                            // delay on mouseout
speed:        "fast",  // animation speed
autoArrows:   "",  // enable generation of arrow mark-up
dropShadows:  ""  // enable drop shadows
});
});
BAM!  jQuery error with CiviCRM on the contribution page.

My temporary solution while I try to debug this would be to remove the inclusion of this plugin on all CiviCRM related pages.  I may continue to debug this plugin or more to a css-only based menu system such as  http://wordpress.org/extend/plugins/dropdown-menu-widget/

So what to do then?

Well of course CiviCRM can't guarantee compatibility with every theme and plugin under the sun, but it does seem like making the contribution page(s) processing less dependent on a completely error free jQuery environment would be a good idea.

I don't feel confident proposing a specific technical solution on CiviCRM's part yet, but we could take action.

Lobo do you have any thoughts on changing the billing block code so it's not heavily dependent on jQuery?  I've noticed a plethora of problems related to relying on jQuery on these contribution pages.  Not just with Paypal, not just with Wordpress, but also with IE.   

Come to think of it, egads, what if someone has javascript turned OFF when they visit a contribution page using Paypal Standard, or is using common plugin like NoScript?   Well apparently then CiviCRM doesn't forward the Paypal Standard at all, according to my testing, but doesn't produce an error either.  Should a donor be required to turn on javascript to give money?  I hope not.

UPDATE: Further reading and ongoing bug reports:
http://issues.civicrm.org/jira/browse/CRM-12203
http://issues.civicrm.org/jira/browse/CRM-12149