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

CorreoMQTT not detecting manually installed plugins after selecting "no" in update search prompt #143

Closed
DezzardHD opened this issue Apr 11, 2023 · 0 comments · Fixed by #146
Assignees
Labels
bug Something isn't working
Milestone

Comments

@DezzardHD
Copy link

Describe the bug
When attempting to manually add plugins to CorreoMQTT, the plugins may not be recognized if the user selects "no" in the prompt during installation that asks whether to automatically search for updates and plugins.

To Reproduce
Steps to reproduce the behavior:

  1. Uninstall CorreoMQTT (including the CorreoMQTT application folder).
  2. Install CorreoMQTT.
  3. During installation, a prompt will appear asking whether CorreoMQTT should search for updates and plugins automatically. Select "no".
  4. Copy a .jar file to the plugins/jars folder.
  5. Restart CorreoMQTT.
  6. Open the plugin settings (under tools).
  7. Check if the plugin you added is recognized by CorreoMQTT.

Expected behavior
The user should be able to manually add a plugin to the jars-directory, restart the application, and have the plugin recognized, even if they selected "no" in the prompt during installation. It would be helpful to provide instructions on how to manually add plugins.

Desktop:

  • Operating System: macOS Ventura 13.0.1
  • CorreoMQTT Version: 0.14.2 (installed from .dmg Installer)

Additional context
To resolve this issue, the user had to uninstall and reinstall CorreoMQTT, including deleting the CorreoMQTT application directory, and select "yes" in the prompt during installation.

@DezzardHD DezzardHD added the bug Something isn't working label Apr 11, 2023
@farion farion added this to CorreoMQTT Jun 4, 2023
@farion farion added this to the 0.15.0 milestone Jun 4, 2023
@farion farion self-assigned this Jun 4, 2023
farion added a commit that referenced this issue Jun 4, 2023
@farion farion mentioned this issue Jun 4, 2023
1 task
@farion farion moved this to In Progress in CorreoMQTT Jun 5, 2023
farion added a commit that referenced this issue Jun 6, 2023
* Fixes #143, Fixes #134

* Improve error handling for version check
@github-project-automation github-project-automation bot moved this from In Progress to Done in CorreoMQTT Jun 6, 2023
farion added a commit that referenced this issue Jun 6, 2023
* Fixes #143, Fixes #134

* Improve error handling for version check
farion added a commit that referenced this issue Jun 7, 2023
* Use JDK 17 in code, added module-info.java, removed/refactored some non-modular deps

* Updated workflows

* Improved CodeQL

* Fixes #143, Fixes #134 (#146)

* Fixes #143, Fixes #134

* Improve error handling for version check

* Disable JPMS for now as not all libs are ready and jlink does not work

* Fixes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants