Plugin Author
alekv
(@alekv)
Hi boyos79
I’ve found this error being around on WooCommerce pages before I’ve developed my plugin. Could you please tell me which version of WordPress and WooCommerce you are running?
Thx
Aleks
Hello alekv,
I am using WP 3.3.2 and woocommerce 1.5.4.
thanks a lot
Plugin Author
alekv
(@alekv)
Ok. You need to update your WooCommerce installation. I know that it works with at least 2.0 and the current version 2.1.2
You need to update WP first, as WC 2.1.2 requires a higher version of WP, if I’m correct at least 3.8
Regards
Aleks
If I do that, I am scared that nothing works anymore or that i need to do too many PHP/HTML changes afterwards…
Is there another way to fudge the code of you plugin?
Plugin Author
alekv
(@alekv)
Probably. But I would have to tweak it for your specific installation. And I would have to break the upward compatibility, meaning you couldn’t update the plugin anymore.
Because this would mean development outside of my effort for my free plugin I would have to charge you the development time.
For security reasons I would highly recommend to update your entire installation and take the effort to do all required changes to your installation. Also I would recommend to segregate all changes to the standard installation into a child theme, so all your updates would be upgrade save. In case you need assistance, I know developers who could to that for you.
Hi alekv,
I am not very comfortable with that and I can’t afford to spend more money for my small business 🙁 .
Would not there be another easy way to add an HTML page after the received order page and to add the code in there?
Thanks a lot for help
regards
Plugin Author
alekv
(@alekv)
Normally one could put the code I’ve wrote into the thankyou template. But there is a WordPress bug which prevents the AdWords tag to be represented correctly. This is also a problem my plugin solves.
Sorry. There is no 2 minutes no effort easy solution I know of.
Do you mean that it would just be a display issue?
thanks a lot alekv
Plugin Author
alekv
(@alekv)
no. the bug breaks the code.