Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 EE4: Exporting registrations after filtering not possible | Event Espresso - Staging Server
I am using the latest version of EE4 and just realized that it is not possible to export the CSV of the registrations after I filter it. So right now, if users register for an event, but does not complete it, it adds them to the registration list, sometimes, I just want to export and filter those who have paid but once I apply a filter, the option to export is no longer there. Is this intentional or is it a bug?
If it is intentional, could we change it such that one may export anything they want after it’s filtered?
Currently the filters run against all registrations. I’ve created a report for the developers to review so this can be considered for a future version of Event Espresso.
the filters are not the issue…as least to me….for now. The issue is that, I cannot export my list of registrations after I apply a filter. I am not sure why running against all registrations would affect my case.
I want to be able to look at all of the registrations of an event, filter them, then export the filtered results. That is not currently possible. As soon as I apply a filter, the export button disappears.
That is also related to what I described earlier. The filter applies to all registrations. However, the export button is available when you are viewing registrations for a specific event.
—
Lorenzo
Viewing 3 reply threads
The support post ‘EE4: Exporting registrations after filtering not possible’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.