This topic has 6 replies, 2 voices, and was last updated 10 years, 3 months ago ago by Eva Kemp
I have been trying to add cardsave payment gateway option to my website. For some reason, in the back-end everything shows up fine. I configure the plugin with correct details and tick the box that say enable plugin.
I have tried several times but nothing shows up at all on the front-end. Paypal and direct bank transfer show up as normal although they are a little misaligned. I have installed and used the cardsave module on al my sites without this problem. I contacted cardsave and they said it must be something to do with the template as it does not use the default Woocommerce templates/files.
I’d appreciate your haste in dealing with this matter as they site has already gone live and I really need to have cardsave as a payment option.
Woocommerce Version 2.1.9
WordPress Version: 3.9.1
Cardsave Version 2.2
Thanks
Hello,
Did you check if the issue persists with default wordpress theme too?
Please check it.
Also please provide us with wp-admin panel and FTP credentials in Private Content.
Regards,
Eva Kemp.
Hello,
Yes I tried deleting all the themes woocommerce files and testing it to no avail. Please check the private content for details requested.
Hello,
Please provide us with the link where we can replicate the problem from our side.
Also as I see you have old version of Woocommerce plugin. Please update it.
Regards,
Eva Kemp.
Hello,
I have updated woocommerce but the problem still persists.
To get to the shop page go to collections and click any of those place holders for the images.
Thanks for being so responsive, I am on a really tight schedule.
Thanks,
Mwaji.
Hello,
I’ve checked the default wordpress theme and cardsave payment gateway option isn’t being displayed there too.
So the issue isn’t related to our theme.
You have to contact the plugin developer and ask them to check it with wordpress theme as well.
Thank you.
Regards,
Eva Kemp.
The issue related to '‘Cardsave payment option not showing up on front end’' has been successfully resolved, and the topic is now closed for further responses