[geeklog-devel] Autotags help?

[Joe Mucchiello]

If you would like some rough code, I had once intended to expand the 
autotag plugin as a control center for autotags. I have code that can 
intercept other plugins' autotags and disable them. Wouldn't be too 
difficult to add permissions based on what was being edited if that 
was needed. I can mail you what I have (it must be for version 1.5.0 
though or perhaps 1.4.1) if you want to look at it.

The way to do this in core would be to force autotags to register 
when the plugin is installed and move a lot of the PLG_collectTags 
code to a database lookup. With the maturity of the plugin auto 
install code, adding a "autotag" line to the autoinstaller array 
wouldn't be hard.

At 04:36 PM 11/22/2009, Tom wrote:
>Speaking of new autotag features,
>
>  I have always wanted to control what autotags a user can use in a post
>(comment, story, forum post, etc..). I have created autotags (mainly from
>the autotags plugin) for all sorts of things and I have about 30 to 40
>different ones in use. Most of them I don't really want a normal user to use
>or even know about.
>
>I haven't really thought of what the best way to actually do this but I
>thought I would throw the idea out there.
>
>
>Tom
>
>-----Original Message-----
>From: geeklog-devel-bounces at lists.geeklog.net
>[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun
>Sent: November-22-09 2:40 PM
>To: geeklog-devel
>Subject: [geeklog-devel] Autotags help?
>
>Now that Geeklog 1.6.1 is out, here's a tiny little feature idea for 1.6.2:
>
>With the increasing amount of autotags provided by Geeklog plugins, it's
>becoming increasingly difficult to tell what they're actually doing. So
>it would be nice if the plugin could provide some help text along with
>the autotag's name.
>
>Simple idea: Let the plugin provide a short text and display that as an
>HTML title attribute.
>
>For backward compatibility, that information would have to be provided
>in the form array('description' => 'autotag'). That's ugly but easily
>fixed by array_flip. Something like
>
>     if ($op == 'tagname' ) {
>         return array_flip(array('staticpage' => 'Link to a static page',
>                                 'staticpage_content' => 'Embed content
>of a static page')
>                          );
>     } else ...
>
>would then be rendered as, say,
>
>     <span title="Link to a static page">[staticpage:]</span>
>
>Of course, there is only limited space available in a title attribute.
>So maybe the plugin should provide a URL to the documentation instead?
>Other ideas?
>
>bye, Dirk
>
>
>--
>http://www.geeklog.net/
>http://geeklog.info/
>
>_______________________________________________
>geeklog-devel mailing list
>geeklog-devel at lists.geeklog.net
>http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
>__________ Information from ESET NOD32 Antivirus, version of virus signature
>database 4628 (20091122) __________
>
>The message was checked by ESET NOD32 Antivirus.
>
>http://www.eset.com
>
>
>
>_______________________________________________
>geeklog-devel mailing list
>geeklog-devel at lists.geeklog.net
>http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
>
>No virus found in this incoming message
>Checked by PC Tools AntiVirus (6.0.0.19 - 10.004.115).
>http://www.pctools.com/free-antivirus/

----
Joe Mucchiello
Throwing Dice Games
http://www.throwingdice.com 



No virus found in this outgoing message
Checked by PC Tools AntiVirus (6.0.0.19 - 10.004.115).
http://www.pctools.com/free-antivirus/