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...> - 2002-01-17 21:14:15
|
If there are no objections, I will crank up the promotion machine and release 1.3.3 some time tomorrow... ~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: Tim B. <tim...@wc...> - 2002-01-17 21:04:48
|
Ah Hah! My db server is not set up properly. In short the postmaster is not running with the -i option. I tried to edit the /var/init.d/postgres file to include it but the service fails to restart no matter where I try to put the thing. The whole line looks like this... su -l postgres -s su -l postgres -s /bin/sh -c "/usr/bin/pg_ctl -D $PGDATA -p /usr/bin/postmaster start > /dev/null 2>&1" < /dev/null I've tried it here... su -l postgres -s su -l postgres -s /bin/sh -c "/usr/bin/pg_ctl -D $PGDATA -pi /usr/bin/postmaster start > /dev/null 2>&1" < /dev/null I've tried it here... su -l postgres -s su -l postgres -s /bin/sh -c "/usr/bin/pg_ctl -D $PGDATA -p -i /usr/bin/postmaster start > /dev/null 2>&1" < /dev/null I've tried it here... su -l postgres -s su -l postgres -s /bin/sh -c "/usr/bin/pg_ctl -D $PGDATA -i /usr/bin/postmaster start > /dev/null 2>&1" < /dev/null and the service fails to start. Any suggestions? > > (If possible,) log in to the machine your HTTP server is running on, then > at a shell prompt try the suggested command. (Also 'man psql' for more > info.) > > (Your original DSN in index.php looked okay, so put that back the way it > was.) > Sorry for the confusion. > > > > > > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk |
From: Lawrence A. <Law...@th...> - 2002-01-17 20:01:55
|
Jeff - you've passed the test - I always knew you would :-) http://aggregator.userland.com/validator?url=http%3A%2F%2Fphpwiki.source forge.net%2Fphpwiki%2FRecentChanges%3Fformat%3Drss Thanks for the tips - I'll see if I can find a convertor Lawrence-------------------------------------------------------- Confidentiality Notice The information contained in this e-mail is confidential. It is for the use of the named recipient only. If you are not the named recipient, please destroy and do not disclose the contents of this e-mail to any other person, or copy it. Thank you for your co-operation. |
From: Jeff D. <da...@da...> - 2002-01-17 19:38:41
|
Tim Bogart said: > //'dsn' => 'mysql://guest@:/var/lib/mysql/mysql.sock/test', > //'dsn' => 'mysql://guest@localhost/test', > 'dsn' => 'pgsql -h 166.32.201.228 -W wiki tim', "What we have heah ... is a FAILyuh to comMUNicate..." Psql (not pgsql) is a command-line utility which can be used to talk to a postgres database. I was suggesting using it as a sanity check to make sure your database/server is set up correctly. (If possible,) log in to the machine your HTTP server is running on, then at a shell prompt try the suggested command. (Also 'man psql' for more info.) (Your original DSN in index.php looked okay, so put that back the way it was.) Sorry for the confusion. |
From: Tim B. <tim...@wc...> - 2002-01-17 19:07:52
|
Additional info ...here's a copy of the database section of my index.php // This array holds the parameters which select the database to use. // // Not all of these parameters are used by any particular DB backend. // $DBParams = array( // Select the database type: //'dbtype' => 'SQL', 'dbtype' => 'SQL', // For SQL based backends, specify the database as a DSN // The most general form of a DSN looks like: // // phptype(dbsyntax)://username:password@protocol+hostspec/database // // For a MySQL database, the following should work: // // mysql://user:password@host/databasename // // FIXME: My version Pear::DB seems to be broken enough that there is // no way to connect to a mysql server over a socket right now. //'dsn' => 'mysql://guest@:/var/lib/mysql/mysql.sock/test', //'dsn' => 'mysql://guest@localhost/test', 'dsn' => 'pgsql -h 166.32.201.228 -W wiki tim', // Used by all DB types: // prefix for filenames or table names /* * currently you MUST EDIT THE SQL file too (in the schemas/ directory * because we aren't doing on the fly sql generation during the * installation. */ // 'prefix' => 'phpwiki_' // Used by 'dba' 'directory' => "/tmp", 'dba_handler' => 'gdbm', // Either of 'gdbm' or 'db2' work great for me //'dba_handler' => 'db2', //dba_handler' => 'db3', 'timeout' => 20, //'timeout' => 5 ); Thanks, Tim B. ----------------------------------------------- On Thursday 17 January 2002 01:42 pm, Tim Bogart wrote: > okay...that made a difference. Changed the symptom to something a little > less clear to me. Here it is... > > --------------------- > > DB Error: not found > > WikiFatalError > > lib/WikiDB/backend/PearDB.php:27: Fatal[256]: Can't connect to database: > wikidb_backend_peardb: fatal database error > > DB Error: not found > () > ------------------------------ > > More suggestions are encouraged and wildly anticipated. > > TIA > > Tim B. > > On Thursday 17 January 2002 01:07 pm, Jeff Dairiki wrote: > > Tim Bogart said: > > > I did copy the wiki_pagedb.gdbm to a pages > > > dir that I created and did a chmod 777 on them. > > > > (Of course, that's only used by the DBA backend, > > and so has nothing to do with postgres...) > > > > > The complete error goes like this... > > > > > > lib/WikiDB/backend/PearDB.php:27: Fatal[256]: Can't connect to > > > database: wikidb_backend_pgsql: fatal database error > > > > > > DB Error: connect failed > > > (pgsql://tim:********@xxx.xxx.xxx.xxx/wiki) > > > > Hmmm. Can you connect from the command line? > > > > I'm not a postgres expert, but I think the command for that would be: > > > > psql -h xxx.xxx.xxx.xxx -W wiki tim > > > > > > > > > > _______________________________________________ > > Phpwiki-talk mailing list > > Php...@li... > > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk |
From: Tim B. <tim...@wc...> - 2002-01-17 18:17:11
|
okay...that made a difference. Changed the symptom to something a little less clear to me. Here it is... --------------------- lib/WikiDB/backend/PearDB.php:27: Fatal[256]: Can't connect to database: wikidb_backend_peardb: fatal database error DB Error: not found WikiFatalError lib/WikiDB/backend/PearDB.php:27: Fatal[256]: Can't connect to database: wikidb_backend_peardb: fatal database error DB Error: not found () ------------------------------ More suggestions are encouraged and wildly anticipated. TIA Tim B. On Thursday 17 January 2002 01:07 pm, Jeff Dairiki wrote: > Tim Bogart said: > > I did copy the wiki_pagedb.gdbm to a pages > > dir that I created and did a chmod 777 on them. > > (Of course, that's only used by the DBA backend, > and so has nothing to do with postgres...) > > > The complete error goes like this... > > > > lib/WikiDB/backend/PearDB.php:27: Fatal[256]: Can't connect to > > database: wikidb_backend_pgsql: fatal database error > > > > DB Error: connect failed > > (pgsql://tim:********@xxx.xxx.xxx.xxx/wiki) > > Hmmm. Can you connect from the command line? > > I'm not a postgres expert, but I think the command for that would be: > > psql -h xxx.xxx.xxx.xxx -W wiki tim > > > > > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk |
From: Jeff D. <da...@da...> - 2002-01-17 18:07:15
|
Tim Bogart said: > I did copy the wiki_pagedb.gdbm to a pages > dir that I created and did a chmod 777 on them. (Of course, that's only used by the DBA backend, and so has nothing to do with postgres...) > The complete error goes like this... > > lib/WikiDB/backend/PearDB.php:27: Fatal[256]: Can't connect to > database: wikidb_backend_pgsql: fatal database error > > DB Error: connect failed > (pgsql://tim:********@xxx.xxx.xxx.xxx/wiki) Hmmm. Can you connect from the command line? I'm not a postgres expert, but I think the command for that would be: psql -h xxx.xxx.xxx.xxx -W wiki tim |
From: Jeff D. <da...@da...> - 2002-01-17 18:00:31
|
Tim Bogart said: >>1. In index.php, define USE_PATH_INFO to 'false'. (Just uncomment the >> sample line which is already there.) >> > > That worked. Good. Eventually you probably want to find a way to re-enable USE_PATH_INFO (if PHP is running as mod_php, and not CGI). (It results in (IMHO) prettier URLs --- not a big deal in any case.) |
From: Tim B. <tim...@wc...> - 2002-01-17 17:59:57
|
The wiki is showing signs of life now. I can see it from other computers and it shows signs of wanting to talk to the postgresql database I created for it. I did copy the wiki_pagedb.gdbm to a pages dir that I created and did a chmod 777 on them. The complete error goes like this... lib/WikiDB/backend/PearDB.php:27: Fatal[256]: Can't connect to database: wikidb_backend_pgsql: fatal database error DB Error: connect failed (pgsql://tim:********@xxx.xxx.xxx.xxx/wiki) (I replaced the password with asterisks and the ip address with x's - company policy) All suggestions, solutions, clues, inuendo, and rumors are eagerly anticipated and appreciated. TIA, Tim B. |
From: Jeff D. <da...@da...> - 2002-01-17 17:58:18
|
Lawrence Akka said: > I think the problem is a 1.0/0.9 incompatibility > > The site can only manage 0.9, or possible 0.91 > > Hmmm ... I suspect there's on on-line converter somewhere which could be used to convert 1.0 feeds to 0.9x feeds on the fly. (But I don't know where it is...) It would be simple enough to write one (using Perls XML::RSS or similar) The problem with 0.9x (for wiki use) is that there's no clean way to include standard wiki meta-information. That said, I don't think it would be a big job to hack some sort of 0.9x support into PhpWiki. (I, for one, am not going to do it right now though --- to many other fish on the plate.) (See MeatBall:ModWiki for our latest efforts at standard wiki extensions for RSS 1.0.) |
From: Lawrence A. <la...@us...> - 2002-01-17 17:44:55
|
I think the problem is a 1.0/0.9 incompatibility The site can only manage 0.9, or possible 0.91 Hmmm ... At 17:16 17/01/2002, Jeff Dairiki wrote: >Lawrence Akka said: > > > > However, I have a problem if I try to use the RSS feed on another site > > which is supposed to display RSS headlines (a bit like my.netscape used > > to). Nothing shows up. > >There are two flovors of RSS: RSS 1.0 (which is a well-defined, >cleanly-extensible, subset of RDF) and RSS 0.9x (which started as a subset >of RDF and quickly evolved to a hodge-podge mish-mash of adhoc not >necessarily so well thought out stuff). (Can you tell which one I like?) > >In any case, PhpWiki only produces RSS 1.0. Some apps may not like that. > >As always, if you've got any examples of problems, I'd like to see them... > > > > >_______________________________________________ >Phpwiki-talk mailing list >Php...@li... >https://lists.sourceforge.net/lists/listinfo/phpwiki-talk |
From: Tim B. <tim...@wc...> - 2002-01-17 17:30:04
|
On Thursday 17 January 2002 11:33 am, Jeff Dairiki wrote: > On Thu, 17 Jan 2002 11:17:22 -0500 > > "Tim Bogart" <tim...@wc...> wrote: > > It seems to be doing redirects to localhost, 127.0.0.1. > > (I'm assuming that you're running PhpWiki 1.3.x, and mod_php...) > > A couple of things to try: > > 1. In index.php, define USE_PATH_INFO to 'false'. (Just uncomment the > sample line which is already there.) > That worked. > or > > 2. Also in index.php, define SERVER_NAME to the name (or ip address) of > your server. > I did this too. > If either fixes the problem, I think it means that apache is not setting > the CGI environment variable $SERVER_NAME correctly... > > It might also be helpful to create a phpinfo script and check what value > is being assigned to SERVER_NAME. (Create a file called, say, > phpinfo.php, in your htdoc tree which contains one line: <?php phpinfo(); > ?> When you browse the file, you'll see loads and loads of information > regarding the configuration of your PHP (and Apache).) > did this one as well and now I am getting errors which make me think I'm on the threshold of solving the last of the issues here. I'll generate a new thread for this one. > > Jeff > > PS. This isn't in a virtual hosting environment is it? No, it isn't If so, then the > problem is probably that you must access the server using a host name, not > an IP number.... Thanks Jeff! |
From: Jeff D. <da...@da...> - 2002-01-17 17:16:14
|
Lawrence Akka said: > > However, I have a problem if I try to use the RSS feed on another site > which is supposed to display RSS headlines (a bit like my.netscape used > to). Nothing shows up. There are two flovors of RSS: RSS 1.0 (which is a well-defined, cleanly-extensible, subset of RDF) and RSS 0.9x (which started as a subset of RDF and quickly evolved to a hodge-podge mish-mash of adhoc not necessarily so well thought out stuff). (Can you tell which one I like?) In any case, PhpWiki only produces RSS 1.0. Some apps may not like that. As always, if you've got any examples of problems, I'd like to see them... |
From: Lawrence A. <la...@us...> - 2002-01-17 17:03:41
|
What is evolution?? Can I see the summary page with the wiki feed on it anywhere? Lawrence. At 20:55 16/01/2002, you wrote: > > Anyone got the RSS feed from RecentChanges working on another site? I > > have been trying today. I think it is probably the site's fault (how > could I doubt > > Jeff's code), but I was just wondering .... > >not another site but it works fine in evolution's summary page. > >adam. > > >_______________________________________________ >Phpwiki-talk mailing list >Php...@li... >https://lists.sourceforge.net/lists/listinfo/phpwiki-talk |
From: Lawrence A. <la...@us...> - 2002-01-17 17:02:59
|
I don't have a publicly viewable example at the moment. I can see the RSS page if click on the RSS icon on RecentChanges. However, I have a problem if I try to use the RSS feed on another site which is supposed to display RSS headlines (a bit like my.netscape used to). Nothing shows up. Now, I am perfectly prepared to believe that the fault lies with the other site, although it seems to have no problem with Linux Today/ Free BSD feeds and others, but I was just interested to know if anyone has got the wiki RSS feed incorporated into a site anywhere. In the meantime, I'll continue to bug hunt. Lawrence At 21:14 16/01/2002, you wrote: >Lawrence Akka said: > > Anyone got the RSS feed from RecentChanges working on another site? I > > have been trying today. I think it is probably the site's fault (how > > could I doubt Jeff's code), but I was just wondering .... > >What sort of trouble are you having? > >If you have a working RecentChanges page, it should "just work". If it >doesn't, it's probably the fault of Jeff's code.... > > > > >_______________________________________________ >Phpwiki-talk mailing list >Php...@li... >https://lists.sourceforge.net/lists/listinfo/phpwiki-talk |
From: Lawrence A. <la...@us...> - 2002-01-17 16:54:19
|
We are looking at doing this over at http://support.postnuke.com , the official documentation site for the postnuke CMS (www.postnuke.com). At the moment, the site is running Postnuke. 0.64, but will shortly (in the next couple of days) be upgraded to 0.7. At that point the wiki "module" (which is basically phpWiki 1.3.2) will be locked down so that only registered site users can edit pages, but anyone can view them. The PostNuke permissions system allows very fine grained control, so that different groups may have different rights over different pages (eg anyone may edit the sandbox, but only admins have read access to pages begiining with "Admin:") It is on my list to implement (or persuade someone else to implement :-)) some code which will allow dumps to be made of the dynamic wiki pages to static html, and maybe even postscript/pdf. Lawrence Akka At 04:34 17/01/2002, you wrote: >Is anyone using phpwiki as a content management system, where a group of >authorized people edit the site via the wiki interface, and then spit >pages out static for a "public" web site? > >A non-profit group I volunteer with has been hunting for good/simple/free >CMS software, and now that we're using phpwiki for an internal >documentation system, I'm starting to wonder whether it might also be the >answer to the CMS question (or maybe everything is starting to look like a >nail). > >Would need to rip out all the wiki-interface bits when dumping (eg, >Edit|PageHistory|Diff|etc.) and extract the content into some templates >that define the "production" site format... > >Any thoughts on the subject would be appreciated. > >--Paul > > >_______________________________________________ >Phpwiki-talk mailing list >Php...@li... >https://lists.sourceforge.net/lists/listinfo/phpwiki-talk |
From: Jeff D. <da...@da...> - 2002-01-17 16:33:35
|
On Thu, 17 Jan 2002 11:17:22 -0500 "Tim Bogart" <tim...@wc...> wrote: > It seems to be doing redirects to localhost, 127.0.0.1. (I'm assuming that you're running PhpWiki 1.3.x, and mod_php...) A couple of things to try: 1. In index.php, define USE_PATH_INFO to 'false'. (Just uncomment the sample line which is already there.) or 2. Also in index.php, define SERVER_NAME to the name (or ip address) of your server. If either fixes the problem, I think it means that apache is not setting the CGI environment variable $SERVER_NAME correctly... It might also be helpful to create a phpinfo script and check what value is being assigned to SERVER_NAME. (Create a file called, say, phpinfo.php, in your htdoc tree which contains one line: <?php phpinfo(); ?> When you browse the file, you'll see loads and loads of information regarding the configuration of your PHP (and Apache).) Jeff PS. This isn't in a virtual hosting environment is it? If so, then the problem is probably that you must access the server using a host name, not an IP number.... |
From: Tim B. <tim...@wc...> - 2002-01-17 15:52:00
|
All, My wiki can be accessed by my local machine on which it resides, but no other machines can get to it. It seems to be doing redirects to localhost, 127.0.0.1. I do not think this is being done by the OS (Linux RH 7.2) configuration or by the server, Apache (v 1.3.20-16). The reason for this belief is that I can pull up the default apache web page by going to my ip address on another machine, but when I add /phpwiki/index.php to the location I get an error message that says "localhost 127.0.0.1 not found." I believe I am missing a piece with regard to the index.php file. Any and all suggestions are most welcome. Tim B. |
From: Paul S. <pa...@et...> - 2002-01-17 04:26:54
|
Is anyone using phpwiki as a content management system, where a group of authorized people edit the site via the wiki interface, and then spit pages out static for a "public" web site? A non-profit group I volunteer with has been hunting for good/simple/free CMS software, and now that we're using phpwiki for an internal documentation system, I'm starting to wonder whether it might also be the answer to the CMS question (or maybe everything is starting to look like a nail). Would need to rip out all the wiki-interface bits when dumping (eg, Edit|PageHistory|Diff|etc.) and extract the content into some templates that define the "production" site format... Any thoughts on the subject would be appreciated. --Paul |
From: Reini U. <ru...@x-...> - 2002-01-16 23:25:35
|
Carsten Klapp schrieb: > I've modified the phpwiki CVS configuration to prevent any commit messages > for LC_MESSAGES from being echoed to the checkins list (they should still > appear in the server log though). Checkin messages for /locale/po/ files > should still show up on the list. > If there are any problems or concerns, or if you'd prefer to not have this > change, let me know. good. -- Reini Urban http://atelier.akbild.ac.at/ (soon) http://xarch.tu-graz.ac.at/home/rurban/ (big) http://tv.mur.at/ (kulturelles) |
From: Jeff D. <da...@da...> - 2002-01-16 21:14:06
|
Lawrence Akka said: > Anyone got the RSS feed from RecentChanges working on another site? I > have been trying today. I think it is probably the site's fault (how > could I doubt Jeff's code), but I was just wondering .... What sort of trouble are you having? If you have a working RecentChanges page, it should "just work". If it doesn't, it's probably the fault of Jeff's code.... |
From: Adam S. <ad...@pe...> - 2002-01-16 20:55:38
|
> Anyone got the RSS feed from RecentChanges working on another site? I > have been trying today. I think it is probably the site's fault (how could I doubt > Jeff's code), but I was just wondering .... not another site but it works fine in evolution's summary page. adam. |
From: Lawrence A. <Law...@th...> - 2002-01-16 20:39:04
|
Anyone got the RSS feed from RecentChanges working on another site? I have been trying today. I think it is probably the site's fault (how could I doubt Jeff's code), but I was just wondering .... Lawrence-------------------------------------------------------- Confidentiality Notice The information contained in this e-mail is confidential. It is for the use of the named recipient only. If you are not the named recipient, please destroy and do not disclose the contents of this e-mail to any other person, or copy it. Thank you for your co-operation. |
From: Carsten K. <car...@ma...> - 2002-01-16 02:36:55
|
There is a problem with base hrefs when virtual_path and data_path are different. As a quick fix I set the links to use a full url, it's probably not too difficult to fix but I just haven't made the time to look at it yet. For example look at the paths on the alpha server: data_path: http://phpwiki.sourceforge.net/alpha http://phpwiki.sourceforge.net/alpha/phpwiki.css etc. http://phpwiki.sourceforge.net/alpha/images/ http://phpwiki.sourceforge.net/alpha/theme/ virtual_path: http://phpwiki.sourceforge.net/alpha/en/ http://phpwiki.sourceforge.net/alpha/de/ http://phpwiki.sourceforge.net/alpha/macosx/ On Tuesday, January 15, 2002, at 08:49 pm, Jeff Dairiki wrote: > On 15 Jan 2002 17:10:05 -0800 > "Adam Shand" <ad...@pe...> wrote: > >> is there any reason that phpwiki shouldn't use relative links for >> everything? it saves a lot of trouble with things like this. > > It's a little problematic when (USE_PATH_INFO is on and) page names > contain '/'. But the asnwer is "no" there's no reason not to (at least > most of the time). We used to use relative URLs. (The PhpWiki wiki uses > relative URLs.) I'm not sure why we don't anymore. (??). > |
From: Jeff D. <da...@da...> - 2002-01-16 01:49:38
|
On 15 Jan 2002 17:10:05 -0800 "Adam Shand" <ad...@pe...> wrote: > is there any reason that phpwiki shouldn't use relative links for > everything? it saves a lot of trouble with things like this. It's a little problematic when (USE_PATH_INFO is on and) page names contain '/'. But the asnwer is "no" there's no reason not to (at least most of the time). We used to use relative URLs. (The PhpWiki wiki uses relative URLs.) I'm not sure why we don't anymore. (??). |