Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide a data migration prompt for choosing to migrate module compendium packs during system data migration #1211

Open
aaclayton opened this issue Jul 28, 2021 · 0 comments
Labels
feature request ui User interface related features or bugs ux User experience related features or bugs

Comments

@aaclayton
Copy link
Contributor

Originally in GitLab by @unsoluble1

We spend a lot of Discord support time directing people to store their actors (and other documents) in "shared compendium" modules — getting their stuff into compendiums to reduce world load, while at the same time making them available across local worlds.

But every time a dnd5e update performs a data migration these documents are skipped, because for various reasons automatically migrating all docs in module compendiums might not be a great idea. This leaves many people's primary source of actors (etc) in an unmigrated state.

The current solution to this is to point folks at a pinned Discord post after every migrating system update, with steps to manually migrate module compendiums with a console command. This is not ideal, for I hope obvious reasons.

Proposal: When a 5e system update will be performing a data migration, provide a prompt for the GM user to select available/appropriate module-provided compendium packs to also migrate.

@Fyorl Fyorl added ui User interface related features or bugs feature request ux User experience related features or bugs labels Jul 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request ui User interface related features or bugs ux User experience related features or bugs
Projects
None yet
Development

No branches or pull requests

2 participants