The size, column position and sorting in the search plugins window are not saved #15894

New issue

Open

opened 2026-02-22 02:36:08 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-22 02:36:08 -05:00

Owner

Originally created by @stalkerok on GitHub (Jul 10, 2024).

qBittorrent & operating system versions

Any version, including the latest of CI.

What is the problem?

The size, column position and sorting in the search plugins window are not saved.

Also last path is not saved when selecting local plugin file.

Steps to reproduce

No response

Additional context

No response

Log(s) & preferences file(s)

No response

Originally created by @stalkerok on GitHub (Jul 10, 2024). ### qBittorrent & operating system versions Any version, including the latest of CI. ### What is the problem? The size, column position and sorting in the search plugins window are not saved. ![2024-07-10_134050](https://github.com/qbittorrent/qBittorrent/assets/63958081/ded0a343-2191-4c7b-b7b1-21ee17aecb81) ![2024-07-10_134101](https://github.com/qbittorrent/qBittorrent/assets/63958081/f1134196-6a5e-4e48-b07d-bb0fe728afdb) Also last path is not saved when selecting local plugin file. ### Steps to reproduce _No response_ ### Additional context _No response_ ### Log(s) & preferences file(s) _No response_

deekerman added the

Feature request

Search engine

GUI

labels

2026-02-22 02:36:08 -05:00

deekerman commented

2026-02-22 02:36:21 -05:00

Author

Owner

@stalkerok commented on GitHub (Jan 29, 2025):

@glassez FYI if you have the time.

@stalkerok commented on GitHub (Jan 29, 2025): @glassez FYI if you have the time.

deekerman commented

2026-02-22 02:36:21 -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.)**