http://themes.tikiwiki.org/ 403? yes http://dev.tikiwiki.org/Release30process#Blockers help needed Welcome to the official Tikiwiki English Irc Channel. TikiWiki or better known as TW, is your Groupware/CMS (Content Management System) solution, you can get more infomation at http://info.tikiwiki.org/ . marclaporte: http://www.facebook.com/share_partners.php click on Making Sure the Preview Works (For Advanced Partners) hello Hello. I've got a problem with my tiki site and I don't know how to explain it. http://www.l4smb.net/tiki-list_articles.php works correctly when authenticated, but when not authenticated, ther eis a lot of 'stuff' on the page. Does anyone have any suggestions? Zylogue: I see a database error at your site. Looks like the site wasn't upgraded completely/correctly. chibaguy, thanks what tiki version? I will look into that. It is hosted, so I will look into it. v2.2 You can see the article correctly when logged in? yes I mean tiki-list_articles.php. That works ok when logged in? Sorry, I've got to go now; will be back later. ok Hi all :) nyloth: hello what data format are exports? ? what exports do you mean? polomorning polomevening, luciash heheh, hi gary :) Zylogue: Do you mean CSV? btw, hi ppl :-) hi luci, hi chibaguy chibaguy: any news about your visa ? :) heya nyloth and all :) nyloth, we're working on the documents for that. No news yet. ok toctoc (<- localization of "polom" in my language ;-) ) Zylogue still around? xavi: cotcot :) toctoc-morning, luciash :-) For the layout.css file that will be imported by theme stylesheets, I was thinking about having two versions in styles/layout/ .... One would be commented (layout_commented.css) and not used, but just for dev and reference... xavi: yup, that one is great :) The actual layout.css would be just the selectors and properties being used, and optimized somewhat. The files woujld be maybe 32KB and 20KB or so. So a significant size reduction for the production file. chibaguy: i'd prefer only one and remove comments at the time of release by a script Ah, ok, and keep layout_commented.css for reference on line someplace. but it should be aware of any "comments" hacks of course yup, in SVN it would stay commented Yeah, I tried a few 'css optimizer' sites and various kinds/levels of optimization. just out of curiousity. Well, I don't know how the script would be run at release time (that's outside my scope). I used an approach that I could handle. ;-) by the release script ok, as long as the hacks are preserved, for sure. There are "* hmtl " for ie6 and that other hard to remember one for ie7... yup, this one will be preserved for sure as it is not css comment caralluna: current syntax highlighter in tiki, afaik, is not lgpl, and thus, it has be installed spearatedly (many people don't know about it), and thus, the CODE plugin doesn't highlight or colorize syntaxes... I thought for many years that that was a bug hehe xavi: though, i meant something else, it was source code editor + highlighterincluded, nevermind :) :-) The 20KB version I got with the online optimizer eliminated multiple selectors when they had the same property, removed comments, but left line breaks at the end of each { } ... so it was still pretty readable. xavi: oh, i thought it colorizes php only xavi: I really want a syntax highlighter ... I think getting that to work is my only showstopper left before I throw out Mediawiki ;-) luciash: if you install an dextra package, it colorizes many other syntaxes example... xavi: i know, but without geshi it should work with php syntax iirc yes, geshi is the name. Without it, only php is highlighted luciash, who can modify the release script to do the optimizing of layout/layout.css? Can you do that? example of geshi usage within tiki: http://www.ub.edu/optics/tiki/conversor (even if not the best example, since geshi doesn't recognize "R" natively; using "python" highlighter instead, and only a few coincidences...9 btw: that site is using a slightly customized eatlon, with white background , chibaguy (FYI) and the reflection on the bottom had to be custommized (quick and dirty customization for me, but it worked for me) s/customization for me/customization by me for info, we activated geshi for tiki at my work :-) it's quite out-of-the-box with tiki :) yeah chibaguy: i think i could try but nyloth did really good job improving the release scripts recently :) lunch time here, bbl everybody luciash: did you try new release script version ? :) luciash: ok, see you later chibaguy: I suppose it's not for 3.0 btw, right ? ok. the theme stylesheets will be pretty trimmed down (no more empty selectors, or comments, anyway) but layout.css is pretty verbose, so especially could benefit from optimization. (btw, only tikinewt.css in branch 3 is importing layout.css; I don't want to risk problems with the other themes this close to release time.) chibaguy: personnaly, I would prefer to let Tiki optimize CSS dynamicaly itself when loading CSS the first time (through php). I don't like to do this through the release scripts, since we will not test the result since we use directly svn I see. that's true. chibaguy: You may reduce other themes (by importing layout.css) by proposing your changes to the Quality Team, as soon as 3.0 is released chibaguy: so they may go in 3.1 yes, that would be good. I just have to create the svn branch that will be used to propose commits to the quality team for minor versions of stable branches We didn't found a name for this branch yet. Any preference ? If not, I may call it "patches" or "backports" or "stable-proposal" or something in this spirit backports sounds intuitive "proposed"? yes, why not :) proposed also (proposed to the "quality team") as long as the meaning is clear hi guys, I have a problem with the branch workspaces :S any help? hi axold; sorry I guess I'm not skilled enough... But just throw your question some other people may answer (now or later) http://themes.tikiwiki.org/ = 403 thx xavi ;) well the main problem is when you grab the code of the svn server you get blank pages when you go to tiki-index.php (the installer works well) I thought that it was conflicts or something like that, so I did a reverse merge to a previous working version same for me o tiki_trunk s/o/on but nothing, also i tried to debug you too? ok, now I trough my question/help request: MultiTiki in subdirectories (as explained in MultiTiki Akira) works fine for Tiki 1.9.x and Tiki 2.x for me, but not for tiki 3.x sites :-/ I don't know why, because I spent all the day yesterday in solve the problem and some other people complained about similar issues in tw.o forums. I?m reproducing it right now, so in a couple of minutes I?ll see the error shown in the screen, in case any "php guru" knows how to solve it :-) xavi copy your error here maybe I can help you in my case the php doesn't throw anything !help You can get a more complete list of commands that work with this bot at http://tikiwiki.org/TikiBot . donri, there is a server problem at themes.tw.o. the site will be moved and upgraded soon, I believe. well, first problem: http://server/site1/tiki-install.php doesn't seem to work (probably, too many db usernames and pass ?) I'll add here (in short) an url of the customzied local.php for multitiki in subdirs (multitiki Akira) chibaguy, ok, thanks that is that customized local.php: http://pastebin.com/d6e341786 axold ^ that is the first problem, if attempting to use tiki-install.php script mmm for multitiki in subdirectories the second problem comes later.... but can you run the tiki-install? or throws any error you cannot continue yes, I see the screen to log in, but I can't log in no error, just no username and pass recognized to keep going mmm did you see the queries executed when you attempt to install into the database? I mean in the installation process you see the queries successful executed now there are 4 that in my case axold: the frist problem isthat tiki-install.php doesn't go deeper than this screen: http://moviments.net/ilp/tiki-install.php probably because there is more than one username and pass here: http://pastebin.com/d6e341786 xavi ^ i copy this url xavi: let me see and the second problem was about the "extractTopPath" function, as far as I remember, from the local.php shown before have you write the correct host? I mean here $host_tiki='localhost'; maybe your isp give you another than localhost :-), no, no, that's fine well, one mistake, I was missing ?> at the end of local.php fixing... ok, got it, the second problem: Fatal error: Cannot redeclare extracttoppath() (previously declared in /home/httpd/tiki30svn/db/local.php:27) in /home/httpd/tiki30svn/db/local.php on line 30 ok, so skip my report of a first problem: false error report (I was missing the ?> at the end of the script: fixed) and line 30 says:      return substr( $in, 0, $point + 2 ); from here: http://pastebin.com/d617963e8 so the problem seems to be at the "estractTopPath function this error is because extracttopath was created before in the script it points the local.php so in the 28 line to clarify: this is the type of installation needed to have (multi)tikis like this: http://yourhost/site1/tiki-index.php , http://yourhost/site2/tiki-index.php , ... you don't need to declare again the extracttopath function go to db/local.php line 27 and check if the function is declare there axold, have you seen the file local.php here?: http://pastebin.com/d617963e8 oh no, sorry ah it's the same http://pastebin.com/m7e604c6c try with this trying oh well, :-) same error on anotehr line: Fatal error: Cannot redeclare extracttoppath() (previously declared in /home/httpd/tiki30svn/db/local.php:6) in /home/httpd/tiki30svn/db/local.php on line 9 well, I need to leave. Btw, I've found out that this error was also happening in tiki2.1 : http://dev.tikiwiki.org/bug2139 bbl (in some hours) cheers ok try with this http://pastebin.com/m732e2198 but anyway i don't know why is happening this sorry :S xavi: ?> is not mandatory in PHP php closing tags ?> should be never used at the end of a php file (it's a bad practice to use them) @marclaporte: about getting access to commit translation updates: my sourceforge username is "gezzzan", my username at tikiwiki.org is "gezza" thanks in advance gezza: r u doing them for upcoming 3.0 ? yes i would like to commit before it comes out gezza: 1st question is if you understand and accept the 3Rules hehe, ok yes, no problem great second step you already answered (your sf.net and tw.o name) ;) fsck, some script is very unresponsive on sf.net :-/ gezza: sorry, you have to wait i have to use another browser to finish adding you gezza: do you want to be listed as developer (contributor) or translator only ? just translator for now :) ok, done :) 3rd step: welcome to the TikiWiki community ! thanks :) gezza: please commit the language.php to barnches/3.0 asap and test before commiting just to be sure the file doesn't break tiki yeap, I am testing locally chibaguy: any idea if the release is postponed or not in the end ? I don't know, luciash i hope nelson gets in shape well soon but it shouldn't be a problem to make the release by someone else using the scripts lucash, what do you think about this article style for Strasa: http://zukakakina.com/tw3/tiki-view_articles.php (and change theme to strasa)? (instead of just a line to separate articles. Is this too 'heavy'? Same style as used in forums and blogs.) chibaguy: it looks pretty good but needs to be tested in articles plugin chibaguy: can i add it to the homepage ? err, you :) ok this sucks me lot :-/ → http://zukakakina.com/tw3/tiki-print_article.php?articleId=1 it's totally not respecting the article settings (same in article preview) also marc will complain about the padding again ;) see the print icon at http://zukakakina.com/tw3/tiki-print_article.php?articleId=1 ok, added here: http://zukakakina.com/tw3/HomePage looks good so far in the article plugin but i guess we need to clone that article to have at least two or three listed there off-topic: i wonder why in opera the sanserif option of thenews still displays serif font in my opera chibaguy: can you duplicate that article ? http://zukakakina.com/tw3/tiki-view_articles.php has two articles now. also home page via plugin great ! yeah, I was wondering about that "serif sanserif" in opera also. looks cool to me, i don't mind the heaviness of the titles uh, some broken images there too: http://zukakakina.com/tw3/tiki-print_blog_post.php?postId=1 ah, actually I just copied/pasted the "tip" text for that dummy text, and it contained ""... ...just removed the brackets. I'll test in the IE's pretty soon. tikiwiki: 03changi67 * r18350 10/branches/3.0/lang/fr/language.php: French Translation luciash: I proposed to take care of releases, so I suppose the release is not postponed luciash: maybe someone else will make the release and I just give help if needed, but I'm around depending on what will be decided at tikifest nyloth: great but with the last version of release scripts, anyone should be able to release extremely easily :) yup yup, that was my thought :) so... bbl yes, the strasa print article needs help. chibaguy: can you commit latest strasa fixes ? ok tikiwiki: 03chibaguy * r18351 10/branches/3.0/styles/strasa.css: [FIX] Better separation between articles, etc. New Forum Posts: Change a WIKI page name - http://tikiwiki.org/tiki-view_forum_thread.php?forumId=4&comments_parentId=32856 chibaguy: thx I wonder why FF adds scrollbar at the right side of the post title in strasa (was just checking the new forum post link ^^ ). ...and why the author info has a little border and is detached from the title. tikiwiki: 03luciash * r18352 10/branches/3.0/styles/strasa/pics/icons/ (folder.png ofolder.png): [FIX] Strasa theme: menu arrows transparent now to display nicely in right column menus too chibaguy: i bet it's the CSS ;) New Forum Posts: Monitor entire wiki - http://tikiwiki.org/tiki-view_forum_thread.php?forumId=4&comments_parentId=32857 The usual reason for odd website appearance and behavior: "It's ART!", screamed by a fellow in a beret. heh, I feel like the manufacturer who says the product was fine when it left the factory, something must have happened in shipping. tikiwiki: 03luciash * r18353 10/branches/3.0/styles/ (4 files in 2 dirs): [FIX] Strasa theme: polishing graphics + some adjustments to article titleb and action icons padding strasa/login.jpg has a 1px #d7e5f3 border on its left and bottom sides at the tw.o forum (background of author information in forum posts), and it doesn't have that border at my test site, etc. and I don't see where it's getting it from. that color isn't set anywhere in strasa.css... and it's not in the jpg itself. tikiwiki: 03chibaguy * r18354 10/branches/3.0/styles/transitions/1.9to2.2.css: [FIX] Avoid scrollbar on post titles. chibaguy: check .author_info yeah, I just found the colors in 1.9-2.0 transition css. cool I checked with transitions turned on but apparently not in all features. damn, transitions css is irritating to me. especially when it does styling like colors and padding, etc. in transitions shouldn't be any colors specified when not special as highlighting diffs without knowledge of what the theme looks like. I think so too, but some major additions like the newer forums layout has default colors, I guess for older themes that had no css for this layout. Hello TikiLand! chibaguy: in Web Developer extension it is great that you can switch off individual stylesheet temporarily and you see the change on the fly on page heya sébastien slordjette, hi, how are you? chibaguy: Tools > Web Developer > CSS > Disable styles > Individual stylesheet > ok thanks. ah, looks quite a bit better without transitions ;-) anyone else than ohertel can svn up tw.o ? heheh I need to add overrides to strasa.css, or remove color etc from transitions +1 for removing the colors and unwanted margins from transitions they should be paddings instead imho gotta go now, bbl ok, cya I'm fine. Just logged in to show support to Tiki people involved in the CodeFest in Montréal. Is there a Twitter channel to follow ? A live cam ? ustream.tv ? slordjette, there's info at http://tikiwiki.org/tiki-index.php?page=TikiFestCodeFest3 yo I don't see anything about live streaming yet. hi marclaporte :) it's a little hectic here codefest is not just TikiFest I put more important things in red: http://dev.tikiwiki.org/Release30process I am especially concerned with CODE/FLASH/ quicktags in blogs & trackers this one: # wikihelp/plugin help works great for wiki pages but * In blogs, the form appears, but the page refreshes if you click "submit query" * In tracker plugin within a wiki page, the form doesn't appear. I think I will make edit plugin experimental because there are still too many quircks As you wish. It will probably be fixed only for 3.1. We can move it outside experimental for 3.1 about "Several admin panels tiki-admin.php?page=xyz are displaying incorrect feedback about which features are turned on/off"... "Blog layout is broken" apparently due to the transitions stylesheet being used at tw.o (or other sites with blog layout problems). ... I used to fix most of this problems (if not all) during tikifestUK ... is there still some problems for some pannels ? yes, according to my tests from after your fixes It's interesting to choose each of the transitions css choices in Look and Feel and watch the site's appearance change. marclaporte: ok, I wonder why I didn't saw them... but I used to test all panels I wonder how many (if any) site admins actually know what those choices mean, or how to make the right choice. but this can wait 3.1, it's not so "blocking" (imo) nyloth: it should be easy to fix and avoid support requests chibaguy: transition styles should be removed now, since your work on layout tikiwiki: 03luciash * r18355 10/branches/3.0/ (lib/tikilib.php pics/icons/page_edit_section.png): [FIX] distinguish whole page edit icon from section edit icon marclaporte: yes, if someone is available to fix before tomorrow for those fixes +1 to distinguish whole page edit icon from section edit icon marclaporte: there is more important things from my point of view ;) What are your top-3? nyloth, ok, I will aim for 3.1 for moving selectors from transition to layout.css. marclaporte: XSS vulnerability that was only fixed for 2.x, for example chibaguy: :) hehe +1 for that Is it an easy merge? marclaporte: yes, I think so. If nobody is working on it until tomorrow, I may fix it then I think you are best to do since you did on 2.x, no? marclaporte: and forums still have some very annoying bugs marclaporte: I made a very quick & dirty fix for 2.x because nobody did something after some days. But I didn't do this in 3.x because it was not a nice solution. But I may have to use the same trick for 3.x since we don't have a lot of time for a better solution for 3.0 ... maybe will we do better for 3.1 ok, I see marclaporte: about forums, our last tests showed that replies to posts in a forum (not flat forum, but when threaded) were not displayed in some (all ?) cases marclaporte: and massive deletion of topics is broken back to topic before: we can make edit plugin experimental. But adding plugins from quicktags shouldn't wait for 3.1 so... those points are more anoying me you know :) :-) marclaporte: so... what's the plan for today's release (RC1) ? :) I hope so it's very difficult because we have too few resources you want to fix blockers before RC1 or before the final release ? Since release scritp has changed, I guess it's good to run it Yup. I would have done an RC1 asap today, with a page that details known problems, and a final release tomorrow ok super! do you have someone that want to make the release, or maybe someone here (luci, sylvie,...) ? If not I'll do, no problem, but it's better to have more people able to do this I have no one here maybe later, some will show up marclaporte: do you have one hour free right now ? :) I will take it we give it a try? Beta5 or RC1 now? marclaporte: Yes, RC1 :) do you have a linux PC ? I have an XO XO ? :) http://en.wikipedia.org/wiki/OLPC_XO-1 with php, mysql and subversion ? I will find a space on a server ok let me know when you have your space + a shell first step: you have to get an svn checkout of tiki branches/3.0 tikiwiki: 03chibaguy * r18356 10/branches/3.0/styles/layout/layout.css: [FIX] More selectors added. nyloth: : http://release.ourwiki.net I am ready I will document here? http://dev.tikiwiki.org/How+to+release marclaporte: OK . Note that you need to work on a checkout that is not a real installation of tiki understood marclaporte: document what you feel important to document. For me it's enough documented in the script ;p is your checkout ready ? If yes, go inside (cd your/checkout/directory/) then first try "php doc/devtools/release.php" it should display the basic help for the release script svn co https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/3.0 yes, or with the destination directory name, like : svn co https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/3.0 my_directory in progress... ok hey Nyloth thank you :-) you're welcome :) marclaporte: feel free to also send a mail to the list to ask people to stop commits on branches/3.0 until RC1 is ready. As you wish. ok, after I succeed once tikiwiki: 03chibaguy * r18357 10/branches/3.0/styles/strasa/options/cold.css: [FIX] Catching up with corresponding changes in strasa.css. I don't want to slow people down until we are sure it works go go Gary! ok, no problem :) heh ok, help works ok you can now read the howto by using --howto option as you should see, first step is "Preliminary manual tasks" I propose to skip the "Test the whole Installer and check if everything is OK" (first point), since it should be ok now same for second point: "run doc/devtools/securitycheck.php and check each "potentially unsafe" file." (at least for the RC) so, next point is : cd db/convertscripts and run convertsqls.sh you can do this (next version of release script will include this, I just did not have the time... it will probably be for 3.1 :) ) tikiwiki: 03gezzzan * r18358 10/branches/3.0/lang/hu/language.php: latest HUN translation tikiwiki: 03chibaguy * r18359 10/branches/3.0/styles/strasa.css: [FIX] A little more padding in .tabcontent. marclaporte: everything's ok ? :) tikiwiki: 03luciash * r18360 10/branches/3.0/pics/icons/shape_square_edit.png: [FIX] better icon for plugin edit Uh, in strasa, the folder icon in the files table on tiki-list_file_gallery.php is the blue triangle image that strasa uses in the menu, not the actual "folder-looking" icon that should be there. Apparently the theme substitution of "folder.png" covers non-menu instances of folder icon? This is probably a bug rather than feature. chibaguy: not a bug, you may want to substitute any icons, including those in filegals (I mean it's in the "Type" column, representing "folder" type of item. doh chibaguy: the main problem is that the same file is used for two different things chibaguy: where can we see it ? ah, tiki-list_file_gallery Yes, under the "T" in the table. for me the fix will be to use another filename for the "Type" column (so, duplicate the folder.png file into folder_type.png or something like that= s/=/)/ right maybe it should rather use pics/icons/tree_folder_open.png there luciash: maybe, but I would vote for a new one (because you don't necessarily want to show an "open" folder there) yup tikiwiki: 03luciash * r18361 10/branches/3.0/lib/tiki-js.js: [FIX] wikiplugin edit: use rather the cross icon from default iconset than the weird fullscreen_minimize icon to close the helper php doc/devtools/release.php 3.0RC1 --no-tagging would that be good? Warning: DOMDocument::loadXML(): Empty string supplied as input in /home/release/public_html/3.0/doc/devtools/svntools.php on line 82 1) Update working copy to the last revision? [Y/n/q/?] y Update in progress...Subcommand 'status' doesn't accept option '--xml' Type 'svn help status' for usage. Warning: DOMDocument::loadXML(): Empty string supplied as input in /home/release/public_html/3.0/doc/devtools/svntools.php on line 82 >> Checkout updated to revision 0. tikiwiki: 03nyloth * r18362 10/branches/proposed/: Quality Team: Creation of new 'branches/proposed' branch to allow developpers to propose patches for the stable branch that may or may not be accepted by the Quality Team (see http://dev.tikiwiki.org/Quality+Team). marclaporte: do you have php 5 ? yes marclaporte: well, at least two problems: the command line is not correct you must have a space between 3.0 and RC1 marclaporte: but, did you make the first steps displayed in --howto ? to seeif it would work lol many errors but now at step 6 40% of files passed the syntax check yay! no problem, but you should follow the steps correcly ;p ... please stop the script and fix the command line :) in fact, any error is bad in the case of a release :) yes I'm not sure your subversion is up-to-date enough, since it seems to refuse the --xml option could you stop the script and try again with this: php doc/devtools/release.php 3.0 preRC1 (there is a space between 3.0 and preRC1) tikiwiki: 03chibaguy * r18363 10/branches/3.0/styles/strasa.css: [FIX] Avoid transparent border backgrounds in popups. if you still have the error about 'status' and '--xml', probably your svn is too old :/ if not, let me know which version of SVN is necessary? not sure. Try this command line to see if it works : svn status --xml (you have to be inside your checkout) it seems version 1.3 or more is needed [release@alpha www]$ svn status --xml Subcommand 'status' doesn't accept option '--xml' ok, you probably have a version older than 1.3 are you able to update it to a new version ? no, I am not root on that account I was expecting something like this marclaporte: don't you have an account ona better server ? :) :) (marclaporte should ask for a good linux laptop for xmas ;) ) [release@alpha www]$ svn --version svn, version 1.1.4 (r13838) not good tikiwiki: 03luciash * r18364 10/branches/3.0/pics/icons/ (eye.png no_eye.png): [FIX] some mascara to improve watch icons http://dev.tikiwiki.org/How+to+release#Requirements Is that ok? luciash, I don't know if that's what marc meant about wanting Tiki to look sexy ;-) . marclaporte: yes. Maybe better to precise : subversion 1.3 or more marclaporte: if you precise "plenty of disk space", you may also want to add something similar for memory for the checkout, maybe precise that it has to be downloaded through svn, not a zip file. It has to be a checkout to work I'll update the page oh, you're still editing it, so I let you update with my comments go for it marclaporte: do you have another server with an account ? marc ? sorry whats the blockers link svp marclaporte: it's ok marclaporte: so... are u able to get a shell with an uptodate svn ? campbe13: http://dev.tikiwiki.org/Release30process thanks nyloth, hi all :) hi :) o = this.people.marclaporte.status; if ( this.people.marclaporte.status == FROZEN ) ; then this.people.marclaporte.reboot(); fi :p lol he's here but he's talking to someone campbe13: yes, I supposed this :) oups lol greetings to TikiFest Canada ! right back at ya! which should be more reliable than btiffin conecction ;p s/conecction/connection/ tikiwiki: 03changi67 * r18365 10/branches/3.0/lang/fr/language.php: French Translation is this weird icon pics/icons/assign.png used anywhere ? cannot grep it That's an ugly icon, and the way it looks doesn't convey any meaning, to me. do we keep images/workspaces/ for 3.0 ? those images must be in the workspaces experimental branch too? yes, http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki/branches/experimental/workspaces/images/workspaces/ back hi to all tikifesters chibaguy: is it safe to remove then ? luciash: IMO there is no urgency to remove such files. For me, it should be done in trunk luciash: as you wish, but take care if you do so we have no way of testing if they are used (yet) hopefully for 4.0 :-) on my server, sh setup.sh gives Fix global perms ...chown: `demotw:apache': invalid group chowned ... done. marclaporte: if you prepare a checkout for the release, no need to use setup.sh. The checkout should be completely clean are you preparing RC now ? is there commit freeze already or what time ? not yet script doesn't work on my server hmm campbe13 will try running the release script ok on another shell account svn, version 1.4.2 (r22196) ok, it should work then back for 30 min or so reading log campbe13: when you are ready, tell me campbe13: you first have to read the output of: php doc/devtools/release.php --howto and you can skip the two first tasks of the first step "Preliminary manual tasks" I propose to also skip 2 and 3 which are used to produce pre-tarballs, but are not really useful anymore, in fact, since the release script is interactive and let you check if every step has succeded before going to next step (I meant "skip step 2 and step 3") so, after finishing step 1, you can directly use this command line: php doc/devtools/release.php 3.0 RC1 and follow instructions on screen tikiwiki: 03luciash * r18366 10/branches/3.0/templates/tiki-install.tpl: [FIX] installer: use the help.png icon as everywhere else in Tiki instead of the M$ copyrighted one this new server has php5 on command line by default grrr php5 is ok campbe13: : usernamer@server:~$ /usr/local/php5/bin/php -v but we still do step 1? step 1 should be 1a, 1b, etc so we know what we can skip :-) luciash, images/workspaces are not used in tiki3 (they are remnant from the time when workspaces was in cvs for 1.10) nyloth: "(13:25:41) nyloth: php closing tags ?> should be never used at the end of a php file (it's a bad practice to use them)" <- local.php has the ending ?> tag yes, skip 1a and 1b do 1c, 1d, 1e skip 2, 3 xavi: not a real problem, but we will probably remove them in 4.0 ok later on (after codefesters end the rfirst release candidate ;-).... nyloth, if you (or any php guru) can have a look at the issue with multitiki in subdirectories not working according to the documentation: it's a blocker for all the sites attempting to upgrade to 3.0 their multitikis in subdirectories.... it's been reported earlier today on this irc channel but for later, I mean (I wouldn't want to distract the release process...) go Montreal, go! :-) tikiwiki: 03luciash * r18367 10/branches/3.0/images/workspaces/: [DEL] removing unused workspaces images (again) from Tiki before 3.0 luciash, about images, did you see the icons I added for new mime types? .odt, odp, .svg, etc. xavi: maybe add this "known bug" to the release30 page... and it will be at least fixed for 3.1 I wanted to add in 3.0, but I though I shouldn't on tiki 3.0.... xavi: yes do you think that they may fit in tiki 3.0? nyloth: it's been already there for some days, at least ok :) :-) and nyltoh, the incons for word .doc in file galleries (those shown just when the file is uploaded), where not equal to their svg counterparts I've re-created them from their svg counterparts in trunk xavi: they're for file galleries ? i don't know, it's late to review I hope that's fine they are also the type of icons shown when you upload a file to the file gallery: a big icons is shown according to the file type why some icons are in lib/images/ ? btw good point: that where they seem to be used by file galleries afaik everyone: please hold your commits ok marclaporte: ok and pics/icons/mime/ ??? we are running script to make 3.0rc1 marclaporte: ok go marclaporte, go! :-) yeah :) luciash: lib/images/icons is where the icons are stored for the uploaded files and pics/icons/mime/ is where the 16x16 images are stored for the files , when they are listed in the file galery list (afaik), or elsewhere when they are used their small versions tikiwiki: 03marclaporte * r18368 10/branches/3.0/lib/setup/twversion.class.php: [REL] Preparing 3.0rc1 release nyloth: Fatal error: Call to undefined function readline() in /home/tikirelease/3.0/doc/devtools/release.php on line 330 campbe13: which version of php ? due to path php4 in path using abs to run script ?? ??[x]: Usage: ?? [> nick] http://fr.php.net/manual/fr/function.readline.php http://fr.php.net/manual/fr/intro.readline.php it seems it's both in php4 and php5, but not on windows platforms it's an extension you may not have it's a linux box ? yes nyloth: : you have mail with login try : php --re readline this should give info about the "readline" extension to see if you have it marclaporte: ok marclaporte: let me know then when we can continue "the cleaning job" ;) marclaporte: it seems your php don't have readline, which is needed to allow the interactive mode. campbe13: I propose to do without the interactive mode campbe13: just a moment, I'll check which command you have to use... campbe13: /usr/local/php5/bin/php --no-readme-update --no-lang-update --no-changelog-update --no-copyright-update --no-secdb --no-packaging --no-tagging --force-yes you can try this it should not ask you any question and do the svn and php syntax check marclaporte: there's syntax error commited in lib/setup/twversion.class.php on line 99 sorry, was disconnected now i get "Parse error: syntax error, unexpected T_LNUMBER, expecting ')' in /mnt/sda1/Devel/SVN/Tiki/3.0/lib/setup/twversion.class.php on line 99" because of it marclaporte: was it caused by the script or manually ? marclaporte: i can fix and commit back if you like luciash: you can fix, it's a missing comma, this is not a step that can be done by the script, too dangerous to parse this file by a script IMO ok tikiwiki: 03luciash * r18369 10/branches/3.0/lib/setup/twversion.class.php: parse error fix: missing comma oups viva collaboration!!! nothing like many eyeballs :) So, I was saying: I propose to do without the interactive mode the command line should be : /usr/local/php5/bin/php doc/devtools/release.php --no-readme-update --no-lang-update --no-changelog-update --no-copyright-update --no-secdb --no-packaging --no-tagging --force-yes to check if the first steps are ok :) literally ? :) btw, thanx campbe13 :) mlaporte: is it running correctly ? If everything gone fine, you can now use this command line : /usr/local/php5/bin/php doc/devtools/release.php --no-first-update --no-check-php --no-secdb --no-packaging --no-tagging --force-yes 3.0 rc1 campbe13 is on top of things :-) mlaporte: there was only two steps because all others were explicitely disabled in the command line :) mlaporte: I just wanted to take no risks and check step by step ok, it worked mlaporte: the second command line I sent should make more things (but still not all steps, especially not secdb, packaging and tagging, which are the most risky) ok so, now, as said above, you can try some next steps : /usr/local/php5/bin/php doc/devtools/release.php --no-first-update --no-check-php --no-secdb --no-packaging --no-tagging --force-yes 3.0 rc1 tell me if you have any error now, we test that ok tikiwiki: 03marclaporte * r18370 10/branches/3.0/README: [REL] Update README file for 3.0rc1 seems to work... xavi: congrats :) it automatically commits111 yes hahahahahah we just thought it was for fun heheh, marc panics this is the behavior with --force-yes ... since you don't have readline() function which allows interactive mode lol luciash: thanks (a bit dirty, but works... ) don't panic, I'll fix if there is a problem :) :-0 :-) :) dinner time (bbl) see you later xavi: ? where are you located ? :-p tikiwiki: 03marclaporte * r18371 10/branches/3.0/lang/ (35 files in 35 dirs): [REL] Update language.php files for 3.0rc1 tikiwiki: 03marclaporte * r18372 10/branches/3.0/changelog.txt: [REL] Update changelog.txt for 3.0rc1 for the moment everything seems ok :) hello guys - back from my community service day (another one next saturday) hi sylvie :) marclaporte is releasing 3.0rc1 :) marclaporte: updating copyrights is always quite long... I sill have my list of blockers I did not time to work om last week (the ajax module problem and the calendar view and the new module calendar) last one is not a blocker tikiwiki: 03marclaporte * r18373 10/branches/3.0/copyright.txt: [REL] Update copyright.txt for 3.0rc1 marclaporte: great :) marclaporte: we can start next steps marclaporte: try this : /usr/local/php5/bin/php doc/devtools/release.php --no-first-update --no-check-php --no-readme-update --no-lang-update --no-changelog-update --no-copyright-update --no-secdb --no-packaging --no-tagging --force-yes 3.0 rc1 oups no it will do nothing :) marclaporte: try this : /usr/local/php5/bin/php doc/devtools/release.php --no-check-php --no-readme-update --no-lang-update --no-changelog-update --no-copyright-update --force-yes 3.0 rc1 or if you prefer to do secdb separately add --no-packaging and --no-tagging , as you prefer campbe13 is on top of things :-) sylvieg: did you get in trouble with the law? :-) :) tikiwiki: 03marclaporte * r18374 10/branches/3.0/db/tiki-secdb_3.0_mysql.sql: [REL] SecDB for 3.0rc1 for the record, campbe13 is committingwith my account but she is doing the real work I am just having a beer and chatting tikiwiki: 03marclaporte * r18375 10/tags/3.0rc1/: [REL] Tagging release ok, thanx a lot campbe13 :) nyloth_: does the release script expect a mysql server? mlaporte: it uses mysql functions Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) in /home/tikirelease/3.0/doc/devtools/release.php on line 192 ?? ??[x]: Usage: ?? [> nick] quelqun is the *g* campbe13: for one step (secdb) it uses php mysql_real_escape_string() function I suppose a mysql server is required, not sure what is there in the world here to? hmmm désolé essais transl mysql is not on localhost but available host mysql.rclaporte.com mlaporte: can you send me by mail a valid user + password on for this sql server, please ? I'll test it mlaporte: you can create a new one if you want mlaporte: no need to have a database (i suppose) ok, I will create db user mlaporte: thx :) nyloth_: : sent campbe13: Ok, there is a way to specify a specific mysql host, user and pass for the release... instead of just "/usr/local/php5/bin/php doc/devtools/release.php", try again your last command with "/usr/local/php5/bin/php d mysql.default_host=mysql.rclaporte.com -d mysql.default_user=MYSQLUSER -d mysql.default_password=MYSQLPASSWORD doc/devtools/release.php" change MYSQLUSER and MYSQLPASSWORD by user/pass that marc just created so... full command should be: /usr/local/php5/bin/php d mysql.default_host=mysql.rclaporte.com -d mysql.default_user=MYSQLUSER -d mysql.default_password=MYSQLPASSWORD doc/devtools/release.php --no-check-php --no-readme-update --no-lang-update --no-changelog-update --no-copyright-update --force-yes 3.0 rc1 oups, -d /usr/local/php5/bin/php -d mys... you should not get any mysql errors anymore then oups it's quite good that it looks like we are going to be able to get it to work on this account of course, we could ask amette for an account like release.tikiwiki.org but this is good dogfood sure it's a bit annoying to have no readline() function, since the interactive mode can't be used... will have to find a way to install it on the server or maybe another function that could do the same, but not sure it exists but, yes, good dogfood :) bbl see you later luciash tikiwiki: 03marclaporte * r18376 10/branches/3.0/db/tiki-secdb_3.0_mysql.sql: [REL] SecDB for 3.0rc1 tikiwiki: 03marclaporte * r18377 10/tags/3.0rc1/: [REL] Deleting tag 'tags/3.0rc1' in order to create a new one tikiwiki: 03marclaporte * r18378 10/tags/3.0rc1/: [REL] Tagging release Ok, this time everything seems fine... I suppose the script is building the tarballs now... if the tarballs are OK, then they just have to be uploaded to sourceforge and the release is done :) good job campbe13 :) Je suis le dactylographe:) yay1 is there a script to / procedure to upload? what have we learned? http://dev.tikiwiki.org/how%20to%20release :) To upload the 'tarballs', copy-paste and execute the following line (and change '$SF_LOGIN' by your SF.net login): cd ~/tikipack/3.0.rc1 scp *bz2 *gz *zip $SF_LOGIN@frs.sourceforge.net:uploads well... the --howto explains that http://tinyurl.com/59uubv contains enough info. I didn't checked it is still running is that normal ?? campbe13: what is still running ? the scp or the release.php ? the release.php has finished and tarballs are in ~/tikipack/3.0.rc1/ campbe13 & mlaporte: you can already upload to sourceforge, but before someone makes them visible for the public, you should put those three files on another web hosting to give us the link to download and test them sorry done now on release.rclaporte.com nyloth: does script gen md5/sha1 chksums ?? campbe13: no, not yet nyloth_: what do you think of md5? mlaporte: for what usage ? s/what/which/ maybe part of the script? well, why not, if it's to give to other people for checking the integrity of tarballs but it's not so reliable and important IMO nyloth: INSERT INTO `tiki_secdb` (`md5_value`, `filename`, `tiki_version`, `severity`) VALUES('a25b5510162a87f8e571ddab7219f1aa', '', '3.0rc1', 0) gettng 68 errors as above db install any ideas ? campbe13: hmm... secdb files are not good probably... I'm checking no, secdb file seems fine meme erreur 68 fois secdb is bad in tag, but ok in branch quoi faire ? I'll fix it, no problem tks let me know ok tikiwiki: 03nyloth * r18379 10/tags/3.0rc1/: [REL] Deleting tag 'tags/3.0rc1' in order to create a new one tikiwiki: 03nyloth * r18380 10/tags/3.0rc1/: [REL] Tagging release campbe13: it should be ok campbe13: please rebuild your packages using this command: /usr/local/php5/bin/php doc/devtools/release.php --no-check-svn --no-check-php --no-first-update --no-readme-update --no-lang-update --no-changelog-update --no-copyright-update --no-secdb --no-tagging --force-yes 3.0 rc1 it will only build the packages files that you will be able to test again and upload to sf.net if ok New Forum Posts: Turning on Tiki + OpenID locked me out for good (3.0 beta 3) - http://tikiwiki.org/tiki-view_forum_thread.php?forumId=4&comments_parentId=32862 Parse error: syntax error, unexpected T_OBJECT_OPERATOR in /home/tikirelease/3.0/doc/devtools/release.php on line 61 campbe13: wait... ok campbe13: I found a bug with the --no-tagging option combined with --force-yes. I'll fix it after the release campbe13: your parse error is not related. did you still used the php5 ? campbe13: btw, I'll make the tarballs and send you the files will fix ... tikiwiki: 03marclaporte * r18381 10/tags/3.0rc1/: [REL] Deleting tag 'tags/3.0rc1' in order to create a new one you have to re-run the script without --no-tagging there is a bug with this option, sorry :) it avoids creating the new tag, but will still delete the existing one, which is not good :) tiki-install gives me blank page towards the end 2nd try: i got: Fatal error: Out of memory (allocated 6029312) (tried to allocate 98304 bytes) in C:\xampp\htdocs\tikiwiki\lib\smarty\libs\Smarty_Compiler.class.php on line 533 tikiwiki: 03marclaporte * r18382 10/tags/3.0rc1/: [REL] Tagging release with latest version of XaMMP mlaporte: allocated 6MB = out of memory ... seems normal to me. It's not enough php.ini says 32 nyloth: didn't see the msg am running script to create tarballs campbe13: ok, everything should be ok now then... you juste have to wait until tarballs are made now :) mlaporte: 32 or 32M ? mlaporte: maybe it's 32M in php.ini, but the server didn't had enough free memory at this moment ? don't now, I think you should try on another server barebones is ok ok :) nyloth; works fine now, uploaded new tarballs & zip ok, great :) mhh... I don't see files on SF.net with my account So, you will have to use your account the one used to do the scp https://sourceforge.net/project/admin/editreleases.php?package_id=312463&release_id=679968&group_id=64258 on release.rclaporte.com not on sf campbe13: ah ok :) hi hi http://doc.tikiwiki.org/TikiWiki+3.0 nyloth: svp https again lost the history marc: svp url again ? https://sourceforge.net/project/admin/editreleases.php?package_id=312463&release_id=679968&group_id=64258 campbe13: I tested an install with the zip file, it seems ok I think you can upload files to sf.net i'm on it ok campbe13: : http://irc.tikiwiki.org/irclogger_log/tikiwiki?date=2009-05-02,Sat&sel=903#l899 campbe13: Thanx. It seems everything is ok now, files apparently on sf.net, there is just the usual communication to do (mails, etc.) that marc knows well :) So, I'll go sleeping because it's very late here. good evening/night tikifesters nloth: thanks for doing the hard work, I did the last easy part! goodniht