Plugin Support
Darian
(@d0153)
Hi @dljordaneku,
Thanks for reaching out. Let me help you with this one.
Upon checking, it appears there is an issue here. Let us investigate this further on our end.
In the meantime, please use the following snippet as a temporary workaround:
add_action(
'admin_init',
static function () {
// phpcs:disable WordPress.Security.NonceVerification.Recommended -- the export handler verifies its own nonce.
if (
empty( $_GET['orders_csv'] )
|| empty( $_GET['event_id'] )
|| ! empty( $_GET['post_id'] )
|| ! isset( $_GET['page'] )
|| 'tickets-commerce-orders' !== $_GET['page']
) {
return;
}
$_GET['post_id'] = absint( $_GET['event_id'] );
$_REQUEST['post_id'] = $_GET['post_id'];
// phpcs:enable
}
);
You can use the Code Snippets plugin to add the snippet. As usual, please test this on a staging site first before applying it to your live site.
Let me know how it goes.
Plugin Support
Darian
(@d0153)
Hi @dljordaneku
I hope you’re doing well. I just wanted to touch base and check in with you. It’s been a little while since we’ve heard from you. I was just curious if you had the chance to try out the recommendation provided above.
Let us know if there’s anything we can assist you with.
Sorry. Yes that is working. Thanks for the help. I am assuming when the next update comes out I can remove the snippet.
Plugin Support
Darian
(@d0153)
Hi @dljordaneku,
Yes, that’s correct. The permanent fix isn’t included in the latest release yet, so please keep the custom snippet active for now, even after updating.
Once the fix is released, it’ll be listed in the plugin’s changelog. At that point, you can safely remove the snippet.
Thanks for your patience while our team works on this.