Your cart is currently empty!
Conflicting with WooCommerce Checkout
—
by
Hi Kento,
I have finished installing Affiliate Enterprise, but just now realise that all purchases are ‘getting stuck’ at the checkout when the final ‘Place Order’ button is pressed. When I deactivate the plugin, they go through. When I reactive, they get stuck.
Have you come across this issue before?
Obviously is a critical one and after all the work I have put into, I hope it can be overcome.
Thank you.
Posted in Affiliates Enterprise
Comments
8 responses to “Conflicting with WooCommerce Checkout”
fixed? and how?
It seems to work fine. I have not really done anything. When I tried worked well.
when you’ve increased the memory or maybe a problem with your browser cache.
cheers
I just noticed this may be of help. In beneath I have this code:
/* That’s all, stop editing! Happy blogging. */
/** Absolute path to the WordPress directory. */
if ( !defined(‘ABSPATH’) )
define(‘ABSPATH’, dirname(__FILE__) . ‘/’);
/** Sets up WordPress vars and included files. */
require_once(ABSPATH . ‘wp-settings.php’);
Thanks.
This is ok 😉
Hi Antonio,
Thank you for your prompt reply.
I increased the WP Memory Limit: 64 MB
In the wp-config.php file I added:
define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);
When I try to go to the front of the site to make a purchase, this error message appears at the top of the screen. The page loads, but with this message.
Notice: Use of undefined constant ABS_PATH_TO_MO_FILE – assumed ‘ABS_PATH_TO_MO_FILE’ in /home/lesleyecocafe/public_html/wp-content/plugins/pie-register/pie-register.php on line 54
Any clues please?
Hi,
I recommend increasing the memory to 128 MB.
This notice is relating to pie-register plugin, but it should not be the problem.
Please share the ..wp-content/debug.log file.
You can send us dashboard admin access to support at itthinx dot com and we’ll have a look (please indicate this topic in the email).
cheers
Ok, email sent!
Hi,
please be sure you have enough memory (you can check it in Woocommerce->System Status).
you could try:
1.- Enable debugging for WordPress, in wp-config.php add/change these lines:
define( ‘WP_DEBUG’, true );
define( ‘WP_DEBUG_LOG’, true );
2.- Place an order.
3. Disable debugging
define( ‘WP_DEBUG’, false );
define( ‘WP_DEBUG_LOG’, false );
4. Please post the contents of the file wp-content/debug.log through pastebin.com
cheers