Repository navigation
Fix OpenVPN and Virtual plugin auto-install failing when they are not enabled - #3567
Merged
Merged
Conversation
Salvialf
added
the
changelog-fix
Mips2648
approved these changes
Oct 9, 2026
Salvialf
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since 856ebbb,
network::dns_create()and the summary virtual creation injeeObjectcheckclass_exists()right after auto-installing OpenVPN / Virtual, before enabling them. The plugin autoloader only loads classes of active plugins, so the check always fails on a box where the plugin was never enabled and the code throws "doit être installé" without ever reaching the activation step (e.g. enabling Jeedom DNS on a fresh box).The
class_exists()checks now run after the activation.