|
pds-capcog
|
August 13, 2024 at 11:46 am
Our Stripe Payment Method keeps getting deactivated on its own. It is the same issue as described here: https://eventespresso.com/topic/plugin-gets-deactivated-on-its-own/.
I’ve added the login and just got this trace when it happened today at 11:59am:
Stack trace: #0 /wordpress/wp-includes/class-wp-hook.php(324): tw_ee_send_email_on_pm_deactivate(Object(EE_Payment_Method)) #1 /wordpress/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(”, Array) #2 /wordpress/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #3 /www/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Payment_Method.model.php(401): do_action(‘AHEE__EEM_Payme…’, Object(EE_Payment_Method)) #4 /www/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php(935): EEM_Payment_Method->_create_objects(Array) #5 /www/wp-content/plugins/event-espresso-core-reg/core/db_models/relations/EE_Belongs_To_Relation.php(165): EEM_Base->get_all(Array) #6 /www/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php(2739): EE_Belongs_To_Relation->get_all_related(Object(EE_Payment), Array) #7 /www/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php(2874): EEM_Base->get_all_related(Object(EE_Payment), ‘Payment_Method’, Array) #8 /www/wp-content/plugins/event-espresso-core-reg/core/db_classes/EE_Base_Class.class.php(2565): EEM_Base->get_first_related(Object(EE_Payment), ‘Payment_Method’, Array) #9 /www/wp-content/plugins/event-espresso-core-reg/core/db_classes/EE_Payment.class.php(613): EE_Base_Class->get_first_related(‘Payment_Method’) #10 /www/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Payment_Shortcodes.lib.php(74): EE_Payment->payment_method() #11 /www/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Shortcodes.lib.php(178): EE_Payment_Shortcodes->_parser(‘[PAYMENT_GATEWA…’) #12 /www/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php(232): EE_Shortcodes->parser(‘[PAYMENT_GATEWA…’, Object(EE_Payment), Array) #13 /www/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php(123): EEH_Parse_Shortcodes->_parse_message_template() #14 /www/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Payment_List_Shortcodes.lib.php(94): EEH_Parse_Shortcodes->parse_payment_list_template(‘\n_get_payment_list(‘[PAYMENT_LIST_*…’) #16 /www/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Shortcodes.lib.php(178): EE_Payment_List_Shortcodes->_parser(‘[PAYMENT_LIST_*…’) #17 /www/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php(232): EE_Shortcodes->parser(‘[PAYMENT_LIST_*…’, Array, Array) #18 /www/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php(72): EEH_Parse_Shortcodes->_parse_message_template() #19 /www/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_Messages_Generator.lib.php(717): EEH_Parse_Shortcodes->parse_message_template(Array, Object(EE_Messages_Addressee), Array, Object(EE_Receipt_message_type), Object(EE_Html_messenger), Object(EE_Message)) #20 /www/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_Messages_Generator.lib.php(619): EE_Messages_Generator->_setup_message_object(‘purchaser’, Object(EE_Messages_Addressee), Array, Object(EE_Message_Template_Group)) #21 /www/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_Messages_Generator.lib.php(300): EE_Messages_Generator->_assemble_messages(Array, Array, Object(EE_Message_Template_Group)) #22 /www/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_Messages_Generator.lib.php(139): EE_Messages_Generator->_generate() #23 /www/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_Messages_Processor.lib.php(254): EE_Messages_Generator->generate(false) #24 /www/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_Messages_Processor.lib.php(459): EE_Messages_Processor->generate_and_return(Array) #25 /www/wp-content/plugins/event-espresso-core-reg/modules/messages/EED_Messages.module.php(289): EE_Messages_Processor->generate_and_send_now(Object(EE_Message_To_Generate_From_Request)) #26 /www/wp-content/plugins/event-espresso-core-reg/core/EE_Module_Request_Router.core.php(232): EED_Messages->run(Object(WP_Query)) #27 /www/wp-content/plugins/event-espresso-core-reg/core/EE_Module_Request_Router.core.php(170): EE_Module_Request_Router->_module_router(‘EED_Messages’, ‘run’) #28 /www/wp-content/plugins/event-espresso-core-reg/core/EE_Front_Controller.core.php(233): EE_Module_Request_Router->resolve_route(‘ee’, ‘msg_url_trigger’) #29 /wordpress/wp-includes/class-wp-hook.php(324): EE_Front_Controller->pre_get_posts(Object(WP_Query)) #30 /wordpress/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #31 /wordpress/wp-includes/plugin.php(565): WP_Hook->do_action(Array) #32 /wordpress/wp-includes/class-wp-query.php(1881): do_action_ref_array(‘pre_get_posts’, Array) #33 /wordpress/wp-includes/class-wp-query.php(3852): WP_Query->get_posts() #34 /wordpress/wp-includes/class-wp.php(696): WP_Query->query(Array) #35 /wordpress/wp-includes/class-wp.php(816): WP->query_posts() #36 /wordpress/wp-includes/functions.php(1336): WP->main(”) #37 /wordpress/wp-blog-header.php(16): wp() #38 /www/index.php(17): require(‘/wordpress/wp-b…’) #39 {main}
|
|
Rio
|
August 13, 2024 at 6:04 pm
Can you provide your site information.
Php Version
EE version
Wp Version
this information can be found on EE -> Help & Support (under extras) -> then look for System information.
does this thing happen before on your install? If this is a new case for you, do you remember what activities or settings you made?
thanks
thanks.
|
|
Rio
|
August 13, 2024 at 6:33 pm
Can you also post the whole error log.
Thanks again.
|
|
Tony
|
August 14, 2024 at 7:07 am
Hi there,
It looks like this is happening when Receipts are being generated, but I’m not reproducing this.
How often is this happening?
Is it happening every time you load a receipt for a registration?
Event Espresso -> Transactions.
Each transaction will have a button to view the Receipt and Invoice. Click to view the receipt, does it deactivate the PM again?
|
|
pds-capcog
|
August 14, 2024 at 7:28 am
WordPress Version: 6.6.1
PHP Version: 8.2.22
MySQL Version: 5.7.44
Event Espresso Version: 5.0.21.p
Event Espresso – Attendee Mover: 1.0.7.p
Event Espresso – Payment Methods Pro: 1.0.2.p
Event Espresso – Stripe Payment Method: 1.1.13.p
Event Espresso – Wait Lists: 1.0.4.p
This is a new occurrence, but unsure of any specific new or changed settings or actions.
@Tony, yes. Spot on. The Stripe Payment Method is disabled every time I go to Event Espresso -> Transactions > View Receipt for a transaction that used Stripe payment. Free or Invoice receipt views/pages do not disable the payment method. Only URLs in this format disable Stripe: /?ee=msg_url_trigger&snd_msgr=html&gen_msgr=html&message_type=receipt&context=purchaser&token=1-c9f481e64363bd42cec2247ac0f3d693&GRP_ID=13&id=246
|
|
Tony
|
August 14, 2024 at 7:49 am
Ok… so do you have a receipt for a paid transaction that did not use Stripe?
Even an unpaid one?
I’m wondering if the same happens there.
You have the Payment Methods Pro add-on active, is that set to do anything with the payment methods on the event that transaction is for? Or is it just loading them all.
Note – I can’t reproduce this currently but we have a ticket open with a possible fix… I’m just trying to see if I can I can reproduce so I can dig into it more
|
|
pds-capcog
|
August 14, 2024 at 7:58 am
We only have “Invoice” and “Stripe” as active payment methods for the site. Most events are Free ($0) and those receipt views do not disable the Stripe method. I can also view receipts for paid transactions which chose the “Invoice” option just fine without Stripe being deactivated. And I can view paid Stripe registration receipts which are still “Incomplete” just fine. It’s only viewing a “Complete” transaction receipt which actively used and was charged via Stripe which appears to disable the Stripe payment method every time.
Although we have the Payment Methods Pro add-on installed, it is not being used on any of the affected events/registrations. Both Invoice and Stripe are active for all events by default, whether free or paid.
|
|
Tony
|
August 14, 2024 at 8:14 am
Very strange!
Would you be ok with me cloning the site locally? To do that I’d use Updraft to create a backup, clone it locally and test, if I can reproduce it I can then troubleshoot further there.
If not I can send you a copy of Event Espresso with the current fix we have for this to see if that prevents it for you?
|
|
pds-capcog
|
August 14, 2024 at 8:34 am
I am happy to try the latest patched version and report back for now. Thanks.
|
|
Tony
|
August 14, 2024 at 9:34 am
This reply has been marked as private.
|
|
pds-capcog
|
August 14, 2024 at 11:40 am
Updated the plugin with this new version. Cleared caches, etc. Doesn’t fix the issue. Still disables the Stripe Payment Method when viewing the receipt. This happens when the receipt link is viewed via admin/dashboard or the registrant views their own after purchase.
I do have a staging site I can give access to if that’s helpful versus making a copy yourself.
|
|
Tony
|
August 14, 2024 at 2:23 pm
Yes, a staging site is fine but I’ll need both WP Admin and FTP/File Manager access.
Which host are you using? If they have a collaborator feature we may already have an account you can add as one for the above.
If not you can send the details over using this form:
https://eventespresso.com/send-login-details/
|
|
pds-capcog
|
August 15, 2024 at 7:16 am
This reply has been marked as private.
|
|
pds-capcog
|
August 15, 2024 at 8:08 am
Following up with the fix:
On a staging site, I deactivated all plugins except Event Espresso ones. Viewing a Stripe receipt link worked and did not deactivate the payment method. So, one by one I activated and tested other plugins and ended up finding the issue.
I have a plugin called “Freesoul Deactivate Plugins” (obvious now, I know) for optimization and compatibility with other plugins. That plugin was set to not load any EE plugins on certain pages and post types. Since this receipt link viewed by an admin or registrant is a normal “Page” post type, it was deactivating EE plugins when viewed. I have added a custom URL to this plugin’s settings to allow EE plugins when the URL matches “*?ee=msg_url_trigger*” which covers invoice and receipts links/views. This has solved the issue.
Thank you for all the time and support. Apologies for the oversight.
|
|
Rio
|
August 17, 2024 at 7:22 am
We’re very happy that you shared to us the caused of your site issue.
We will put this into our note.
thanks again.
|
