No bulk delete with cancelled subs?

[cathysarisky]

Issue Summary

My client had some subscriptions accidentally cancelled. (It's a long and snarly story.)

We were able to restore them in Stripe, but although Ghost shows the new payments as members activity, it doesn't pick back up the subscriptions.

I can't re-import them, because they already have customer IDs.

While I can delete them one at a time, I cannot bulk delete them and re-uploading them. (One-at-a-time deletion and then re-uploading the csv of customer IDs works, but is super tedious.)

Steps to Reproduce

see above

Ghost Version

5.109

Node.js Version

na

How did you install Ghost?

na

Database type

MySQL 8

Browser & OS version

No response

Relevant log / error output

Code of Conduct

• I agree to be friendly and polite to people in this repository

[jatinder14]

Hi @cathysarisky
Could please attach some screenshots for my reference

[cathysarisky]

Hi @cathysarisky Could please attach some screenshots for my reference

Sorry, not without creating a repro install without my client's proprietary data, no. But if you're serious about fixing it, here's a slightly more detailed repro case. Install Ghost, link Stripe, (be sure to set up webhook secrets if running locally, using the Stripe CLI), make a paid user subscription in Ghost, verify that the user shows up as paid. Cancel the subscription over in Stripe. Repeat for a couple users, then filter on cancelled subscriptions, and look for the deletion button under the gear. (It won't be there.)

This is likely not a good first issue, as it's likely baked into both Ember /and/ the api and permissions system.

[ErisDS]

The bulk delete action has been hidden for subscription-related filters, because the underlying data model for members <-> subscriptions doesn't work properly with filters.

When you search for a member with a cancelled subscription, it looks for ANY cancelled subscription, which means the member could have cancelled in the past and resubscribed since - but that wouldn't be clear from the filter.

This means bulk deleting can remove active members - which is not good.

We've got a plan to get this fixed up, but for now I recommend manually verifying which members you want to delete, and scripting it against the api.

Gonna close this, as I wouldn't accept a PR that fixes this bug, without fixing the underlying issue - if that makes sense?