You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to add search and filter options for the following areas when adding printers/print queues for the web admin interface?
"Discovered Network Printers" - search or filter via IP or other search criteria to narrow down from the list
Based on the text that's auto populated in discovery it can be hard to determine which printer is which, especially if no IP is
shown. This can be problematic on networks with over 20 printers.
"Model" - search via model number to narrow PPD list
This is especially difficult when setting up an HP printer as the selection list for PPD's is quite long.
Attaching screenshots of said areas.
Apologies if this is the wrong venue for feature requests.
The text was updated successfully, but these errors were encountered:
Ad the first part - the PR #397 should help with that, so please check the PR in question.
Ad the second part - the listed models there are actually drivers which you have on your machine, and CUPS is going to remove the driver support in the near future, so we are not going to implement such filters for model lists.
Would it be possible to add search and filter options for the following areas when adding printers/print queues for the web admin interface?
"Discovered Network Printers" - search or filter via IP or other search criteria to narrow down from the list
Based on the text that's auto populated in discovery it can be hard to determine which printer is which, especially if no IP is
shown. This can be problematic on networks with over 20 printers.
"Model" - search via model number to narrow PPD list
This is especially difficult when setting up an HP printer as the selection list for PPD's is quite long.
Attaching screenshots of said areas.
Apologies if this is the wrong venue for feature requests.
The text was updated successfully, but these errors were encountered: