Frog CMS - Tagger 1.1.0 RC1 is here

Tagger 1.1.0 RC1 is here

46 posts, 9 voices

Page: 1 2

Feb 20, 2009 11:32 silentworks 109 posts	After long evening and weekend work I have finally completed Tagger 1.1.0 RC1 for Frog CMS 0.9.5RC1, There has been some new features added in which improves Tagger on a whole allowing the user to worry about less configuration and making it alot easier to get your tags working. I want to say thank you to David for continuous testing of Tagger and Tyler(mtylerb) for his help on development. You should be able to just uninstall current version and install this version without any problems since, tagger doesn’t mess with the tags in the database. You can get the new version from here. Tagger Google Code And you can see the new features added from here. The Hub Edit: I have also moved Tagger over to Github. But if you don’t like Git you could always download the not so updated version from the Google code link above, but I won’t be supporting that one at all.

Mar 22, 2009 04:13 BlueFrog 184 posts	Thanks easylancer. Moving to 1.1.0 RC1 works great.

Apr 16, 2009 20:51 mtylerb 316 posts	I’m so sorry I haven’t been around to help with Tagger. After the birth of my second son, Landon, in December, life got way too hectic. I had to cut back and this took the brunt of it. I haven’t kept very up to date, but I’m glad to see that Frog and Tagger is coming along well. Sorry again!

Apr 20, 2009 05:33 silentworks 109 posts	That is ok mtylerb, I know what its like to have a new born and trying to balance everything else at the same time. I will keep developing Tagger until you get back, its been a but slow lately due to work on a CMS i’m working on.

Apr 23, 2009 06:59 vh 18 posts	I’ve just installed tagger 1.1.0 RC1 and so far it’s working great except for this error message showing up just above the tag cloud on my site: Notice: Undefined variable: limit_set in /var/www/html/frog/plugins/tagger/index.php on line 62 Any help would be great :)

Apr 23, 2009 07:08 silentworks 109 posts	Download the index.php from the SVN, I just fixed it. I will try and add it to the featured download later on today. Also I havent tested it as I don’t have the time to at the moment. Or you can just change line 61 to look like this: `if($limit){ $limit_set = " LIMIT 0, {$limit}"; } else { $limit_set = ""; }`

Apr 23, 2009 07:14 vh 18 posts	I edited the index.php file and it worked like a charm. Thanks so much for the great plugin and quick response!

May 12, 2009 14:32 martinpm 3 posts	There are some issues in PDO with sqlite in some php version 5.x, the rowCount always return 0. So this plugin not working with sqlite. I made some change and work like a charm :). Great plugin.

May 18, 2009 02:23 silentworks 109 posts	Development has been slow for awhile, but now I want to get back up to speed. I have also moved Tagger over to Github. I would like to know what features would you like in Tagger?

May 18, 2009 04:35 martinpm 3 posts	Can you transform all rowCount to query “select count(*)”, because rowCount not always return the correct value. http://www.usenet-forums.com/php-language/360201-sqlite-pdo-numrows-problem.html#post741943

May 18, 2009 06:39 silentworks 109 posts	Your request has been added to the code martinpm except in the enable.php file. I have very limited knowledge of sql lite so I am unable to support it to the fullest. You can get the latest code from the github link above.

May 19, 2009 14:34 martinpm 3 posts	thank you easylancer!!!

May 28, 2009 04:14 wiag 35 posts	Hi, First, a bug report: The nice plugin, a must for my sites anyway, has a little bug that is very annoying. 1 If I have a tag, say 9/11, and I click on that tag in the cloud, the page listing for that tag stays empty. Frog (the mod-rewrite rule?) links it as ‘…/tags/911′. I would expect it to link to ‘…/tags/9-11′. If I change the URL manually, I get still nothing. 2 If I have a tag with accents in the name, lets say ‘exposé’, I get the same problem, it leaves out the special character (’expos’), BUT, changing the URL manually to ‘…/tags/expose’, where I leave out the accent, it works! As Dutch, German and French even more so, use quite some accented and special characters, it would be great if this could be fixed. Nice plugin though, and the new version works nice in 0.9.5 latest SVN version.

May 28, 2009 04:23 wiag 35 posts	Second, I saw it is possible to change your own posts. Easylancer, could you edit your first post, and refer to Github from there? It saves people who scan a thread (like lazy me) some extra downloads and installations :) Suggestion: wouldn’t it be best to change this forum to StackOverflow ? They have a wonderful system for keeping answers up to date and minimise obsolete knowledge. If you don’t know what it is, I absolutely recommend a visit. Any opinions on this matter? As for that, the Frog plugin page seems a bit quirky, unmaintanable, and with some old references as well… Nonetheless, I think Frog’s simplicity, maintainability and foremost flexibility rocks.

May 28, 2009 04:43 silentworks 109 posts	Just when I thought Tagger was working perfectly, now a bug. waig I will look into this when I get some time and let you know when its updated. BTW why would you have a tag called 9/11, this is not a normal tag convention.

May 28, 2009 04:49 wiag 35 posts	Easylancer, thanks in advance, and besides the bug: it gets better and better and I still love it ;)

May 28, 2009 04:56 wiag 35 posts	Maybe you are right about the ’9/11’ tag, but to me, when I put my user hat on, I would say ’9/11’ is the best syntactic way to describe the event. If possible, technology should be able to handle it. With some proper input handling by frog (tag-field) and output handling (tagger), like the one used for the slug field, it should work I think. Just my two cents anyway.

May 28, 2009 05:40 silentworks 109 posts	Ok did some quick research, the way how Frog save tags is incorrect, because if your store 9/11, you cant actually put that in the url, this should be stripped before it gets stored so it is 911 but then again because a tag is also the name and slug it is hard to achieve this. I will need to use a different regex to work this out but it might lead to over complexity.

May 28, 2009 05:47 wiag 35 posts	Easylancer, if problem 1 (‘9/11’) will make things too complicated, problem 2 (éáö…) is probably the worst from a user perspective. I’m not sure they can’t be tackled by the same algorithm, I would guess it can, but if it’s easier to fix 2 I would certainly recommend fixing that one… And yes I know, RegExes can be very time consuming. Thanks for your time!

May 28, 2009 05:57 wiag 35 posts	Less important, I wouldn’t mind having the option not too override the case in settings: Next to ‘lowercase’ and ‘UPPERCASE’ the option ‘As orginal’ or something of the sort. Also you might include in the documentation a reference to the CSS-handlers one might want to style, like `ul.tagger {}` and maybe `ul.tagger a:link {}` `ul.tagger a:hover {}` etc… If I start being obnoxious just let me know ;)

May 28, 2009 06:06 silentworks 109 posts	Less important, I wouldn’t mind having the option not too override the case in settings: Next to ‘lowercase’ and ‘UPPERCASE’ the option ‘As orginal’ or something of the sort. I have no clue what you mean by that, I will include the css handlers in the documentation. I have also solved the issue with expose but not the 9/11 asyet. I will commit it to Github soon, just need to run a few test scenarios. Don’t want to fix something and bread something else.

May 28, 2009 06:13 wiag 35 posts	Ah, my bad, sorry! On the Settings page for Tagger, you have the option how Tagger displays the Tags in the tag cloud, and you have two options: I read the one saying Uppercase to be: make a tag Uppercase to display as UPPERCASE. But it means To leave the case of the tag unchanged. Sorry for the confusion. Maybe the options could be named a little clearer? UPDATE: If you want me to test it on my system just send it to ‘frog at godswonder.nl’…

May 28, 2009 06:26 silentworks 109 posts	Ok i have checked in the code to Github repo. wiag: I don’t think there is anyway for me to do the 9/11 scenario, because frog saves the tag as 9/11 and if I was to remove that for the url slug i would have to replace it again when the code searched the database and there is no way of knowing where the / came from. URL Slug for 9/11 would be http://www.website.com/tag/911, but in db it is stored as 9/11 so when the tag page gets loaded it will search for 911 because of the slug, there is no way for me to find 9/11 because I have no reference to it. Tagger is only using what is already available in Frog CMS.

May 28, 2009 06:45 wiag 35 posts	I see your problem. I will change the tag usage in my site. I think Frog should store / in the tag field as some kind of HTML entity in the db, as it is for display purposes, but as it does not… I will check your version out right now, and report the results. Thanks!

May 28, 2009 07:06 wiag 35 posts	Hi, as it didn’t fix my link problem I took a look at your code. Clever function i’d say, but you missed at least the ë etc. Here’s my minimal addition: `$search = array(' ','ä','á','à','â','ã','ª','Á','À','Â','Ã','é','ë','è','ê','Ë','É','È','Ê','ï','í','ì','î','Í','Ì','Î','ö','ò','ó','ô','õ','º','Ó','Ò','Ô','Õ','ü','ú','ù','û','Ú','Ù','Û','ç','Ç','Ñ','ñ'); $replace =array('-','a','a','a','a','a','a','A','A','A','A','e','e','e','e','E','E','E','E','i','i','i','i','I','I','I','o','o','o','o','o','o','O','O','O','O','u','u','u','u','U','U','U','c','C','N','n');` Would there be some way to do something about the ß character, which in German is written also as ‘ss’ when ß is not available? I don’t know for sure, but maybe just replacing it with one ‘s’ is best. Thanks for the update!

Page: 1 2