Taggable for ExpressionEngine 2.0.1 is now in BETA.
Development and Programming
I’m happy to announce that I’ve launched the free public BETA of Taggable, my folksonomy engine for ExpressionEngine 2.0.1 has been released. Taggable is an easy-to use, powerful folksonomy engine designed exclusively for ExpressionEngine 2.0. It works with any channel entry, so you can add tags to your blog, news archive, pages, photo gallery - anything that’s powered by a channel! It features a rich set of template tags that let you list, filter, and display tags and their entries with no code necessary.
Features
- A great user interface for browsing and displaying tags
- Tight integration with the publish form
- Autosuggest powered by Alchemy
- A set of powerful template tags
- Loads of developer hooks for additional functionality
Pricing
For the BETA, Taggable is free. However, I won’t update it with any bug fixes or feature requests until 1.0, which is when Taggable will become a commercial product. I’m hoping to get 1.0 out next week sometimes, so be quick! Taggable 1.0 will sell for €39 per site license.
More Info?
Head over to http://gettaggable.com for more information about Taggable, to access the support forums and to download and try out the BETA!
Thanks!
Jamie
Installed okay, but clicking on Taggable in modules screen after install gives three errors:
Object of class CI_Table could not be converted to string databaseDB_drive.php (line 1242)
Object of class CI_Table to string conversion databaseDB_drive.php (line 1242)
Table my_database.exp_Object doesn’t exist SELECT COUNT(*) AS numrows FROM exp-Object
Hey Russ,
Are you running EE2.0.1? You have to be running the most recent build or else everything will fail spectacularly!
Jamie
Yah …. 2.0.1 PB01. I tried de-installing, which worked as expected (deletion of data from actual database). Reinstalled. Same error messages.
Spectacular failures are the most fun and are a specialty of mine.
Another data point: until deinstalled, even the simplest exp:channel tags in templates do not throw an error …. or display the results of the query they represent. For instance:
{exp:channel:entries channel="this_one" entry_id="1"}Nothing.
Once Taggable is deinstalled, records retrieved from database are shown as expected.
Jamie - thinking this is better posted to forum than to our offline emals.
I set up clean 2.X sandbox and Taggable worked. So, good news. Your code must indeed be … spectacular.
I returned to original site and now did the usual tedious install/uninstall, not only of Taggable, but modules, extensions, plugins and ….. accessories. Bingo. Not just any accessory failed but only the News and Stats accessory. it is colliding big-time with Taggable and producing the error messages I reported.
Sorry I didn’t do this at the start - would have been standard operating procedure for me on 1.6.8. But I’m guessing this is specific enough that it may help you track down the issue. If access to my site is still useful, just ping me offline and we’ll continue down that road.
(N.B. Did I miss something or can I not find the needed beta license key to do stuff with Taggable once installed?)
You can still use Taggable without the license key… it’ll just complain about it 😊 like EllisLab, the license key system is really built around trust.
Could you move this over to the Support Area? I’d like to keep all the support stuff over there. Cheers!
Jamie
Jamie,
So Taggable is looking pretty cool. I haven’t tried it yet. Just a quick question: how stable is the module? I have a production site running on EE 2.0.1 (www.pinedaledental.com) and I am already pushing my luck by using beta software in production… I don’t want to push my luck too far. 😉 What about browser dependent issues? I know EE 2.0.1 has not been playing well with IE 7 & 8 (although there are workarounds). My client uses Mac for personal stuff but his staff and office all use IE so if I implement anything it needs to play nice with both PC and mac browsers.
Looks pretty promising. I’ll probably check it out on my local machine but I’ll hold until later if needed.
Cheers, Wes