- This topic has 7 replies, 3 voices, and was last updated 1 year, 7 months ago by David.
December 4, 2019 at 2:14 am #1092829pairfum
We have noticed that the WooCommerce Coupon Code Field has gone missing on the Checkout Page and we don’t understand why.
This is our website:
We have switched from our GeneratePress Child Theme (with customisations) to the standard (parent) GeneratePress Theme and the Coupon Code Field retuns.
Hence, we know it is linked to the customisations of our GeneratePress Child Theme.
However, when looking at functions.php and style.css we can’t see anything that we believe might cause it.
Can you help?
Here is a comparison of the Child Theme’s style.css file (left is the live site and right is the staging site, where the coupon code field is visible):
Here is the same comparison but for the Child Themes’s functions.php file (left pairfum.com and right staging.pairfum.com):
Can you spot the problem?
Many thanks for your help.
Pairfum LondonDecember 4, 2019 at 8:47 am #1093331LeoStaffCustomer SupportDecember 4, 2019 at 3:02 pm #1093769pairfum
Many thanks for your reply.
We fully understand that you cannot go through the entire code.
However, the two links show the differences between the two files.
The files on the right hand side belong to our staging site where we don’t have the problem of the coupon code disappearing:
We were hoping you could at the difference between the two files to see whether you can spot why the live site does not show the coupon code field but the staging site does.
Many thanks for your help.
Pairfum LondonDecember 4, 2019 at 3:19 pm #1093776LeoStaffCustomer SupportDecember 5, 2019 at 6:26 am #1094500pairfum
I am really disappointed by your reply, particularly since your forum does help to solve problems of Theme customisation and malfunction, i.e. not just Parent Theme issues.
We are under the impression that part of the license fee is for ongoing support.
Hence, I disagree with your logic that because the parent theme works, you don’t have to help.
Has there been a change in your support policy because in the past I suspect the answer to our support request would have been different.
Pairfum LondonDecember 5, 2019 at 7:56 am #1094698DavidStaffCustomer Support
NB: We haven’t changed our support policy. Our support has always been 100% theme and GP Premium plugin related. And any custom development to a users site is outside of our scope. But we unfortunately have this annoying habit of wanting to help wherever we can hence the lines get a little bit blurred.
Back to the matter – i can’t see how those code differences would affect the coupon field being displayed. But that is not the only difference between the two sites. The live site has additional payment notifications and methods that may be affecting how those woo functions are called.
First thing to check – What happens if you remove the function for disabling the cart coupon field on the live site?
Let us know.December 13, 2019 at 2:39 am #1102977pairfum
Many thanks for your reply, explanation and for taking the time to look at the code.
Having said this, your suggestion of removing the function that disables the coupon on the cart page, did the trick! Thank you for this tip.
It does not seem to make any sense but it works!
Thank you for your help. I really appreciate it.
Pairfum LondonDecember 13, 2019 at 4:09 am #1103065
- You must be logged in to reply to this topic.