<!-- Some styling for better description lists --><style type='text/css'>dt { font-weight: bold;float: left;display:inline;margin-right: 1em} dd { display:block; margin-left: 2em}</style>

   ***: anna has joined #tikiwiki
   anna: hallooo
   <br> testing
   ***: anna has quit IRC (Client Quit)
   <br> Lucymoz has quit IRC (Read error: 104 (Connection reset by peer))
   <br> Lucymoz has joined #tikiwiki
   <br> conner_bw has joined #tikiwiki
   conner_bw: Hey, what's the path to the 3.0 branch? I'm on a new computer and forgot the checkout path
   ***: Caarrie is now known as Caarrie|sleeping
   conner_bw: nvmd, found it, http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki/branches/3.0/
   ***: mib_ld92q2 has joined #tikiwiki
   <br> mib_ld92q2 has quit IRC (Client Quit)
   <br> btiffin has quit IRC (Remote closed the connection)
   <br> Redhatter has joined #tikiwiki
   <br> danopia` has joined #tikiwiki
   <br> conner_bw has quit IRC ("http://www.sux0r.org/")
   <br> danopia has quit IRC (Read error: 101 (Network is unreachable))
   <br> marclaporte has joined #tikiwiki
   <br> mib_y9y8gm has joined #tikiwiki
   mib_y9y8gm: Hey tiki folks
   ***: mib_y9y8gm is now known as shoq
   shoq: We are trying to get the left pull down menus working in EALTON theme. Is that hopeless in anything 3.0 beta? Or easy?
   <br> None of the tear off menus are working on the side menu, They work fine in top user nav.
   <br> And in any pre 3.0 theme. Do we just have to give up the 3.0 themes, for now?
   marclaporte: polom
   <br> chibaguy would be to answer that
   <br> <u>shoq</u>: : can you help to fix?
   <br> that theme is quite nice
   <br> would be nice to work on 3.0
   shoq: hey
   <br> it's really nice.. but have no idea where to start. we're coming back after 3+ years
   <br> we could live with a menu hack. are there other very delicate things that may fail that need testing?
   <br> I am willing to try to repain ealton, but it sounds like 3.0 has huge changes from 2.x.  Would that be just begging for trouble?
   <br> without a lot of familiarity, that could be a huge learning curve.
   marclaporte: 3+ years?
   shoq: yeah
   marclaporte: tell me more :-)
   shoq: we were trying to bend tiki in ways it just didn't want to bend back then :)
   <br> but now we need, badly
   <br> for a site that has to be up ASAP
   <br> so trying to decide what our best course is.  2.x that works, or 3.0
   <br> is the different to 3.0 huge?
   <br> difference?
   marclaporte: <u>shoq</u>: : new project or upgrade?
   shoq: new
   marclaporte: timeframe?
   shoq: 2yesterday :)
   marclaporte: what are most important features?
   shoq: 2wiki, and forum
   marclaporte: do you have devs to fix bugs?
   shoq: 2yes, but really only in desperation. very busy on other code. for small bugs, yes
   <br> 2I can do CSS bugs
   marclaporte: do you need stuff here? http://doc.tikiwiki.org/TikiWiki+3.0
   shoq: 2but it seems the menuing is core + jquery?
   marclaporte: mostly everything is core in Tiki
   shoq: 2but jquery is   not pre-3?
   <br> 2Which theme would be most stable in 3.0  Strassa?
   <br> 2ping?
   <br> 2have I lost you?
   marclaporte: multi-tasking
   <br> jquery is core but optional and experimental
   <br> <u>shoq</u>:  do you use SVN?
   shoq: 2we can
   marclaporte: UI in 3.0 is much improved
   shoq: 2my partner can do all that, yes.. when needed..but trying to avoid that time suck if i can help it
   marclaporte: many more features than 2.x
   shoq: 2would it be stable enough on big issues,?
   <br> 2to go right to a live site?
   <br> 2it's not a commercial site. just an important community
   marclaporte: tikiwiki.org, doc.tikiwiki.org and dev.tikiwiki.org are running it
   shoq: 2oh.. that's good
   <br> 2in its shipped form?
   <br> 2but the menus work on your site
   <br> 2wait. let me check that
   marclaporte: Have 15-20 things I want solve first: http://dev.tikiwiki.org/Release30process
   <br> <u>shoq</u>: : for a new project, I would say go with branches/3.0 from SVN and help iron the bugs along the way
   <br> open source is not just about taking and using
   <br> it's also about sharing &amp; contributing
   <br> hundreds of people have worked on Tiki over 6 years to build an amazing piece of software
   <br> can't you take some time to fix some bugs?
   shoq: 2yes, of course we can, long term. our issue is just getting something up immediately. the project cannot delay
   <br> 2obviously, once we're using it, we will fix things. We need something that runs and looks professional literally this week. If strass works, we're ok.
   <br> 2but the "my tiki" page on your site looks completely broken
   <br> 2have you looked?
   <br> 2it looks like some CSS has completely broken down
   <br> 2Marc, iss the EALTON theme designer here?
   <br> 2Or can I reach him?
   <br> 2That's really the theme we would love to  use.
   marclaporte: <u>shoq</u>: no offense but I have heard this many times before
   <br> including by some people that have helped the project
   shoq: 2heard what? That someone wants to use a beta?
   marclaporte: they hack something up and intend to share later
   <br> because they are in a rush
   <br> and then, another rush comes along
   shoq: 2this project is for developers. We hope to have hundreds. But we can't even start without a site
   marclaporte: chibaguy is designer for that theme
   shoq: 2people were pushing for Drupal. I hate drupal. I want tiki
   marclaporte: (I think)
   shoq: 2because you have the features
   <br> 2but if we had to spend days or weeks getting a basic site to run, that would be bad. that's all. We can fix the serious stuff as we go later.
   <br> 2can I email him?
   <br> 2if  he thinks it will work, or gives me a clue where the problem might  be
   <br> 2i'm pretty good with css
   <br> 2just need some clues
   marclaporte: what browsers will you be supporting?
   <br> does eatlon.css look ok on 2.4?
   shoq: 2can't tell. is the themes.tikiwiki.org running 2.4 or 3?
   <br> 2i assume 2.4
   <br> 2and yes, I believe it looked fine there
   marclaporte: themes.tw.o is 2.4 I think
   shoq: 2but strassa was broken on your main site, on the mytiki page
   marclaporte: url?
   shoq: 2let me double check the demo
   marclaporte: <u>shoq</u>:  I don't think I am able to give advice with the info you provide
   <br> on one hand, UI of 3.0 is better, and there are more features
   shoq: 2http://themes.tikiwiki.org/tiki-index.php?page=Eatlon
   <br> 2That is working fine
   marclaporte: however, maybe you don't need the new features and 2.4 UI may be good enough
   <br> 2.x bugs are not fixed, so it's best to report on 3.x so they get fixed
   <br> and if you are in a rush, I am not sure you can deal with this
   <br> So I see pros &amp; cons to each option
   shoq: 2were forums and wikis upgraded all that much, or are 2.4 pretty decent?
   <br> 2perhaps that is our option. just to to 2.4
   marclaporte: wiki is excellent in terms of power and stability but UI is so-so in 2.4
   shoq: 2shame though. seems you have put so much work into 3
   marclaporte: UI in 3.0 is very nice, but not yet rock-solid stable
   shoq: 2UI for users, admins, or both?
   marclaporte: both
   <br> but we don't care for admins
   <br> I mean, you just admin once
   shoq: 2I understand
   marclaporte: it's the user edit interface which is the most important if you are deploying
   <br> forum is very good in 2.x
   shoq: 2where are the biggest shortcomings in UI, in 2.x?
   marclaporte: are you using WYSIWYG?
   shoq: 2yes
   marclaporte: I recommend not to
   shoq: 2not to use wizzy in 2.4, 3.0 or both?
   marclaporte: never
   shoq: 2that may not work then. a lot of these users are coming from wikis like wetpaint, pbworks, etc
   <br> 2that would be a huge change from wizzy, down to text
   <br> 2the devs, no problem
   <br> 2but they are not the only users
   <br> 2hmmmm
   marclaporte: mediawiki has lots of users
   <br> wikipedia I mean
   shoq: 2it';s just a wiki
   <br> 2we need far more than a wiki. that's tiki's strength
   marclaporte: yes
   <br> of course, I don't know what you are trying to do
   <br> and each use case is different
   <br> and you must choose for your project
   <br> Do you have projects with Wizzy?
   shoq: 2sure. this is basically a community site, for planning the use of  very large #hashtag on twitter.
   <br> 2so people will have various skillsets
   <br> 2forum and document authoring (or wiki) are most important
   marclaporte: http://tikiwiki.org/Why+Wiki+Syntax+Is+Important
   ***: caralluna has joined #tikiwiki
   shoq: 2yeah. i know all the strenghts of wiki syntax. But I also know the resistance I get :)
   marclaporte: I think WYSIWYG can be ok for publishing
   shoq: 2You and I love it. Plain users, not so much
   marclaporte: but for intense collaboration, great diffs is essential
   shoq: 2Agree
   marclaporte: <u>shoq</u>:  do you have real experience with users complaining?
   shoq: 2This community has been using Wetpaint. They need more features... but to step down from full blown WIZZY to markup would be a hard sell
   marclaporte: that is speculation?
   <br> or real?
   <br> I repeat the example of Wikipedia
   shoq: 2a bit of both. some key players were adamant, and demanded wizzy. could the battle be fought? Probably
   marclaporte: and Wikipedia has lots of html in the syntax
   shoq: 2Wikipedia is a very generic, very fixed format.
   marclaporte: of course, everyone want everything
   <br> <u>look</u>: You can use FCKEditor which is bundled in Tiki
   <br> FCK is one of the leading Wizzies
   shoq: 2fck is fine
   <br> 2i know it well
   <br> 2i  never have a new theme for it
   <br> 2that i wrote last year
   marclaporte: But don't come complaining to me about problems after
   <br> I will tell you,
   shoq: 2never finished it, but it might be somethign i can contribute
   <br> 2lol
   marclaporte: "Wiki syntax is rock solid"
   <br> let me tell you about a fck bug
   shoq: 2but used can flip thought, right?
   <br> 2they can use wiki if they know it?
   marclaporte: that a company that uses Tiki had
   shoq: 2and fck if not?
   marclaporte: they had weird problems where hyperlinks were destroyed
   <br> sometimes
   <br> they couldn't pinpoint
   ***: SEWilco2 has quit IRC ("Leaving.")
   marclaporte: they spent days trying to figure out
   <br> why some users
   <br> sometimes
   <br> but not all the time
   shoq: 2is fck3 released?
   <br> 2it was a big improvement last year, but very unstable then
   <br> 2it sounds like that problem is more with the tiki integration than fck, right?
   marclaporte: This was the bug: http://dev.tikiwiki.org/wish1703
   <br> <u>shoq</u>:  I think Tiki integration has some blame for WYSIWYG issues
   shoq: 2that issue was closed, but not fixed?
   marclaporte: I think also that it's just a very complex problem and when people use successively different browsers, it causes surprises
   <br> I dunno why it's closed
   <br> so, can you help fix WYSIWYG issues?
   shoq: 2probably, yes. i am pretty good at javascript. PHP, not so much
   <br> 2but my partner is good at both
   <br> 2and ihave capable admins. but again.. it's all a matter of choices. not sure we have the time. but at least I have discussion points for morning meeting
   <br> 2where are you, marc? What time zone?
   marclaporte: Montreal, EST
   shoq: 2oh, good
   <br> 2so you might be around in morning, if we have a question?
   marclaporte: Round-trip WYSIWG &lt;-&gt; wiki works in theory
   <br> sure
   shoq: 2iam going  to way everyone through all this
   marclaporte: what you can do
   shoq: 2do things at least work in ie and firefox?
   <br> 2is there a demo of 2.4 running still?
   <br> 2so I can play without installing&gt;
   marclaporte: for wizzy, I would think so but I don't know
   <br> yes, at opensourcecms.com
   <br> http://profiles.tikiwiki.org/WYSIWYG_Wiki  &lt;- If you do end up using Wizzy, use this profile
   shoq: 2i remember my partner grousing about "unfriendly URLS" in tiki. are there solutions for that?
   marclaporte: <u>shoq</u>: : yes there is
   <br> I suggest to start in plain wiki, and add Wizzy later only if necessary, and ideally just for some pages that really need it
   <br> <u>URLs</u>: as you can see, the URL above is short
   <br> since a long time now, you just put .htaccess file and short URLS can work
   ***: mib_s861y6 has joined #tikiwiki
   marclaporte: the problem is that URLs generated by Tiki are still long ones
   <br> this is improved in 3.0
   <br> (experimental)
   shoq: 2The news theme on that site is plain, but menus are working
   marclaporte: this would be a place you could help
   shoq: 2perhaps we could just dress than up, a bit
   marclaporte: not to difficult
   shoq: 2is that theme stable?
   marclaporte: yes, thenews is quite stable
   <br> the most stable of all 3.x themes I would say
   shoq: 2and wizzy will at least work in it?
   marclaporte: 1- because we used it more
   <br> 2- because it's simple
   shoq: 2maybe that's our annwer
   marclaporte: there is a SEFURL recipe. Just need to deploy the recipe to places where it's not yet deployed
   <br> <u>shoq</u>: : http://dev.tikiwiki.org/How+to+get+commit+access
   shoq: 2i will show this to simon first thing
   <br> 2boy, I am glad you were here
   <br> 2tell me this. i could not tell in the docs. Is there a module that can generate dynamic menus of a set of child pages?
   marclaporte: :-)
   shoq: 2so that if a user adds a chilld page, it's automatically in a breakcrumb or sidebar navigation menu?
   marclaporte: within the page, us {toc}
   shoq: 2that's really what my users are used to
   <br> 2and in the side?
   marclaporte: I guess {toc} in a module
   <br> modules are boxes on sides (in Tiki Lingo)
   shoq: 2and the module could be specific to one set of pages?
   marclaporte: gimme 3 min, I will try something
   shoq: 2let me find a wet paint  site that resembles this
   <br> 2there  are a few
   marclaporte: <u>shoq</u>: :do you think you will make many sites?
   shoq: 2hard question to answer. we've discussed that. depends greatly on how things go
   marclaporte: ok
   shoq: 2we might make a great many
   marclaporte: if you do, two important tools
   <br> <u>TRIM</u>: http://dev.tikiwiki.org/TRIM     to deploy/manage many sites
   ***: Lucymoz has quit IRC (Read error: 110 (Connection timed out))
   shoq: 2ah
   <br> 2subsites?
   marclaporte: http://profiles.tikiwiki.org/ -&gt; to pre-configure sites
   <br> no, not subsites, but distinct installs
   shoq: 2great
   marclaporte: say you have 20 projects
   <br> 20 tikis
   <br> on 8 severs
   <br> servers
   <br> TRIM helps you manage them all
   shoq: 2great
   <br> 2http://p2pt0.wetpaint.com/
   marclaporte: install, upgrade, backup, security monitor, etc
   shoq: 2now look at that left side nav
   <br> 2thats wetpaint
   <br> 2notice it's a tree menu of wiki pages
   <br> 2very easy for users to "move" pages to the tree
   -: marclaporte looks
   shoq: 2it's very popular
   marclaporte: top menu always stays the same?
   shoq: 2yes
   <br> 2throught the site, yes
   marclaporte: this is your site?
   shoq: 2but of course, pages get added. but no, the nav  doesn't shift, and that of course is one of the things that should be improved
   <br> 2nah.. just one of many wetpaint sites
   <br> 2a million of them
   ***: xavi has joined #tikiwiki
   xavi: toctoc-morning...
   marclaporte: yo xavi
   shoq: 2hi
   -: marclaporte creates wetpaint account to test
   shoq: 2easy enough
   xavi: <u>marclaporte</u>: still around?
   -: xavi wonders which brand are the "batteries" inside marclaporte...
   shoq: 2you "move pages" with the menu "other options" on the end of the page bar
   <br> 2it is the ONLY wiki to do have this. And it's very popular. If tiki had it, it could be a big deal
   marclaporte: <u>wow</u>: http://tikiwiki.wetpaint.com/
   <br> I didn't know about his site
   <br> <u>xavi</u>: my batteries are better since I stopped travelling
   xavi: :-)
   shoq: 2it's done very very well
   <br> 2there are two
   <br> 2wetpaint, which is huge in education
   <br> 2and pbworks, which does better in biz
   <br> 2pbworks lacks that navigation
   <br> 2and it hurts them
   <br> 2wetpaint has forums added to every page
   <br> 2that's all good
   <br> 2but thats' about it
   <br> 2after that, it starts to fall down
   <br> 2and the forums are really not well done
   <br> 2and the wizzy editing can be slow and awkward at times, but beginners do love it
   <br> 2but you know how that goes, beginners love anything somewhat easy
   <br> 2I have wanted that navigation for years
   <br> 2and presto, they added it, and it's been the most important selling feature
   <br> 2people simply do not  kknow how to structure a site or a wiki, so giving them  TOC is pointless
   <br> 2they need place to see new pages as they create them
   <br> 2in an tree.  then they can move them
   <br> 2this is hurting google sites too
   marclaporte: http://tikiwikiworld.wetpaint.com/?t=anon
   shoq: 2they have the side navigation, but NO TREE
   <br> 2(yet)
   marclaporte: <u>shoq</u>: : are you familiar with structures in tiki?
   shoq: 2i remember we played with structured wikis some
   <br> 2and yes, these are just structures, right?
   <br> 2can we simple render the structure in the sidebar, that way?
   <br> 2simply
   marclaporte: <u>shoq</u>: I am pretty sure this is done for 4.0
   shoq: 2lol
   <br> 2which is how far away?
   marclaporte: Oct 2009
   <br> but you can backport to 3.1
   <br> to 3.x I mean
   <br> just a few file changes
   shoq: 2In the interim, we can do that, but it just has to be inpage?
   <br> 2is there a collapsing TOC for the structure?
   marclaporte: I am testing on doc.tw.o
   shoq: 2but we just have to  float it inside the main body?
   <br> 2ah
   marclaporte: {toc} in module doesn't work
   <br> but yes, {toc} anywhere in a page works well
   <br> and sometimes, it makes sense to put
   <br> sometimes, not
   shoq: 2and it's collapsible, as the category menus are ?
   marclaporte: dunno
   <br> default it just list
   shoq: 2Well..we could drive the system
   marclaporte: maybe collapsible option
   <br> my take on this
   shoq: 2and use absolute positioning
   marclaporte: :
   shoq: 2and place it on the leeft
   <br> 2left
   marclaporte: improving the rendering of structures will be easy
   <br> and it's something that tiki needs so you can share back and are not alone
   shoq: 2yes, and my guy is good at that. so long as getting up to speed on structures is easy
   marclaporte: Sylvie, Seb and other are working on that
   <br> However
   <br> The problem with structures is UI to move things around
   shoq: 2what do people do for page navigatino now? They just manually make little child page indexes?
   marclaporte: it's a top of page
   shoq: 2can a categories tree be used as a navigation module?
   marclaporte: look at doc.tikiwiki.org
   <br> <u>shoq</u>: : yes, I have an example on profiles.tikiwiki.org
   <br> a little ugly but it works
   <br> about structures: look at top here: http://doc.tikiwiki.org/tiki-index.php?page=Module&amp;bl=y
   shoq: 2did i  have to be signed in to see this top of page example?
   marclaporte: no
   <br> (I think)
   shoq: 2you just meant the top pull down nav menus?
   <br> 2that's not dynamic,
   marclaporte: correct
   <br> but if people click arrows, they can navigate all pages
   shoq: 2I am talkign about if users create a child page, is there anythig that lets them find it easily from their current location
   <br> 2or is it jsut "out there" until they link to it?
   marclaporte: <u>shoq</u>:  if {toc} is in current page, they see
   <br> I have somewhere a hack about structures and menus
   <br> hold on
   shoq: 2brb.. gotta brush :)
   marclaporte: http://dev.tikiwiki.org/wish1045  -&gt; here is wish.   In comments, there is a link to the 4.0 code
   <br> <u>shoq</u>: : where are you?
   <br> {wikistructure id=2}
   <br> is a feature
   ***: chibaguy has joined #tikiwiki
   marclaporte: ah chibaguy
   chibaguy: polom
   marclaporte: shoq has questions for you :-)
   chibaguy: i read the log.
   xavi: hi chibaguy
   chibaguy: hi xavi
   marclaporte: <u>shoq</u>: : categories are an option too. YOu can have hierarchy but no order
   -: xavi nearly finished reading the log
   shoq: 2back
   <br> 2hi chib
   <br> 2chib, are you the Eatlon  themer?
   xavi: marclaporte and shoq: remember also http://tikiwiki.org/TikiLiveCD for a working 2.4 and 3beta out of the box
   chibaguy: I'm not the original designer, but I did the Tiki implementation.
   xavi: and shoq and marclaporte: wizzy and wiki out and return doesn't produce 100% perfect results
   shoq: 2is the left nav supposed to be working as pull downs., or vertical toggles (as they are)
   <br> 2we assumed they are supposed to be pull downs, and it's broken
   xavi: I mean: for a production site aiming to last many months or years, you'd better suggest your users to use wysiwyg or wiki syntax on each page: one or the other, but not both indistinctly and changing the editor on each page
   chibaguy: Eatlon for Tiki 3 is here: http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki/mods/trunk/themes/eatlon_for_tiki_3.tar.gz?view=tar ...
   <br> But I have made more changes that aren't committed yet.
   <br> You can see tiki3 and eatlon at http://zukakakina.com/tw3/ (and select the theme).
   shoq: 2great.  is the menuing  problem   near to a fix?
   chibaguy: What menuing problem?
   <br> (sorry)
   shoq: 2ok, the top menus of ealton are pull down menus, on mouseover, right?
   marclaporte: bedtime for me
   shoq: 2we assumed the  left side nav was supposed to be doing the same thing
   <br> 2but it's not
   chibaguy: Yes, both suckerfish and PHP Layers menus
   xavi: g'night marclaporte
   marclaporte: <u>shoq</u>: : as a reminder:
   chibaguy: ..are supported.
   shoq: 2not on our site, or yours
   <br> 2nite marc
   <br> 2thank you
   marclaporte: I think making nice output from structures is low hanging fruit
   chibaguy: g'night marc
   marclaporte: the challenge is that it's tedious to manage structures for end users
   <br> easy to add page
   <br> but aweful to move around
   <br> we'd need some UI work
   <br> jquery would be nice
   shoq: 2yeah
   chibaguy: The left-column suckerfish and php layers menus have a flyout for the second level.
   marclaporte: so if you build it and they fill it, it's ok
   shoq: 2right, but that is not working in 3 for us
   marclaporte: if they must manage, maybe categories is better
   <br> because category picker is easy
   shoq: 2and then categories could act like folders, with articles in them?
   marclaporte: yes
   xavi: shoq : structures work pretty well in 2.4. See this quick howto, if interested to see them in action on a real (production) site: http://www.iesbarcelona.org/ESSO350/How+to+edit+the+Wiki+Structure
   marclaporte: and pages can be in one or many
   shoq: 2but pages cannot have child pages
   marclaporte: only limitation is  that there is no order, so you can't print a book
   xavi: I added some mini howto for my newbie students (some of them and very very low skilled with computing, even if at university)
   shoq: 2they can only be placed in child categories, right?
   chibaguy: (If that 'not working' is about the menus, then something must be wrong/incomplete at the installation. These normally work as designed.)
   xavi: <u>shoq</u>: yes, pages can have child pages
   marclaporte: can be placed anywhere
   <br> <u>shoq</u>: : login to profiles.tikiwiki.org and play with it
   <br> just add pages to categories and see how they appear in menu
   shoq: 2I will do this in morning, after meeting
   <br> 2i can do that at profiles.?
   marclaporte: as a bonus, people can watch categories and get email
   shoq: 2Chiba
   <br> 2http://p2tag.com/tiki-index.php
   <br> 2can you register there
   <br> 2and I can show you the menu bug?
   marclaporte: yes, profiles.tikiwiki.org  -&gt; left menu is build from categories
   shoq: 2I think you have to be logged in
   chibaguy: (Incidentally, the theme files at zukakakina.com/tw3 are in the middle of switching to a new css file method, so things may not be 100%.)
   shoq: 2No, you can see the problem
   <br> 2without even logging in
   xavi: <u>marclaporte</u>: but new pages are not shown in the left menu where the categories are
   shoq: 2you can see the problem in left menu
   <br> 2and your demo site has the same problem
   xavi: I never tried myself, but there is a module for "structures toc" even in 2.x, I think...
   chibaguy: Did you get the Eatlon files from the link I gave at 14:48 ^^ ?
   shoq: 2you mean just now?
   chibaguy: I mean is http://p2tag.com/tiki-index.php using those files?
   shoq: 2I cannot install new files. I have to have the admin do in morning
   <br> 2they are using 3,0 out of the box
   <br> 2whatever that is
   <br> 2or wherever she get the theme
   <br> 2she got nothing from the svn
   chibaguy: Well, the Eatlon files for Tiki 2 won't work correctly with Tiki 3, so that'll be the first thing to change.
   shoq: 2so what exactly does she want?
   chibaguy: She can get the compressed archive at the link I gave above, decompress it, and put the files into the right places in Tiki's directory.
   <br> If she installed Eatlon before, she'll know what to do.
   shoq: 2gotcha
   <br> 2let me find that link
   chibaguy: If any problems, I'm usually here at this time of day and will be glad to help.
   <br> (The old Eatlon files should be removed, and the new ones put in their place.)
   shoq: 2GREAT
   <br> 2you guys rock
   <br> 2so we should look at the structures module in 2.x?
   <br> 2Chib, is the theme stable enough in forums, main nav, and wiki?
   <br> 2I can help there. CSS I can ")
   <br> 2do
   xavi: you could give it a try
   <br> to structures module in 2.4, I mean
   shoq: 2i could not code that
   <br> 2but i could help design it
   -: xavi wonders if that module is documented.... checking...
   Tikiwiki|bot: New Forum Posts: (Noob) img tag not seeming to work for me - http://tikiwiki.org/tiki-view_forum_thread.php?forumId=4&amp;comments_parentId=32875
   shoq: 2chiib. xavi.. hit my wall for now.  I must sleep or meeting will be washout. WIll you be around in morning?
   chibaguy: sorry, was away. Most of the Eatlon css is carried over from the Tiki 2 file, so should be ok throughout TIki, pretty much.
   shoq: 2great
   chibaguy: Of course if you see places to improve, that'd be great.
   shoq: 2let's get her started on that
   xavi: shoq, maybe not me.
   shoq: 2i just wish i had some answer for this navigation
   xavi: but you are in god hands in this channel with its current inhabitants
   chibaguy: (sometimes I get lazy, or maybe don't have some feature or other activated when doing/checking the theme.)
   xavi: s/god/good (or maybe also "god"???)
   shoq: 2are them some  examples of someone doing simply page structures like that?
   chibaguy: I'm in Japan, so don't know just what you mean by morning, but I'm usually around, more or less.
   shoq: 2lol
   <br> 2i mean in 7 hours
   chibaguy: what -&gt; when
   <br> Yep, should be here.
   shoq: 2great
   <br> 2http://tikiwiki.org/tiki-my_tiki.php
   <br> 2that page is broken
   <br> 2on my Ubuntu Firefox 3
   <br> 2is it on yours?
   ***: LordVan has joined #tikiwiki
   chibaguy: yeah, I know that's a mess.
   shoq: 2oh, ok
   chibaguy: It was started on an ajax implementation that was abandoned, I think.
   shoq: 2are you  japanese, or just living there?
   chibaguy: american long-time resident.
   shoq: 2never been. would love to go
   xavi: <u>shoq</u>: see this navigation from a wikistructure (or right column): http://www.iesbarcelona.org/ESSO350/
   <br> using 2.4
   <br> page names are too long for that, I know. It's just a quick and dirty trial from the structure I was using with my students, the one documented here: http://www.iesbarcelona.org/ESSO350/How+to+edit+the+Wiki+Structure
   shoq: 2Now if user added a page, would it show up in the structure on the fly?
   xavi: that navigational module is generated on the fly from the structure
   <br> yes
   shoq: 2so all we have to do is make it collapsing wiht jquery menus?
   xavi: <u>shoq</u>: yes, for instance: That would be lovely!
   shoq: 2and the structure be limited to one set of pages, and not the whole site?
   xavi: btw, it's not a pre-defined module, but pre-defined content to be added on a user-defined module
   shoq: 2but the instructions were from the structure docs above?
   xavi: <u>shoq</u>: it's predefined to a structure page. The smaller the structure, the smaller the content. Not necessarily all
   <br> and it's already coded to show only down to several level of the structur enodes
   <br> see http://doc.tikiwiki.org/toc
   -: xavi trying the maxdepth param in that 2.4 site
   shoq: 2So basically, so long as TOC appears in main page body
   xavi: <u>shoq</u>: btw, which theme style are you using in tw.o? (in your acount, I mean)
   <br> with strasa, everthing looks fine to me...
   shoq: 2we can do dynamic structures as users add pages
   xavi: <u>shoq</u>: yes
   shoq: 2we were using strassa, but two of our people just disliked it
   <br> 2they want ealton
   <br> 2lol
   <br> 2i think i like news.. but i prefer simple
   xavi: http://tikiwiki.org/tiki-my_tiki.php is showing ok to me with strasa. that's what I mean.
   <br> what was yuor problem?
   shoq: 2i find it hard to believe with all the wikis build with tiki, no one build something like the wet paint module, using toc
   xavi: maybe I didn't understand the layout problem you mentioned....
   shoq: 2strassa was ok
   <br> 2our problem was ealton
   xavi: ah, ok
   shoq: 2Ok, thank you guys. I will reread all of this in morning
   <br> 2thanks again
   <br> 2will let you know how we progress with ealton
   <br> 2nite!
   xavi: <u>shoq</u>: maxdepth is not working in 2.4 [wikistructure id= } navigation menus on the side, but it is when the {toc} is generated in the main body of the page
   -: xavi disabled that trial menu from that production 2.4 site
   xavi: nite
   shoq: 2would you guys recommand 3.0
   <br> 2or still with 2.4 for now?
   <br> 2marc was iffy on that
   <br> 2it sounds like  we will want things in 3
   <br> 2but don't know
   xavi: it's up to you and your users, I would say, how strict they will be with tiny bugs here and there for some weeks/months (you said you needed site for production for last week)
   shoq: 2tiny bugs
   <br> 2no problem
   chibaguy: I'm not sure yet about 3.0. For sure it has a lot of new features and some things are done more nicely....
   shoq: 2big bugs, yes
   xavi: if it was me, for real users (not skilled and afraid of wiki syntax), and used to wetpaint sites, etc, I would go with 2.4, and when they are used to it, change/upgrade to 3.0
   chibaguy: ....but because a lot is new, using 2.4 would be more predictable, for a live site that needs to be solid.
   shoq: 2what do you see tiki competitive with today/ Drupal?
   <br> 2what's your nearest?
   chibaguy: 3.0 is still being debugged.
   xavi: tiny vs. big: it's subjective. Search was failing completely for anonymous users for a week at least (fixed yesterday)
   <br> on 3.0
   <br> is this big for you, or just tiny? (for registered or editors, that seemed to be working fine)
   <br> this is just an example.
   shoq: 2search is big
   <br> 2oh
   <br> 2for anonymous
   xavi: my users would have got impressed negatively if search didn't work for them for a week!
   shoq: 2small
   <br> 2:)
   xavi: so it's up to you, I would say
   <br> if in doubvt, then, go for 3.0, and help improve it! :-)
   <br> and document it! ;-)
   shoq: 2my problem is these people are used to creating a page, and hooking it to that wetpaint.com left nav tree
   <br> 2easy
   <br> 2they are totally used to that
   xavi: http://doc.tikiwiki.org/Documentation need lots of care to upgrade many pages to hold information about 3.0 changes
   shoq: 2i need some answer to that
   <br> 2but enough
   <br> 2thanks guys
   <br> 2more tomorrow
   xavi: {wikistructure id=N} does this job
   <br> ok, c u
   chibaguy: marc wrote some pages on tikiwiki.org about comparisons to drupal, joomla, etc.
   shoq: 2you mean, wikistructure is the same thing. We jsut can't display it in side bar
   <br> 2right?
   xavi: you do can display in the side bar
   <br> I showed it for you a moment ago on that 2.4 production site
   shoq: 2Oh
   <br> 2right
   luciash: polom polom
   shoq: 2and we could set that up from existing code?
   <br> 2and just work in  the collapser
   xavi: yes, from out-of-the-box 2.4
   luciash: huh, i cannot read the dark blue on black background :-p
   shoq: 2but not 3?
   xavi: <u>shoq</u>: probably yes also, ....
   <br> just trying right now...
   shoq: 2oh , that would rock
   xavi: yes, it works even with the maxdepth param! :-)
   <br> see this in the left menu: http://doc.tikiwiki.org/Documentation
   <br> compare the menu in the left with the menu in the central column
   <br> in the left column, set to display maxdepth=2 (only headers of 1st and 2nd level), and in main page, show full strucgture, with all levels
   <br> Tiki 3 rocks! :-D
   ***: franck has quit IRC ()
   xavi: <u>shoq</u>: go for tiki 3 and add the jquery thing to that navigation thingy :-)
   <br> shoq, did you see that on doc.tw.o?
   <br> I need to disable it after that, since that's the production site for documentation, and too manu menus right now with that enabled
   shoq: 2well this looks like what we we want
   xavi: yes!
   shoq: 2so long as plain dumb users can just add  to the structure with no training
   -: xavi is looking forward to see the jquery-fication of that dynamic navigation menu from structures.... :-)
   shoq: 2check out superfish for jquery
   xavi: if they can understand this type of image: http://www.iesbarcelona.org/ESSO350/How+to+edit+the+Wiki+Structure
   shoq: 2buddy of mine did that in australian
   xavi: it would take them 1 min seconds to figure out hjow to do it, do it, and ensure that they got it right. 1 min.
   -: xavi goes back to work on other stuff
   xavi: good luck, shoq, and keep us informed
   <br> module removed from doc.tw.o
   luciash: <u>shoq</u>: i cannot read all the log but i suppose you figured the left menu out
   shoq: 2back
   <br> 2was looking it all over
   <br> 2luc.. i think  we just need the right css
   <br> 2or did you mean the dynamic toc menu?
   <br> 2thank you all
   <br> 2we have much ti figure out
   xavi: <u>shoq</u>: welcome back to TikiWiki Community! :-) (after 3 years)
   chibaguy: shoq, Tiki 3 already uses superfish for css menus.
   shoq: 2thanks you!
   <br> 2hahah
   chibaguy: if jquery is turned on by site admin.
   shoq: 2he will be thrilled
   <br> 2that means
   <br> 2i have already contributed
   <br> 2because  i did a LOT of work on superfish
   <br> 2mostly the design and css debugging, and the autowidths
   <br> 2which rock
   xavi: free software (FLOSS) rocks! :-)
   shoq: 2but that was about 9 months ago, so now i wil be rusty
   <br> 2but we will get back together
   xavi: <u>shoq</u>: were are you from?
   chibaguy: shoq, our css menus are now (in Tiki 3) kind of a mix of earlier work on suckerfish, since in tiki 3 jquery is optional/experimental...
   <br> ...so there should be a reworking of css menus for TIki 4 (refactoring, etc.)...
   <br> so your help would be much appreciated, if possible, I think.
   shoq: 2yeah, superfish took what was good about suckerfish, blended with jquery, and threw out the crap
   <br> 2Well, i can't promise yet. I have many things to analyse and disucss with partners. but this is more promising than it was
   <br> 2thanks guys
   <br> 2good night!
   chibaguy: Tiki menus also have classes for menu levels, etc., so it all needs to be blended nicely.
   <br> good night.
   ***: mib_zwel0q has joined #tikiwiki
   <br> mib_zwel0q has quit IRC (Client Quit)
   luciash: hi chibaguy and xavi :)
   xavi: hi luciash
   chibaguy: hey luciash
   <br> Actually (to clarify) I think the css menus are in good shape, but since jquery has been added, maybe they could be improved, be more efficient. Something to look at maybe.
   xavi: +1 (good shape), and improvable with jquery maybe
   ***: Wilkins has joined #tikiwiki
   luciash: i just thought he forgot to add overflow=y to the module
   <br> and type=vert
   <br> <u>chibaguy</u>: i still wonder why it produces no shadows in Tiki with superfish
   chibaguy: oh, maybe so, luciash. I forgot about that point.
   <br> yeah, I wonder too.
   ***: gezza has quit IRC ("http://www.mibbit.com ajax IRC Client")
   luciash: i also thought maybe it could be better to have some longer delay for the superfish menu disappearing (it's configurable in jq params)
   <br> sometimes i have trouble especially with laptop touchpad to operate with the css menus
   xavi: sylvieg (for whenever you are up): I've deleted the "test" gallery (with no images) that you created in doc.tw.o
   <br> fyi
   -: xavi is documenting a  bit the new image upload behavior in 3.0, using doc.tw.o as example, and that test was kind if ugly in the screenshots
   xavi: s/kind if/kind of
   <br> <u>chibaguy</u>: there is display problem with strasa (at least) and file gallery browser
   <br> you click on it to collapse file gallery browser on the left of http://doc.tikiwiki.org/tiki-list_file_gallery.php?galleryId=0&amp;filegals_manager=editwiki ,a nd it collapses ok
   <br> you click again, to expand it, and it expands ok, and less than 1 sec. later, it shrinks to a few hundred pixels wide
   <br> using ff3
   <br> not important, but I just noticed
   luciash: <u>xavi</u>: i'd recommend not to use the strasa theme for documentation but the default one, it's more clean and better for printing the screenshots imho... just my 2 cents
   xavi: uh? strasa showed up as my default, afaik...
   <br> yes :-) I have "site default" in tw.o
   <br> so that, I imagine that this is why I get also strasa in doc.tw.o? (intertiki passing that info?)
   luciash: huh ? default is still thenews after fresh install nope ?
   xavi: well, default in tw.o is strasa
   luciash: i mean for making screenshots
   <br> for documentation
   LordVan: hi
   chibaguy: yes, I see what you mean, xavi. At first glance, that looks like something that I don't know how to fix. ;-)
   LordVan: maybe i'm stupid 7 blind, but I can't find where to activate plugins in the admin interface .. can someone help me out please?
   chibaguy: admin textarea, I believe.
   xavi: ok, oh well, I like some more colors in the screenshots... like strasa... but I understand what you say about printing... I dunno what to do... anyway, screenshots are in many colors right now... (xavi copes well with diversity, in fact)
   LordVan: as mentioned iun http://doc.tikiwiki.org/tiki-index.php?page=Wiki+Plugins
   <br> chibaguy, ok thanks i'll look
   -: chibaguy has learned that admin textarea is the secret hiding place for such things.
   xavi: <u>LordVan</u>: and if you can update documentaion pages for that, that would be awesome! :-)
   luciash: can we still rename it to Edit &amp; Plugins for 3.0 ?
   xavi: <u>chibaguy</u>: hide/collapse issue: ok, not important nor urgent imho if not trivial to fix
   LordVan: first i need to figure it out ;)
   xavi: <u>luciash</u>: "Edit area &amp; Plugins"?
   <br> <u>LordVan</u>: I know, but when you figure it out, you'll probably not come back to offer documenting it, so that's why I'm asking this right now, so that when you figure it out, you know that you have been requested to help improving documentation pages about it :-P
   <br> otherwise, doc.tw.o will remain outdated for months, if all users asking for help (becuase they don't find things in the documentatation) don't help to improve it
   ***: aardvarq has joined #tikiwiki
   xavi: s/months/years
   <br> in fact
   <br> sorry to feel like a (time) bank robber, but I honestly think that otherwise it's not a sustainable way of ensuring a healthy live for doc.tw.o...
   LordVan: yeah i know
   xavi: in case anyone sees me as a time robber! :-)
   <br> do what you can, as we all do
   -: xavi back to documenting
   CIA-46: tikiwiki: 03chibaguy * r18463 10/branches/3.0/styles/thenews.css: [FIX] Tiki-top suckerfish menu top-level items' side border goes full height again.
   Beestje: quick Q : what tools / environments do you guys use to code and / or design?
   <br> I'm using dreamweaver on OSX for coding, but PHP coding doesn't go smoothly... for designing I use the Firebug plugin from Firefox
   ***: franck has joined #tikiwiki
   Beestje: I want to be more active as a developer as well and I'm just wondering what tools you use... :)
   ***: Wilkins is now known as Wilkins_
   xavi: <u>Beestje</u>: in case it helps (I'm not a coder, nor a designer in fact, but power user). I compiled a list that you can see through "Tools" pages at doc.tw.o See links from here: http://doc.tikiwiki.org/Tools
   <br> hth
   chibaguy: I use Dreamweaver, too, as editor for smarty templates, also TopStyle for css files.
   xavi: and you know, as always, you are very welcome to improve that list with whatever answers you get from others or from yourself ;-)
   chibaguy: Fireworks for graphics, WinMerge for file comparisons, TortoiseSVN, FF+ Firebug
   LordVan: i prefer gimp for gfx ;)
   <br> chibaguy, but for windows winmerge &amp; tortoisesvn r a must i agree - although i use linux myself ;)
   -: LordVan is not a tiki dev though
   chibaguy: yeah, I like winmerge and tortoisesvn a lot; they do the job really well, I think.
   LordVan: although tortoise has a nice merge tool too ;)
   chibaguy: (though tortoisesvn slows down my file manager displays quite a bit sometimes)
   LordVan: hmm
   xavi: Beestje , LordVan and chibaguy: that would depend on the platform/OS of the user. Beestje seems to be using OSX. That list of Tools pages comprises windows, linux MAc and multiplatform tools
   <br> in different pages
   LordVan: yep
   <br> i duno bout mac
   <br> although gimp works on mac too ;)
   xavi: http://doc.tikiwiki.org/Linux+tools
   chibaguy: I'd like to get more familiar with gimp and inkscape but don't have much time to explore, so just do jobs with familiar tools.
   xavi: http://doc.tikiwiki.org/Mac+tools
   <br> http://doc.tikiwiki.org/Windows+tools
   chibaguy: have used fireworks for a long time so it's easy.
   xavi: http://doc.tikiwiki.org/Multiplatform+tools
   <br> fyiç
   LordVan: :)
   luciash: <u>xavi</u>: Edit area &amp; Plugins sounds good
   chibaguy: Does "Edit area" have a clear meaning?
   luciash: <u>Beestje</u>: try Eclipse (jonny uses that on OS X), i use it on Linux and for simple/quick editing i use vim
   <br> <u>chibaguy</u>: still far better than textarea
   <br> <u>chibaguy</u>: what do you propose ?
   -: chibaguy has no better idea ;-)
   chibaguy: How about "Editing and Plugins"?
   luciash: it could be "Wiki Syntax &amp; Plugins" too but it's not shorter ;)
   chibaguy: Gotta take dog out. will be back soon...
   luciash: give your dog his time, gary ;)
   <br> no hurry :)
   ***: tomb_ has joined #tikiwiki
   xavi: luciash and chibaguy (after dog walk): "Edit window &amp; Plugins"?
   ***: FrankP_german has joined #tikiwiki
   xavi: dunno, many simple users might call it "ah, at the editing window"...
   luciash: <u>xavi</u>: nope :) window is confusing
   xavi: ok
   <br> confusing for devs (maybe not for simple users), but I agree, it's not a good name for everyone
   luciash: "Editing &amp; Plugins" could work too as gary suggested
   xavi: however, I can foresee many users wondering: "Editting" what? Articles? trackers?....
   <br> s/editting/editing
   <br> my 2 cents
   luciash: unfortunatelly i have no time left to change it so if you do, please, welcome
   xavi: not enough time left today for that, sorry (still aiming to finish documenting about image upload + translatio + non-tiki work urgent for today)
   luciash: gotta plenty of work here still so i think i'll be available only after 3.0 release and switch to trunk
   xavi: so, we can leave it as it is for 3.0
   <br> I would say
   luciash: better would be to change but if chibaguy doesn't do that simple change, we have to live with that explaining users where to find plugins all the time until 3.1 ;)
   <br> <u>marclaporte</u>: what do you think ?
   ***: artbody has joined #tikiwiki
   luciash: :)
   <br> bbl
   Beestje: wow tnx for the tips!  Boss called me aside for a meeting so couldn't respond sooner :)
   xavi: <u>Beestje</u>: np
   <br> for the record: I?ve created this page: http://doc.tikiwiki.org/Module+wikistructure
   <br> I know this is not a real module as the other predefined ones, but from the point of view of end users, they will not mind (I would say), and they would look for "module structure" (probably) in documentation to see if they can do what that shoq user wanted to do (long discussion/conversation hours ago today here in irc)
   <br> hth
   ***: Beestje has quit IRC ("ChatZilla 0.9.84 [Firefox 3.0.10/2009042316]")
   xavi: luciash and chibaguy: how would you proceed with PluginVersions display: each time I'm reading a page with plugin version usage, I wonder how long does it last that version usage, and when does the static content follows.
   <br> I started adding manually boxes (^versions plugin and text  ^ ) so that I can see that...
   <br> ... but I'm wondering if this shouldn't be something to add by default to whatever tpl (if any) is using pluginversions...
   <br> of php, whatever (add display info in the code so that each theme style can be set up as desired for each site
   <br> if in doubt, see http://doc.tikiwiki.org/Manual+Installation (with boxes added) or http://doc.tikiwiki.org/Upgrade (without boxes added)
   CIA-46: tikiwiki: 03luciash * r18464 10/branches/3.0/lang/cs/language.php: czech language update
   chibaguy: xavi, looks like div class=versions needs a border or background color.
   CIA-46: tikiwiki: 03luciash * r18465 10/branches/3.0/lang/cs/language.php: minimal file ready for the final release generated using "get_strings.php?lang=cs&amp;groupwrite&amp;nohelp&amp;nosections" params
   chibaguy: or some graphic way to distinguish from nonversions content.
   xavi: <u>chibaguy</u>: yes, where should I add that?
   <br> at the php file itself? (I'm newbie on this)
   luciash: <u>chibaguy</u>: strasa horiz css menu is too low z-index
   chibaguy: ah, what does it conflict with?
   luciash: submenu items go under right column content
   chibaguy: xavi, I can do the versions div styles.
   <br> it should be in the theme css file.
   xavi: <u>chibaguy</u>: great, thanks
   <br> ah, ok
   luciash: <u>chibaguy</u>: more specifically they go under the module titles
   chibaguy: luciash, maybe because of module titles positioning.
   CIA-46: tikiwiki: 03luciash * r18466 10/branches/3.0/lang/cs/language.php: argh ! running get_strings with these params removed "$lang=Array(" too :-/
   xavi: argh, plugin list pages kicked me out of the edition due to sql error :-/
   -: xavi will try again (with backup of his edition this time :-) ) since plugin list pages seems much more powerful than TITLESEARCH, that he was used to, and somebody assked about them both in the releaseprocess30 page
   ***: danopia` is now known as danopia
   CIA-46: tikiwiki: 03luciash * r18467 10/branches/3.0/templates/tiki-show_help.tpl: [FIX] there's no "display: all" in CSS
   ***: Caarrie|sleeping is now known as Caarrie
   <br> spoonypjk has joined #tikiwiki
   <br> FrankP_german has quit IRC ("Nettalk6 - www.ntalk.de")
   chibaguy: luciash, what browser is having a problem with css menu dropdowns and module titles? It tests ok at my site in FF and Opera.
   luciash: FF3 and Opera too
   chibaguy: are other themes ok?
   luciash: <u>chibaguy</u>: with jQuery off
   <br> <u>chibaguy</u>: yes, thenews is working fine
   chibaguy: That's something I had been checking because IE had some trouble at one point.
   <br> It's may be related to the way the top menu is positioned in strasa.
   luciash: try jQuery off
   chibaguy: jquery is off at my test site already.
   ***: Beestje has joined #tikiwiki
   chibaguy: but I don't have menu dropdowns long enough to hit the right column. ;-)
   <br> in strasa
   luciash: hehe
   <br> then i don't wonder it works for you :)
   LordVan: any recent updates i should apply to my svn install from last week?
   <br> important stuff i mean
   chibaguy: :P
   luciash: i have mootools off too if it matters
   chibaguy: i'll add some menu items...
   <br> hey, we only add important stuff. ;-)
   <br> (LordVan )
   LordVan: chibaguy, ;) i mean like big fat security hole or sth
   <br> obviously i'll upgrade to 3.0 when it's out instead of svn
   chibaguy: ah, no security fix that I know of.
   luciash: <u>chibaguy</u>: i've just switched jQuery on and the problem persist
   <br> <u>LordVan</u>: yep, there was some sec related fix
   LordVan: now which is it ? ;)
   luciash: see the SVN logs ;)
   LordVan: :P
   <br> what is general estimate for 3.0 anyway? days?weeks?
   luciash: days
   LordVan: cool
   luciash: it should be yesterday already
   LordVan: so all i'll have to do once it is out remove my svn tree and dump 3.0 in there (after copying the config file i guess)
   <br> - i don'T want all the .svn dirs,.. ;)
   luciash: <u>chibaguy</u>: seems jQuery or Mootools have no effect on the css menu bug
   xavi: <u>LordVan</u>: again: http://doc.tikiwiki.org/Upgrade
   <br> so LordVan: please, first read the docs. After that, if possible, ask for help, and please, help to improve them
   LordVan: xavi, sure, but the docs don'T mention svn 3.0 to release ;)
   -: xavi wonders how many time he will have to repeat it...
   xavi: well, they do mention from some 3.0 to 3.0beta4
   <br> someone like you asked weeks ago, we answered, and request him to document it, and he did.
   chibaguy: luciash, now that I have 10 menu items in the dropdown, I confirm the problem. :-)
   xavi: now you are asking for the "release" (which is not even ready).
   LordVan: cool ;) looks like i didn'T read properly
   chibaguy: This is in opera, first test.
   xavi: so please, read what is in there, ask for help, and improve it, please
   LordVan: xavi, i knwo that i was just wondering that all
   xavi: Some minutes ago I just moved that under a tab of the version plugin...
   <br> so since some minutes ago, that link should be under the "Choose an upgrade path &gt; Others"
   luciash: <u>chibaguy</u>: i'm editing strasa now so maybe i can fix it
   xavi: please, feel free to take those links out of that version-name others if you feel that for a general audience they might be somewhere else (out of the versions plugin, maybe?)
   LordVan: xavi, ok lemme reload the page
   <br> ok seen it ;) thanks
   chibaguy: ok, luciash, I see that menu has z-index: 0.
   <br> xavi, I'll do the versions plugin css and add the highlight css where it's missing (for that plugin) -- in coelesce so far noticed.
   xavi: thanks chibaguy, and in fact, I could see inmy local that the highlight that I committed is better than nothing, but not as clear as in thenews, since the highlighter yellowish color falls behind the button like bluish in strasa
   <br> so feel free to improve (but I would suggest anything clearer than just the darker blue from the hover button)
   chibaguy: ok, I'll check on that.
   xavi: my 2 cents
   chibaguy: ok
   luciash: <u>chibaguy</u>: i'll add z-index higher than module titles, right ?
   chibaguy: yep, should be ok.
   <br> but module titles don't have a z-index, so.....
   <br> that's why I think the problem is related to the absolute position of the menu in strasa.
   <br> (why we don't see the problem in other themes that don't position the menu that way)
   luciash: <u>chibaguy</u>: yep, it must be related
   chibaguy: time to eat here; will be back soon.
   ***: danopia` has joined #tikiwiki
   <br> tomb_ has left "Ex-Chat"
   xavi: <u>luciash</u>: to preserve the environment: why not "Text area &amp; Plugins" as that title at the admin panel?
   <br> sorry to come back with this issue... and specially now that chibaguy is at dinner time :-/
   <br> I'm just enabling some plugins in dev.tw.o, and I thought about it again, sorry
   <br> I might even commit it myself if not too many places to change (I guess just at one tpl, isn't it?)
   <br> ok, I see that current "text area" in tiki 3.0 also has settings for things other than just wiki (like forum minimm size)
   luciash: <u>xavi</u>: i'm not sure all these settings affect only form textareas
   xavi: +1 then to change to "Editing &amp; Plugins", if you don't like the more conservative (towards "preserve" environment) proposal
   luciash: it's two tpls
   xavi: 2 tpl's, ok, not too much , I can cope with it
   luciash: tiki-admin-include-anchors.tpl
   <br> tiki-admin-include-list-sections.tpl
   xavi: not only textareas, I agree, after looking to it again
   luciash: i can help fix translations but i don't know how to say "Editing" in languages though :)
   <br> maybe we have already translated "Edit" but not "Editing" i guess
   ***: danopia has quit IRC (Network is unreachable)
   xavi: neither do I know all langs... :-/ (neither google translate does 100% good translation, but that could help)
   <br> oups, I've just got the plugin help text in dev.tw.o in french! (and my interface has been in English for months)
   <br> and some minutes ago it was in English, as usual
   CIA-46: tikiwiki: 03sylvieg * r18468 10/branches/3.0/styles/darkroom.css: [FIX]darkroom: calfocus on
   <br> tikiwiki: 03sylvieg * r18469 10/branches/3.0/styles/darkroom.css: [FIX]darkroom: border around day in view mode
   chibaguy: I'm back now
   xavi: wb chibaguy . so "Editing &amp; Plugins" for those 2 tpls, then.
   ***: MatWho has joined #tikiwiki
   chibaguy: Ok, personally I like "and" better than "&amp;" in titles.
   xavi: ok chibaguy
   CIA-46: tikiwiki: 03luciash * r18470 10/branches/3.0/styles/strasa.css: [FIX] strasa: slightly higher z-index for css horiz menus to prevent undergoing right col module titles + improvements to the edit/search helper specific to strasa (for now)
   chibaguy: yay luciash
   ***: ricks99 has joined #tikiwiki
   CIA-46: tikiwiki: 03sylvieg * r18471 10/branches/3.0/ (styles/darkroom.css templates/tiki-calendar_calmode.tpl): [MOD]calendar: a little icon to link to the day detail directly in the day cell
   -: chibaguy wonders if other themes should have styling for that little icon in tiki-calendar_calmode.tpl....)
   sylvieg: Is ok in strsa darkroom et thenews...
   <br> s/et/and
   <br> in any case the cell classes is hard coded in the template mainly :-(
   chibaguy: ah, ok, thanks sylvieg.
   sylvieg: I think that the add event button must be smaller too
   <br> just the green plus will be enough..
   xavi: chibaguy and luciash: col size in split plugin is broken to me in strasa, but working as usual with thenews. Example: http://doc.tikiwiki.org/tiki-index.php?page=PluginTitleSearch
   <br> is this easy to fix it myself adding something in strasa.css?
   <br> in strasa,css I see div.split {	border: 1px dashed #696969; clear: both}
   luciash: <u>xavi</u>: how broken ?
   xavi: hold on...
   <br> this {SPLIT(colsize=&gt;30%|5%|65%)} has no efect in strasa.css
   <br> the one in the left (35%) and the one in the right (65%) are shown equally wide
   <br> under strasa, but shown as expected (and as usual) under thenews.css
   ***: gbertrand has quit IRC ("http://www.mibbit.com ajax IRC Client")
   xavi: I see that in thenews.css there is no div.split defined....
   <br> and related to table.wikiplugin-split, both of them have the same content
   <br> maybe the "clear: both" is responsible for the problem with width display in split...
   chibaguy: I think the left column containing a code plugin might be a problem there...
   <br> it's coded in css to be 500px wide,
   <br> so putting it in a table td that's 30% wide would make the entire table very wide. Maybe the browser wants to reduce the 60%-wide td instead.
   xavi: about "Editing and Plugins" or "Editing &amp; Plugins": I see "Look &amp;amp; Feel" but "Site Ads and Banners"...
   <br> any preference from the devs in irc right now?
   chibaguy: Yes, I know. Look &amp; Feel should be Look and Feel imho
   -: chibaguy tries not to think of erotic alt meanings of phrase.
   xavi: why code plugin width "hard"coded in css?
   <br> :-)
   <br> alt meanings :-)
   <br> luciash?
   chibaguy: Because without a width, the code box can sometimes be extremely wide, so I wanted it to have a scrollbar in such a case. Ideally, it'd be width: 100% or slightly less...
   <br> ...but some browsers produced strange results with a percent width, so I made it 500px as a rough idea of what people would want in the center column.
   xavi: ok, I understand
   <br> issues with percent: which browsers, for curiosity? (I never saw that and I've been using % in split plugin for years)
   CIA-46: tikiwiki: 03sylvieg * r18472 10/branches/3.0/styles/darkroom.css: [MOD]darkroom: beter to put cell with info on a darker background
   chibaguy: I'm editing strasa.css now (for versions), so will try something for the split table.
   xavi: but I manily use ff if I can, of IE if there is no other option in public or univ. computers
   ***: artbody has left
   xavi: thanks again, chibaguy
   ricks99: hi all. what is current status of 3.0 release?
   xavi: good question ricks99 :-) (and hi). No idea myself
   <br> relase30process has many things on it
   ricks99: tx
   <br> (and hi xavi)
   -: xavi 's personal guess is that marclaporte would love to release 3.0 in the next tikifest (ontario, I think) at the latest, if not selforganized the release earlier
   xavi: but please, don't share my personal guess with anyone ;-)
   ricks99: ur prob right
   ***: Floh1111 has joined #tikiwiki
   CIA-46: tikiwiki: 03luciash * r18473 10/branches/3.0/templates/tiki-show_help.tpl: [FIX] tiki show help: usability fix to give hint the help sections are clickable and display "toggle" in a tooltip + if shadowbox is on allow to expand the help to fill the screen in it
   chibaguy: xavi, I found that div class="codelisting" can be 95% wide in the split table's tds, so it won't insist on 500px wide and so should conform to the td cell width there. :-)
   <br> I'll commit the edited strasa.css soon.
   xavi: ok, great, thanks
   chibaguy: your guess on the release time makes sense to me too.
   <br> the up-side of the delay is that lots of things are getting fixed/improved.
   xavi: code plugin will be much nicer also on wider screen resolutions... :-)
   <br> :-)
   chibaguy: well, it's still 500px wide outside of the wikiplugin_split's table...
   xavi: ah, ok
   ***: MatWho_ has joined #tikiwiki
   xavi: no problem, forget my last comment about code plugin in wider screens...
   -: xavi wonders how to go back in irc and delete a comment as if it was not written a moment ago :-)
   chibaguy: well, that 500px width bothers me too, so I'd like to find a way to have a percentage width.
   xavi: hi MatWho and MatWho_ :-)
   MatWho_: hi
   <br> hi_
   ricks99: in 3.0, how to disable full-screen option when editing wiki pages?
   <br> dont see an option on wiki or text area admin pages
   marclaporte: on barebones install, there are two different looking edit section icons: why?
   <br> (on entry page)
   xavi: marclaporte, ricks and MatWho_: ok also with renaming "Text area" with "Editing and Plugins"? (see irc back log if needed)
   <br> s/ricks / ricks99
   ricks99: "and" instead of "&amp;"... fine w/ me
   -: xavi is ready to commit the change in those 2 tpl's...
   MatWho_: +1
   marclaporte: just label or name of file?
   ***: mib_79dxxp has joined #tikiwiki
   xavi: so also "Look &amp; Feel" for "Look and Feel"?
   <br> <u>marclaporte</u>: just labels
   ***: mib_79dxxp has quit IRC (Client Quit)
   xavi: name of file?
   marclaporte: tiki-admin_include_text_area.php
   xavi: argh, you are right, name of file should be also, to be consistent...
   marclaporte: if you rename file, it's more risky.
   xavi: I know (and also tpl file name involved)
   marclaporte: I have no opinon, what you think is best
   xavi: mmm, -1 to rename files at this pre-3.0 stage
   marclaporte: file name and label doesn't have to be consistent
   ricks99: agree (with xavi) -1
   marclaporte: better but not deal breaker
   <br> so if you think it's better label, it's ok to change while keeping old file names,
   MatWho_: leave a stub for tiki-admin_include_text_area.php and change name of file
   xavi: ok. And "Look &amp; Feel" for "Look and Feel"?
   ***: Traveler has joined #tikiwiki
   <br> Traveler has quit IRC (Client Quit)
   <br> mib_rxjjq9 has joined #tikiwiki
   <br> mib_rxjjq9 has quit IRC (Client Quit)
   marclaporte: <u>ricks99</u>: on first run, this tiki-admin.php?page=community throws a lot of false messages. Do you know why?
   <br> <u>xavi</u>: : no objection
   ricks99: i think because a new install, a lot of "defautls" are not yet set
   <br> the options that are not selected are not yet in the db.
   <br> imho, ideally shouldn't tiki *completely* populate the preferences table?
   xavi: no clear opinion on that, ricks99 myself
   amette: dev and doc are svn upped
   xavi: hey amette! welcome back! :-)
   amette: heya xavi - thanks! :)
   CIA-46: tikiwiki: 03campbe13 * r18474 10/trunk/doc/devtools/release.php: [FIX] undo 18450 replace readline() func
   marclaporte: <u>amette</u>: : yay
   <br> amette : tiki-mind-map?
   amette: <u>marclaporte</u>: where does it come from?
   marclaporte: instructions are here: http://dev.tikiwiki.org/tiki-mindmap.php
   MatWho_: is the "report a bug" page if IE problem fixed/being worked on by someone I have a feew hous spare for bug fixing
   CIA-46: tikiwiki: 03nagendra016 * r18475 10/branches/3.0/lib/setup/prefs.php: [FIX]After a new install, in metatags admin page, enabling one or two options of threadtitle, imagetitle, freetags results in notes which shows information about all three option rather than only changed features.
   amette: huaaa... flush, err. flash, well, needs to be flushed, well, whatever...
   <br> <u>marclaporte</u>: done
   <br> so this visorFreemind.swf needs to be put there manually every time? doesn't go into the distribution?
   sylvieg: MatWho_ I posted a question with np was used in the MODULE
   <br> if you delete the param np it works
   MatWho_: Hi all nagendra016 is our GSOC student from India, who has just started. He is blocked from IRC at University (this will be fixed in a few days) I have sent him some more bugs to look at but it might be nice to say hi.
   sylvieg: - there is probably a conflict in the wiki parsing
   MatWho_: <u>sylvieg</u>: ok, so is it worth trying to fix?
   marclaporte: <u>MatWho</u>: :irc.tikiwiki.org for web access
   sylvieg: if somebody has an explanation for using np param...
   ricks99: @MatWho_ can nagendra016 join via mibbit?
   MatWho_: no the university has blocked mibbit as well!
   marclaporte: : amette: http://doc.tikiwiki.org/tiki-mindmap.php
   <br> hahahah
   amette: <u>marclaporte</u>: coming
   <br> <u>marclaporte</u>: distro or custom file=
   <br> s/=/?
   MatWho_: he is off to get a different connection. If he comes back do we still do the ceremony?
   marclaporte: yes!
   ***: c_schmitz has joined #tikiwiki
   c_schmitz: guys, I love Tikiwiki
   luciash: <u>chibaguy</u>: are you done editing strasa ?
   <br> <u>c_schmitz</u>: welcome
   c_schmitz: but the worst thing ever is that anonymous users can change linked translations - there is no permission to to repvent that - nor there is a log entry to soo what happened
   MatWho_: marc OK so when he is back - lets do it.He is working on the admin lockout bug now.
   c_schmitz: that really sucks
   luciash: <u>chibaguy</u>: need to fix z-index of edit helper
   CIA-46: tikiwiki: 03chibaguy * r18476 10/branches/3.0/lib/wiki-plugins/wikiplugin_versions.php: [FIX] Version content given a class for css styling.
   c_schmitz: it makes the whole linked translation thingy useless
   luciash: chibaguy put 20 instead of 2
   ricks99: @c_schmitz: there is a 	tiki_p_detach_translation permission.
   <br> remove that from anonymous group?
   c_schmitz: it is removed
   <br> but keeps people only from detaching
   <br> not changing the language of a page or attaching
   xavi: <u>c_schmitz</u>: if you know how to fix, you are welcome
   chibaguy: ok luciash, I'll do the edit helper z-index change.
   ricks99: sounds like need a new perm
   c_schmitz: yes
   xavi: <u>c_schmitz</u>: I mean, you are welcome anyway :-). And of course, if you know how to fix, you are welcome to fix it :-)
   c_schmitz: <u>xavi</u>: this is not a fix but a whole new permission needed - it is a huge shortcoming from whoever implemented that part - I am, running a Wiki in 6 languages and all the translation links are garbled because of this shortcoming
   ricks99: quick fix: maybe just fix the wording on  bottom half of "tiki-edit_translation"?
   <br> or check for specific admin-level perm for the "Change lang for this page" section?
   CIA-46: tikiwiki: 03luciash * r18477 10/branches/3.0/templates/tiki-plugin_help.tpl: [FIX] plugin help: when using Shadowbox and inserting new plugin block via plugin helper + plugin edit, close Shadowbox "window"
   xavi: <u>c_schmitz</u>: we know in wiki-translation.com , bots use to do it form time to time. And so far, nobody found it (or cold look at it). adding a new perm is easy. Unluckily, I'm not a php coder, and it's not adding a perm into the database, probably, but touching the whatever php files that ned to check for that
   c_schmitz: what I did in the past was editing the code so the "translate feature' would not show up for anonymous users by attaching it to the detach_translation permission
   <br> but with an update the changes are (naturally) gone
   xavi: <u>c_schmitz</u>: propose those changes in devel list (where other coders for i18n are), and commit your changes to themain code base, I would say
   <br> this way, we all benefit from your fixes, in the same way that you benefit from the fixes in themain code base
   c_schmitz: <u>Xavi</u>: it is mainly caused by users who think that 'transalte' mean they can translate the page an don't realize they are changing the page language
   xavi: sorry, I'm off to urgent things to fix before late luch.
   ***: shoq has quit IRC ("http://www.mibbit.com ajax IRC Client")
   c_schmitz: well.. I guess for the 1.x branch no new feature will be implemented anymore, won't it?
   marclaporte: even 2.x, no new feature
   <br> and 3.x, only in certain cases
   <br> new features normally go on 4.x
   CIA-46: tikiwiki: 03chibaguy * r18478 10/branches/3.0/styles/transitions/2.0to3.0.css: [FIX] Increase #tikihelp z-index (thanks luci).
   marclaporte: wow
   <br> already 4.x
   <br> time flies
   c_schmitz: I see
   <br> so If i need a permisison like that which version would it be?
   sylvieg: did lph develop the plugin interface validation?
   <br> sorry found it
   luciash: <u>chibaguy</u>: thank you
   xavi: <u>c_schmitz</u>: trunk (will be 4.0), and to the new branch called "proposed", so that the "Quality team" can review to include it in 3.1 or not (I guess yes, since this is a know bug for long)
   <br> <u>c_schmitz</u>: see http://dev.tikiwiki.org/Commit
   <br> the "proposed" branch might not be documented yet, since it's pretty new
   marclaporte: <u>c_schmitz</u>:  what version are you on?
   c_schmitz: latest 2.x
   sylvieg: I have a fun one... how can I approve the module register in http://dev.tikiwiki.org/report%20a%20bug
   chibaguy: Some of the core themes have #tikihelp css also. I'll add it to the ones that don't, to be safe. But this redundancy will be resolved when layout.css replaces transitions.
   marclaporte: because I remember Alain_Desilets explaining that one problem is that people change the page language when they intend to translate
   sylvieg: I need to be admin to validate = but I only see it as anonymous :-D
   marclaporte: <u>sylvieg</u>: : yes, I know!  I created another wiki page with plugin content, so I could validate
   sylvieg: btw seems that user modules must be validated now???
   marclaporte: <u>sylvieg</u>:  I added validation on module plugin
   sylvieg: is it optional?
   luciash: <u>chibaguy</u>: but seems thenews still have z-index for css horiz menu higher than that
   marclaporte: <u>sylvieg</u>: : this is totally debatable and maybe we should remove
   xavi: <u>marclaporte</u>: +1 :-)
   marclaporte: the thing is, with 100+ modules, I feel it gives too much power to any user
   sylvieg: should be a apram I suppose..
   marclaporte: to add a module which discloses info that the admin doesn't want to disclose
   <br> for example
   <br> I do not know how to make more fined-grained
   <br> but it's quite annoying now
   <br> safer, but annoying
   sylvieg: and group perms on modyule are not enough?
   marclaporte: do we have that now?
   ricks99: need to b able to "group" modules &amp; plugins, then mass approve by user group.
   <br> <u>example</u>: Anon users can auto-approve modules in group Foo, Registered can autoapprove modules in groups Foo and Bar, etc.
   sylvieg: I hope it is working..
   marclaporte: <u>c_schmitz</u>: i think, in version 3.0, changing the current language of a page, is still there but much less obvious because it's something people should do very rarely
   c_schmitz: ok
   marclaporte: <u>c_schmitz</u>: can you take a look at branches/3.0 and see if this seems ok, or if you think there still should be an additional perm
   c_schmitz: if it can be misused it will be ;)
   sylvieg: ... this part seems to be missing: MODULE does not check the perm set (I know for column) in admin-&gt;modules...
   chibaguy: yeah, I'll change that.
   <br> luciash, oh, wait, maybe I misunderstood.
   amette: doc.tw.o is mindmapped
   luciash: <u>chibaguy</u>: i'll check your commit
   chibaguy: I only committed the transition file so far.
   luciash: <u>chibaguy</u>: seems ok, that's what i meant
   chibaguy: TheNews gets its css menu z-index from css/cssmenus.css.
   <br> ah, ok.
   luciash: <u>chibaguy</u>: what is the value of it ?
   <br> is it higher than 20 ?
   ***: nagendra016 has joined #tikiwiki
   xavi: <u>luciash</u>: nice change in "plugin help" display through shadowbox, but nowadays, when you click on the insert icon, the user keeps seing the shadowbox, and he/she would think that he/she did nothing on the text...
   MatWho_: hi nagendra016
   chibaguy: oh yeah: 800 (#header .cssmenu_horiz)
   luciash: <u>xavi</u>: i fixed it
   nagendra016: hi
   MatWho_: welcome to tikiwiki IRC
   xavi: if after insert click, the shadow box could be minimized, that would be even better, from the usability point of view for end users
   luciash: <u>xavi</u>: svn up
   xavi: <u>nagendra016</u>: welcome to TikiWiki Community! :-)
   nagendra016: thank you
   ricks99: hi nag
   xavi: <u>luciash</u>: well, it's in doc.tw.o :-)
   ricks99: nagendra016 (oopd)
   MatWho_: hi all can I introduce nagendra016  he is out GSOC sutudent from India
   luciash: <u>xavi</u>: amette was svn upping earlier than the fix came out ;)
   xavi: so I can't myself, only amette, if he hasn't shared account and howto details
   <br> :-)
   MatWho_: he really starts today, and has just made his first commit!!
   nagendra016: hi all
   sylvieg: hi nagendra016
   luciash: <u>nagendra016</u>: welcome
   <br> <u>MatWho_</u>: great :)
   xavi: <u>luciash</u>: ok
   nagendra016: thank you all :)
   MatWho_: I have given nagendra016  some onother bug to fix, it is a good way to get him going on Tikiwiki
   nagendra016: i am very delighted to be a part of our community
   marclaporte: hi nagendra016 and welcome to TikiWiki!
   amette: <u>xavi</u>: the howto is the problem
   <br> find someone that fixes the structure/permission-bug... ;)
   xavi: amette, I thought so :-)
   amette: ... but I'll start documenting without structures!
   -: amette goes svn upping
   xavi: structure/permission-bug?
   amette: yeah, if you're not admin, you can't add pages to a structure
   xavi: amette, why not also gtk-recordmysektop-ing?
   ***: sacra has joined #tikiwiki
   amette: the permission-check is wrong
   xavi: <u>amette</u>: :-) that's not true
   <br> at least for 2.4 :-)
   <br> I've been doing this for month with my students here for production: http://iesbarcelona.org/esso350
   amette: because gtk-recordmydesktop-ing facilitates stupid people following stupid guidelines step-by-step without thinking...
   <br> ... and I want people to understand what they are doing - otherwise it's worthless and doomed to fail.
   xavi: ammete, I storngly disagree, but I respect your opinion, of course
   amette: hmm, well, in 3.0 it doesn't work, we checked that out in Montreal...
   <br> ... we traced it to the problematic line, but didn't really know how to fix
   xavi: this way, no videos for documentation would be used... and they speed up the process of getting a quick idea of how the thing works
   amette: well, however with the videos: it will take more time to get the video stuff running than writing wiki-pages on it ;)
   ***: SEWilco2 has joined #tikiwiki
   amette: so I will forget about the structures and start documenting :)
   xavi: amette, ok. In 2.4, afair, you had to grant permission on the homepage of the structure,
   amette: hmmm....
   <br> I have tiki_p_edit_structure (or something like that) for Registered
   <br> actually I have all the wiki-perms for Registered and no special perms afaik
   marclaporte: how do I set perms for modules?
   amette: Admin-&gt;Modules ??
   xavi: amette, afaik, you had to set the local perm on that homepage of the structure for your users also
   <br> and from there, you can grant also to the other pages of the same structure, afair
   <br> and they can do it
   <br> (they can add pages then, I mean, through the top navigational bar)
   amette: <u>xavi</u>: I juggled all the perms and gave up, then I debugged that problem (because I wanted to document in Montreal) with nyloth and we didn't get it going...
   <br> ... and I used that before..
   <br> .. so I know that it once worked..
   xavi: ok, there might be a bug in 3.x then
   amette: <u>xavi</u>: can you try to get it running on your setup in 3.0?
   xavi: sorry, not now
   amette: yeah, the top navigation bar doesn't even show the possibility to add a page - it's completely missing
   xavi: I'm kind of 4h late for deadline for today, aside of tw stuff, which is still quite in most of my screens on the computer
   <br> (finishing some pages for upgrade, tiki3, multitiki, and file gals behavior for images in tiki 3)
   amette: :)
   MatWho_: <u>amette</u>: are you up for running a welcome ceremony for nagendra016
   amette: <u>MatWho_</u>: I'm always in for a ceremony! :)
   <br> just need an admin here! :)
   ***: Tikiwiki|bot has quit IRC (Read error: 110 (Connection timed out))
   -: amette gets a cup of coffee first..
   amette: <u>luciash</u>: ceremony?! :)
   MatWho_: yes!!!
   luciash: <u>chibaguy</u>: isn't 800 too high ?
   ricks99: @xavi? whats issue w/ structures?
   xavi: ask amette
   ricks99: seemed ok on my sites (upgradded to 3.0
   chibaguy: luciash, I found other z-indexes in the files and 800 was near but not at the top, iirc.
   <br> can be lowered if there are no problems doing that.
   luciash: if you prefer to stay with 800, the #tikihelp must have 801 at least, otherwise the menu goes over in thenews and others which place the help on top right corner
   <br> sorry, guys, kind of rushy here for the ceremony
   chibaguy: I don't have a reason to stay with 800. As long as it's at a good level...
   luciash: <u>marclaporte</u>: ? ^
   MatWho_: <u>amette</u>: are you back?
   amette: <u>MatWho_</u>: back? or back? ;)
   <br> I'm at least more available again!!
   MatWho_: hoho
   marclaporte: admin modules permits me to put groups, but not tiki_p_edit, tiki_p_view  (http://dev.tikiwiki.org/wish1887)
   MatWho_: <u>nagendra016</u>: is waiting to be introduced ..
   -: marclaporte things a dev.tikiwiki.org/z-index page would be welcome to gather common understand on this
   chibaguy: marclaporte, I agree; there are actually dozens of z-index settings in our files.
   CIA-46: tikiwiki: 03luciash * r18479 10/branches/3.0/templates/tiki-edit_help.tpl: no need to display the little help icon only for wiki syntax (no plugins) when there's the complete help on top right
   MatWho_: <u>luciash</u>: amette Can we do a ceremony for nagendra016 ? It is his first day and his first commit.
   sylvieg: <u>xavi</u>: I am trying to merge which icon like lib/images/icons/abw.png must I use in trunk - the one in trunk or the one in 3?
   xavi: the one in 3 is ok
   sylvieg: thx
   xavi: I ported the fixes to 3 and trunk
   CIA-46: tikiwiki: 03luciash * r18480 10/branches/3.0/lib/smarty_tiki/block.add_help.php: smarty add help block/icon: better not to hardcode the width and height for shadowbox
   luciash: <u>MatWho_</u>: try marclaporte or sylvie, if you don't succeed, i'm listening but very busy
   xavi: there will be many more icons like that
   -: xavi put the ceremony hat on
   LordVan: cya
   xavi: ^ MatWho_ and nagendra016
   ***: LordVan has quit IRC ("Leaving")
   xavi: s/put/puts on himself:-)
   MatWho_: thanks xavi
   xavi: so nagendra016, first question: Do you know and agree with the three rules?
   nagendra016: yes
   <br> i agree
   xavi: :-)
   nagendra016: :)
   xavi: this sounds to me like a wedding! lol
   nagendra016: haha
   -: marclaporte takes wedding pictures
   MatWho_: Hey take this seriously ;)
   xavi: the second question is (in my version of the ceremony, sorry for the other devs ;-): are your ready to be thanked by the community for your commits/fixes?
   -: xavi wonders why some people find this question difficult to answer...
   nagendra016: yes
   xavi: :-)
   <br> and the third and more difficult one....
   -: xavi hears some devs saying "tachan"...
   xavi: what's your sf.net account?
   nagendra016: that easy question :P
   CIA-46: tikiwiki: 03sylvieg * r18481 10/trunk/ (158 files in 70 dirs): [MRG] Automatic merge, branches/3.0 18299 to 18473
   nagendra016: nagendra016
   -: xavi is confused and delayed because sf.net changed layout...
   MatWho_: he is already set up
   ***: Lucymoz has joined #tikiwiki
   nagendra016: :)
   MatWho_: just nice to have a ceremony :)
   xavi: hey, man, then why the ceremony if not for granting the permissions! :-)
   MatWho_: to welcome him to us - WELCOME nagendra016
   nagendra016: thank you !! thank you !! :)
   xavi: ok, welcome again nagendra016, but this time as official committer to tw! :-)
   ricks99: *clap*
   nagendra016: :)
   marclaporte: *clap *  *clap*  *clap*
   -: chibaguy pours drinks
   <br> xavi is still wondering how to find tw project in sf.net using latest konqueror... those software upgrades.... (I feel like the users from a tiki2 site when they will find their site upgraded to tiki3-jqueryfied... :-)
   MatWho_: drinks it
   -: chibaguy refills
   <br> luciash missed nagendra016 's commit ?
   amette: welcome nagendra016 !! :)
   -: amette hugs nagendra016
   MatWho_: r18475 /branches/3.0/lib/setup/prefs.php
   nagendra016: thank you amette
   xavi: <u>nagendra016</u>: so from India and in UK, or is MatWho_ in India drinking from your cup?
   luciash: <u>MatWho_</u>: ah
   MatWho_: if only I was in India, the tea is very good :)
   CIA-46: tikiwiki: 03sylvieg * r18482 10/branches/3.0/tiki-admin.php: typo
   xavi: :-)
   -: xavi vanishes again to unfinished stuff
   MatWho_: Thanks all, back to work!
   nagendra016: Thanks all :)
   -: rodrigo_sampaio just finished reading the page http://doc.tikiwiki.org/TikiWiki+3.0 and is amazed by the huge list of new features in tiki 3.0
   rodrigo_sampaio: :)
   ***: danopia`xchat has joined #tikiwiki
   xavi: :-) well, this is not all (hi Rogrido :-), but just the tiny part a few of us could document. The full list is in dev (linked from the beggning of the doc page)
   <br> s/Rogrido/Rodrigo
   -: xavi 's fingers are getting mad because they didn't get any food yet since marclaporte was going to bed...
   xavi: <u>rodrigo_sampaio</u>: for instance, it doesn't say anything about the new version of morcego... :-)
   <br> so that there is room for improvements from things you know... (I don't very well know the improvements you made in there, btw), as far as it's back working fine :-)
   rodrigo_sampaio: <u>xavi</u>: actually i also don't about the improvements in the new version of morcego, i just did the upgrade in tikiwiki, luis is the one who made it a long time ago
   <br> <u>xavi</u>: i did not have the chance yet to test mindmap but i feel like mindmap and morcego have the same goals, right?
   xavi: ok, fine , just realized about the fact that I forgot to mention morcego in there
   rodrigo_sampaio: <u>xavi</u>: and morcego is not working on 64bits :(
   ***: MatWho has quit IRC ()
   <br> nagendra016 has quit IRC ("http://www.mibbit.com ajax IRC Client")
   <br> Tikiwiki|bot has joined #tikiwiki
   <br> Wilkins_ is now known as Wilkins
   luciash: <u>rodrigo_sampaio</u>: and i wondered why morcego java browser doesn't work anymore in my browsers :-o
   CIA-46: tikiwiki: 03luciash * r18483 10/branches/3.0/styles/transitions/2.0to3.0.css: [FIX] z-index 20 for #tikihelp wasn't succesfull, giving it 820 because the css menus have 800
   <br> tikiwiki: 03sylvieg * r18484 10/branches/3.0/ (7 files in 5 dirs):
   <br> tikiwiki: [FIX]calendar: change only focus when click on change focus link and not when
   <br> tikiwiki: navigating in the calendar + new_option : viewmode for mod-calendar_new (as was
   <br> tikiwiki: cited as a feature in doc.tw) + new param month_delay to be able to display one
   <br> tikiwiki: month before or after +_ some css tuning
   rodrigo_sampaio: <u>luciash</u>: maybe one day batawata will fix morcego for 64bits...
   chibaguy: ah, luciash, the 800 z-index for css menus is lower than shadowbox?
   <br> at one point I noticed the menus bleeding through, but am not sure if it got fixed or not.
   ***: danopia` has quit IRC (Read error: 110 (Connection timed out))
   CIA-46: tikiwiki: 03luciash * r18485 10/branches/3.0/templates/tiki-show_help.tpl: no need to keep the help_sections open when opening to shadowbox from there
   <br> tikiwiki: 03marclaporte * r18486 10/branches/3.0/templates/tiki-print_pages.tpl: [FIX] Remove link to nowhere. We would need help with http://doc.tikiwiki.org/Restore+Help+Pages to clean everything up.
   rodrigo_sampaio: after upgrading tiki 2.4 to tiki 3.0 RC1 the sidebar is broken (appear below the main content div) using a default tikineat style. any ideas? the url for this is is http://wiki.hacklab.com.br
   CIA-46: tikiwiki: 03pkdille * r18487 10/branches/3.0/styles/coelesce.css: [FIX] coelesce: fix the sitesearchbar look when the selected language is not english
   chibaguy: <u>rodrigo_sampaio</u>: tikineat is no longer compatible with Tiki 3.
   sylvieg: <u>rodrigo_sampaio</u>: tikineat is no more maintained
   chibaguy: :-)
   rodrigo_sampaio: <u>chibaguy</u>: ok :)
   CIA-46: tikiwiki: 03xavidp * r18488 10/branches/3.0/templates/ (2 files):
   <br> tikiwiki: [FIX] As discussed on irc today, change 'Text area' label for 'Editing and
   <br> tikiwiki: Plugins', and 'Look &amp; Feel' for 'Look and Feel'. Sorry for the inconveniences
   <br> tikiwiki: for translators, but this is to reduce the number of continuous suport requests
   <br> tikiwiki: even from devs not finding where to enable plugins, etc.
   rodrigo_sampaio: <u>chibaguy</u>: which is the default theme now?
   <br> as tikineat is not maintained anymore should we put a message for users using tikineat after upgrading?
   sylvieg: did you averwrite your intall?
   <br> on a fresh install it would have work I think
   <br> there is instruction somewhere how to add lite.css to have old themes working in 3
   -: luciash wonders why on bare bones default install Tiki changes theme to Strasa after installation :-/
   marclaporte: <u>luciash</u>: : log out
   sylvieg: s/working in 3/working in 2
   luciash: do we really want to clone tw.o sites ?
   rodrigo_sampaio: <u>sylvieg</u>: i did an upgrade (copy the new tiki files over the old installation directory), so i still have all the old themes in my tiki installation
   marclaporte: if you re-install while already logged in, you get weirdness
   luciash: <u>marclaporte</u>: log out ?
   <br> <u>marclaporte</u>: ah
   <br> <u>marclaporte</u>: but i'm logged out
   CIA-46: tikiwiki: 03chibaguy * r18489 10/branches/3.0/styles/coelesce.css: [FIX] Version plugin styling; #tikihelp z-index increased.
   Tikiwiki|bot: New Forum Posts: admin validation email setup and configured but not working properly! - http://tikiwiki.org/tiki-view_forum_thread.php?forumId=2&amp;comments_parentId=32883
   marclaporte: ok, then I have no explanation :-)
   luciash: <u>marclaporte</u>: i only choose "use existing connection"
   SEWilco2: Did you flush caches?
   <br> Maybe the bot should issue a cache flush reminder upon the word "weird" or "weirdness"
   -: luciash goes to change the site theme to thenews and flush cache to see
   CIA-46: tikiwiki: 03chibaguy * r18490 10/branches/3.0/styles/darkroom.css: [FIX] Version plugin styling; #tikihelp z-index increased.
   SEWilco2: "Get your thenews here!"
   sylvieg: is http://doc.tikiwiki.org/tiki-mindmap.php working? I do not understand what I have to do ...
   CIA-46: tikiwiki: 03chibaguy * r18491 10/branches/3.0/styles/feb12.css: [FIX] Version plugin styling; #tikihelp z-index increased.
   ***: rodrigo_sampaio has quit IRC (niven.freenode.net irc.freenode.net)
   marclaporte: <u>sylvieg</u>: : also blank for me :-(
   ***: mib_s861y6 has quit IRC (niven.freenode.net irc.freenode.net)
   CIA-46: tikiwiki: 03chibaguy * r18492 10/branches/3.0/styles/strasa.css: [FIX] Version plugin styling; #tikihelp z-index increased.
   luciash: <u>SEWilco2</u>: you wereright, now it works
   CIA-46: tikiwiki: 03chibaguy * r18493 10/branches/3.0/styles/thenews.css: [FIX] Version plugin styling; #tikihelp z-index increased.
   SEWilco2: <u>luciash</u>: No, you were right to describe it as "weird".  That's all that I responded to.
   sylvieg: <u>marclaporte</u>: what are you suppose to put in the input box?
   luciash: <u>marclaporte</u>: funny i get now _HOMEPAGE_CONTENT_ when i choosed czech language during the installation
   SEWilco2: Up and up the z-index goes.
   ***: rodrigo_sampaio has joined #tikiwiki
   SEWilco2: That doesn't look Czech.
   luciash: <u>marclaporte</u>: seems newbie is lost when not remembering admin:admin from the installation steps and translator will be lost because in language.php they will get no idea what to put there
   <br> <u>SEWilco2</u>: heh about the z-index
   <br> <u>chibaguy</u>: actually for strasa the z-index for #tikihelp wasn't necessary to increase because the #tikihelp appears under the header not over it as in other themes
   <br> <u>chibaguy</u>: but it shouldn't hurt anyway
   chibaguy: ok, btw, why does strasa have different #tikihelp css than other themes (width and height are different, for example)?
   CIA-46: tikiwiki: 03chibaguy * r18494 10/branches/3.0/styles/layout/layout.css: [FIX] Version plugin styling; #tikihelp z-index increased.
   chibaguy: any idea?
   luciash: <u>chibaguy</u>: because i was improving the look of it specifically for strasa and while placing it under #header (there was nice space for it) i had to change the height of it, otherwise it went too down with these percents, then i found out it's very hard to doo it with percents at all so i changed to pixels and the result is fine i think
   chibaguy: ok, was just wondering.
   -: marclaporte wishes we could set password in installer
   marclaporte: with a checkbox, force change at first run
   <br> optional off,  but this would be useful for farms
   xavi: <u>rodrigo_sampaio</u>: morcego and wiki 3d cited in tiki3 page. My 2 cents to honur your work ;-)
   <br> s/honur/honour
   <br> http://doc.tikiwiki.org/tiki3 I mean
   -: luciash thought it's batawata's baby
   xavi: <u>luciash</u>: yes, but rodrigo_sampaio did the implementation in tiki :-)
   ***: Floh1111 has quit IRC (Read error: 54 (Connection reset by peer))
   luciash: aah, really ?
   xavi: or the upgrade in tiki3, anyhow, share part of paternality :-)
   luciash: iirc it's there for ages, but might be improved in tiki3, unfortunatelly it doesn't work for me on doc.tw.o
   MatWho_: <u>marclaporte</u>: I will give it to nagendra once he has fixed the admin lock out bug
   <br> <u>marclaporte</u>: its all good warm up stuff!
   luciash: *g*, /me just realized profiles have different themes
   xavi: <u>luciash</u>: are you on 64bit box?
   luciash: <u>xavi</u>: i have no idea but my machine was changed recently so it's possible, yes :-p
   marclaporte: MatWho_ : yay!
   <br> that will make it easier for new people
   rodrigo_sampaio: <u>xavi</u>: thanks :)
   xavi: a pleasure :-)
   rodrigo_sampaio: <u>luciash</u>: morcego is batawata baby, all i did was update the morcego version in tiki
   MatWho_: <u>marclaporte</u>: he was very happy to have a ceremony, thanks everyone
   luciash: MatWho_ and marclaporte: trunk or 3.0 ? this admin pass setting in installer is very sensitive imho and needs some time for testing
   MatWho_: <u>marclaporte</u>: do you have requirements for admin password change on a wiki page somwhere?
   Tikiwiki|bot: New Forum Posts: Edit button not showing - http://tikiwiki.org/tiki-view_forum_thread.php?forumId=4&amp;comments_parentId=32884
   luciash: <u>rodrigo_sampaio</u>: ah, great
   MatWho_: <u>luciash</u>: sure
   ***: artbody has joined #tikiwiki
   sylvieg: +1 luciash
   -: marclaporte is pretty sure he'll get in trouble with Quality Team but perhaps they won't notice
   MatWho_: <u>luciash</u>:  so what is it sensitive to exactly
   <br> <u>marclaporte</u>: this is for trunk not 3.0 sorry I assumed that was obvious
   luciash: <u>MatWho_</u>: security, mess-up when user sets his password and then forgots, etc.
   marclaporte: hehe
   <br> still excellent on trunk
   <br> so we can test and apply for 3.1
   MatWho_: <u>marclaporte</u>: no seriously, feature freeze on 3.0 is very important
   sylvieg: +1 marclaporte
   <br> 'can' does not mena we will do... or I need some English lesson
   marclaporte: <u>apply</u>: I mean submit an application for review/approval by quality team
   MatWho_: <u>sylvieg</u>: I will try to use trunk as much as I can. Just wonder if all the activity on 3.0 recently is going to be there.
   sylvieg: I just merged .. 1 hour ago...
   luciash: <u>MatWho_</u>: i'm switching to trunk today ;)
   MatWho_: OK that is all great. hey this is going to work out well!!
   sylvieg: if merges are not done enough oftern - do it yourself or ask me ;-)
   MatWho_: OK I will try both! Thanks.
   xavi: <u>marclaporte</u>: quick question. is trim designed also to handle different tikis in the same server, or only in different servers?
   -: xavi is upgrading "Multitiki" page in doc.tw.o
   ***: Tikiwiki|bot has quit IRC (Read error: 145 (Connection timed out))
   sylvieg: can be same server but different tiki root (not multitiki)
   xavi: yes, I know it's not multitiki. ok, thanks, from your answer I guess that yes, uit's been designed to also handle different tiki installations in the same server, not only in different servers.
   <br> thanks sylvieg
   marclaporte: <u>xavi</u>: : could be on  same server, TRIM asks which directory
   xavi: ok, thanks
   sylvieg: for the multitiki , mose/niclone have a metaw.. they never commit - but if .... perhaps
   xavi: btw, I don't knwo how to set up a multitiki using only ftp (symlinks are needed in my approach, the closest to multitiki by ftp...): http://doc.tikiwiki.org/Manual+Installation
   <br> <u>sylvieg</u>: metaw ?
   ***: Wilkins has quit IRC (Remote closed the connection)
   chibaguy: cya later, everyone. :-)
   ***: chibaguy has left
   <br> snarlydwarf has joined #tikiwiki
   <br> snarlydwarf has quit IRC (Remote closed the connection)
   <br> snarlydwarf has joined #tikiwiki
   <br> MatWho_ has quit IRC ()
   <br> MatWho has joined #tikiwiki
   CIA-46: tikiwiki: 03sylvieg * r18495 10/trunk/tiki-listpages.php: [FIX]listpage: memo orphan choice
   ***: marclaporte has quit IRC (Success)
   <br> MatWho has quit IRC ()
   rodrigo_sampaio: another issue after migrating from 2.4 to 3.0: the plugin toc is enabled in the plugin manager but it displays a message "WARNING: Plugin disabled toc!". ideas?
   sylvieg: you need to validate them manually the list is in tiki-plugins.php
   ***: Caarrie is now known as Caarrie|away
   rodrigo_sampaio: <u>sylvieg</u>: on tiki-plugins.php: "No plugin pending approval."
   ricks99: @rodrigo confirm the plugin is enabled, clear tiki cache
   CIA-46: tikiwiki: 03sylvieg * r18496 10/branches/3.0/lib/menubuilder/menulib.php: [FIX]menu: to have the selected option working with an url with :
   sylvieg: disabled - sorry
   <br> need to go to admin-&gt;plugin and allowed it
   ***: Redhatter has quit IRC (Read error: 54 (Connection reset by peer))
   <br> Redhatter has joined #tikiwiki
   rodrigo_sampaio: ricks99, sylvieg: the plugins is enabled in admin -&gt; text area -&gt; plugins. i've checked the database base and in tiki_preferences i have wikiplugin_toc:  'y'
   ***: mlaporte has joined #tikiwiki
   rodrigo_sampaio: im going to clean the cache and test it again
   xavi: <u>rodrigo_sampaio</u>: this is known issue
   <br> upgrade disable the structures, unluckily :-(
   <br> It happened to me days ago.
   rodrigo_sampaio: <u>xavi</u>: there is a know fix?
   xavi: I added it yesterday (or ealier this morning) to the release30process on dev.tw.o
   <br> I don't know how to fix
   ricks99: @xavi: wrt structures, becaise struts are now optional (disabled by default)
   sylvieg: the prefs feautre_structures? or something like this?
   ***: fantoms has quit IRC (Read error: 104 (Connection reset by peer))
   xavi: oh well, yes, there should be somewhere in the upgrade sql scritps (installer/schema) where structures are disabled
   <br> <u>ricks99</u>: ok for new install disabled by default, but for the god's sake: not on upgrade!
   ricks99: in 2.x if wiki=y, then i agree 100%
   xavi: this is anoying to existing admins doing  upgrades and getting confusing messages
   <br> my 2 cents
   ricks99: i also found that the {poll id=xx} is no longer valid (although {poll pollId=XX} works
   <br> ^ found while upgrading Smarties to 3.0
   <br> other than that, upgrade was *very* smooth
   xavi: please, those of you who did upgrades, review the http://doc.tikiwiki.org/Upgrade and it's corresponding pages
   mlaporte: the condition for keeping structures should not be wiki=y but if there are any structures
   xavi: I did my best, but other eyes are needed to avoid further support requests of users getting confused
   <br> <u>mlaporte</u>: +1
   mlaporte: count structures &gt; 0
   ricks99: @xav: should this b in rel notes instead/in addition?
   mlaporte: because so many people never used structures and they just have dead / extra links
   ricks99: theres a link from installer to rel notes, but not to this Upgrade doc
   xavi: <u>last</u>: I started to document the new behavior for image galleries usingn file galleries. People were getting lost, and requesting help in tw.o forums...
   <br> please, review and improve: http://doc.tikiwiki.org/File+Gallery+for+Images
   <br> or move elsewhere
   <br> I NEED FOOD!
   rodrigo_sampaio: i'm using tikinewt after the upgrade. i cant browse through the tabs of some of the admin pages (for example in the wiki and text area admin). can anyone confirm this?
   ricks99: *rick loves structures :)
   xavi: c u, enough for today for me
   <br> congrats to all for you hard work improving tiki 3! :-)
   <br> I won't be able to be much on irc for some days. I need to meet non-tiki deadlines
   <br> cheers
   ***: xavi has left
   sylvieg: thx to you too xavi good evening
   CIA-46: tikiwiki: 03luciash * r18497 10/branches/3.0/styles/thenews.css: [FIX] thenews theme: put #tikihelp 25px from top for this theme so it doesn't cover the search bar input and it leaves space for the fullscreen feature icon too
   sylvieg: <u>rodrigo_sampaio</u>: confirms too
   rodrigo_sampaio: <u>sylvieg</u>: ill try to fix it
   sylvieg: the newt is the less standard one
   rodrigo_sampaio: <u>sylvieg</u>: im using it after the upgrade as it is the more similar to the good old tikineat :)
   luciash: sylvieg, rodrigo_sampaio : there are slight differencies, i think it should be done like on General or Features pages for the other ones too to be consistent
   <br> e.g. on Features it also remembers last opened tab and switches to it after applying changes
   <br> (cookietab)
   <br> but i thing it's huge work still to be fixed and tested on trunk first, then maybe backported to 3.1
   rodrigo_sampaio: <u>luciash</u>: right now i have only a few minutes to it and then i have to go back to work. im just going to look for a quick fix to the tabs that hidden
   luciash: <u>rodrigo_sampaio</u>: check on which admin page they work and take as a model
   rodrigo_sampaio: <u>luciash</u>: thanks
   CIA-46: tikiwiki: 03sylvieg * r18498 10/branches/3.0/modules/mod-calendar_new.php: [FIX]calendar_new: pick the current date for month_delay not now
   ***: mark_f has joined #tikiwiki
   mark_f: Hi - getting stumped by custom site header. looked at http://doc.tikiwiki.org/tiki-index.php?page=Site%20Identity&amp;redirectpage=Site%20Logo%20and%20Identity%20Config amongst others - got the images to display. The problem is the text to display as a site title. It ends up below the images, not overlaid as I would like. Heres the code I used: http://widget.mibbit.com/pb/iXNT2B
   ***: MatWho has joined #tikiwiki
   luciash: <u>mark_f</u>: you have to position the h1 via style
   mark_f: Ok, can you point me in the right direction - I have no idea!
   luciash: e.g. style="position: absolute; left: 5px; top: 15px"
   mark_f: Sorted - thanks:D
   ***: ricks99 has quit IRC (Remote closed the connection)
   <br> mark_f has quit IRC ("http://www.mibbit.com ajax IRC Client")
   <br> mark_f has joined #tikiwiki
   <br> marclaporte has joined #tikiwiki
   mark_f: Luciash helped me get an openstreetmap displaying in a wiki page as a module the other night. I got stuck when i had a tall thin map and he suggested "width=100%". I had to go to bed after trying various searches and permutations. this is what I have now, but it doesn't work Can someone show me how to format the code. Thanks +++
   ***: sacra has quit IRC ("http://www.mibbit.com ajax IRC Client")
   <br> danopia`xchat is now known as danopia
   <br> marclaporte has quit IRC (Read error: 104 (Connection reset by peer))
   <br> mlaporte has quit IRC ("http://www.mibbit.com ajax IRC Client")
   CIA-46: tikiwiki: 03pkdille * r18499 10/branches/3.0/styles/coelesce.css: [FIX] coelesce: different parts of find section should not wrap
   ***: patrickallard has joined #tikiwiki
   luciash: salut patrickallard :)
   patrickallard: Salut, Luciash
   luciash: <u>mark_f</u>: what you have now ?
   <br> <u>mark_f</u>: any link ?
   ***: guybertrand has joined #tikiwiki
   patrickallard: http://avantech.ourwiki.net/tiki-index.php
   <br> I use Thenews Theme
   <br> but I want juste a simple theme
   <br> not fullscreen option
   ***: marclaporte has joined #tikiwiki
   patrickallard: because i want customize thme
   <br> for a simple center design
   <br> with no column
   <br> and watch at the button
   <br> of this page
   <br> the white space
   <br> the backgrond doesn't go at the button of the page
   <br> I searh why
   luciash: <u>patrickallard</u>: you can remove the modules from left/right
   <br> <u>patrickallard</u>: something like this Tiki 3.0 site ? → www.menghao.cz
   patrickallard: yes I know
   <br> but I have problem with the white space in the footer
   luciash: ah, give #main height: 100% for IE and min-height: 100% for others
   <br> then the included content div must have 100% too
   <br> can you do that ?
   ***: fantoms has joined #tikiwiki
   <br> FrankP_german has joined #tikiwiki
   luciash: <u>patrickallard</u>: if you only want to have the background gradient follow whole browser viewport, then move it from body {} to html {} in CSS
   <br> s/follow/fill/
   patrickallard: No the white space is still there
   <br> I try
   <br> ok for the background :)
   luciash: <u>patrickallard</u>: move to html helps, ok ?
   patrickallard: yes
   <br> thank you
   <br> I will try to remove the space in the bottom of page
   <br> you have a idea?
   luciash: you must play with the height: 100%
   patrickallard: in the #main?
   luciash: #main and then the others which are inside
   <br> but i think body needs it too to make it work
   <br> search internet for full-height css solution
   ***: luminoso has quit IRC ("Leaving")
   patrickallard: I think it's this tag
   <br> .clearfix:after { clear: both;visibility: hidden;content: "."; display: block;height: 0;}
   <br> content:"."
   <br> what that?
   <br> when i remove this
   <br> the bottom of ppage is ok
   luciash: ah, it renders a dot there
   ***: luminoso has joined #tikiwiki
   <br> Caarrie|away is now known as Caarrie
   luciash: <u>patrickallard</u>: you can specify #tiki-top.clearfix:after, #middle.clearfix:after {content: ""; display: none}, it's not needed for them actually i think but it can be necessary for other tags
   <br> err, sorry, not for tiki-top, only for the #middle
   patrickallard: ok
   luciash: if it doesn't help, let me know
   patrickallard: no It ils the same probleme with the bottom
   luciash: try the same with #wrapper or #tiki-center ?
   <br> and #footer
   <br> it must be one of them ;)
   <br> or all of them :)
   <br> (ah, you have no #footer there)
   ***: Zylogue has quit IRC (Read error: 110 (Connection timed out))
   <br> mib_d33uej has joined #tikiwiki
   <br> marc-etienne has joined #tikiwiki
   mib_d33uej: Hi,  A few months ago I installed TikiWiki to my website. Unfortunately, things are going in a different direction for my site and I need to remove TW and all of the associated files and content.  How do I do this?
   MatWho: just delete all of the files and remove the database you created - i think that is all
   mib_d33uej: I am not sure which files were there before I got TW, so I don't know what is safe to get rid of
   MatWho: oh dear
   <br> where ever you installed tw is where the files are you need to delete
   mib_d33uej: alright, thank you
   ***: gezza has joined #tikiwiki
   <br> nyloth has joined #tikiwiki
   marclaporte: <u>gezza</u>: : tks for translations
   nyloth: Hi all :)
   marclaporte: hi nyloth!
   -: SEWilco2 has to think for a moment to translate "tks" :-)
   ***: Caarrie is now known as Caarrie|away
   MatWho: hi
   sylvieg: so do I commit an option to have calendar view list either on period boundary or from focudate + focudate+period in 3.0?
   <br> last message from nyloth was yes...
   <br> seems not dangeurous at all
   ***: rodrigo_sampaio has quit IRC ("Leaving.")
   <br> patrickallard has quit IRC ()
   nyloth: <u>sylvieg</u>: personnaly I trust you, do what you feel is better since its a usability fix
   sylvieg: thx - I do not trust myself...
   nyloth: :)
   sylvieg: it is a smaller change - smaller than the focus change - but it is a -new- feature / bug fix
   mark_f: trying to get a module to display 100% width bu cant get the syntax. Ploease help
   gezza: hi
   <br> <u>marclaporte</u>: no problem :) I have a question though: the mouseover descriptions of WYSIWYG editor buttons dont seem to react to translation. Any hints what I should do to get them translated?
   ***: Tikiwiki|bot has joined #tikiwiki
   marclaporte: <u>gezza</u>: no idea
   <br> perhaps in FCKEditor stuff?
   ***: MatWho has left
   Tikiwiki|bot: Info: June 11-12-13-14, 2009: TikiFest Québec and online! - http://info.tikiwiki.org/tiki-read_article.php?articleId=60
   gezza: ok, I look it up, maybe find something
   ***: marc-etienne has quit IRC ("http://www.mibbit.com ajax IRC Client")
   CIA-46: tikiwiki: 03nyloth * r18500 10/branches/3.0/ (3 files in 3 dirs): [FIX] fren translations + change how TR are placed in one tip in admin wiki in order to be able to translate it correctly
   <br> tikiwiki: 03nyloth * r18501 10/branches/3.0/ (installer/tiki-installer.php templates/tiki-install.tpl):
   <br> tikiwiki: [FIX][ENH] installer: in step 6/7, get existing info from database if exists, to
   <br> tikiwiki: prefill fields with old values in case of an upgrade. Do not skip this step
   <br> tikiwiki: anymore in this case. This was a 3.0 blocker. + fix SSL preferences set by the
   <br> tikiwiki: installer (there was a typo in the feature name)
   ***: mark_f has quit IRC ("http://www.mibbit.com ajax IRC Client")
   <br> Zylogue has joined #tikiwiki
   CIA-46: tikiwiki: 03sylvieg * r18502 10/branches/3.0/ (6 files in 3 dirs): [FIX]calendar: option to have the list view to begin on the focus date or on the period first date + fix when list view since the focus date - to have effectively all the events of the period
   marclaporte: tks Nyloth: this will save a lot of people a lot of time
   Tikiwiki|bot: New Forum Posts: Module in wiki page full width - http://tikiwiki.org/tiki-view_forum_thread.php?forumId=4&amp;comments_parentId=32886
   ***: franck_ has joined #tikiwiki
   Tikiwiki|bot: New Forum Posts: Can no longer login - http://tikiwiki.org/tiki-view_forum_thread.php?forumId=6&amp;comments_parentId=32887
   ***: FrankP_german has quit IRC ("Nettalk6 - www.ntalk.de")
   nyloth: <u>marclaporte</u>: :)
   ***: franck has quit IRC (Read error: 113 (No route to host))
   <br> mib_ugrjwm has joined #tikiwiki
   nyloth: <u>marclaporte</u>: I know that you don't like the "page has been saved..." message after saving a wiki page... but concretly, what is the real problem with it ? It is in the list of blockers, but addind an option for messages seems going too much deep in the optionality from my point of view. We already have a huge amount of options. What if we make optionnal every messages everywhere ? Honestly I don't understand right now what is bad with this message..
   <br> .
   marclaporte: <u>nyloth</u>: : I think Gary put on list of blockers
   <br> some of the problems we had have been solved.
   <br> 1 problem was in the stats/URLs
   <br> I think that may be solved since the URL is different, it counted as a different page for Google Analytics.    CGCOM had mentioned this to me.
   nyloth: <u>marclaporte</u>: yes, I saw it's gary, but he is not here and you had the same opinion.
   marclaporte: ok
   nyloth: <u>marclaporte</u>: I remember the problem with URLs/bookmarks, but this is fixed nowadays, as you say.
   marclaporte: second problem was in terms of themes.   Since the themes were not adapted, it looked very ugly in some cases
   sylvieg: I think the guys wanted the info in session to have a clena url
   <br> is it fixed?
   nyloth: <u>sylvieg</u>: yes, it is fixed
   <br> <u>sylvieg</u>: since a long time now
   sylvieg: I suppose I work on non svn up version sometimes - ok - thx
   marclaporte: since themes are now ok and URL is nice, I am OK with this message
   nyloth: <u>marclaporte</u>: ok, for you, is there a need to make it optional ? is the theme option still there ? For themes, honestly, I can't imagine that there is a real problem with a simple message at the top of the page when the whole HTML structure was changed in 2.x and 3.x .....
   <br> <u>sylvieg</u>: try on dev.tw.o , it's up-to-date, and see if it's ok for you
   sylvieg: my local is ok
   nyloth: <u>marclaporte</u>: ok, so I need to check with gary then
   marclaporte: yup :-)
   nyloth: <u>marclaporte</u>: I can make options, but I think it's crazy to have one option per message
   sylvieg: I am asking sebastien
   nyloth: <u>marclaporte</u>: thx for your answer ;)
   ***: slordjette has joined #tikiwiki
   sylvieg: :-)
   slordjette: Hello
   nyloth: hi slordjette :)
   slordjette: Hey nyloth
   sylvieg: so slordjette - do you want an option for the save message?
   <br> or a clean url is enough
   <br> for me a clean url is enough
   slordjette: I think so, too.
   nyloth: great :)
   <br> ok, thanx, I suppose we will be able to remove it from blockers then...
   slordjette: What would be a good use case for a message in the url ?
   <br> In my opinion, it just creates url in the stats...
   nyloth: <u>slordjette</u>: yep. It's no more the case if you try a quite recent 3.0
   <br> <u>slordjette</u>: should already be ok for you on a recent code
   slordjette: But what was the use of this "feature" in the first place ?
   <br> I has always bugged me from the day it was implemented... 2.0 I thnik.
   sylvieg: do we reintroduce the jscalendar stuff (see devel)?
   <br> perhaps we can invite this guy to be in the team?
   nyloth: <u>slordjette</u>: I coded it but I think pkdille will be able to answser this question more than me. Some users asked for it.
   ***: mib_ugrjwm has quit IRC ("http://www.mibbit.com ajax IRC Client")
   sylvieg: nyloth is a slave ;-)
   <br> me too..
   nyloth: <u>slordjette</u>: I suppose that when you make small changes in a big page, it's better for some users to have a message that garanties the save has worked, or something like that
   <br> <u>sylvieg</u>: sometimes :)
   slordjette: Well, in that case, the message in the page is OK. But adding &amp;save=y (if I remember well) in the URL is irrelevant.
   nyloth: <u>sylvieg</u>: I would agree on jscalendar if it's not too much visible. The revamp tried to make a lighter UI which is usually better for users / more professional.
   <br> <u>sylvieg</u>:  in which team ?
   <br> <u>sylvieg</u>: QT ?
   sylvieg: tw devel
   Tikiwiki|bot: 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/ .
   nyloth: <u>slordjette</u>: ok :) btw the save=y is no more there
   slordjette: Yeah, I know. Good thing.
   nyloth: <u>sylvieg</u>: so you meant "on the list", not "in the team" ;)
   <br> <u>sylvieg</u>: well, he is already tw devel subscriber, no ?
   sylvieg: we do not handle very well people who propose patches
   nyloth: <u>sylvieg</u>: yes I know, this worry me too. Patches are usually not applied. He should commit directly.
   marclaporte: <u>sylvieg</u>: : http://dev.tikiwiki.org/Report+a+Bug  -&gt; module is not parsed, even if http://dev.tikiwiki.org/tiki-admin_modules.php?um_edit=registration_info&amp;cookietab=2#editcreate
   <br> <u>slordjette</u>: can you put nice new tikifest logos on http://info.tikiwiki.org/tiki-index.php ?
   slordjette: Huh, sure.
   <br> I  though Nelson and Martin would do it since it's their TF...
   sylvieg: ok marclaporte- on my list - in any case there is a couple of bugs around it... now trying to fix all the cal bug I can see
   marclaporte: tks sylvieg and slordjette
   ***: btiffin has joined #tikiwiki
   <br> chibaguy has joined #tikiwiki
   nyloth: <u>sylvieg</u>: since we are speaking about that, really thanx a lot for making so much bugfixes and taking care of quality. I was feeling that it was something forgotten by too many people in tiki last years.
   chibaguy: Hi, I read the log about the "saved by" message and will agree to go along with the majority on this. :-)
   nyloth: <u>sylvieg</u>: there is a lot of people that prefers a quite bug-free software with a few features rather than a full-featured software with bugs or display problems everywhere
   <br> <u>chibaguy</u>: hi, ok, thanx :)
   gezza: hi! i would need some advise about the wysiwyg fckeditor
   <br> i noticed that the frontend does not respect the language selection of TW although the necessary translation is present in the fckeditor lib in TW, also the FCKConfig.AutoDetectLanguage property is set to true in the fckconfig file, browser is in my language, also OS, so all should be good to go
   sylvieg: perhaps .. we are beginning a thanks circle - but slordjette , for example, is a sponsor who prefers good habit to save money ... everything is about balance,,,
   gezza: does someone know who implemented this? maybe he/she could advise what to do
   nyloth: :)
   gezza: it would be useful at the office where we use TW, many colleagues dont speak english :)
   nyloth: <u>gezza</u>: implementation has been made by multiple people and started by a guy you will have difficulties to find (mose) :)
   sylvieg: but every setting is in a file..
   ***: SEWilco2 has quit IRC ("Leaving.")
   nyloth: <u>gezza</u>: I think it work for french in our config, but personally I'm not using wysiwyg (yet) because it's too much experimental (in my opinion)
   gezza: <u>nyloth</u>: I see..but can you confirm it is the same for you? maybe something is wrong on my end..
   <br> <u>nyloth</u>: it worked by default or u hacked something? and yes, it is a bit xperimental but very good for end users, gives them the familiar "MS office" feeling and they tend to invlove more in content writing since I switched it on
   <br> they just complain about the english stuff :)
   nyloth: <u>gezza</u>: no hack here :)
   <br> <u>gezza</u>: I just tried on a fresh 3.0 install, it works out-of-the-box for french
   <br> <u>gezza</u>: Try a fresh install in french and check if it's in french or english
   sylvieg: <u>gezza</u>: which language?
   nyloth: <u>gezza</u>: yes I know, it's our organisation that paid mose for it for the same reasons, but... it's not future-proof yet
   <br> <u>gezza</u>: we are still working on it
   gezza: i also have tiki3rc1 now, i am testing it, switched to french, wysiwyg stayed in english
   nyloth: <u>gezza</u>: hmm... with an install done in which language ? french ?
   gezza: <u>sylvieg</u>: hungarian
   <br> no, install script was run in english
   <br> wait, i make a new db and try
   nyloth: <u>gezza</u>: 'k
   ***: luminoso_ has joined #tikiwiki
   <br> luminoso has quit IRC (Read error: 104 (Connection reset by peer))
   nyloth: <u>gezza</u>: I need to go now, it's late here
   gezza: <u>nyloth</u>: it works with feash instal
   <br> tried french and hungarian too
   <br> thanks for the tip
   nyloth: <u>gezza</u>: ok, great :)
   <br> So, good day/night all
   ***: nyloth has left "Konversation terminated!"
   <br> gezza has quit IRC ("http://www.mibbit.com ajax IRC Client")
   <br> fantoms has quit IRC (Read error: 104 (Connection reset by peer))
   <br> snarlydwarf has quit IRC ("Ex-Chat")
   <br> Caarrie|away is now known as Caarrie
   <br> mib_3pov25 has joined #tikiwiki
   mib_3pov25: Hello,  I currently enabled need admin validation as its not working and i have a valid email account setup for admin. I am running the latest centos and tikiwiki2.4 with firefox latest version. I have linux firewall turned off and disabled SELinux. So when a new user registeres, admin should receive the email in which they dont. But if i login to tikiwiki wi
   <br> sometimes i receive the email that someone registered but most of the time i dont
   <br> not sure what is wrong
   ***: franck has joined #tikiwiki
   <br> c_schmitz has quit IRC (Read error: 101 (Network is unreachable))
   chibaguy: mib_3pov25, sorry, this is the slow time of day in this channel. Maybe you should try again in 12 hours or so.