[00:06] *** raji1 has left [01:23] *** Caarrie is now known as Caarrie|sleeping [01:31] *** tomb__ has quit IRC ("Ex-Chat") [01:53] *** chibaguy has joined #tikiwiki [02:06] *** danopia has joined #tikiwiki [02:35] *** Lucymoz has joined #tikiwiki [02:53] *** NefariousC has left [02:59] *** marclaporte has quit IRC (Read error: 113 (No route to host)) [03:06] SVN: Commit by chibaguy :: r 14856 /mods/trunk/themes/tikipedia/theme/templates/styles/tikipedia/tiki-pagehistory.tpl: [FIX] Updated reflecting changes in default tiki-pagehistory.tpl. [03:38] Is there a problem editing templates through look and feel? I keep getting an error "You do not have permission to write the template:" When I look at the path that is displayed there is a double forward slash (//) showing at templates//styles. If it is not a problem what permissions are needed? [03:45] Paragtim, there is a tiki_p_edit_templates permission. Maybe it needs to be set. [03:48] Tried that one and the view. I'm thinking that it is going to the double forward slash in the path. Could you check it for me please? [03:50] Where do you go to edit a template? I never use that feature. [03:51] Admin Home - look and feel [03:51] Oh, yeah, I see.... [03:52] Do you think it is a bug? [03:52] Hmm. "You don't have permission to use this feature" [03:52] But further into the path there is a double forward slash [03:52] * chibaguy feels sullen for being denied, even as admin..... [03:52] Between the template and the style [03:53] Maybe we are not being denied - just looking in the wrong place [03:54] Well, I got the denial just clicking on the "Edit templates" link. Maybe I need to clear caches... [03:55] I've tried that already. Normally I ftp files up but my ftp rights have been suspended at the moment [04:00] tiki_p_view_templates is also checked for.... [04:02] Heh, a perm which I don't seem to have at my site... must have missed an update. [04:04] But I see it's at my fresh-install 2.0 site. [04:04] I've got the perm but it doesn't seem to help ;) [04:05] Well, at my 2.0 (actually 2.1 now) fresh install, everything works ok. [04:05] Is your site upgraded from an earlier version? [04:06] I can up from 1.10 - but can rememer if I did a clean install or an upgrade. I think it was an upgrade [04:07] Also, I don't see any "templates//styles" urls. Typically, mine are like "...tiki-edit_templates.php?template=antibot.tpl" [04:08] Sorry - I don't understand [04:09] Where is the double forward slash that you mention? In what url or path? [04:10] In the error message path "You do not have permission to write the template: /templates//styles....... [04:14] Ah, ok. [04:15] Hmm, I could submit an edit; the save button says "Save only in the theme feb12" and apparently the save was made. [04:16] On mine - No changes to the file [04:16] And the permission error is returned [04:27] *** leon007 has joined #tikiwiki [04:28] Hmm, I don't know. I see where that perm message is in tiki-edit_templates.php, but the file hasn't changed in 2 months at least. [04:29] Anyway, a file fix wouldn't help your immediate problem if you can't ftp. [04:30] *** leons007 has joined #tikiwiki [04:31] Hi. Especial greetings to chibaguy :) [04:32] Hi leons007. So nice, and not even my birthday [04:32] *** leon007 has quit IRC ("CGI:IRC (Ping timeout)") [04:33] Just came accross another software suprise. Did a clean install and can use ftp. I needed to get the "Switch User" function out of the mod-login.tpl. Got rid of it but unless the login box is the last module in the list it stops all modules below from showing. Repeat after me - 1 step forward 1 step back is a good day !! [04:33] I am still having troubles with "user trackers", so if anyone has any advice - it would be good... I set up user trackers so that on registration users are asked what city / country they live in. If I login as admin, I see that new tracker item created - no problem. However, if I login as a new user and try to see that tracker info under "User Settings", I see empty fields... [04:33] Worse than that... An empty tracker item is actually created :( [04:33] What the hell is going on... [04:34] *** franck has left [04:34] Paragtim, any experience with using user trackers with registration? [04:34] Just looking now [04:35] * chibaguy recalls Paragtim doing something in this area, maybe.... [04:35] Yep. I'll dig out a link. Had a similar problem but I think its solved [04:35] that would be great! [04:37] Ok my version of the tracker works when displaying data. Problem with the T's & C's acceptence check box. But you migh not need that or might have a fix for it. Link in 1 min [04:38] Try this link: http://www.oops-again.co.uk/tiki-index.php?page=Tracker%20User%20Registration%20Tracker&structure=001. Can you let me know if you have problems [04:43] let me check, there are a lot of steps, but they seem to be the steps I was following... By looking at the created tracker items, i looks like 2 were created - 1st had all teh fields except for the user field. 2nd one item had all empty fields BUT it did have the user field set... [04:44] (Noticing that page, I see I need to add a #page-bar {border-top: 0} to tikipedia.css to override the 1.9to2.0.css transitions stylesheet's property there.) [04:45] When I was doing this I found that you could change what you thought you would get by displaying the field labels [04:45] (I don't test themes with "use transition stylesheet" enough, obviously.) [04:47] Chibaguy - Would still like to transplant that tool box into other themes. I think its really neat and it would give back a reasonable amount of screen real estate. [04:47] How best to go about it? [04:49] Probably the best approach is to make it a module, which would be easy since the content is already done. [04:50] Then the page-bar stuff would need to be commented out or removed from tiki-show_page.tpl. [04:51] I think there is a "display at top/display at bottom" switch for these links already on an admin page. Hypothetically it could also include "display in module" I imagine. [04:51] Yeah, that is a good idea. The clutter at the top of wiki pages has always bothered me. [04:52] I've looked at commenting out the page bar. That seems pretty straight forward. But there again I thought commenting out the Switch user code would be as well. [04:53] You never know..... ;-) [04:54] Still - Ive saved that part of the log and will have a look at doing it in a couple of weeks. System is on "Go-Live" for 6 Oct and I still have a load of "little" jobs to do. [04:54] Feature set gets locked off tomorrow [05:00] Oh, now I see what I was thinking of was incorrect: it's {if $prefs.wiki_page_navigation_bar neq 'bottom'} -- the page nav stuff is switchable top and bottom. [05:00] ... not the page-bar (edit link, etc.) [05:00] *** SEWilc1 has quit IRC (Read error: 110 (Connection timed out)) [05:00] *** vilisi_t has quit IRC ("Leaving.") [05:00] So making it switchable to a module would introduce new code, not just add to existing. [05:01] *** SEWilco has joined #tikiwiki [05:03] Info overload today, but if you do decide to make it work I would love a copy [05:04] Paragtim, chibaguy... The link didn't give me any success unfortunately... On registration, user tracker item is created without the field for user... I followed steps from here http://doc.tikiwiki.org/tiki-index.php?page=User%20Tracker&redirectpage=Registration%20Tracker [05:05] the only thing I had confusion with is under tracker field setup: ""Specify the user tracker fieldID with the feeding=1 option you created in the tracker " [05:05] I entered "feeding=1" in that form... [05:12] SVN: Commit by chibaguy :: r 14857 /mods/trunk/themes/tikipedia/theme/styles/tikipedia.css: [FIX] Transitions css override needed. [05:15] paragtim, chibaguy? [05:16] sorry leons - was lost in thought - catching up now [05:17] no problem, I appreciate your help... BTW, if u want to try this abortion :( it's www.schneidermans.org [05:18] leons007, sorry, I'm just clueless on this, and don't really have the time to study it. [05:20] np, chibaguy, I am sure I am more clueless though [05:20] If I can remember the problem hinges around the user selector [05:21] The only thing that doesn't work on the link I gave you is the Accept Option. [05:22] If you built the tracker up with jsu a couple of option like firtname and last name, with the user selector as per the link - What happens? [05:24] I only tried with all of the fields I needed. With that - fields show up OK and info is entered, but that tracker item is created without user info in it... [05:25] I mean everything is there as was entered by the user, EXCEPT for the user info [05:25] If I login as a user and then go to "User Preferences" then a new tracker item is created with just the user info... [05:26] *** Lucymoz has quit IRC (Read error: 110 (Connection timed out)) [05:28] I've just run a couple of registrations using that script and apart from the Acceptance problem they are working fine. The data is recorded correctly into the tracker. What permissions have you used? [05:29] something crazy is going on... [05:32] it sounds crazy, but it started to work... it started to work after I cleared all tracker items AND set that user_selector option to just "1", not "feeding=1"... But I could have swore that prior to wasting everyone's time on this channel I tried all these combinations [05:33] Thats not a problem - if it working thats great [05:35] :) well, thanks for your time! [05:35] your welcome [05:37] oh... almost forgot... it's a minor thing... but it looks like during registration that tracker item description is not tiki-parsed. I inserted a link there which appears great in the description under say List trackers, but during registration I see my [ ] or (( [05:38] it's not a big deal, just thought may be there is something else that I am doing that is silly... [05:39] I deliberately stayed away from as mush extra stuff as possible - and when I made it work I stopped there. I do have to spend some more time on it over the next couple of days - so i will have a look at it [05:42] Paragtim - did u answer that to me? [05:42] yep [05:43] ah ok, yeah, it's not a serios thing - iterative implementation works for me :) thanks again 4 your help [05:50] *** leons007 has quit IRC ("http://www.mibbit.com ajax IRC Client") [05:57] *** navster has joined #tikiwiki [06:33] *** fane has joined #tikiwiki [06:44] polom [06:46] * luciash confirms to Paragtim the he fixed the template editing perm check _after_ 2.0 release [07:00] hi luciash. I think I'll delete a bunch of link classes today. Seem like a good idea? ;-) [07:04] (just kidding.) [07:08] *** Jyhem has quit IRC (verne.freenode.net irc.freenode.net) [07:08] *** niclone has quit IRC (verne.freenode.net irc.freenode.net) [07:17] *** Wilkins has joined #tikiwiki [07:21] *** CIA-53 has quit IRC (Read error: 110 (Connection timed out)) [07:22] *** Paragtim has quit IRC (Read error: 110 (Connection timed out)) [07:29] lol [07:30] chibaguy: but sylvie is right we should distinguish images from text links somewhat [07:31] *** Jyhem has joined #tikiwiki [07:31] *** niclone has joined #tikiwiki [07:34] chibaguy: it'd be easy if IE6 supported a.hover > img, but it doesn't, so we need some "little crutch" [07:35] yes, that's right. [07:35] most of the "linkbuttons" are text, right ? [07:36] all, I think [07:36] ok, where appear the icons in the navbar then ? [07:37] i'd use some class on the links for these exceptions only then [07:38] *** CIA-48 has joined #TikiWiki [07:38] like tiki-list_file_gallery.php [07:43] I agree. [07:47] i don't see the watch icon in the darkroom there though on my local install :-/ [07:47] what do i have to enable as admin ? [07:47] I see the watch icon on specific gallery pages, like tiki-list_file_gallery.php?galleryId=6 [07:48] (looking at a 2.1 install now) [07:48] * luciash at trunk and cannot even upload a little image :-/ [07:48] it says "Uploading file..." indifinitely [07:49] *infinitely [07:49] I haven't tried uploading a file for the last week or two... [07:50] * luciash doesn't like tiki magic is not optional :( [07:51] so should i look at the 2.0 branch ? [07:51] But tiki-browse_gallery.php?galleryId=xx in the Darkroom theme shows button madness. Both the span and the a have borders ;-) Who is responsible for this? [07:51] i thought you removed the linkbut class on trunk ? [07:52] yes, I did. I'm looking at 2.1 here. [07:52] are you talking about trunk or 2.1 ? [07:52] ah [07:52] (probably me responsible, btw ;-) ) [07:53] I don't like the 3px white borders on thumbnail cells, tho. Pretty sure that's not my work. [07:53] do we have BRANCH-2-1 now ? [07:53] There was a 2.1 release a few days ago. [07:54] lemme have a look/comparison between trunk and 2.1 [07:54] i know, but branch stays 2-0 ? [07:54] Apparently. [07:55] Well, I don't know how that's supposed to work. [07:57] uploading the file on 2-0 branch worked flawlessly [07:58] i don't see any watch icon in file galleries on 2-0 either [07:59] * chibaguy finds he is the author of the 3px white border on gallery thumbnail tds and hangs head in shame.... [07:59] but yes, i see the mess on the links in image gallery ;) [07:59] (and the 3px border too) [08:00] I'd consider that a bugfix for 2.2. [08:01] (worthy of a 2.2 bugfix) [08:02] ah i see, there's still the linkbut but span button2 is also styled in the darkroom there [08:02] so it seems styled twice there now [08:03] * chibaguy hangs head in shame some more... [08:03] heh [08:03] Anyway, a good example of how things are confusing now. [08:04] And opportunity for improvement, as I tell my kids. :-) [08:05] ouch ! my eyes burn ! :-p [08:05] tiki-browse_image.php?galleryId=1&sort_mode=created_desc&imageId=2&scalesize=640 [08:05] in darkroom ;) [08:07] What site is that? [08:07] localhost [08:07] oh, I'm relieved... [08:08] branch-2-0 [08:09] My localhost is a windows laptop and there's an error with image uploading, always has been, so I don't have galleries here. But that's a problem for some other day. [08:09] styleswitcher doesn't work, me goes to check his cookie names for trunk and branch local install [08:12] Is it possible to use the "float =>left" parameter on this: {FLASH(movie=http://www.youtube.com/v/wWmE6Zvo37E,width=>425,height=>350,quality=>high)}{FLASH} ? [08:13] stix, the parameters are limited to those listed in the "show plugin help" table at the bottom of wiki edit page, generally. [08:13] But you can put the flash plugin in a div of the same size and float it left. [08:14] hmm that's what I thought [08:14] in a div you say, I'll look into that [08:14] using the DIV plugin. [08:14] okay, I found some documentation on that now, thank you [08:15] sure [08:16] Subway time. bbl. [08:16] *** chibaguy has left [08:20] *** WildPikachu has joined #tikiwiki [08:21] * WildPikachu wonders if there is a way to manually order the forum list [08:32] WildPikachu: click on the column name [08:33] manually :) not by name or date or whatever [08:33] for instance [08:33] tiki-forums.php?sort_mode=name_asc [08:33] I always want NEWS at the top :) [08:33] ah [08:41] WildPikachu: prefix your forum names with a number and goto tiki-admin.php?page=forums and set there Ordering for forums in the forum listing [08:42] yea [08:42] was thinkg of that [08:42] thanks [08:51] *** MatWho has joined #tikiwiki [08:59] *** SEWilco has quit IRC (Read error: 110 (Connection timed out)) [09:00] *** SEWilco has joined #tikiwiki [10:09] *** Caarrie|sleeping is now known as Caarrie [10:10] Guys, I'm from Denmark and we have some special letters "æøå". I can create wiki-pages containing these letters, but I cannot link to them in other wiki-pages with the ((name)) syntax. Is there a solution for that? [10:14] *** tomb_ has joined #tikiwiki [10:18] SVN: Commit by luciash :: r 14858 /branches/2.0/templates/modules/user_module.tpl: [FIX] typo in module_params caused nobox param unuseful (thanks to Jose F. Garcia) [10:21] stix: do you have "complete" set on Admin -> Wiki ? [10:22] stix: for Wiki Link Format [10:26] luciash, I don't see "complete" anytwhere on tiki-admin.php?page=wiki [10:26] oh in stead of english [10:26] see for Wiki Link Format [10:26] yep [10:30] that worked great :) thank you [10:31] I have another thing I would like to get working; all my users reside in a windows server 2003 AD. Can I find a guide somewhere on how to set up LDAP auth for a windows AD? [10:43] stix: no idea, sorry, no windows here, only open doors... [10:43] stix: try search on tw.o [10:44] * Caarrie laughs at luciash [10:44] *** chibaguy has joined #tikiwiki [10:44] * luciash laughs back to Caarrie :) [10:44] wb chibaguy [10:44] * Caarrie hands luciash a few very large windozes :P [10:45] wow, fast reaction. thanks. [10:45] Caarrie: thanks, they don't fit in my environment somewhat though :-p [10:45] hehe [10:45] * Caarrie hands luciash kde4 [10:46] Caarrie: already here but it wasn't much usable yet [10:46] then you have not updated to 4.1 [10:46] i have been using it for months with almost no issues [10:48] these almost no issues were the reason i didn't choose it as my main desktop ;) [10:48] it is _mine_ ;) [10:48] i dont even have kde3 installed anymore ;) [10:49] * luciash neither, only gtk stuff here now [10:49] i did manage to crash plasma yesterday :P [10:49] gnome rocks [10:49] plasma can crash ? wow [10:49] * Caarrie does not like gnome [10:49] yep [10:49] xfce rocks [10:49] i have a battery widget on the screen, and i removed my battery=plasma crash [10:51] doesn't plasma leak ? :-p [10:51] not that i have seen [10:51] :P [10:51] or burn ? *g* [10:52] http://icari.no-ip.org/snapshot7.jpg [10:54] nice, what's the game on your wall ? [10:54] planeshift ;) [10:54] reminds me settlers :) [10:55] have you not checked my host cloak? or PS|bot's ;) [10:55] :P [11:05] http://pakkerejser.dk/Screenshot.png [11:05] 2 screens? [11:05] yes I have two monitors [11:06] i *almost* thought you had a mac :P http://icari.no-ip.org/FinderScreenSnapz005.jpg [11:06] at first [11:06] yes that's the avant window navigator [11:06] very nice :) [11:07] i like my mac for mac things and linux for everthing else ;) [11:09] yes me also, just thought it was a little cooler than the normal bar at the bottom :) [11:09] since i have no "top bar" it works for me ;) [11:22] *** raji1 has joined #tikiwiki [11:29] *** ricks99 has joined #tikiwiki [11:29] http://www.strangehorizons.com/2004/20040405/badger.shtml [11:42] mine looks even more like Mac [11:42] oh? [11:42] i'm using cairo-dock in the bottom [11:43] and i have no idea what that is ;) [11:43] avant window navigator is also nice but somewhat slow here [11:43] the dock on the bottom simmilar to OS X one [11:43] ok [11:46] LOL about the badger link :D [11:49] is there a way to add perms to a section edit? to make only specific sections/headings editable? [11:51] we should develop or bring back from aulawiki the edit structure - with all the pages in the same page [11:55] sylvieg: +1 [11:56] have an idea to use dynamic content instead... [11:57] ricks99: what is your idea [11:57] in 2.1, how do i turn on dcs? [11:57] dcs? [11:57] ahh.. in text area... [11:57] [11:57] dcs = dynamic content system [11:58] @matwho: im going to create a dynamic content area with my "uneditable" text, then add it to a wiki page via {content id=xx} [11:59] not perfect, but ok (for now) [11:59] ricks99: I am a bit new to all this, what is your uneditable text [11:59] you can use also tracker and page selector with a pretty tracker... [12:00] major downside of trackers is that there is no revision history [12:02] woo hoo. dcs *does* accept wiki formatting :) [12:03] *and* plugins. this may work after all :) [12:05] @MattWho: my usecase is that for some wiki pages, i need to display text (instructions, notices, etc.) that should *not* be editable (although the rest of the wiki page *is* editable) [12:06] would be nice if i could somehow "hide" or "secure" the {content id=xx} so users dont accidentally delete it [12:10] ricks99: Yes that sound just like something I have o do quite soon on my project [12:10] wondering outloud... could the propsed security for "dangerous" plugins (i.e., JS) be applied to {content id=xx} too? [12:10] * chibaguy suggests special no-contrast text color for the dns tag... [12:11] *** raji1 has quit IRC (Remote closed the connection) [12:11] to {content ..} no... not a plugin [12:11] however, you could have a plugin that only contains {content ...} in the body and it would work [12:15] lphuberdeau: ricks99 is there some doc on the security feature? [12:16] a plugin that calls {content..}? seems like adding another level of complexity? [12:18] plugin alias can hide most of it... basically create a wrapper around the content thing to add functionalities [12:18] *** raji1 has joined #tikiwiki [12:19] *** marclaporte has joined #tikiwiki [12:19] starting to think I should modify the parser to remove all those {content } or {img } special syntaxes, make them into plugins and map that syntax back to plugins for inline-only [12:20] +1 [12:20] I could probably remove a good 100 lines to the parser code [12:20] ++1 [12:21] uh [12:22] matt, that causes a runtime error in PHP I think... can't increment a constant [12:22] ok try +++1 [12:22] * sylvieg thinks that if we begin/ are ready to change tw syntax, we should at least write the tw grammar to be sure that it is easily parseable [12:23] did I just hear someone thinking to take over a piece of work? [12:23] sorry, didnt mean to add work... just looking for a way to have un-editable portions of a page :) [12:24] if we drop the current wiki syntax support we can directly start calling tiki something else and using wikicreole or something... :-p [12:24] yes so was I :) [12:24] don't worry about that, I keep adding myself work all the time, if it can end up being useful, that's good [12:25] :-) I agree to participate only if we define a parseable grammar (LL1 will be great)before and nobody is allowed to add whatever without checking the grammar is still ll1 [12:26] well, if you have a grammar, you might as well parse with it, so you need to modify it to change it [12:26] sylvieg: lphuberdeau I will defiantly be able to offer my services to check and proof read the grammar. Dont think I know all of TW to help write it. [12:27] *rick thinkgs that wiki syntax is dead/dying and wysiwyg is the way to go :) [12:27] I'm also better at reading them than writing them ... I guess we'll need to write a bunch of tests to verify the corner cases [12:28] I think wysiwyg died before birth in a wiki context [12:29] * lphuberdeau relocates [12:30] * chibaguy likes wiki syntax [12:30] *** martinalex has joined #tikiwiki [12:31] i like wiki syntax too, but my users are complaining that it is a giant step backwards. [12:31] from ms word, yeah, probably so. [12:31] makes them recall their wordstar days [12:31] tough to compete with packages like confluence with a nearly perfect rtf/wysiwyg editor [12:31] Well, I'm in the lucky position of not really having users to please.... ;-) [12:33] ricks99: There is a need for a safe text based way to combine page contents and plug-ins, look at the explosion in wiki sites/software over the last 5 years. What we now need is WYSIWYG + plugins. But the text (be it XML or WikiSyntax - or wikisyntax generating XML) will be the basis for a good WYSYWIG implementation - surly. [12:33] I agree that laying out a page with wiki syntax can be a bother, really. I do quite a bit of trial and error myself sometimes. [12:33] But wysiwyg just feels boring to me. I don't like the intermediary layer. [12:34] I am not sure we want to do wysywig editing in Microsoft Office products or integrate in with Share Point, which I beleve is Confluence's strong point [12:34] chibaguy: I know what you mean, the are some that like ASCII others that like WISYWIG - we must support both [12:35] Sure, my own tastes are probably on the fringe. [12:35] ;-) [12:35] for non-techie users, a [B] button makes *a lot* more sense than using __bold__ [12:35] chibaguy: Also it is easy to generate content in ASCII, not WISYWIG this is a big +1 for the ASCYII route [12:35] the quicktags are a good learning step, but true wysiwyg is my goal [12:36] ricks99: I agree TW must have good WISYWIG and very soon [12:37] So we get both if we hold the core in XML and allow either WikiSyntax or WYSIWIG editors to work on it. [12:39] *** PS|bot has quit IRC (Read error: 104 (Connection reset by peer)) [12:40] *** PS|bot has joined #tikiwiki [12:41] an interesting read: http://www.steptwo.com.au/columntwo/wiki-markup-has-no-future/ [12:43] * marclaporte heard that many years ago [12:43] * marclaporte is still waiting [12:43] http://dev.tikiwiki.org/Why+Wiki+Syntax+is+Important [12:46] I've wondered what page authors want to do, when they say they need wysiwyg. Is there any breakdown or wisdom on this? What's the top-10 styles wanted, or something like that? [12:46] *** lphuberdeau has quit IRC (Read error: 113 (No route to host)) [12:47] ricks99: Now I am not saying the article is wrong, but most of the comments he makes can be pointer at "modern" word processor software. You must have watched people trying to get pictures in the correct place on the page in Word. Or a TOC to have all the correct formatting. I dont this that is easy either. In his article he does say he thinks in a wiki environment we should stick to "Simple, locked-down formatting (bold, italic, paragraph styl [12:47] pointer = pointed [12:47] forma = forms [12:48] I agree. I think, one beyond the basic text styling, editors have a learning curve to, and it takes training to get good results. [12:48] IOW, wysiwyg is no panacea. [12:48] to -> too [12:48] @chibaguy: last study i saw fro ms-word 2000 showed that 90%+ of users used less than 10% of the "features" [12:49] for most users, Notepad works as well (if not better) than ms-word [12:49] That is correct, this is exactly why Wikis have exploded on the world. They let people do lost of stuff they could not do with word [12:49] ricks99: Exactly [12:50] Sounds right to me. In my office, most people don't know there's file storage beyond the icons on the desktop. "Oh, no, I'm out of space!" ;-) [12:50] y, but using ''italic'' and __bold__ is a PITA [12:50] give me a simple wysiwyg rtf editor and i'll be fine [12:50] ricks99: absolutly, hence we need the simple WYSYWIG editor and soon [12:50] yeah, I agree with you guys. [12:51] lets do it!! [12:51] i asked a while back... could a client-side, browser plugin be a simplier solution? i use the greasemonkey + ff extension to get wysiwyg with mediawiki installs [12:51] Actually to do big tables for my Tikis, I do it first in Dreamweaver and then find and replace the html tags with wiki syntax. :-) [12:52] the wikiEd extension in greasmemonkey, i mean [12:53] correct me if I am wrong but the editor is not the difficult bit, it is how we store the contents in TW that will take some careful surgery [12:54] maybe if we limit to 5-6 WYSIWYG syntaxes [12:55] marclaporte: say that again, in a different way [12:57] * chibaguy hears Yoda say "If limit we maybe to wysywyg syntaxes 5-6"..... [12:57] let's say WYSIWYG is just bold, italic, a link builder and an image picker [12:57] no still dont understand [12:58] marclaporte: Yes now I do [12:58] @marc: to be useful, i want/need all formatting options (bold, italic, underline, etc), plus list buliders (# and *), headings, and tables [12:59] a plugin picker would be a bonus [13:00] marclaporte: Defiantly, but the big project is changing the way content is stored in TW. Then we can start with a simple wisywig editor and add on in later versions. But from a solid base. And the pluging picker would be the most imortant bit, that is what you cana not do in Word [13:00] cana - can not [13:01] My fingers are not WWIT - Write what I think - today [13:01] Is FCKeditor not working out? (I'm really ignorant about this.) [13:01] chibaguy: FCKeditor is fine, it just produces HTML, which is not good for TW because it cant have plugins in it [13:02] Ah, ok. [13:02] chibaguy: and plugins is what it is all about [13:02] ??? if options are welll set the fckeditor in tw accepts plugins [13:03] sylvieg: How can I do that [13:03] in admin->wysiwyg - there are options to accept tw syntax [13:04] sylvieg: OK looking at my browser ... [13:07] *** CIA-48 has quit IRC () [13:08] Basic docs: http://doc.tikiwiki.org/tiki-index.php?page=Wysiwyg+Editor+Admin&bl=y [13:08] great [13:10] *** lphuberdeau has joined #tikiwiki [13:11] * lphuberdeau is resuming normal operations [13:11] chibaguy: So if I create a wiki page with wysiwyg and then go back to the wikisyntax can I edit there or is it all HTML if I do that? [13:12] lphuberdeau: :) [13:14] MatWho, to tell you the truth, I don't know for sure. I've only tried the editor a few times, mostly back when it was new in Tiki. [13:14] But I get that meaning from the docs. [13:14] Choose ""Content is parsed like a wiki page"" [13:15] chibaguy: Yes I am having a go now, it does work with headers. Some one has put a lot of effort in over the last few months. Last time I tried this I have to reinstall TW [13:15] Then "all content of the wiki page is parsed, then __bold__ is shown as bold in parsed result, and is still displayed __bold__ in the source of the wiki page. Then you can mix wysiwyg edition and wikistyle code." [13:15] *rick has had little luck with switching back and forth [13:15] somone was working on patches i think... [13:16] I used it so long ago, surely it has been improved since then. [13:18] I tried typing {BOX (title="hello world")}In a box {BOX} in to the editor but just get it back not a box format. So I guess that was too hard. Headings and bold work fine. [13:19] try this... brand new 2.1 install. enable wysiwyg. edit the default home page. change to wysiwyg. [13:19] what you get is a mess :( [13:20] wasn't supposed to be fixed in 2.1 [13:20] ahhh. patches are only in 3.0? [13:20] no patches yet [13:20] the problem is much deeper and no one knows how to solve it yet [13:21] I get it without too many problems - in fact it looks great. I am on 3.x [13:21] ricks99: Get 3.0 it will answer many of you issues with WISYWIG right now! [13:21] ok, maybe it makes it not as bad, but the problem is still existing [13:22] still think we should re-engineer TW to have XML as the core representation. :) [13:22] @matWho: can you (1) create a wiki sytnax page. (2) reopen the page in wysiwyg & make edits. (3) reopen the page in wiki syntax? [13:22] I think mike kerr's '2.5' has some patches backported [13:22] matwho, I need som time for that ;) [13:23] ricks99: I have not tested it very hard but for the home page you definatly can. [13:23] donc t'arrive pour le diner? :) [13:23] oops [13:23] off to grab 3.0.... [13:23] lphuberdeau: hurry up, all the eating is slowing the coding down - stop it! [13:24] Hey I just got some plane tickets to Canada arrive on my desk!! :) [13:24] paper tickets? [13:25] I don't think I ever saw those [13:25] Yup, cute. [13:27] mat, you are officially the first one to create a DB patch [13:28] After just checking the wysiwyg editor, I'm really impressed. Edited with wysiwyg in FF3 and normal editor in older Opera and everything is respected, and as expected in wiki source. [13:29] try special syntaxes... things that don't exist in HTML for example [13:29] lphuberdeau: I am still very very happy :) [13:33] The box plugin and {cookie} tag work and show up in both editors as expected.... [13:33] *** martinalex has quit IRC (Read error: 110 (Connection timed out)) [13:34] wow. wysiwyg in 3.0 is pretty tight! [13:35] chibaguy: How did you get BOX to work, I just got the code back [13:35] Just the magic touch, I guess. ;-) [13:36] This is a site upgraded to the 2.1 release, and wysiwyg set as described earlier. [13:36] chibaguy: I can see you are a very powerful kind of magic! [13:37] Maybe just the right alignment of asteroids or something. [13:37] :) [13:39] chibaguy: do you know why we have 2 tick boxes one for "partially parsed" and the other for "parsed like a wiki page" surly the second one subsumes the first [13:44] *** CIA-54 has joined #TikiWiki [13:47] Partially parsed seems to be more limited. [13:48] partial parsing includes: [13:48] * parsing of links [13:48] * parsing of images and generally what is included in { } [13:48] * parsing of wikiplugins [13:48] *** PS|bot has left [13:48] <-only, apparently. [13:48] *** PS|bot has joined #tikiwiki [13:52] whereas "parsed like a wiki page" parses all wiki syntax. Maybe "partially parsed" is safer for mostly wysiwyg users since it won't convert wiki syntax that might be typed in unintentionally. [13:52] (just guessing) [13:54] *** Caarrie is now known as Caarrie|away [14:00] *** rodrigo_sampaio has joined #tikiwiki [14:01] If anyone comes up with good use case examples for these settings, it'd be great to add them to the doc page. [14:03] *** rodrigo_sampaio has quit IRC (Client Quit) [14:23] *** PS|bot has quit IRC (Remote closed the connection) [14:28] *** PS|bot has joined #tikiwiki [14:32] SVN: Commit by sylvieg :: r 14859 /trunk/ (2 files in 2 dirs): self_link + pagination [14:33] *** lphuberdeau has quit IRC (Read error: 104 (Connection reset by peer)) [14:33] *** CIA-54 has quit IRC () [14:34] *** lphuberdeau has joined #tikiwiki [14:37] SVN: Commit by sylvieg :: r 14860 /trunk/tiki-adminusers.php: self_link [14:45] chibaguy: when you write something in bold does the wysiwyg save it in wiki syntax as __bold__ ? [14:46] (it didn't last time i tried) [14:49] You mean write it as bold using normal editor and wiki syntax? [14:49] *** stix has quit IRC (Remote closed the connection) [14:54] If I make it bold in the wysiwyg editor, it has tags in the source. [14:54] If I do it in the normal editor, it's wiki syntax. [14:54] (naturally :-) ) [14:55] Thed w5g editor (sorry, tired of typing all those letters ;-) ) doesn't produce wiki syntax, but leaves it alone, it seems. [14:56] hell I am on 2.1 ... and I have access denied for my images galeries ... [14:56] idea ? [14:57] chibaguy: i mean wikiwyg should save in wiki syntax so then when other users edit the page with wysiwyg on they can continue in wiki syntax [15:00] gillesMMM: you were a bad boy it seems ;) [15:01] yes, luciash, that seems to work ok. [15:01] luciash: yes I know but ... [15:01] I was using the two kinds of editors in two browsers and both could edit and view ok. [15:02] gillesMMM, is it a new install, or an upgrade? [15:02] an upgrade [15:03] an upgrade from 1.9.9 [15:03] chibaguy: but if you say it saves as then it doesn't, nope ? [15:03] I wonder if a permission was missed or something. [15:03] *** lphuberdeau_ has joined #tikiwiki [15:03] You used the tiki-install.php update? [15:04] chibaguy: no ... manually . copy of local.php and mysql --force base Maybe the database should be checked to be sure the permissions are all there. [15:06] (or anyway the relevant one) [15:11] Though, if the perm was there before, it should still be. [15:11] yes I needed to re assign perms to imagegaleries [15:13] *** marclaporte has quit IRC (Read error: 110 (Connection timed out)) [15:14] aha [15:14] If one stores tracker data in its own tables (tickbox in the Tracker admin panel), it doesn't appear to use the description field if specified for a field [15:15] *** CIA-53 has joined #TikiWiki [15:21] Here's something interesting about the wiki editors: using w5g editor to make a list, the
  • s are indented in typical HTML formatting style, which makes them monotype. In the normal editor, the indents can be removed to make the list items the normal wiki text font. [15:21] Not a big deal, kind of funny. [15:21] tracker with mirror tables are no more maintained ... I thought we deleted this option.... [15:21] WildPikachu, I guess what you're seeing there would be a bug, right? [15:22] .... or old code..... [15:22] chibaguy, Im inclined to think so .... changing the storage of the tracker to not being in its own table works 100% :) [15:23] Well, that's consistent with sylvieg's comment. :-) [15:23] :) [15:23] v2.1 btw [15:28] Actually (about the font style in lists), I guess it's not so good for the wiki syntax to intrude on the wysiwyg output that way, if page appearance is important in all details. So in a case like that, either it should be cleaned up in the normal editor (indents removed), or maybe the option to use both editors should not be chosen. [15:30] *** Caarrie|away is now known as Caarrie [15:30] *** MatWho has quit IRC () [15:33] chibaguy: is the parsing of indented text to monospace on by default ? [15:33] *** ricks99 has quit IRC ("ChatZilla 0.9.83 [Firefox 2.0.0.3/2007030919]") [15:34] *** martinalex has joined #tikiwiki [15:42] *** PS|bot has quit IRC (Remote closed the connection) [15:44] *** PS|bot has joined #tikiwiki [15:47] luciash, yes, it's turned on in my wiki prefs. So that could be turned off to eliminate that problem. [15:47] (I don't know about the default setting in a fresh install -- off?) [15:48] I lost the style for the description in top of wiki pages [15:57] *** SEWilco2 has joined #tikiwiki [15:59] *** martinalex has quit IRC (Read error: 110 (Connection timed out)) [16:03]
    is there a way to delete the clear ? [16:04] *** djst has joined #tikiwiki [16:09] gillesMMM, edit the theme's stylesheet, is that what you mean? [16:10] ...find div.wikitopline or just .wikitopline and delete "clear:both" ? [16:11] I don't see clear both in the stylesheet [16:11] *** nikhilodeon has joined #tikiwiki [16:12] Maybe it's inline CSS, then, in the template itself. [16:13] hi - i had a question about the "Site Login Bar" feature that is configured in the Look and Feel section of Tiki - /tiki-admin.php?page=look# - when I logout, it disappears from the page, but reappears when I refresh [16:13] has anyone had that experience? [16:15] gillesMMM, then you can add .wikitopline {clear:none !important} to the stylesheet. [16:16] nikhilodeon, no, what theme is it? [16:16] *** lphuberdeau_ has quit IRC (Read error: 110 (Connection timed out)) [16:16] chibaguy - i used moreneat.css as the base, and then created my own [16:17] one caveat - i did add some style formatting to the login box in the .tpl file, but i don't think it should have disrupted anything [16:18] Heh, famous last words..... [16:18] ;-) [16:19] heh heh [16:21] I don't know off hand. I noticed sometimes things not appearing until I log in, that should always display, such as the horizontal menu/top bar. But I haven't investigated. [16:21] *** gillesMMM has quit IRC (Read error: 54 (Connection reset by peer)) [16:22] because it only happens once in a while, not consistently, and I'm busy with something else at the time. [16:23] *** MatWho has joined #tikiwiki [16:24] Maybe there is a permission check problem with your login bar. You could check for "if $user" kinds of things or other "if" statements. [16:25] chibaguy - that is a good point re: permissions; but why would it then appear when I refresh my browser? [16:26] Maybe a cookie changed. [16:27] Or something like that. [16:28] Geting late here... ;-) [16:28] Getting [16:29] *** Wilkins has quit IRC (Remote closed the connection) [16:31] *** snarlydwarf has joined #tikiwiki [16:32] g'night all. :-) [16:32] *** chibaguy has left [16:39] *** GillesMM has joined #tikiwiki [16:42] *** marclaporte has joined #tikiwiki [16:48] salut marclaporte [16:49] marclaporte: Are you there [16:49] *** Lucymoz has joined #tikiwiki [16:52] yes, in taxi [16:52] just have a few minutes [16:52] wasssup? [16:52] polom GillesMM [16:52] GillesMM: : I am back in Paris end of November [16:53] cool [16:53] call me to have a lunch together [16:53] GillesMM: : do you have any shows early Dec? [16:54] I don't know we are recording ... [16:54] marclaporte: just want to talk to whoever did the WYSYWIG see if I can get the documentation improved and find out how it works do you know who it is [16:55] Johnny Bradley worked on trying to make more reliable [16:55] Our Strasbourg friends implemented (Nyloth & co) [16:55] svn blame should help [16:56] ok [17:04] *** kerrnel has joined #tikiwiki [17:04] howdy [17:05] *** Redhatter has quit IRC (Read error: 104 (Connection reset by peer)) [17:06] *** Redhatter has joined #tikiwiki [17:06] *** Caarrie is now known as Icari|away [17:06] *** Icari|away is now known as Caarrie|away [17:07] Anybody know why a