Issue Summary
When exporting content & settings as JSON, the filename includes the blog name (e.g. myblog.ghost.YYYY-MM-DD.json), which makes it easy to identify the source site.
However, when exporting members as CSV from Dashboard → Members → Export, the filename does not follow the same convention — it lacks the blog name (currently members.YYYY-MM-DD.csv), making it harder to identify which site the data comes from when managing multiple Ghost instances.
This is the same problem that was reported and fixed for analytics CSV exports in #28227 — the fix should be applied consistently to the members export as well.
Steps to Reproduce
- Go to Settings → export content/settings → JSON file is named with the blog name ✅
- Go to Dashboard → Members → Export → filename does not include the blog name ❌
Expected Behavior
The members CSV export should follow the same naming convention as the JSON export and the (now fixed) analytics CSV export, e.g. <site-name>.ghost.members.YYYY-MM-DD.csv.
Ideally, when an export is filtered (e.g. "Paid members"), the filter could also be reflected in the filename.
Why
Consistency across exports and easier file management when handling multiple Ghost sites.
Issue Summary
When exporting content & settings as JSON, the filename includes the blog name (e.g.
myblog.ghost.YYYY-MM-DD.json), which makes it easy to identify the source site.However, when exporting members as CSV from Dashboard → Members → Export, the filename does not follow the same convention — it lacks the blog name (currently
members.YYYY-MM-DD.csv), making it harder to identify which site the data comes from when managing multiple Ghost instances.This is the same problem that was reported and fixed for analytics CSV exports in #28227 — the fix should be applied consistently to the members export as well.
Steps to Reproduce
Expected Behavior
The members CSV export should follow the same naming convention as the JSON export and the (now fixed) analytics CSV export, e.g.
<site-name>.ghost.members.YYYY-MM-DD.csv.Ideally, when an export is filtered (e.g. "Paid members"), the filter could also be reflected in the filename.
Why
Consistency across exports and easier file management when handling multiple Ghost sites.