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

Adding custom plugin does not load in future sessions after first use of plugin. #1993

Open
slothoth opened this issue Feb 15, 2025 · 0 comments

Comments

@slothoth
Copy link

slothoth commented Feb 15, 2025

Preflight Checklist

  • [x ] I agree to follow the Code of Conduct that this project adheres to.
  • [x ] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

You must agree to search and the code of conduct. You must fill in this entire template. If you delete part/all or miss parts out your issue will be closed.

Describe the bug
A clear and concise description of what the bug is.
When developing new plugins on Windows, there is a fault where the plugin can only load the first time when rebooting draw.io.
To Reproduce
Steps to reproduce the behavior:

  1. Make a js test plugin with this code:
Draw.loadPlugin(function(ui) {
    console.log('Plugin initialized');
}
  1. Load the plugin by going to Extras>Plugins>Add>External Plugins>Select File and choose your file
  2. Close and relaunch drawio, making a new blank diagram. Check Help>DeveloperTools>Console and see the log message works
  3. Close and relaunch drawio a second time, making a new blank diagram. Check Help>DeveloperTools>Console and see the log message is not present, and so the plugin has not loaded. Open Extras>Plugins to see the plugin still shows as listed.

Expected behavior
A plugin that is added and says it is loaded in the dialog persists across sessions.

Screenshots
If applicable, add screenshots to help explain your problem.

draw.io version (In the Help->About menu of the draw.io editor):

  • draw.io version v26.0.9

Desktop (please complete the following information):

  • OS: Windows 10

Additional context
Add any other context about the problem here.
Done using a fresh install with default settings, beyond running with the --enable-plugins argument

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

No branches or pull requests

1 participant