I always fill like I did a bad thing when I edit the lib-common.
Can you make it will autolinks from plugs are pulled separately in the theme files and not with allowed HTML.
Few good reasons why. Some sights like the one I am working on has plug-ins that we just don't want people to know about.
Some I'm working on and don't want people pulling them.

Also a good reason is so we can list them for plugs that it's a good idea.
Say the forums. I think most if not all tags work in the forums.
So a tool tip can be easily be added. Also I am working on a way to add them to my admin story just because there is so many I can't remember them all.
And on my page it just reads "All HTML is allowed".

I do know how to turn them off in the cofig. But I don't want them stopped.
I still want to use them just not till everyone about them.

So to do it I had to go in the lib-common and commit it out.
It just makes me fill dirty and also I may forget when I update.

Yeah, there should probably be a way to make certain autotags only accessible to users with certain permissions. Not just hide them, make them not work for those that are not allowed to use them. A bit like the separation into HTML for admins and normal users.

I've had that idea before, but haven't really thought it through yet. Since most autotags are coming from plugins nowadays, we would need new plugin API functions and all that ... Someone with some ideas submit a feature request, please.

bye, Dirk

Version 2.0 of my autotags plugins jumps through a few hoops (but no core edits) to allow you to turn autotags (even ones from other plugins) on or off. I was thinking about making them follow GL permissions but I wasn't sure what that would do. If a story has a tag in it, does the reader need the permission to see the output?

But I need to clean that up before releasing it but I have no time with the calendar plugin on my plate.

Would a new API be needed or will plugins not just need to add this level of control as a permission?

Adding a generic permissions 'group allowed' to use pluginABC autotag in pluginABC would not be hard for plugin developers to do. Question is: will one generic 'enable autotag' access control be sufficient.

Or - will sites want to enable autotags usage in different contexts
allows the filemgmt autotag in stories but not in the forum for group logged-in users
allow the filemgmt autotag anywhere if in group 'members'

---

Geeklog components by PortalParts -- www.portalparts.com