Textpattern Support Forum

Hi Stef,

you know, I like to run plugins from plugin_cache_dir. It makes my life easier, it let me do versioning and other crazy things, like having a /txp_plugins/ folder, full of TXP plugins (and its versions) somewhere on my system and symlink each plugin I need on a per-TXP-installation basis.

But there is one thing that I miss from installing/activating/running plugins from DB, and that is, that some plugins (glz_custom_fields, arc_twitter, and others too), when activated, they add an “Options” link in the “Manage” column (on “Admin -> Plugins”).

Do you think it would be possible to have this “Options” link on the “Publish” column, in “Extensions -> Plugin composer”, for those plugins that have options.

If not, there is no way to easily access/find-out that a plugin have an Options tab. And that always catch me…

Of course, it may be the price to pay for being so über-cool and run plugins from filesystem, but, hopefully, it’s just that you forgot to add it :)

Thank you.

Hi Bloke,
Thanks for the prompt reply.
Applied the change, job done. Thank you very much for that one too.

I can live with the [Options] link right there, next to the plugin name. Someday, having it on the Publish column will be a nice thing too :)

Amazing what less than 24 hours of background processing can do. Think I’ve figured out how to handle textpacks:

1. Allow you to specify a prefix for each plugin which I’ll stash somewhere (probably in a tmp file). It’ll default to the name of your plugin
2. Add a smallish textarea (or two) to allow you to add strings one by one (or maybe one per line or something so you can add more than one at once)
3. Add a dropdown nearby which lists all the installed languages you have
4. The strings will be inserted directly in txp_lang under the given language, thus you can use them immediately in your code with gTxt('abc_plugin_some_string', array('{rep}' => 'replacement'))
5. At export time, the plugin composer will collect together all lang entries that are prefixed with your given prefix, group them by language and create a textpack from them on the fly. It will insert that at the relevant place in the plugin
6. I’ll add a dedicated export button at the bottom so you can export the pack as an entire file or as one pack per language for standalone redistribution
7. I guess I’ll also need a management screen so you can see which strings have been installed for the current plugin and edit, rename or delete them as necessary. Might be nice to do this in a floaty panel like wet_quicklink so you can see at a glance which are in use, filter them and maybe even insert the names raw or as a formatted gTxt() string into your code at the cursor location. Not sure yet if that’d be of any use
8. When editing the template file directly in the plugin cache dir, the strings will be written into the file as you go

Anyone see any flaws in the above, or can think of anything better / neater?

Last edited by Bloke (2010-11-04 14:30:26)

Until I can get round to the Textpack thing I mentioned above, here’s a quick bug fix update to v0.92.

Fixes:

• Options link for plugins from cache dir (thanks maniqui)
• Escaping of exported php files (thanks maniqui)
• Escaping when importing from PHP file (hopefully… never fully got my head round magic_quotes_gpc in PHP)
• jQuery bug on setup panel
• Cosmetic tweaks:
  • plugin_cache_dir section only displayed if there are valid PHP files
  • View Help link improved slightly
• Extended resizer cookie to one year expiry

Should tide you over until Textpack support comes along. Enjoy.

MarcoK wrote:

Is a bug?

Yes, sorry. When I fixed the jQuery toggle behaviour I broke something else. Will fix asap.