Closed melohagan closed 7 months ago
The app_metadata
document for an app DB contains a list of plugins that are used, when an app is imported a new app metadata document is generated, we need to copy over the list of plugins used from the old app metadata when importing apps.
This issue has been automatically marked as stale because it has not had recent activity.
Hey! Having the same issue here.
Can you provide instructions to do the export/import workflow correctly with custom plugins?
Like where is this app_metadata
? Is it something that would have to be copied manually, or is it on the roadmap to export it with the export function?
Thanks!
Edit:
Ok I just found the line in db.txt
file... I guess it is to be implemented to restore usedPlugins
from the exported app into the imported one?
Or is there another way to "boot up" plugins without actually having to add one on an app screen for them to show? It's not really a big deal but kinda annoying...
Thanks again!
This issue has been automatically marked as stale because it has not had recent activity.
This issue is still present on 2.32.17.
Hosting
Describe the bug When importing an app that uses custom plugins into a new environment, you have to import the necessary plugins. The screens do not immediately update to begin showing again. You have to add another instance of the same plugin to reload the existing one.
To Reproduce Steps to reproduce the behavior:
Expected behavior Upon importing custom component plugins, existing apps should reload the components without having to insert another component.
Screenshots Header Image is missing
Add another header image, the existing one will now reload
App Export Hugo Plugin Submission-export-1673001481044.tar.gz
Additional context Plugin Github URLs used: