fix: use user ids resulting from custom query by pmpro_members_list_s… #2811
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…ql filter
All Submissions:
Changes proposed in this Pull Request:
Using
pmpro_members_list_sql
filtered query to actually generate the CSV to.I implemented a custom query (with other filters based on user meta) using the pmpro_members_list_sql filter.
I can see the users by the filters I setted in the membership table via UI. If I click the export csv button, the code actually use the custom query to generate an array of users, and then it uses "between" with those array.
If the users are not consecutives, the member UI data and the one extracted via CSV are not equal.
With this change it'll be the same.
How to test the changes in this Pull Request:
pmpro_members_list_sql
Other information:
Changelog entry