@silvieg : did you read my long message. I make shorter : Titles of articles can be used into prefs into cache. Then part of init query (restore prefs) if these titles contains " ' " (simple quote) that are not escaped this crashes tikiwiki (4.x), unknown for 5.x (not tested. New Forum Posts: Where do i change the invitation text? - http://tikiwiki.org/tiki-view_forum_thread.php?forumId=4&comments_parentId=36879 They can't be escaped because the search into database the fails because they are store not escaped. Many various solutions, which one is the best. They can't be escaped because the search into database will fail because they are stored not escaped. Many various solutions, which one is the best. *whew* offical news releases for 5.0 beta have been delivered :-) better late then never :P hello, after six years i return to tiki huhu? nobody here, will check later im here tikiwiki: 03chealer * r26598 10/branches/5.x/styles/thenews.css: tikiwiki: [FIX] Calendar names looking partly struck in popups with thenews (r15918 regression) tikiwiki: Cf: http://article.gmane.org/gmane.comp.cms.tiki.cvs/54522 tikiwiki: 03nkoth * r26599 10/branches/5.x/lib/tikilib.php: [FIX] Prevent plugin execution if stripplugins is being requested tikiwiki: 03nkoth * r26600 10/branches/5.x/lib/tikilib.php: [FIX] Snippets should not contain line breaks polom Recent Bug: Tracker item: #3111 - - Judy theme is not functioning - http://dev.tikiwiki.org/tiki-view_tracker_item.php?trackerId=5&itemId=3111 good morning changi: is it possible to have a svn up on dev? New Forum Posts: Changing Username Character Pattern causes failure to register - http://tikiwiki.org/tiki-view_forum_thread.php?forumId=4&comments_parentId=36883 tikiwiki: 03jonnybradley * r26601 10/trunk/ (2 files in 2 dirs): tikiwiki: [NEW] First phase of a freetag plugin, to show similarly tagged objects, or objects with a specific tag or set or tags. tikiwiki: Much more to do on the rendering of specific obejcts. Only articles, files and wiki pages done so far. @sylvieg: yes it is :) Thanks tikiwiki: 03jonnybradley * r26602 10/trunk/ (69 files in 23 dirs): [MRG] Automatic merge, branches/5.x 26526 to 26600 polom du jour hi morning all jonnyb: lol hi changi and all morning RavenC hiya jonnyb Hi Kimberlee :) Hi johnyb hi Kimberlee an' RavenC (beginning to sound like a rap - stop it!) lol rappin with an English accent. tikiwiki: 03sylvieg * r26603 10/branches/5.x/lib/wiki-plugins/wikiplugin_trackerlist.php: [FIX]TRACKERLIST: move the test of filterfield validity before adding the user filter that is not always in the fields list (fix optimization 26395) changi: can you do another svn up on dev :-) this should fix the list yours problem polom polom luciash jonnyb: hi :) jonnyb: nice reveal on dev list, i als o see it as a blocker having no cached JS/CSS... i also wondered back then if no wiki cache for registered users was such a good idea (i would say the contrary) i thought i was just for admins (no cache) iirc it was for all non-anonymous but i might be wrong :-/ anyway, i would prefer it optional :-p even admin can get frustrated with slow tiki sounds like a big fix is needed to cover various perms (by group maybe?) if you are ready to have a cache for each possible setting of perms - registered can be cached it is not by group basis - it is by set of perms... aren't perms derived from groups though? (hi sylvieg) hi well, i didn't see a problem having wiki cache for registered as we had before because you always could make an individual wiki page set to 0 cache when necessary but a page can have something like {GROUP(groups=A)}sdffdg {GROUP(groups=B)}sdfsdfs so depending a user is in A or B or A and B... but wouldn't caching by groups deal with that? would be nasty when group membership changes though... i don't see a reason why to complicate it or try to be super-clever over the group perms/admins, people setting up a "sensitive" page should just know they need to set the page to 0 cache, that's all... isn't it ? why trying to be more clever than users ? but i have no idea how it relates to the headerlib/js/css caching problem was absent for longer time recently, sorry a user has no understanding that a page with {GROUP()} for instance can not be cached it's his/her problem... they should read the docs when using advanced plugins ;) isn't it plugin to be approved anyway ? (hmm, maybe not) but maybe we could introduce wiki "cache by section" as we have the edit by section ? it is an example - there aer other plugins too (include page for instance) just a dreamy idea i know, probably not that easy to code as it sounds it was cached a long time ago for registered but too many trouble with people who do not read the doc ;-) or maybe we can detect if there are the wiki cache sensitive plugins present in the page content to switch the wiki cache to 0 automagically yes [perhaps - if the page has one plugin - no cache well, i would do it as we do with the approval plugins not all plugins need that 0 cache like CENTER etc. but IMG needs as there is a perm check sure, it would need to be determined i think the (one of the) problem is that there's only a place for one chunk of data for each cached page, and it goes in the tiki_pages table. It would seem like that should be replaced by a file/memcache cachelib system, then each permutation of groups could be cached separately (with it's headerlib info) but that's A Big Thing yes, hopefully we can do that for 6.x but not for 5.x i think i would prefer to rollback to pre-anononlycache time though or make it per plugin check - if plugin can be cached, cache it, otherwise 0 cache we can simply add it in the plugin setup args, can't we ? like 'cache' => 'y' what to do with the headerlib thingy i don't have a clue though @sylvieg: on going hello, i'm trying to include some protovis visualizations (http://vis.stanford.edu/protovis/) on my wiki articles and wondering how should i set this up. i know i need to put the protovis .js somewhere so i can call it with "
" on the article, so it will read the "