|
apaindiana
|
February 13, 2013 at 4:13 pm
Hello,
I am wondering if anyone knows how to disable two buttons on the payment method selection page. As you can see in the image below (yellow arrows), I have two buttons that respond to rollovers, but are not clickable. Is there a way to disable these two buttons so that people are not confused as to where they need to click to download the invoice. Users need to click the “Download PDF Invoice” to download the PDF.
Thanks!
|
|
Josh
|
February 13, 2013 at 4:48 pm
Hi there,
The payment page is designed to hide the information that’s appearing below the invoice button. However, if there’s a JavaScript error on the page, it will fallback and display everything. The result is the button doesn’t do anything.
Can you check the payment page in Firebug or the web inspector for JavaScript errors? There is probably a simple fix that can be made. Actually, I checked your site and it looks like it’s using the super Skeleton theme. I recently did a project and there were some settings I turned on that would cause JavaScript errors, I didn’t need the features that were turned on and by turning them off, the JavaScript errors went away.
|
|
apaindiana
|
February 14, 2013 at 4:18 am
Thanks, Josh. Do you recall what those features were?
|
|
Josh
|
February 14, 2013 at 7:59 am
The one that I remember turning off was the one that said “use the Chosen Dropdown replacement script?” in the Basic setup theme options panel. I noticed there were JS errors when that was set to yes.
|
|
apaindiana
|
February 19, 2013 at 7:17 am
Hey Josh – I turned off the “Chosen Dropdown Replacement Script” option, but it still did not resolve the dead button issue. Any other ideas? I’m not sure exactly how to determine whether or not we’re dealing with a JS error.
|
|
Sidney Harrell
|
February 19, 2013 at 1:13 pm
There is definitely a JS error on that page:
Syntax error, unrecognized expression: #.portfolio-4 .container .module-container:nth-child(4n+5)
The expression seen is being sent to jquery, which doesn’t see the element referenced, and crashes, keeping any other JS from running. The expression is probably being generated by the theme. Can you switch to the WordPress default twentytwelve theme, and see if that clears the issue?
|
