[00:00]  redflo joined #tikiwiki
[00:01] fabricius cool
[00:01] fabricius so after two days nonstop I have to restart
[00:01] fabricius brb
[00:20]  redflo1 joined #tikiwiki
[00:22]  rodrigoprimo joined #tikiwiki
[00:58] Tiki|bot Recent Bug: Tracker item: #4271 - - Not possible to comment a tracker entry - Tiki 8.4  - http://dev.tiki.org/item4271
[01:22]  goj_killedByISP joined #tikiwiki
[02:07]  yanick_ joined #tikiwiki
[02:07] yanick_ hi, how do I upgrade from 7.1 to 9.x ?
[02:08] yanick_ when I check for upgrade, it tells me I'm up-to-date
[03:08]  goj_killedByISP joined #tikiwiki
[04:47] CIA-75 tikiwiki: 03chibaguy * r42519 10/branches/9.x/templates/comment/list.tpl: [ENH][bp/r42517] Increased heading size of comment title to distinguish it from body text; moved avatar out of post body. Todo: CSS improvements.
[04:49] CIA-75 tikiwiki: 03chibaguy * r42520 10/branches/9.x/styles/layout/design.css: [FIX] [bp/r42516, 42517] An ordered list is used to display comments, but they shouldn't be numbered. Article comments don't need to be indented by default.
[05:38] yanick_ hi, how do I upgrade from 7.1 to 9.x ?
[07:40] jjgoth amette: I couldn't send to the devel list
[09:24]  jacmoe joined #tikiwiki
[09:30]  xavi joined #tikiwiki
[09:39]  redflo joined #tikiwiki
[11:31]  dennmans joined #tikiwiki
[12:06]  wu-lee joined #tikiwiki
[12:08] wu-lee hello, I'm running into encoding issues having upgraded 1.8 ----> 9.0
[12:09] wu-lee the Mysql DB appears to be utf-8 encoded correctly now, judging by my checks
[12:09] wu-lee but certain characters are rendered in webpages with "garbage" characters prefixing them
[12:10] wu-lee local.db says $client_charset='utf-8'
[12:11] wu-lee s{local.db}{db/local.php}
[12:11] wu-lee oddly if I set it to latin1, it appears to fix the rendering, but this seems reverse to what I'd expect
[12:23] wu-lee HTTP and HTML headers both say utf-8
[12:23] wu-lee I suspect something inside tiki is double-encoding the utf-8 text from mysql
[12:52] xavi wu-lee, see the doc page for upgrade, specially the section about encodin issues
[12:52] xavi there was a change between 5.0 and 5.1
[12:52] * xavi fetching a url for you....
[12:53]  changi_ joined #tikiwiki
[12:53]  panamaus joined #tikiwiki
[12:54] xavi mmmm, the doc page is not loading for me right now: http://doc.tiki.org/Upgrade
[13:17]  vmachine joined #tikiwiki
[13:35]  jacmoe joined #tikiwiki
[14:01]  jacmoe joined #tikiwiki
[14:18] wu-lee xavi: thanks, although I've read all that quite carefully
[14:19] wu-lee one nit I discovered: one table wasn't being converted to utf8 and it continually triggered the "something is wrong" warning in the tiki-install.php wizard
[14:20] wu-lee the tiki_search_stats table contained characters in "term" which create duplicates when the table is converted from latin1 to utf8
[14:20] wu-lee which prevented the upgrade from completing the job
[14:21] wu-lee I needed to force the issue by doing it manually, using 'ALTER IGNORE TABLE ...'
[14:21] wu-lee the warning is gone, but my pages stil render wrongly
[14:22] CIA-75 tikiwiki: 03chibaguy * r42521 10/trunk/templates/article.tpl: [FIX] Break tag isn't needed because preceding element is block level, and it causes unwanted white space.
[14:23] wu-lee I think it may be because my php.ini settings for character_set_client are unset, causing a latin1 default
[14:23] wu-lee hunting for ways to override in on a my shared hosting
[14:42]  jacmoe joined #tikiwiki
[14:53] xavi wu-lee: I suggest that you follow at least once, the 3 steps indicated here: http://doc.tiki.org/Upgrade#If_you_need_to_fix_the_encoding_issue
[14:53] wu-lee xavi: yep, more than once
[14:53] xavi from your 1.8 tiki site (without manually touching anything)
[14:53] xavi in the same server where the 1.8 site is (in the same mysql, I mean)
[14:54] wu-lee the final step (correcting double encoding) didn't seem to be an option offeret to me
[14:54]  marclaporte joined #tikiwiki
[14:54] wu-lee I've actually had to upgrade in several steps
[14:54] xavi hack the php installer file if needed to have that option shown for you
[14:54] wu-lee 1.8 -> 1.9 -> 3.9 -> 6.7 -> 9.0
[14:55] wu-lee because of a bug in the 9.0 installer, I think
[14:55] xavi did 6.7 work for y ou?
[14:55] marclaporte polom
[14:55] wu-lee this worked, yes
[14:56] xavi the strong issue used to be between 5.0 (or before) and 5.1 (or after)
[14:56] wu-lee (I'm looking for the reference)
[14:56] xavi then, no idea. Refer (when asking for help) then to a problem in the upgrade from 6.7 to 9.0
[14:56] marclaporte wu-lee:  I suggest you use 9.1 from daily build
[14:57] xavi to avoid considering many potential source  of enconding problem when upgrading to version 6 or so.
[14:57] marclaporte Tiki 1.8 (2004-02-08) to 9.1 (http://dev.tiki.org/Daily+Build#x_2)
[14:58] marclaporte (quite an upgrade!)
[14:58] xavi From 6 to 9, there shouldn't be many (any?) issues regarding wrong encoding chars (there were just some issues with html entities, but apparently fixed)
[14:58] wu-lee "Fatal error: Call to a member function query() on a non-object in lib/profilelib/installlib.php
[14:58] wu-lee on line 115"
[14:58] wu-lee looks like this to me: http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki?view=revision&revision=42327
[14:58] wu-lee that just prevented the installer from completing
[14:58] xavi ah, ok
[14:58] wu-lee the encoding was another issue
[14:59]  RobertPlummer joined #tikiwiki
[14:59] xavi so follow marclaporte 's advice
[14:59] marclaporte wu-lee:  what happens if you go directly from 1.8 to 9.1?
[14:59] wu-lee ok, I did look for a newer release but it wasn't on the downloads page
[15:00] marclaporte 9.1 will be released this month
[15:00] wu-lee i didn't know where else to go offhand, but decided that anything newer was potentially adding risks to something already problematic
[15:01] wu-lee the upgrade docs say explicitly that 1.8 can't be upgraded to anything above 1.9
[15:01] wu-lee so I first tried 1.8 -> 1.9 -> 9.0
[15:01] marclaporte ah?  do you remember which page?
[15:01] wu-lee and hit the "non-object" error above
[15:02] marclaporte Let's prove that doc incorrect and we'll fix it :-)
[15:02] wu-lee yes, it's here: http://doc.tiki.org/Upgrade#Determine_the_version_of_your_current_Tiki
[15:03] xavi well guys, I have to leave (urgent work to finish for today)
[15:03] xavi cheers
[15:03]  xavi left #tikiwiki
[15:03] * marclaporte checks
[15:04] marclaporte That sentence seems illogical (and I have a feeling I am the author!)
[15:04] marclaporte "If your current Tiki is less than 1.9.0Tiki 1.9.0 was released on 2005-04-27 so it's highly unlikely that you still are running one. Older data upgrades scripts were removed from Tiki but are still available to download.
[15:04] marclaporte : You need to upgrade to 1.8 first: Upgrade 1.7 to 1.8 and then, Upgrade 1.8.x to 1.9.y (do not upgrade directly from 1.7.x to 1.9.x or later)"
[15:05] wu-lee the "fix the encoding issue" here http://doc.tiki.org/Upgrade#If_you_need_to_fix_the_encoding_issue
[15:05] wu-lee also ran into a problem in the 9.0 installer (as mentioned above, repeating for marclaport's benefit)
[15:06] wu-lee because tiki_search_stats had a duplicated key when converted from latin1 -> utf8
[15:07] wu-lee I needed to "ALTER IGNORE TABLE ..." to resolve that, and then I got through the 3 steps without the "something is wrong with your encoding" warning
[15:08] wu-lee although there was no option in step three to "fix double encoding"
[15:08] wu-lee I'm pretty sure my database is now utf8 both in declaration and content
[15:09] wu-lee and HTTP/HTML headers say utf-8 is in use
[15:11] wu-lee and phpinfo() tells me I've managed to set al the php.ini parameters described here http://doc.tiki.org/UTF-8#PHP_in_association_with_a_web_server
[15:14] marclaporte wu-lee:  Tiki 9.x contains SQL code to upgrade from 1.8: http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki/branches/9.x/db/tiki_1.8to1.9.sql?revision=42521&view=markup
[15:15] wu-lee ok - we live and learn I suppose :)
[15:15] marclaporte Can I ask you a favor?
[15:15] wu-lee although I suspect it'd still run into the "non-object" bug
[15:16] marclaporte Can you try an upgrade from 1.8.x to 9.1 (from daily build) in one shot?
[15:16] wu-lee ask away, I can always say no :)
[15:16] marclaporte hehe
[15:17] wu-lee hm, I might try, but i do have to try and fix the encoding
[15:17] wu-lee is that likely to help?
[15:17] marclaporte yes, fix the encoding as the last step of 9.x upgrade
[15:19] wu-lee ok, but I've already completed the last step
[15:19] marclaporte sure, just try again on your initial backup
[15:20] marclaporte on a copy
[15:20] marclaporte and then, you can compare both
[15:20] * wu-lee sighs
[15:20] wu-lee "oh no not again"
[15:20] wu-lee can I ask one question first tho?
[15:20] marclaporte sure!
[15:21] wu-lee if I set $client_charset = 'latin1' in db/local.php the pages render apparently correctly
[15:21] marclaporte right
[15:21] wu-lee $client_charset = 'utf-8'  doesn't
[15:22] wu-lee I suspect tiki's connection to the DB is using latin1
[15:22] marclaporte so you can stay in latin1 and not run the converter, or move to utf8 and run the converter
[15:22] wu-lee I've run the converter, I'd prefer utf-8
[15:22] marclaporte I agree
[15:23] marclaporte How many wiki pages do you have (approx)
[15:23] wu-lee so what controls the mysql connection encoding setting?
[15:23] wu-lee hm
[15:24] wu-lee not my wiki, "lots", mostly articles tho
[15:24] wu-lee site's been around a long time
[15:24] marclaporte ok
[15:26]  dhazel joined #tikiwiki
[15:28] wu-lee marclaporte: I'm going to have to take a short break to eat something, before I do any more upgrading
[15:29] marclaporte ok :-)
[15:41] marclaporte wu-lee: never mind
[15:49] marclaporte I will update the doc to be clearer
[16:02]  vmachine left #tikiwiki
[16:13]  benoitg joined #tikiwiki
[16:21]  sandroandrade joined #tikiwiki
[16:21] wu-lee marclaporte: just doing the 1.8 -> 9.0 now... is there anything specific you want to know?
[16:28] marclaporte it won't work, sorry
[16:29] marclaporte 1.8->1.9->9.1 should work
[16:29] marclaporte you don't need to install 1.9.x though
[16:29] wu-lee oh, ok
[16:30] marclaporte you can manually run 1.8.x to 1.9.x though: http://doc.tiki.org/Upgrade+1.8.x+to+1.9.y
[16:31] wu-lee I've followed that already, i think
[16:31] wu-lee right at the beginning
[16:32] wu-lee I started 1.8 -> 1.9.11 -> 9.0
[16:32] marclaporte that was perfect
[16:32] marclaporte except that it crashed?
[16:32] wu-lee there were still encoding issues I think, but the showstopper was the bug I referred to above,
[16:33] wu-lee 13:58 < wu-lee> "Fatal error: Call to a member function query() on a non-object in lib/profilelib/installlib.php
[16:33] wu-lee 13:58 < wu-lee> on line 115"
[16:33] wu-lee 13:58 < wu-lee> looks like this to me: http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki?view=revision&revision=42327
[16:33] wu-lee 13:58 < wu-lee> that just prevented the installer from completing
[16:33] marclaporte right, so that will be fixed in 9.1
[16:34] wu-lee So I tried 1.8 -> 1.9.11 -> 3.9 -> 9.0
[16:34] wu-lee ditto
[16:34] marclaporte The doc says: "However, if you are having trouble with a database upgrade of anything prior to 3.0 (so including 1.9 and 2.0, especially if it started life before 1.9) it is recommended you upgrade to 3.x (currently 3.8) first, and then to your final version."     I want to remove that if it's confirmed
[16:34] wu-lee then 1.8 ->  1.9.11 -> 3.9 -> 6.7 -> 9.0
[16:34] wu-lee that one finally worked without the error
[16:34] marclaporte oh, I see
[16:35] marclaporte So you are all good now?
[16:35] wu-lee nope
[16:35] wu-lee encoding problems
[16:35] marclaporte hmmm
[16:35] marclaporte is your site public?
[16:36] wu-lee old site is here: http://railfuture.co.uk/
[16:36] wu-lee new site being built here: http://testing.railfuture.org.uk <-- currently mid install
[16:37] wu-lee the first issue I hit is always "Something is wrong with the database encoding. The schema has UTF-8 as default encoding but some tables in the schema have a different collation, latin1_swedish_ci. Converting to UTF-8 may solve this but may also make matters worse."
[16:39] marclaporte Site is closed for maintainance; please come back later.
[16:39] wu-lee oh yes
[16:39] marclaporte Does site have anything else than English?
[16:40] wu-lee hm, maint mode should be off.  admin panel says it is
[16:41] wu-lee The site is in English, ye
[16:41] wu-lee s
[16:41] wu-lee nothing else
[16:41] marclaporte so can I see encoding issues?
[16:42] wu-lee not in the old site
[16:42] wu-lee the new site does (when I get it back)
[16:42] wu-lee symbols like £ and non-ascii quotes, apostrophes, things like that
[16:42] marclaporte right
[16:43] wu-lee two-trains-each-way “service” to
[16:43] wu-lee is one example
[16:43] marclaporte ok, that confirms
[16:43] marclaporte so you did the UTF-8 fix in the installer and that didn't fix it?
[16:44] wu-lee yes. it tried, but I think it didn't quite complete the job
[16:45] marclaporte error message?  timeout?  blank page?
[16:46] wu-lee sorry, just preparing a paste
[16:46] wu-lee here are some more detailed notes http://pastebin.com/SL6Z9iFp
[16:47] wu-lee basically, no errors shown, but the warning remains, despite clicking the "convert database and tables to utf-8" button several time
[16:47] wu-lee the reason is explained in the paste
[16:49] wu-lee to summarise I think the UTF-8 conversion worked, bar one table, which was easily fixed
[16:50] wu-lee but the output remained broken
[16:50] wu-lee http headers state content is utf-8, as does html souce
[16:50] wu-lee source
[16:53] wu-lee marclaporte: just to confirm that 1.8 -> 9.0 doesn't work, I tried it
[16:54] wu-lee it doesn't, but it seems to fail with the same error I had when I upgraded via 1.9 (and 1.9 and 3)
[16:54] wu-lee on upgrading I get a blank screen with the error: "Fatal error: Call to a member function query() on a non-object in lib/profilelib/installlib.php on line 115"
[17:00] wu-lee marclaporte: the (semi-)successfully upgraded 9.0 site is now back up http://testing.railfuture.org.uk/
[17:01] wu-lee an example of a page exhibiting the encoding problems is: http://testing.railfuture.org.uk/tiki-read_article.php?articleId=1293
[17:06] wu-lee is there a minimal example of some tiki code which will get some (utf-8) text out of the tiki database anywhere?
[17:07] wu-lee (i.e. in the same way tiki does it)
[17:19]  benoitg joined #tikiwiki
[17:38]  sandroandrade joined #tikiwiki
[17:38] Tiki|bot New Forum Posts: Favicon only works on server - http://tiki.org/tiki-view_forum_thread.php?forumId=4&comments_parentId=44453
[17:41] marclaporte wu-lee:  I clarified the docs: https://doc.tiki.org/Upgrade#Determine_the_version_of_your_current_Tiki
[17:44] marclaporte wu-lee: check installer/tiki-installer.php   function convert_database_to_utf8   and function fix_double_encoding
[17:44] * marclaporte reads wu-lee's paste
[17:50] marclaporte en_gb: yes, you may very well be right.  Someone from that part of the world should look into this :-)
[17:51] wu-lee I've noticed my locale seems to revert to plain "en"
[17:53] marclaporte "However, the documentedoption to "fix double encoding" isn't an option."   -> You should see this at the last last step
[17:54] marclaporte wu-lee:  do you PHP^
[17:54] marclaporte Do you code PHP?
[17:57] marclaporte wu-lee:  I have a hint
[17:57] marclaporte re-run the installer, but go step by step
[17:58] marclaporte On the last step, you should see: "Upgrading and running into encoding issues? We can try to fix it, but make sure you have backups, and can restore them."
[17:58] marclaporte And if you go the installer but skip some steps, it doesn't appear (that is what I just experienced on http://demo.tiki.org/9x/tiki-install.php)
[18:02] wu-lee Hm
[18:02] wu-lee I did look for that
[18:02] wu-lee I don't think I skipped any steps at all
[18:03] wu-lee here's what I'm wondering: the text in the database appears to be utf8, I can access it using MySQL and it looks perfect
[18:03] wu-lee and yet the web page, which is also utf8, appears to contain garbage
[18:04] marclaporte I am making you a screencast
[18:04] marclaporte http://demo.tiki.org/trunk/wu-lee
[18:04] wu-lee thanks
[18:04] * wu-lee goes to look
[18:05] * marclaporte likes dogfooding/showing off the new Tiki Screencast feature :-)
[18:06] marclaporte db/local.php probably needs to be UTTF-8 for this to work
[18:06] wu-lee right, so I can tell you I did more or less what you did, and skipped *fewer* steps :)
[18:07] wu-lee the upgrade docs say that you should not use the default db connection, I think
[18:07] wu-lee ..checking
[18:07] wu-lee It says "Even if you have a local.php file already there, click on "Modify database connection" instead of "Use Existing Connection". "
[18:08] wu-lee here http://doc.tiki.org/Upgrade#If_you_need_to_fix_the_encoding_issue
[18:08] wu-lee so I clicked "Modify database connection" and set the information there
[18:09] wu-lee I was then told in a warning "something is wrong with your encoding"
[18:09] marclaporte ok, can you try what I did?
[18:10] wu-lee I don't think I'd be able to even if I tried
[18:10] wu-lee because I get a warning you don't
[18:10] marclaporte ah
[18:10] wu-lee about "something is wrong"
[18:10] wu-lee and the suggestion course of action is to convert the database content
[18:10] wu-lee which (silently) doesn't completely work
[18:11] marclaporte ok, can you try just to rule this out?
[18:11] wu-lee the warning  won't go away
[18:11] marclaporte what is exact warning?
[18:11] wu-lee and if I ignore it and continue, there's no option to "fix dobule encoding"
[18:12] wu-lee the warnign says:  "Something is wrong with the database encoding. The
[18:12] wu-lee schema has UTF-8 as default encoding but some tables in the schema
[18:12] wu-lee have a different collation, latin1_swedish_ci. Converting to UTF-8 may
[18:12] wu-lee solve this but may also make matters worse. You should investigate
[18:12] wu-lee what happened or only proceed with backups."
[18:12] marclaporte which tables?
[18:12] wu-lee it doesn't say, but initially, all of them
[18:13] wu-lee they're all latin1
[18:13] marclaporte which version of MySQL do you have?
[18:13] wu-lee then after clicking "convert..." all but one are utf8
[18:13] marclaporte tiki_search_stats
[18:13] wu-lee mysql  Ver 14.14 Distrib 5.1.63, for unknown-linux-gnu (x86_64) using readline 5.1
[18:13] marclaporte any data in tiki_search_stats ?
[18:13] wu-lee yep tiki_search_stats
[18:14] wu-lee yep, lots
[18:14] wu-lee including lots of non-ascii
[18:14] wu-lee apparently
[18:15] marclaporte Any way we could ignore it for testing purposes?
[18:15] marclaporte make a backup DB, and delete that table, and we see if you'll then have double encoding fix available?
[18:15] wu-lee ok, I'll try that
[18:18] marclaporte also would be interesting to see if you ask MySQL or phpMyAdmin to convert tiki_search_stats
[18:18] wu-lee one question: should I create the fresh database with urf8 or latin1 defaults?
[18:18] wu-lee I converted tiki_search_stats with MySQL
[18:18] marclaporte utf-8 since you aleady converted
[18:19] wu-lee and should I start from the tiki-6.7 version?
[18:19] wu-lee I guess I have to
[18:19] marclaporte sure
[18:24] marclaporte http://testing.railfuture.org.uk/tiki-index.php?page=cookies     coming to Tiki10: http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki?view=revision&revision=42231
[18:28] wu-lee right, good news, it seems to have worked as your screencast did
[18:28] wu-lee thank you
[18:29] wu-lee (I copied your steps and didn't modify the DB connection, I am not sure if that is significant)
[18:29] wu-lee the main extra thing is that the "something is wrong with your encoding" warning appeared
[18:30] wu-lee this time, however, it succeeded and disappeared after I clicked "Covert...."
[18:30] wu-lee finally, the option to fix double encoding was there, which I think was what really did the job
[18:31] wu-lee result: http://testing.railfuture.org.uk/tiki-read_article.php?articleId=1293
[18:31] wu-lee no garbgage
[18:32] marclaporte great!
[18:33] wu-lee I am wondering why the apparently double-encoded text looked perfect when rendered using the mysql command line?
[18:34] marclaporte dunno
[18:34] wu-lee (ironically, it now looks encoded)
[18:34] marclaporte so what about tiki_search_stats ?
[18:34] wu-lee mysql> delete from tiki_search_stats;
[18:34] wu-lee Query OK, 536262 rows affected (0.01 sec)
[18:35] marclaporte so maybe you can re-instate and see what happens
[18:36] wu-lee that's a lot of stats.  blown away now.  utf8_unicode_ci fields
[18:36] wu-lee re-instate tiki_search_stats?
[18:37] marclaporte well, do you want to use that data?
[18:38] marclaporte it was blocking your upgrade, but maybe tiki_search_stats with messed up accents is better than being empty
[18:39] wu-lee I suspect no-one used it and it was a big pile of spambot-generated poo-poo
[18:39] wu-lee I'll ask the users
[18:39] wu-lee I can re-instate it later i presume?  (i.e. nothing else relies on it?)
[18:40] wu-lee re. cookies: thanks, hadn't noticed that.
[18:41] wu-lee I think the next thing to do is take a pain killer and go lie down for a bit
[18:41] wu-lee if only I didn't have to go out.
[18:44] wu-lee marclaporte: thank you very much I owe you a drink
[18:45] wu-lee ttfn
[19:02]  vmachine joined #tikiwiki
[19:15] marclaporte I'll have a pale ale :-)
[19:34]  vmachine joined #tikiwiki
[20:09]  vmachine joined #tikiwiki
[20:14]  redflo joined #tikiwiki
[20:37]  Sp4rKy joined #tikiwiki
[20:37]  mjeanson joined #tikiwiki
[20:37]  DarkCalf joined #tikiwiki
[20:37]  changi_ joined #tikiwiki
[20:37]  marclaporte joined #tikiwiki
[20:37]  redflo joined #tikiwiki
[20:37]  vmachine joined #tikiwiki
[20:37]  sandroandrade joined #tikiwiki
[20:37]  benoitg joined #tikiwiki
[20:37]  dhazel joined #tikiwiki
[20:37]  panamaus joined #tikiwiki
[20:37]  g0th joined #tikiwiki
[20:37]  Caarrie|away joined #tikiwiki
[20:37]  goth joined #tikiwiki
[20:37]  CIA-75 joined #tikiwiki
[20:38]  Tiki|bot joined #tikiwiki
[20:41]  RobertPlummer joined #tikiwiki
[20:44]  blast_hardcheese joined #tikiwiki
[20:44]  vmachine joined #tikiwiki
[20:54]  blast_hardcheese joined #tikiwiki
[20:58]  dennmans joined #tikiwiki
[21:17]  vmachine joined #tikiwiki
[21:49]  vmachine joined #tikiwiki
[21:50]  marclaporte joined #tikiwiki
[22:09] Tiki|bot New Forum Posts: Party Dresses - http://tiki.org/tiki-view_forum_thread.php?forumId=24&comments_parentId=44472
[22:09] Tiki|bot New Forum Posts: tiffany sets online - http://tiki.org/tiki-view_forum_thread.php?forumId=23&comments_parentId=44471
[22:09] Tiki|bot New Forum Posts: Versace - http://tiki.org/tiki-view_forum_thread.php?forumId=22&comments_parentId=44470
[22:24]  vmachine joined #tikiwiki
[22:39] Tiki|bot New Forum Posts: Vacheron Constantin watches - http://tiki.org/tiki-view_forum_thread.php?forumId=16&comments_parentId=44485
[22:39] Tiki|bot New Forum Posts: panerai for sale - http://tiki.org/tiki-view_forum_thread.php?forumId=15&comments_parentId=44484
[22:39] Tiki|bot New Forum Posts: Prada Sunglasses online - http://tiki.org/tiki-view_forum_thread.php?forumId=14&comments_parentId=44483
[22:49] Tiki|bot New Forum Posts: Christian Louboutins Flats cheap - http://tiki.org/tiki-view_forum_thread.php?forumId=23&comments_parentId=44491
[22:49] Tiki|bot New Forum Posts: Paul Smith Briefcases online - http://tiki.org/tiki-view_forum_thread.php?forumId=22&comments_parentId=44490
[22:49] Tiki|bot New Forum Posts: tiffany accessories - http://tiki.org/tiki-view_forum_thread.php?forumId=20&comments_parentId=44489
[22:59]  vmachine joined #tikiwiki
[23:13] Jyhem is there a way of mass-removing forum posts ? Like all from 44454 to 44491 ?
[23:32]  vmachine joined #tikiwiki
[23:43] amette jjgoth: apparantly you managed to write to devel-list - and it didn't take half a day to get quite good answers - looking forward to you testing what Louis-Philippe suggested !! :)
[23:59]  Tiki|bot joined #tikiwiki