Note: Originally posted at CivicSpace.

URLFilter is an input filter, not a module, and therefore should not be treated like a module in the UI.

When I enable a module, I expect something to change—or for a new functionality to be exposed. This is not the case w/ URLFilter, since I have to go admin my input filters to get it to work.

A new workflow for installing and enabling input filters needs to be created.

Comments

Bèr Kessels’s picture

Bèr Kessels commented

a big -1 from me.

First of all technical: a filter lives in a module, thus a module must be installed.
Secondly, taken #1 in consideration: you would have to go to /admin/modules and then to /admin/filters to switch this module on.

Thirdly (most important) we would need YAMS (yet another module system) to handle your request. Again: not an option, IMO.

And last: I am very (as in very) busy, but I am rewriting most of the weblinks, to make it (yes, there we are again) a "bundle". ;) Urlfilter will be part of a standard filter system in the weblinks bundle. Feel free to be creative in that, and propose a feature in that direction (?)

Bèr

PS if you agree, can you close this issue?

deekayen’s picture

deekayen commented
Component: User interface » Documentation
Status: Active » Closed (works as designed)

It's been a year, the extra step isn't that painful, and it's documented.