amette_: left #tikiwiki
zlinux: joined #tikiwiki
Telesight: joined #tikiwiki
zlinux: joined #tikiwiki
Tiki|bot: Recent Bug: - http://dev.tiki.org/item6496
Recent Bug: - http://dev.tiki.org/item6500
zlinux_: joined #tikiwiki
amette_: joined #tikiwiki
jonnyb: joined #tikiwiki
Bsfez: joined #tikiwiki
miaou
robertokir: joined #tikiwiki
fabricius: polom
jonnyb: joined #tikiwiki
amette_: wuff
zlinux: joined #tikiwiki
fabricius: *zonk*
Bsfez: lol
luciash: polom
jonnyb: joined #tikiwiki
fabricius: joined #tikiwiki
wolod
rehi
jonnyb: pompom fabricius
fabricius: ah hi jonnyb
synched!
nearly.
jonnyb: sorry fabricius - meeting, how oyu doing? I'm going to try and fix that menu admin position = 0 thing you reported next :)
fabricius: jonnyb: I think it is when I do alter a lot of menu items in a large menu.
jonnyb: oh really, ok - i'll re-read your email, i must have misunderstood... (but real life things getting in the way now! ;) )
Bsfez: joined #tikiwiki
robertokir: joined #tikiwiki
jonnyb: joined #tikiwiki
amette_: left #tikiwiki
joined #tikiwiki
Jyhem_: polom
jonnyb: hi Jyhem
Jyhem: hi jonnyb
jonnyb: can I replace 20171010_action_log_info_new_column_tiki.sql with a corrected 20171010_action_log_info_new_column_tiki.php?
jonnyb: why?
Jyhem: It seems to create errors on unattended svn upgraded tikis
https://dev.tiki.org/Get+Code → Upgrade issues with 18.x from SVN
If you’ve run a 18.x installation from SVN before 18.0-alpha release, you might run into an error like this:
Error 4 in 20171010_action_log_info_new_column_tiki
ALTER TABLE `tiki_actionlog` ADD COLUMN `log` TEXT NULL DEFAULT NULL AFTER `client`;
Duplicate column name ‘log’
And then someone is expected to run ALTER TABLE `tiki_actionlog` DROP COLUMN `log`; by hand???
fabricius: joined #tikiwiki
Jyhem: so i just intent to replace 20171010_action_log_info_new_column_tiki.sql with a corrected 20171010_action_log_info_new_column_tiki.php unless it causes even more issues?
Bsfez: joined #tikiwiki
Jyhem: Why did lfagundes add _tiki, BTW?
jonnyb: sorry Jyhem - wasn't watching the irc window...
imho best not to add code to work round pre-alpha developer testing issues, but it's up to you of course (for me if the release works well that's good enough)
installer update schema and scripts without _tiki at the end get run every update as they are expected to be custom additions (i would have done it the other way round, but LP didn't - as documented here https://dev.tiki.org/Database-Schema-Upgrade#Third_Party_Modifications_and_Customization )
ok, i see you did it anyway Jyhem - please run the merge to trunk script now to sort out any possible tree conflict :)
https://dev.tiki.org/Semi-automatic-merging-period
Jyhem: I did it for the many unattended self-updating Tiki instances which exist
Like show and demo which people keep complaining that they don't work even though they work perfectly: it's these kind of udates which break things.
merging n trunk now
zlinux: joined #tikiwiki
robertokir: joined #tikiwiki
Jyhem: merge done
trebmuh: joined #tikiwiki
fabricius: joined #tikiwiki
amette_: joined #tikiwiki
Tiki|bot: joined #tikiwiki
fabricius: joined #tikiwiki