Search Plugins export and import #16125

New issue

Open

opened 2026-02-22 02:49:20 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-22 02:49:20 -05:00

Owner

Originally created by @daVe55w on GitHub (Oct 1, 2024).

Suggestion

Add the feature to export and import search plugins to make it simple to reinstall search plugins if qBit crashes or a version update removes plugins (as happened to me with v5.0.0 update) or if installing qBit on another computer.

Use case

No response

Extra info/examples/attachments

No response

Originally created by @daVe55w on GitHub (Oct 1, 2024). ### Suggestion Add the feature to export and import search plugins to make it simple to reinstall search plugins if qBit crashes or a version update removes plugins (as happened to me with v5.0.0 update) or if installing qBit on another computer. ### Use case _No response_ ### Extra info/examples/attachments _No response_

deekerman added the

Feature request

Search engine

labels

2026-02-22 02:49:20 -05:00

deekerman commented

2026-02-22 02:49:29 -05:00

Author

Owner

@Mike-Litoreece commented on GitHub (Oct 3, 2024):

AT this point it's better to not install 5.0.0. Unrecognnizable low quality and with so many serious bugs. Something must have happend. People fired or change of ownership perhaps.

@Mike-Litoreece commented on GitHub (Oct 3, 2024): AT this point it's better to not install 5.0.0. Unrecognnizable low quality and with so many serious bugs. Something must have happend. People fired or change of ownership perhaps.

deekerman commented

2026-02-22 02:49:29 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 25, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 25, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**