←Prev date Next date→ Show only urls(Click on time to select a line by its url)
WhoWhatWhen
redflojoined #tikiwiki [00:00]
fabriciuscool
so after two days nonstop I have to restart
brb 		[00:01]
.... (idle for 19mn)
redflo1joined #tikiwiki [00:20]
rodrigoprimojoined #tikiwiki [00:22]
........ (idle for 36mn)
Tiki|botRecent Bug: Tracker item: #4271 - - Not possible to comment a tracker entry - Tiki 8.4 - http://dev.tiki.org/item4271 [00:58]
..... (idle for 24mn)
goj_killedByISPjoined #tikiwiki [01:22]
.......... (idle for 45mn)
yanick_joined #tikiwiki
hi, how do I upgrade from 7.1 to 9.x ?
when I check for upgrade, it tells me I'm up-to-date 		[02:07]
............. (idle for 1h0mn)
goj_killedByISPjoined #tikiwiki [03:08]
.................... (idle for 1h39mn)
CIA-75tikiwiki: 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.
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. 		[04:47]
.......... (idle for 49mn)
yanick_hi, how do I upgrade from 7.1 to 9.x ? [05:38]
......................... (idle for 2h2mn)
jjgothamette: I couldn't send to the devel list [07:40]
..................... (idle for 1h44mn)
jacmoejoined #tikiwiki [09:24]
xavijoined #tikiwiki [09:30]
redflojoined #tikiwiki [09:39]
....................... (idle for 1h52mn)
dennmansjoined #tikiwiki [11:31]
........ (idle for 35mn)
wu-leejoined #tikiwiki
hello, I'm running into encoding issues having upgraded 1.8 ----> 9.0
the Mysql DB appears to be utf-8 encoded correctly now, judging by my checks
but certain characters are rendered in webpages with "garbage" characters prefixing them
local.db says $client_charset='utf-8'
s{local.db}{db/local.php}
oddly if I set it to latin1, it appears to fix the rendering, but this seems reverse to what I'd expect 		[12:06]
HTTP and HTML headers both say utf-8
I suspect something inside tiki is double-encoding the utf-8 text from mysql 		[12:23]
...... (idle for 29mn)
xaviwu-lee, see the doc page for upgrade, specially the section about encodin issues
there was a change between 5.0 and 5.1
xavi fetching a url for you.... 		[12:52]
changi_joined #tikiwiki [12:53]
panamausjoined #tikiwiki [12:53]
xavimmmm, the doc page is not loading for me right now: http://doc.tiki.org/Upgrade [12:54]
..... (idle for 23mn)
vmachinejoined #tikiwiki [13:17]
.... (idle for 18mn)
jacmoejoined #tikiwiki [13:35]
...... (idle for 26mn)
joined #tikiwiki [14:01]
.... (idle for 17mn)
wu-leexavi: thanks, although I've read all that quite carefully
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
the tiki_search_stats table contained characters in "term" which create duplicates when the table is converted from latin1 to utf8
which prevented the upgrade from completing the job
I needed to force the issue by doing it manually, using 'ALTER IGNORE TABLE ...'
the warning is gone, but my pages stil render wrongly 		[14:18]
CIA-75tikiwiki: 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:22]
wu-leeI think it may be because my php.ini settings for character_set_client are unset, causing a latin1 default
hunting for ways to override in on a my shared hosting 		[14:23]
.... (idle for 19mn)
jacmoejoined #tikiwiki [14:42]
xaviwu-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-leexavi: yep, more than once [14:53]
xavifrom your 1.8 tiki site (without manually touching anything)
in the same server where the 1.8 site is (in the same mysql, I mean) 		[14:53]
wu-leethe final step (correcting double encoding) didn't seem to be an option offeret to me [14:54]
marclaportejoined #tikiwiki [14:54]
wu-leeI've actually had to upgrade in several steps [14:54]
xavihack the php installer file if needed to have that option shown for you [14:54]
wu-lee1.8 -> 1.9 -> 3.9 -> 6.7 -> 9.0
because of a bug in the 9.0 installer, I think 		[14:54]
xavidid 6.7 work for y ou? [14:55]
marclaportepolom [14:55]
wu-leethis worked, yes [14:55]
xavithe 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]
xavithen, no idea. Refer (when asking for help) then to a problem in the upgrade from 6.7 to 9.0 [14:56]
marclaportewu-lee: I suggest you use 9.1 from daily build [14:56]
xavito avoid considering many potential source of enconding problem when upgrading to version 6 or so. [14:57]
marclaporteTiki 1.8 (2004-02-08) to 9.1 (http://dev.tiki.org/Daily+Build#x_2)
(quite an upgrade!) 		[14:57]
xaviFrom 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
on line 115"
looks like this to me: http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki?view=revision&revision=42327
that just prevented the installer from completing 		[14:58]
xaviah, ok [14:58]
wu-leethe encoding was another issue [14:58]
RobertPlummerjoined #tikiwiki [14:59]
xaviso follow marclaporte 's advice [14:59]
marclaportewu-lee: what happens if you go directly from 1.8 to 9.1? [14:59]
wu-leeok, I did look for a newer release but it wasn't on the downloads page [14:59]
marclaporte9.1 will be released this month [15:00]
wu-leei didn't know where else to go offhand, but decided that anything newer was potentially adding risks to something already problematic
the upgrade docs say explicitly that 1.8 can't be upgraded to anything above 1.9
so I first tried 1.8 -> 1.9 -> 9.0 		[15:00]
marclaporteah? do you remember which page? [15:01]
wu-leeand hit the "non-object" error above [15:01]
marclaporteLet's prove that doc incorrect and we'll fix it :-) [15:02]
wu-leeyes, it's here: http://doc.tiki.org/Upgrade#Determine_the_version_of_your_current_Tiki [15:02]
xaviwell guys, I have to leave (urgent work to finish for today)
cheers
left #tikiwiki 		[15:03]
marclaportemarclaporte checks
That sentence seems illogical (and I have a feeling I am the author!)
"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.
: 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:03]
wu-leethe "fix the encoding issue" here http://doc.tiki.org/Upgrade#If_you_need_to_fix_the_encoding_issue
also ran into a problem in the 9.0 installer (as mentioned above, repeating for marclaport's benefit)
because tiki_search_stats had a duplicated key when converted from latin1 -> utf8
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
although there was no option in step three to "fix double encoding"
I'm pretty sure my database is now utf8 both in declaration and content
and HTTP/HTML headers say utf-8 is in use
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:05]
marclaportewu-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:14]
wu-leeok - we live and learn I suppose :) [15:15]
marclaporteCan I ask you a favor? [15:15]
wu-leealthough I suspect it'd still run into the "non-object" bug [15:15]
marclaporteCan you try an upgrade from 1.8.x to 9.1 (from daily build) in one shot? [15:16]
wu-leeask away, I can always say no :) [15:16]
marclaportehehe [15:16]
wu-leehm, I might try, but i do have to try and fix the encoding
is that likely to help? 		[15:17]
marclaporteyes, fix the encoding as the last step of 9.x upgrade [15:17]
wu-leeok, but I've already completed the last step [15:19]
marclaportesure, just try again on your initial backup
on a copy
and then, you can compare both 		[15:19]
wu-leewu-lee sighs
"oh no not again"
can I ask one question first tho? 		[15:20]
marclaportesure! [15:20]
wu-leeif I set $client_charset = 'latin1' in db/local.php the pages render apparently correctly [15:21]
marclaporteright [15:21]
wu-lee$client_charset = 'utf-8' doesn't
I suspect tiki's connection to the DB is using latin1 		[15:21]
marclaporteso you can stay in latin1 and not run the converter, or move to utf8 and run the converter [15:22]
wu-leeI've run the converter, I'd prefer utf-8 [15:22]
marclaporteI agree
How many wiki pages do you have (approx) 		[15:22]
wu-leeso what controls the mysql connection encoding setting?
hm
not my wiki, "lots", mostly articles tho
site's been around a long time 		[15:23]
marclaporteok [15:24]
dhazeljoined #tikiwiki [15:26]
wu-leemarclaporte: I'm going to have to take a short break to eat something, before I do any more upgrading [15:28]
marclaporteok :-) [15:29]
wu-lee: never mind [15:41]
I will update the doc to be clearer [15:49]
vmachineleft #tikiwiki [16:02]
benoitgjoined #tikiwiki [16:13]
sandroandradejoined #tikiwiki [16:21]
wu-leemarclaporte: just doing the 1.8 -> 9.0 now... is there anything specific you want to know? [16:21]
marclaporteit won't work, sorry
1.8->1.9->9.1 should work
you don't need to install 1.9.x though 		[16:28]
wu-leeoh, ok [16:29]
marclaporteyou can manually run 1.8.x to 1.9.x though: http://doc.tiki.org/Upgrade+1.8.x+to+1.9.y [16:30]
wu-leeI've followed that already, i think
right at the beginning
I started 1.8 -> 1.9.11 -> 9.0 		[16:31]
marclaportethat was perfect
except that it crashed? 		[16:32]
wu-leethere were still encoding issues I think, but the showstopper was the bug I referred to above,
13:58 < wu-lee> "Fatal error: Call to a member function query() on a non-object in lib/profilelib/installlib.php
13:58 < wu-lee> on line 115"
13:58 < wu-lee> looks like this to me: http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki?view=revision&revision=42327
13:58 < wu-lee> that just prevented the installer from completing 		[16:32]
marclaporteright, so that will be fixed in 9.1 [16:33]
wu-leeSo I tried 1.8 -> 1.9.11 -> 3.9 -> 9.0
ditto 		[16:34]
marclaporteThe 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-leethen 1.8 -> 1.9.11 -> 3.9 -> 6.7 -> 9.0
that one finally worked without the error 		[16:34]
marclaporteoh, I see
So you are all good now? 		[16:34]
wu-leenope
encoding problems 		[16:35]
marclaportehmmm
is your site public? 		[16:35]
wu-leeold site is here: http://railfuture.co.uk/
new site being built here: http://testing.railfuture.org.uk <-- currently mid install
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:36]
marclaporteSite is closed for maintainance; please come back later. [16:39]
wu-leeoh yes [16:39]
marclaporteDoes site have anything else than English? [16:39]
wu-leehm, maint mode should be off. admin panel says it is
The site is in English, ye
s
nothing else 		[16:40]
marclaporteso can I see encoding issues? [16:41]
wu-leenot in the old site
the new site does (when I get it back)
symbols like £ and non-ascii quotes, apostrophes, things like that 		[16:42]
marclaporteright [16:42]
wu-leetwo-trains-each-way “service” to
is one example 		[16:43]
marclaporteok, that confirms
so you did the UTF-8 fix in the installer and that didn't fix it? 		[16:43]
wu-leeyes. it tried, but I think it didn't quite complete the job [16:44]
marclaporteerror message? timeout? blank page? [16:45]
wu-leesorry, just preparing a paste
here are some more detailed notes http://pastebin.com/SL6Z9iFp
basically, no errors shown, but the warning remains, despite clicking the "convert database and tables to utf-8" button several time
the reason is explained in the paste
to summarise I think the UTF-8 conversion worked, bar one table, which was easily fixed
but the output remained broken
http headers state content is utf-8, as does html souce
source
marclaporte: just to confirm that 1.8 -> 9.0 doesn't work, I tried it
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)
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" 		[16:46]
marclaporte: the (semi-)successfully upgraded 9.0 site is now back up http://testing.railfuture.org.uk/
an example of a page exhibiting the encoding problems is: http://testing.railfuture.org.uk/tiki-read_article.php?articleId=1293 		[17:00]
is there a minimal example of some tiki code which will get some (utf-8) text out of the tiki database anywhere?
(i.e. in the same way tiki does it) 		[17:06]
benoitgjoined #tikiwiki [17:19]
.... (idle for 19mn)
sandroandradejoined #tikiwiki [17:38]
Tiki|botNew Forum Posts: Favicon only works on server - http://tiki.org/tiki-view_forum_thread.php?forumId=4&comments_parentId=44453 [17:38]
marclaportewu-lee: I clarified the docs: https://doc.tiki.org/Upgrade#Determine_the_version_of_your_current_Tiki
wu-lee: check installer/tiki-installer.php function convert_database_to_utf8 and function fix_double_encoding
marclaporte reads wu-lee's paste 		[17:41]
en_gb: yes, you may very well be right. Someone from that part of the world should look into this :-) [17:50]
wu-leeI've noticed my locale seems to revert to plain "en" [17:51]
marclaporte"However, the documentedoption to "fix double encoding" isn't an option." -> You should see this at the last last step
wu-lee: do you PHP^
Do you code PHP?
wu-lee: I have a hint
re-run the installer, but go step by step
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."
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) 		[17:53]
wu-leeHm
I did look for that
I don't think I skipped any steps at all
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
and yet the web page, which is also utf8, appears to contain garbage 		[18:02]
marclaporteI am making you a screencast
http://demo.tiki.org/trunk/wu-lee 		[18:04]
wu-leethanks
wu-lee goes to look 		[18:04]
marclaportemarclaporte likes dogfooding/showing off the new Tiki Screencast feature :-)
db/local.php probably needs to be UTTF-8 for this to work 		[18:05]
wu-leeright, so I can tell you I did more or less what you did, and skipped *fewer* steps :)
the upgrade docs say that you should not use the default db connection, I think
..checking
It says "Even if you have a local.php file already there, click on "Modify database connection" instead of "Use Existing Connection". "
here http://doc.tiki.org/Upgrade#If_you_need_to_fix_the_encoding_issue
so I clicked "Modify database connection" and set the information there
I was then told in a warning "something is wrong with your encoding" 		[18:06]
marclaporteok, can you try what I did? [18:09]
wu-leeI don't think I'd be able to even if I tried
because I get a warning you don't 		[18:10]
marclaporteah [18:10]
wu-leeabout "something is wrong"
and the suggestion course of action is to convert the database content
which (silently) doesn't completely work 		[18:10]
marclaporteok, can you try just to rule this out? [18:11]
wu-leethe warning won't go away [18:11]
marclaportewhat is exact warning? [18:11]
wu-leeand if I ignore it and continue, there's no option to "fix dobule encoding"
the warnign says: "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. You should investigate
what happened or only proceed with backups." 		[18:11]
marclaportewhich tables? [18:12]
wu-leeit doesn't say, but initially, all of them
they're all latin1 		[18:12]
marclaportewhich version of MySQL do you have? [18:13]
wu-leethen after clicking "convert..." all but one are utf8 [18:13]
marclaportetiki_search_stats [18:13]
wu-leemysql Ver 14.14 Distrib 5.1.63, for unknown-linux-gnu (x86_64) using readline 5.1 [18:13]
marclaporteany data in tiki_search_stats ? [18:13]
wu-leeyep tiki_search_stats
yep, lots
including lots of non-ascii
apparently 		[18:13]
marclaporteAny way we could ignore it for testing purposes?
make a backup DB, and delete that table, and we see if you'll then have double encoding fix available? 		[18:15]
wu-leeok, I'll try that [18:15]
marclaportealso would be interesting to see if you ask MySQL or phpMyAdmin to convert tiki_search_stats [18:18]
wu-leeone question: should I create the fresh database with urf8 or latin1 defaults?
I converted tiki_search_stats with MySQL 		[18:18]
marclaporteutf-8 since you aleady converted [18:18]
wu-leeand should I start from the tiki-6.7 version?
I guess I have to 		[18:19]
marclaportesure [18:19]
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:24]
wu-leeright, good news, it seems to have worked as your screencast did
thank you
(I copied your steps and didn't modify the DB connection, I am not sure if that is significant)
the main extra thing is that the "something is wrong with your encoding" warning appeared
this time, however, it succeeded and disappeared after I clicked "Covert...."
finally, the option to fix double encoding was there, which I think was what really did the job
result: http://testing.railfuture.org.uk/tiki-read_article.php?articleId=1293
no garbgage 		[18:28]
marclaportegreat! [18:32]
wu-leeI am wondering why the apparently double-encoded text looked perfect when rendered using the mysql command line? [18:33]
marclaportedunno [18:34]
wu-lee(ironically, it now looks encoded) [18:34]
marclaporteso what about tiki_search_stats ? [18:34]
wu-leemysql> delete from tiki_search_stats;
Query OK, 536262 rows affected (0.01 sec) 		[18:34]
marclaporteso maybe you can re-instate and see what happens [18:35]
wu-leethat's a lot of stats. blown away now. utf8_unicode_ci fields
re-instate tiki_search_stats? 		[18:36]
marclaportewell, do you want to use that data?
it was blocking your upgrade, but maybe tiki_search_stats with messed up accents is better than being empty 		[18:37]
wu-leeI suspect no-one used it and it was a big pile of spambot-generated poo-poo
I'll ask the users
I can re-instate it later i presume? (i.e. nothing else relies on it?)
re. cookies: thanks, hadn't noticed that.
I think the next thing to do is take a pain killer and go lie down for a bit
if only I didn't have to go out.
marclaporte: thank you very much I owe you a drink
ttfn 		[18:39]
.... (idle for 17mn)
vmachinejoined #tikiwiki [19:02]
marclaporteI'll have a pale ale :-) [19:15]
.... (idle for 19mn)
vmachinejoined #tikiwiki [19:34]
........ (idle for 35mn)
joined #tikiwiki [20:09]
redflojoined #tikiwiki [20:14]
..... (idle for 23mn)
Sp4rKyjoined #tikiwiki [20:37]
mjeansonjoined #tikiwiki [20:37]
DarkCalfjoined #tikiwiki [20:37]
changi_joined #tikiwiki [20:37]
marclaportejoined #tikiwiki [20:37]
redflojoined #tikiwiki [20:37]
vmachinejoined #tikiwiki [20:37]
sandroandradejoined #tikiwiki [20:37]
benoitgjoined #tikiwiki [20:37]
dhazeljoined #tikiwiki [20:37]
panamausjoined #tikiwiki [20:37]
g0thjoined #tikiwiki [20:37]
Caarrie|awayjoined #tikiwiki [20:37]
gothjoined #tikiwiki [20:37]
CIA-75joined #tikiwiki [20:37]
Tiki|botjoined #tikiwiki [20:38]
RobertPlummerjoined #tikiwiki [20:41]
blast_hardcheesejoined #tikiwiki [20:44]
vmachinejoined #tikiwiki [20:44]
blast_hardcheesejoined #tikiwiki [20:54]
dennmansjoined #tikiwiki [20:58]
.... (idle for 19mn)
vmachinejoined #tikiwiki [21:17]
....... (idle for 32mn)
joined #tikiwiki [21:49]
marclaportejoined #tikiwiki [21:50]
.... (idle for 19mn)
Tiki|botNew Forum Posts: Party Dresses - http://tiki.org/tiki-view_forum_thread.php?forumId=24&comments_parentId=44472
New Forum Posts: tiffany sets online - http://tiki.org/tiki-view_forum_thread.php?forumId=23&comments_parentId=44471
New Forum Posts: Versace - http://tiki.org/tiki-view_forum_thread.php?forumId=22&comments_parentId=44470 		[22:09]
.... (idle for 15mn)
vmachinejoined #tikiwiki [22:24]
.... (idle for 15mn)
Tiki|botNew Forum Posts: Vacheron Constantin watches - http://tiki.org/tiki-view_forum_thread.php?forumId=16&comments_parentId=44485
New Forum Posts: panerai for sale - http://tiki.org/tiki-view_forum_thread.php?forumId=15&comments_parentId=44484
New Forum Posts: Prada Sunglasses online - http://tiki.org/tiki-view_forum_thread.php?forumId=14&comments_parentId=44483 		[22:39]
New Forum Posts: Christian Louboutins Flats cheap - http://tiki.org/tiki-view_forum_thread.php?forumId=23&comments_parentId=44491
New Forum Posts: Paul Smith Briefcases online - http://tiki.org/tiki-view_forum_thread.php?forumId=22&comments_parentId=44490
New Forum Posts: tiffany accessories - http://tiki.org/tiki-view_forum_thread.php?forumId=20&comments_parentId=44489 		[22:49]
vmachinejoined #tikiwiki [22:59]
Jyhemis there a way of mass-removing forum posts ? Like all from 44454 to 44491 ? [23:13]
.... (idle for 19mn)
vmachinejoined #tikiwiki [23:32]
amettejjgoth: 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:43]
.... (idle for 16mn)
Tiki|botjoined #tikiwiki [23:59]
←Prev date Next date→ Show only urls(Click on time to select a line by its url)