I just attached the file "tag/taglib.php" to this bug, and sent a big patch to http://moodle.pastebin.com/m3849f2a5 ... These two things together should apply to 19_STABLE (as of 21/02).

Many fixes, changes and probably a few bugs still.

I was in a hurry last night, so here's a bit more information about the patch... It solves the "tag cron error" and the "correlation sql error" and it makes it possible to use any character in a tag (letters, numbers, symbols, anything unicode).

It also removes a bit of code in a few files, using tag_* functions instead.

Hi Mathieu,

yesterday I was looking to the pastebin code above and I found it quite interesting, causing more clean and readable code, for sure. B-)

Anyway one think I personally disagree y the use of arrays to pass parameters to functions and I've seen some of them in your code. Wouldn't it better to use "standard" multiple parameters instead of relying in arrays of them?

Ciao

And another, really minor comment is about WHERE the taglib.php should be? Within /tag ? Or within /lib, leaving /tag for interface and so on... uhm... not critical at all but I love to have libraries in /lib. For your consideration.

Ciao

Thanks for the comments Eloy! Martin also commented on both things.. so, I changed the parameters (removed the array thingy) for the two "public" functions (tag_set and tag_set_add). It wouldn't be so much work to remove all the arrays, and actually, I was trying to come up for a good reason to use them after all while talking with Martin, but couldn't really... so I think I might modify it all, next week.

I had named the file taglib.php to make it obvious, while using moodle, which files depended on tag/lib.php. I renamed it lib.php, and separated a few "tag_print_*" functions in tag/locallib.php. I think that, as tags become more a part of "core moodle", the file should be moved to /lib/taglib.php, but this would require some work on making sure the right files get included .. and I won't attack this on a Friday night.

This is not perfect, though. The tag management interface needs a lot of work, among others...

Great Mathieu,

I really like the API itself, just were some "formal" details. You've done a good job reorganizing and fixing the tag system (I'm sure we'll use it intensively for 2.0 and so on). With arrays out from parameters next week... things will be really better!

Happy weekend anyway, really Friday isn't a good timing to break things, hehe!

Ciao

unfortunately I had to revert the commit, because it was missing a file tag/locallib.php which was preventing admin login and breaking tags code. tried to use the functions from the file above but encountered some other problems.

Mathieu please recommit it on Monday, I will have look at the code and we can polish the remaining details on Tuesday

Thanks for reporting this issue.

We have detected that this issue has been inactive for over a year. It was reported as affecting versions that are no longer supported.

If you believe that this issue is still relevant to current versions (2.5 and beyond), please comment on the issue. Issues left inactive for a further month will be closed.

Michael d.

TW9vZGxlDQo=

As I've commented on some of the sub-tasks... these still seem relevant - unless you take the view that tagging has never taken off with general users, particularly in education, and is therefore not worth the effort.

However, this issue strikes me that it should be an Epic not a task.

Thanks Jenny, I agree with you that it would be better as an epic.