You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(103) |
Jul
(105) |
Aug
(16) |
Sep
(16) |
Oct
(78) |
Nov
(36) |
Dec
(58) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(100) |
Feb
(155) |
Mar
(84) |
Apr
(33) |
May
(22) |
Jun
(77) |
Jul
(36) |
Aug
(37) |
Sep
(183) |
Oct
(74) |
Nov
(235) |
Dec
(165) |
2002 |
Jan
(187) |
Feb
(183) |
Mar
(52) |
Apr
(10) |
May
(15) |
Jun
(19) |
Jul
(43) |
Aug
(90) |
Sep
(144) |
Oct
(144) |
Nov
(171) |
Dec
(78) |
2003 |
Jan
(113) |
Feb
(99) |
Mar
(80) |
Apr
(44) |
May
(35) |
Jun
(32) |
Jul
(34) |
Aug
(34) |
Sep
(30) |
Oct
(57) |
Nov
(97) |
Dec
(139) |
2004 |
Jan
(132) |
Feb
(223) |
Mar
(300) |
Apr
(221) |
May
(171) |
Jun
(286) |
Jul
(188) |
Aug
(107) |
Sep
(97) |
Oct
(106) |
Nov
(139) |
Dec
(125) |
2005 |
Jan
(200) |
Feb
(116) |
Mar
(68) |
Apr
(158) |
May
(70) |
Jun
(80) |
Jul
(55) |
Aug
(52) |
Sep
(92) |
Oct
(141) |
Nov
(86) |
Dec
(41) |
2006 |
Jan
(35) |
Feb
(62) |
Mar
(59) |
Apr
(52) |
May
(51) |
Jun
(61) |
Jul
(30) |
Aug
(36) |
Sep
(12) |
Oct
(4) |
Nov
(22) |
Dec
(34) |
2007 |
Jan
(49) |
Feb
(19) |
Mar
(37) |
Apr
(16) |
May
(9) |
Jun
(38) |
Jul
(17) |
Aug
(31) |
Sep
(16) |
Oct
(34) |
Nov
(4) |
Dec
(8) |
2008 |
Jan
(8) |
Feb
(16) |
Mar
(14) |
Apr
(6) |
May
(4) |
Jun
(5) |
Jul
(9) |
Aug
(36) |
Sep
(6) |
Oct
(3) |
Nov
(3) |
Dec
(3) |
2009 |
Jan
(14) |
Feb
(2) |
Mar
(7) |
Apr
(16) |
May
(2) |
Jun
(10) |
Jul
(1) |
Aug
(10) |
Sep
(11) |
Oct
(4) |
Nov
(2) |
Dec
|
2010 |
Jan
(1) |
Feb
|
Mar
(13) |
Apr
(11) |
May
(18) |
Jun
(44) |
Jul
(7) |
Aug
(2) |
Sep
(14) |
Oct
|
Nov
(6) |
Dec
|
2011 |
Jan
(2) |
Feb
(6) |
Mar
(3) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
(11) |
Feb
(3) |
Mar
(11) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(4) |
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(8) |
Dec
(1) |
2015 |
Jan
(3) |
Feb
(2) |
Mar
|
Apr
(3) |
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
2016 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
(5) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(6) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
2022 |
Jan
(11) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
(3) |
2024 |
Jan
(7) |
Feb
(2) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Steve W. <sw...@pa...> - 2001-10-05 19:39:21
|
Hi Marjorie, The instructions I wrote here are for version 1.2; I keep copies running on my home box, and I went through the whole process myself to make sure it worked... is there a URL you can send me for your Wiki? I'd like to check myself to see if it's there. cheers ~swain On Fri, 5 Oct 2001, Marjorie Roswell wrote: > In version 1.2 the zip utility is _not_ part of the admin function. > > Doesn't seem like anybody here is using 1.2. Is everybody using hacks or are people generally using one of the more recent versions? > > I sort of wanted to use the stable one, but if there's one I should upgrade to (or if an upgrade is imminent) let me know... > > I don't see more recent versions, actually, at > http://sourceforge.net/projects/phpwiki/ > > ---------- Original Message ---------------------------------- > From: Steve Wainstead <sw...@pa...> > Date: Fri, 5 Oct 2001 14:53:12 -0400 (EDT) > > > > >Hi Marjorie. I'm very sorry about the trouble you had recently. :-( > > > >You are right that version 1.2 is lacking in documentation, esp. wrt > >administration. Here's how to get a zip copy of the wiki pages: > > > >First, go to the directory where PhpWiki is installed and edit admin.php. > >There is a spot in there to set the login and password for the > >administrator: > > > ><?php // $Id: admin.php,v 1.5 2000/11/13 10:59:27 ahollosi Exp $ > > > > function rcs_id($id) {} // otherwise this gets in the way > > > > define('WIKI_ADMIN', true); // has to be before includes > > > > include("lib/config.php"); > > include("lib/stdlib.php"); > > > > // set these to your preferences. For heaven's sake > > // pick a good password! > > $wikiadmin = ""; > > $adminpasswd = ""; > > > >Set these to whatever you want, like "admin" and "itsasecret". > > > >Now you want to go to your Wiki in your browser, but to admin.php: > > > >http://yourhost.yourdomain/path-to-wiki/admin.php > > > >You should be prompted for the login/password you just set. Once that's > >done, go to FindPage, type "admin" into the title search and that should > >pull up PhpWikiAdministration for you. > > > >Here you can get two kinds of zip dumps of the Wiki pages: the latest > >versions and a dump with all archived versions as well. Just click the > >link and your browser should ask you where to save the zip file. > > > >Let me know it that works for you. Also, did you post your problems with > >mysql here? Most of the people on the list are Mysql wizzards and should > >be able to pinpoint the problem. > > > >~swain > > > >--- > > http://www.panix.com/~swain/ > >"Without music to decorate it, time is just a bunch of boring > >production deadlines or dates by which bills must be paid." > > -- Frank Zappa > > > > > --- http://www.panix.com/~swain/ "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." -- Frank Zappa |
From: Marjorie R. <mro...@ma...> - 2001-10-05 18:59:49
|
In version 1.2 the zip utility is _not_ part of the admin function. Doesn't seem like anybody here is using 1.2. Is everybody using hacks or are people generally using one of the more recent versions? I sort of wanted to use the stable one, but if there's one I should upgrade to (or if an upgrade is imminent) let me know... I don't see more recent versions, actually, at http://sourceforge.net/projects/phpwiki/ ---------- Original Message ---------------------------------- From: Steve Wainstead <sw...@pa...> Date: Fri, 5 Oct 2001 14:53:12 -0400 (EDT) > >Hi Marjorie. I'm very sorry about the trouble you had recently. :-( > >You are right that version 1.2 is lacking in documentation, esp. wrt >administration. Here's how to get a zip copy of the wiki pages: > >First, go to the directory where PhpWiki is installed and edit admin.php. >There is a spot in there to set the login and password for the >administrator: > ><?php // $Id: admin.php,v 1.5 2000/11/13 10:59:27 ahollosi Exp $ > > function rcs_id($id) {} // otherwise this gets in the way > > define('WIKI_ADMIN', true); // has to be before includes > > include("lib/config.php"); > include("lib/stdlib.php"); > > // set these to your preferences. For heaven's sake > // pick a good password! > $wikiadmin = ""; > $adminpasswd = ""; > >Set these to whatever you want, like "admin" and "itsasecret". > >Now you want to go to your Wiki in your browser, but to admin.php: > >http://yourhost.yourdomain/path-to-wiki/admin.php > >You should be prompted for the login/password you just set. Once that's >done, go to FindPage, type "admin" into the title search and that should >pull up PhpWikiAdministration for you. > >Here you can get two kinds of zip dumps of the Wiki pages: the latest >versions and a dump with all archived versions as well. Just click the >link and your browser should ask you where to save the zip file. > >Let me know it that works for you. Also, did you post your problems with >mysql here? Most of the people on the list are Mysql wizzards and should >be able to pinpoint the problem. > >~swain > >--- > http://www.panix.com/~swain/ >"Without music to decorate it, time is just a bunch of boring >production deadlines or dates by which bills must be paid." > -- Frank Zappa > > |
From: Steve W. <sw...@pa...> - 2001-10-05 18:53:15
|
Hi Marjorie. I'm very sorry about the trouble you had recently. :-( You are right that version 1.2 is lacking in documentation, esp. wrt administration. Here's how to get a zip copy of the wiki pages: First, go to the directory where PhpWiki is installed and edit admin.php. There is a spot in there to set the login and password for the administrator: <?php // $Id: admin.php,v 1.5 2000/11/13 10:59:27 ahollosi Exp $ function rcs_id($id) {} // otherwise this gets in the way define('WIKI_ADMIN', true); // has to be before includes include("lib/config.php"); include("lib/stdlib.php"); // set these to your preferences. For heaven's sake // pick a good password! $wikiadmin = ""; $adminpasswd = ""; Set these to whatever you want, like "admin" and "itsasecret". Now you want to go to your Wiki in your browser, but to admin.php: http://yourhost.yourdomain/path-to-wiki/admin.php You should be prompted for the login/password you just set. Once that's done, go to FindPage, type "admin" into the title search and that should pull up PhpWikiAdministration for you. Here you can get two kinds of zip dumps of the Wiki pages: the latest versions and a dump with all archived versions as well. Just click the link and your browser should ask you where to save the zip file. Let me know it that works for you. Also, did you post your problems with mysql here? Most of the people on the list are Mysql wizzards and should be able to pinpoint the problem. ~swain --- http://www.panix.com/~swain/ "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." -- Frank Zappa |
From: Adam S. <ad...@pe...> - 2001-10-05 16:40:33
|
> This is a fluke, actually. But I would, indeed, like to figure out > that phpwiki zip utility thing, in version 1.2 (or what I should > upgrade to, to make it more obvious what to do. (It's not built into > the admin utility.) it works great for me in 1.3. i just click the button on the admin page and it downloads a zip file to my local computer. > Okay: these files are in my /tmp directory. Do I just physically pick > the files up and move them to a different directory, and then point to > the new location somewhere in the configuration file? yep. that should work just fine. adam. |
From: Marjorie R. <mro...@ma...> - 2001-10-05 15:33:45
|
>lesson? never trust anyone to do your backups. This is a fluke, actually. But I would, indeed, like to figure out that phpwiki zip utility thing, in version 1.2 (or what I should upgrade to, to make it more obvious what to do. (It's not built into the admin utility.) >> I was able to retrieve off of a single hard disk cache one of my main >> files. I definitely lost some stuff, which my ISP is trying to track >> down from deleted files, though apparently there is some risk of >> screwing things up more. > >check google (and maybe other search engines) for cached copies. you >might be lucky. Yeah, tried that: no luck. What other utilities save cached copies? Does anyone know? >good luck! Okay: these files are in my /tmp directory. Do I just physically pick the files up and move them to a different directory, and then point to the new location somewhere in the configuration file? -rw-r--r-- 1 nobody nobody 0 Oct 4 15:20 wikipagesdb.lck -rw-r--r-- 1 nobody nobody 0 Oct 4 15:20 wikilinksdb.lck -rw-r--r-- 1 nobody nobody 0 Oct 4 15:20 wikihottopicsdb.lck -rw-r--r-- 1 nobody nobody 1536 Oct 4 15:20 wikihottopicsdb -rw-r--r-- 1 nobody nobody 0 Oct 4 15:20 wikihitcountdb.lck -rw-r--r-- 1 nobody nobody 0 Oct 4 15:20 wikiarchivedb.lck drwxrwxrwt 2 xfs xfs 4096 Oct 4 18:31 .font-unix/ -rw-r--r-- 1 nobody nobody 3057 Oct 4 19:06 wikiarchivedb -rw-r--r-- 1 nobody nobody 41945 Oct 4 19:20 wikipagesdb -rw-r--r-- 1 nobody nobody 15358 Oct 4 19:20 wikilinksdb drwxrwxrwt 14 root root 4096 Oct 5 04:02 ./ -rw-r--r-- 1 nobody nobody 1685 Oct 5 08:59 wikihitcountdb |
From: Adam S. <ad...@pe...> - 2001-10-05 03:45:49
|
> That's exactly what happened. I hadn't looked at the wiki in 10 very > busy days, and the server was set to delete such unused /tmp files. > Honestly, sincerely, this wiki is a truly good thing, which truly, > really and truly again could use some better documentation on how to > install and configure it. lame. if your isp is clueful make then find an undelete utility for your server and try and they should be able to restore a version of it. but you *HAVE* to do this really really soon or the disk blocks where the file was stored may get over written. it may also be impossible as on some unix's /tmp is a ram drive and then there really is nothing to recover (it will probably work if the server was linux, it probably won't if the server is solaris). lesson? never trust anyone to do your backups. > I was able to retrieve off of a single hard disk cache one of my main > files. I definitely lost some stuff, which my ISP is trying to track > down from deleted files, though apparently there is some risk of > screwing things up more. check google (and maybe other search engines) for cached copies. you might be lucky. > My co-author and I are planning a visual guide to nutrition. The wiki > seems like a good tool to help us to put it together. (Security is > obviously a concern...) She's terrific, and he had a good meeting, > despite my missing (gaping hole, the ocean swallowed it up, the earth > is coming to an... okay, okay) content. good luck! adam. |
From: Adam S. <ad...@pe...> - 2001-10-05 03:11:40
|
trying to remove a page fails with this error: Fatal error: Failed opening required 'lib/template.php' (include_path='.:/var/lib/phpwiki-alpha') in /var/lib/phpwiki-alpha/admin/removepage.php on line 19 and template really doesn't exist anywhere that i could see. updating admin/removepage.php to point to Template.php fixes this but then it gets caught in a loop and won't delete the page when you click "here". adam. |
From: Marjorie R. <mro...@ma...> - 2001-10-05 03:09:28
|
>'directory' variable. this points to the directory where the >wiki_pagedb.db2 file lives which is what stores all the data. > >if you didn't configure this file to start with it stores everything in >/tmp which means that you're gonna loose all your data everytime your >isp reboots their web server. :-( That's exactly what happened. I hadn't looked at the wiki in 10 very busy days, and the server was set to delete such unused /tmp files. Honestly, sincerely, this wiki is a truly good thing, which truly, really and truly again could use some better documentation on how to install and configure it. I had started to try to upgrade to mysql, and got plain stuck there, as some may recall. (I remained stuck to this day.) Today when I got the one-two punch that my wiki was gone, and then that it was REALLY gone (not backed up - my ISP admits to "screwing up") I felt sick to my stomach, as I was just on the verge of picking up my coauthor at the train station so that I could show her this cool collaberative web environment, along with all the neat content I'd added to it. Lots of things went wrong, including the /tmp directory, the lack of a backup that should've been done (I'm paying for this server, they admit that they blew it), and even that the zip file utility was not as well-documented as it could've been, and helpful guidance from this group was all based on something apparently more recent than the 1.2. I had tried to take that snapshot, and had failed at that too. This is a great group! I respect you! all! And your skill, and the cool inclusive project that we're all building. I'm just trying to document what went wrong, though slightly too tired to do so. I was able to retrieve off of a single hard disk cache one of my main files. I definitely lost some stuff, which my ISP is trying to track down from deleted files, though apparently there is some risk of screwing things up more. I'm going to: a. try to be a better participant in this group by trying to resolve the problem accessing this email using pine from a linux box (which I prefer). The web imail interface I'm using now is actually preventing me from being a full participant, (it's a terrible interface.) Sounds dumb, but it's just a barrier, for now. b. I'm thankful that I found a cached version of one of my key files. c. I plan to stick with this wiki, figure out how to not make it disappear, and probably offer some suggestions (when I'm not bleary-eyed, and still slightly naseous) on how to improve some of the default documentation. My co-author and I are planning a visual guide to nutrition. The wiki seems like a good tool to help us to put it together. (Security is obviously a concern...) She's terrific, and he had a good meeting, despite my missing (gaping hole, the ocean swallowed it up, the earth is coming to an... okay, okay) content. I had shown this wiki to my boss. Maybe her computer will have some of my lost stuff.... Thanks guys, for responding right away, today. It helped. Sincerely, tiredly, (forgive me, and my adverb abuse) Margie |
From: Adam S. <ad...@pe...> - 2001-10-04 23:45:19
|
Hey. I'm in the process of migrating from MoinMoin to PhpWiki for my personal wiki site. In the process I'm writing some docs for hosting a PhpWiki farm (cause I now run 4 wiki's for friends and projects and I only see the number getting larger with time :-). The docs aren't great yet because I keep reshuffling how I think it should be done but I'll test them and fix them up in the next few days. http://www.spack.org/index.cgi/InstallPhpWiki http://www.spack.org/test/index.php/InstallPhpWiki So my first project was to manually port the InstallPhpWiki page from Moin mark up to Phpwiki mark up as prep for writing a perl script to batch all the pages into my new wiki! Well easier said then done, it appears I've grown used to things working a certain way. * Is there anyway to do indented mono-spaced text other then just lots of spaces? In Moin one leading space always indents to the level of a list indent. In Phpwiki it seems to just indent a space. * Is there any way to do a single word (or phrase) mono-spaced within a normal sentence? Moin does it {{{like this}}}. * Should mono-spaced text also escape all automatic linking? The main thing I use mono-spaced text for is cut and paste of config files etc and it's annoying to have to ! each accidental wiki word. * What determines when a list ends and a new one starts. The way I've been using lists seems to make them start over (so I just get repeated single element lists). I don't think lists should start over until there is a non-indented paragraph or line. * With Interwiki links what is the reason for having Wiki:WikiClone actually show up as Wiki:WikiClone as apposed to just WikiClone? It seems unwiki'ish to break the natural flow of language. Does it really matter that you know which site you're going to when you click on a link? * InterWiki links only work if the part after the : is a wiki word. This means that things like an ISBN, IMDB or Category InterWiki link can't work. It would also be nice if page names with +'s would work so that an InterWiki word like Google:php+wiki would work. Examples here: http://www.spack.org/test/index.php/SandBox * The c2 wiki is listed twice in the interwiki.map file (as Wiki and as PPR). * I've made an aggregate interwiki.map file which includes everything listed by Moin, Phpwiki and Meatball. If you want it you can download it from here: http://www.spack.org/download/interwiki.map Overall though it was pretty painless. When you consider that all the tricks I'm using in Moin I've learned over the last year, and I've figured out how to get Phpwiki to do almost all of them in less then a day! Thanks! Adam. |
From: Adam S. <ad...@pe...> - 2001-10-04 21:28:14
|
> I'm not thinking straight. Which config file? Honest, I'm shaking.... > (because My ISP hadn't backed up this stuff, either...) i'm not sure because i don't use 1.2 and i don't use a sql backend, but for me in the new cvs version using dba it's all in index.php and it's the 'directory' variable. this points to the directory where the wiki_pagedb.db2 file lives which is what stores all the data. if you didn't configure this file to start with it stores everything in /tmp which means that you're gonna loose all your data everytime your isp reboots their web server. :-( adam. |
From: Adam S. <ad...@pe...> - 2001-10-04 20:48:01
|
> I just lost everything on my wiki. It was as though it was starting > from scratch, reloading everything. why would that happen? i'm not particularly familiar with the 1.2 release but the only thing i can think of which would cause that would be if you changed something in your config file which caused it to move where it keeps your data. if something changed and it's now looking for the page data in a different directory or sql table then it's going to think it's a fresh install and reload the data from pgsrc. adam. |
From: Marjorie R. <mro...@ma...> - 2001-10-04 20:37:32
|
Help? I just lost everything on my wiki. It was as though it was starting from scratch, reloading everything. why would that happen? This is a big problem! Is there anything I can do. I'm on hold to find out if a backup can be restored. Any guidance for this? Margie 410-455-6802 |
From: Adam S. <ad...@pe...> - 2001-10-04 18:10:15
|
> Subpages really are just syntactic sugar, and merely provide a > shorthand notation for related pages. Here's, sort of, how I see this > would work: okay after reading through all this on meatball i finally understand the point of this. this would be really useful for some of the stuff that happens on my wiki all the time where people don't want everythign on one page for some reason so they create a billion pages, all with the same prefix. > Within page SuperPage, a link starting with a period, [.SubPage], would > refer to SuperPage.SubPage. I'm still uncertain as to: while starting it with a . makes sense from a tech point of view i'm not sure it's obvious enough to clue in new users that there's something different about that page. / makes it obvious that something's different about it but really confused me because that means "root" in filesystem terms and that really not what it is. what about +? also, do subpages show up in RecentChanges? > 1. Whether there can be sub-sub-pages. i think this is probably asking for trouble. > Subwikis are true partitions of the wiki namespace (with separate > RecentChanges, etc...). Within the page 'SubWiki/PageName', normal > links, like [OtherPage], refer to 'SubWiki/OtherPage'. If you want to > link to a page that's not in your subwiki, you have to start with a > slash ([/TopLevelPage], or [/OtherSubWiki/OtherPage]). i think this is very useful for two things. * having one wiki run multiple different wiki's. this is sort of what twiki does so that by default it ships with a main, knowledge base, twiki ... wiki's by default. * automated plugins which create a lot of pages (maybe calendar, or todo, or addressbook or photogallery etc). however having now played with NiKKi which does this i have to say that it's not nearly as nice as it sounds. it gets really complicated and unituitive until you understand what all the categories are supposed to be used for. > Mostly as an aside, somewhere (UseMod?) I saw a suggestion of using a > Category: InterWiki prefix as a hack for this. Category:Example would > be converted, by the InterWiki linker, to a link to CategoryExample, > but it won't show up as a backlink... this is a great idea! thanks. > Hack lib/editpage.php so that when one edits an non-existant/empty > page, instead of the regular editpage form, one gets a template-choice > form. This would allow one to set the initial contents of the page to > any one of a set of skeletons. The skeletons would taken from pages > matching a particular pattern, like Template*. Eg. TemplateHomePage > would be a skeleton for a home page, ... this is exactly how moinmoin does it and it works pretty well. the only annoying thing is people's tendancy to create really dumb (and far too many) templates. it would be good to have a TemplateDefault as well so you can edit what gets loaded if they don't choose a template (i use this to put a [CategoryUnknown] at the bottom so i can search for things in the unknown category and categorize them). adam. |
From: Adam S. <ad...@pe...> - 2001-10-04 16:42:22
|
> What title will we give that page? Will it depend on the name it was > given when it was created? that makes sense to me. if it was created with thte wrong name then it's a job for the editor of the wiki to fix just like if they created a page called RunnningTogether or any other of the mistakes which happen on an active wiki. > If there are to be any equivalences, I personally think that FooBarBaz > should be equivalent to [foo bar baz], which is also three words, but > not [foobarbaz] which is presumably one word. This would mean that > "RunningTogether" would be distinguishable from "RunningToGetHer". i think that this is a rare enough case that the number of times this will be a problem are outweighed by the convenience of people being able to link to the same page in slightly different ways. adam. |
From: Jeff D. <da...@da...> - 2001-10-04 16:39:53
|
Hi There, Sorry, I've been AWOL for awhile. I'm still not quite back, but thought I'd check in. WikiNames: I think case insensitivity in page names is a bad idea. Mostly for the reasons that Malcolm Ryan listed. Capitalization is the punctuation of a wiki --- capitals in WikiWords (should) have clear semantics attached to them, and one should ignore them by smashing the case. (I also think page names like EquipMent are a bad idea. That's why brackets were introduced... better yet: add a word to make the page name a more descriptive title: EquipmentInventory.) I agree that HowToEatASandwich should match $WikiNameRegexp. Subpages/Subwikis: I see two separate ideas here: Subpages really are just syntactic sugar, and merely provide a shorthand notation for related pages. Here's, sort of, how I see this would work: Within page SuperPage, a link starting with a period, [.SubPage], would refer to SuperPage.SubPage. I'm still uncertain as to: 1. Whether there can be sub-sub-pages. 2. If there is a shorthand notation which a sub-page can use to refer to a sister subpage. Subwikis are true partitions of the wiki namespace (with separate RecentChanges, etc...). Within the page 'SubWiki/PageName', normal links, like [OtherPage], refer to 'SubWiki/OtherPage'. If you want to link to a page that's not in your subwiki, you have to start with a slash ([/TopLevelPage], or [/OtherSubWiki/OtherPage]). Plugins: I like Joe's IncludePage plugin, and agree that it looks to be a good way to provide partial page locking, etc... If no one beats me to it I'll try to get it merged into the CVS code next week sometime. Ticket tracking / ctime in link table: It's doable. The "right way" to do it (IMHO) is to add the ability to attach arbitrary meta-data to links, not just ctime. To be brutally honest, it's not high on my todo list right now though... Half-links: Could easily be kludged with a plugin. Mostly as an aside, somewhere (UseMod?) I saw a suggestion of using a Category: InterWiki prefix as a hack for this. Category:Example would be converted, by the InterWiki linker, to a link to CategoryExample, but it won't show up as a backlink... Templates: What exactly do y'all mean by "templates"? I'm guessing you mean the ability to choose between various content skeletons when you're editing a new page. If so, then, no there's currently no support for it. Here's how I would envision adding support for them: Hack lib/editpage.php so that when one edits an non-existant/empty page, instead of the regular editpage form, one gets a template-choice form. This would allow one to set the initial contents of the page to any one of a set of skeletons. The skeletons would taken from pages matching a particular pattern, like Template*. Eg. TemplateHomePage would be a skeleton for a home page, ... Once the user selects a template (or none), he gets the regular editpage form... Jeff |
From: Malcolm R. <mal...@cs...> - 2001-10-04 05:04:42
|
On Wed, Oct 03, 2001 at 09:39:02AM +0100, Reini Urban wrote: > > > > But the current 1.3 release splits WikiWords in the page titles, so that > > FrontPage is shown as "Front Page". If you are going to make EquipMent > > the same as [equipment] then should it also be the same as [Equip Ment]? > > no, SplitPageInTitle is only for output in the header and the title, > but not for anything else. (linking and other WikiWord magic) > > this is mainly for being search engine friendly. Still, it is indicative of an underlying assumption that BumpyCaps is being using to indicate word boundaries, whereas ignoring case indicates the opposite. I think we need to get it clear in our minds which way want want to go. Consider this. If I add a link FooBarBaz to a wiki page, and then click the question mark I will get to edit a page, and the title of that page will be shown as "Foo Bar Baz". If I create a link to [foobarbaz] I will edit a page with title "foobarbaz". If we are to ignore capitalisation, both of these links will refer to the same page. What title will we give that page? Will it depend on the name it was given when it was created? Or the referring name? Or what? If there are to be any equivalences, I personally think that FooBarBaz should be equivalent to [foo bar baz], which is also three words, but not [foobarbaz] which is presumably one word. This would mean that "RunningTogether" would be distinguishable from "RunningToGetHer". Malcolm -- Malcolm Ryan - mal...@cs... - http://www.cse.unsw.edu.au/~malcolmr/ AI Dept, CSE, UNSW, Australia, Phone: +61 2 9385-6906 Fax: +61 2 9385-4936 "He causes his sun to rise on the evil and the good, and sends rain on the righteous and the unrighteous." - Matt 5:45 |
From: Adam S. <ad...@pe...> - 2001-10-04 05:00:56
|
> [Equip Ment] would be a different page from [equipment] and EquipMent > because of the space. Making FrontPage into "Front Page" for display > purposes... well.. it seemed like a good idea at the time! :-) I think it still is a good idea. most wiki words are MultipleWords and spliting them for the <title> and page title means search engines will index the pages properly. adam. |
From: Steve W. <sw...@pa...> - 2001-10-04 02:42:04
|
On Wed, 3 Oct 2001, Malcolm Ryan wrote: > > Well, I meant in the implementation, we store the page name in lowercase. > > The user would see EquipMent and [equipment] as links to the same page. > > This would avoid the problem of EquipMent and [equipment] being different > > pages... users could link them in whichever manner they see fit. > > But the current 1.3 release splits WikiWords in the page titles, so that > FrontPage is shown as "Front Page". If you are going to make EquipMent > the same as [equipment] then should it also be the same as [Equip Ment]? [Equip Ment] would be a different page from [equipment] and EquipMent because of the space. Making FrontPage into "Front Page" for display purposes... well.. it seemed like a good idea at the time! :-) ~swain --- http://www.panix.com/~swain/ "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." -- Frank Zappa |
From: Reini U. <ru...@x-...> - 2001-10-03 08:39:13
|
Malcolm Ryan schrieb: > On Tue, Oct 02, 2001 at 03:37:54PM -0400, Steve Wainstead wrote: > > On Mon, 1 Oct 2001, Adam Shand wrote: > > > > > i'm very in favor of case insenstive page names. i think case sensitive > > > page names are unintuitve, especially when people insist on doing single > > > word page links like EquipMent, exactly which letters are capitalized is > > > kind of arbitrary, and i see no reason for them to link to different > > > pages. > > > > Well, I meant in the implementation, we store the page name in lowercase. > > The user would see EquipMent and [equipment] as links to the same page. > > This would avoid the problem of EquipMent and [equipment] being different > > pages... users could link them in whichever manner they see fit. > > But the current 1.3 release splits WikiWords in the page titles, so that > FrontPage is shown as "Front Page". If you are going to make EquipMent > the same as [equipment] then should it also be the same as [Equip Ment]? no, SplitPageInTitle is only for output in the header and the title, but not for anything else. (linking and other WikiWord magic) this is mainly for being search engine friendly. |
From: Malcolm R. <mal...@cs...> - 2001-10-03 02:09:28
|
On Tue, Oct 02, 2001 at 03:37:54PM -0400, Steve Wainstead wrote: > On Mon, 1 Oct 2001, Adam Shand wrote: > > > i'm very in favor of case insenstive page names. i think case sensitive > > page names are unintuitve, especially when people insist on doing single > > word page links like EquipMent, exactly which letters are capitalized is > > kind of arbitrary, and i see no reason for them to link to different > > pages. > > Well, I meant in the implementation, we store the page name in lowercase. > The user would see EquipMent and [equipment] as links to the same page. > This would avoid the problem of EquipMent and [equipment] being different > pages... users could link them in whichever manner they see fit. But the current 1.3 release splits WikiWords in the page titles, so that FrontPage is shown as "Front Page". If you are going to make EquipMent the same as [equipment] then should it also be the same as [Equip Ment]? Malcolm -- Malcolm Ryan - mal...@cs... - http://www.cse.unsw.edu.au/~malcolmr/ AI Dept, CSE, UNSW, Australia, Phone: +61 2 9385-6906 Fax: +61 2 9385-4936 "He causes his sun to rise on the evil and the good, and sends rain on the righteous and the unrighteous." - Matt 5:45 |
From: Adam S. <ad...@pe...> - 2001-10-02 21:25:19
|
> Well, I meant in the implementation, we store the page name in > lowercase. The user would see EquipMent and [equipment] as links to > the same page. This would avoid the problem of EquipMent and > [equipment] being different pages... users could link them in > whichever manner they see fit. i *thought* that's what i said. regardless, what you said above? that's what i meant. :) adam. |
From: Steve W. <sw...@pa...> - 2001-10-02 19:37:57
|
On Mon, 1 Oct 2001, Adam Shand wrote: > i'm very in favor of case insenstive page names. i think case sensitive > page names are unintuitve, especially when people insist on doing single > word page links like EquipMent, exactly which letters are capitalized is > kind of arbitrary, and i see no reason for them to link to different > pages. Well, I meant in the implementation, we store the page name in lowercase. The user would see EquipMent and [equipment] as links to the same page. This would avoid the problem of EquipMent and [equipment] being different pages... users could link them in whichever manner they see fit. ~swain --- http://www.panix.com/~swain/ "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." -- Frank Zappa |
From: Adam S. <ad...@pe...> - 2001-10-02 01:52:29
|
> It should also be possible to refer to a "local" subpage without > naming the parent page. Eg: The "MalcolmRyan" page should be able to > refer to "MalcolmRyan/AnnoyingHabits" as just "/AnnoyingHabits". > > [Personally, I would prefer '.' over '/']. won't there need to be some way to differentiate between relative and absolute wiki paths? and can you have sub-sub-wiki's? and can the parents have a page as well as children or are the just the equivelent of directories? hrm, i'll shutup now and go play with usemod some more, i'm not sure i understand what sub-wiki's are actually for. adam. |
From: <jo...@or...> - 2001-10-02 01:08:14
|
>> * I really want my searches to be able to tell me when a Category was >> added to a page, even if that page has been modified several times >> since then. > I think this won't work because every time a page is edited/saved, we > first delete all frompage entries in the link table, parse the page for > links, and reinsert them. It would be a nightmare to try to do this the > other way (select all links from the table; parse the page; compare the > two sets; delete the ones not in set 1, insert the ones only in set 2.) Why is this a nightmare? If the links table is indexed the select shouldn't take any time. foreach ($select_result as $s) { $prevlinks[$s] = 1; } $newlinks = ExtractWikiPageLinks($page_submission); foreach ($newlinks as $n) { if (!$prevlinks[$n]) $to_insert[] = $n; $prevlinks[$n] = 0; } $to_delete = (array_flip($prevlinks))[1]; Looks to me like the PHP running time is O(N), where N is the number of links, and the SQL running time is probably O(N log N) but is so fast it doesn't concern us. Not that any of this matters. AN ALTERNATIVE: If word-level diffs are implemented then hopefully the new links will be the ones that show up as added words/lines, and the deleted links will be the ones that show up as deleted words/lines. > My idea has been to keep a log of all transactions in the database, or > maybe a flat file, and you could trace edits that way. Otherwise you have > to resort to looking at diffs. An internal log of edits would provide an > audit trail. I think that one internal-code thing that would be neat to work on would be a kind of diff API. For instance email notifications should be able to send diffs. And imagine if you wanted to confirm every email address that appeared on the site-- it would be no good to check up on all of them in a page in each page save, if there were long lists, but if you had ready access to just the part of the last edit that was different... that seems feasible. Finally there is the possibility of syncronizing multiple wikis using machine readable diffs instead of the CVS backend. >> /SubPages > It's just "syntactic sugar," isn't it? That is, allowing slashes in page > names? I think it's a change to the ParseAndLink or the Link*WikiLink code: bracket links starting with a dot or a slash ("[.Link]") on MyPage need to be linked to WikiURL('MyPage.Link') instead of just WikiURL('.Link'). > I'm wondering at the moment if we shouldn't just make the implementation > of page names case insensitive. I think that's a good idea. |
From: Malcolm R. <mal...@cs...> - 2001-10-02 01:01:30
|
> > > * The /SubPages like on UseMod would be really easy to implement. Should > > they be? > > It's just "syntactic sugar," isn't it? That is, allowing slashes in page > names? It should also be possible to refer to a "local" subpage without naming the parent page. Eg: The "MalcolmRyan" page should be able to refer to "MalcolmRyan/AnnoyingHabits" as just "/AnnoyingHabits". [Personally, I would prefer '.' over '/']. Malcolm -- Malcolm Ryan - mal...@cs... - http://www.cse.unsw.edu.au/~malcolmr/ AI Dept, CSE, UNSW, Australia, Phone: +61 2 9385-6906 Fax: +61 2 9385-4936 "He causes his sun to rise on the evil and the good, and sends rain on the righteous and the unrighteous." - Matt 5:45 |