Skip to content

Reorder plugin/component order in package#149

Merged
JLTRY merged 2 commits intomasterfrom
parapente/issue148
Jul 24, 2025
Merged

Reorder plugin/component order in package#149
JLTRY merged 2 commits intomasterfrom
parapente/issue148

Conversation

@parapente
Copy link
Collaborator

Fixes #148 where the plugins would not be enabled after a new installation of the extension.

Also when the component is reinstalled after an update, deactivated plugins are not re-enabled automatically.

@yild
Copy link
Contributor

yild commented Jul 19, 2025

Ok, installation is ok, update - disabled plugins stay disabled, but when uninstallation I get result as below, BUT it's same message when original 4.1.5 was installed and uninstalled.

obraz

@parapente
Copy link
Collaborator Author

@yild you probably selected all packages and selected to uninstall. If you just uninstall the package, all parts of the extension should uninstall without all these warning messages.

@yild
Copy link
Contributor

yild commented Jul 19, 2025

@parapente yup, that's what I did :)

My mistake

obraz

@JLTRY JLTRY merged commit a218333 into master Jul 24, 2025
@parapente parapente deleted the parapente/issue148 branch July 24, 2025 21:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Plugins not enabling after fresh installation

3 participants