500 Internal Error on WooCommerce & Activation Key Format Query

T

team

New member
Hi there,

I'm facing a 500 Internal Server Error when testing with a random file on WooCommerce. I've followed the documentation and received a successful message when testing the installation. However, the error pops up when I test with a random product.
Screenshot.webp

I've checked all required details (product ID, private key, master key, user ID, and order ID) and can confirm they are correctly set. Could you please help with this issue?

Also, is there any way to customise the format of the activation key, rather than using the default [user_email]-[order_id] format?

Thanks
 
Solution
gdgsupport
You probably have a third-party plugin in WordPress that also uses Monolog. Try identifying which one by searching for "monolog" in your wordpress directory.
team said:
Also, is there any way to customise the format of the activation key, rather than using the default [user_email]-[order_id] format?
Click to expand...
Sure, if you have enough PHP knowledge, you can customize the format of the activation token. The most important part is the order ID. The email is a way to avoid someone just entering an order ID as the activation token.
Sort by date Sort by votes
You probably have a third-party plugin in WordPress that also uses Monolog. Try identifying which one by searching for "monolog" in your wordpress directory.
team said:
Also, is there any way to customise the format of the activation key, rather than using the default [user_email]-[order_id] format?
Click to expand...
Sure, if you have enough PHP knowledge, you can customize the format of the activation token. The most important part is the order ID. The email is a way to avoid someone just entering an order ID as the activation token.
 
Upvote 0 Downvote
Solution
Thanks for the reply and the kind reminder. Regarding the format, could you let me know which files I should review? Or if there is any documentation available that covers this topic?
 
Upvote 0 Downvote
Hi team,

Just reopening this thread as I haven't received an update on this issue via support ticket.

It seems the conflict is between the Hostinger AI Assistant plugin and the XLS Padlock. Since the website is hosted on the Hostinger platform and their AI Assistant is part of their native functionality, could you please help with resolving this compatibility issue?

This may also be a common issue for other users on the Hostinger platform, so any insights or fixes would be helpful. Thanks
 
Upvote 0 Downvote
You must log in or register to reply here.
Back
Top