Menu
▾
▴
phpwiki-talk
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
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Bishop <bi...@pl...> - 2003-12-22 01:03:38
|
Steve said:
> This release contains lots of bugfixes and optimizations by Carsten.
But CVS (index.php) said:
> define ('PHPWIKI_VERSION', '1.3.7pre');
And I wondered:
Are ya teasing, Steve, or has cvs just not been committed?
My CVS RPM thingy only triggers on the SF cvs, and that file's not been
altered in 16 days.
- bish
|
|
From: Steve W. <sw...@pa...> - 2003-12-21 22:32:05
|
This release contains lots of bugfixes and optimizations by Carsten. I've been thinking about the 1.4 release, and I'd like to push the date back to January 25th, which will be PhpWiki's 4th birthday. I also have some time off after Christmas and New Year's that I want to devote to the project (primarly, making sure all install instructions are up to date, adding pages, etc). See http://phpwiki.org/ for the new release. Happy hollidays! ~swain |
|
From: Steve W. <sw...@pa...> - 2003-12-21 21:46:30
|
I see this at work when I "attach" an XML file to a page in Twiki. I don't think PHP is generating this error... perhaps it's the server or the browser? I'm usually using Safari at work. ~swain On Nov 24, 2003, at 2:24 PM, Stanislaw Berka wrote: > One of my PHPWiki's, displays a message "The XML page cannot be > displayed". If you do refresh, the page shows fine and from now on it > all works. The error is only the first time per session. Any ideas? > Stan Berka > > ----- The complete error message: > > The XML page cannot be displayed > Cannot view XML input using XSL style sheet. Please correct the error > and then click the Refresh button, or try again later. > > > ----------------------------------------------------------------------- > --------- > > Cannot have a DOCTYPE declaration outside of a prolog. Error > processing resource > 'http://www.saintclarechurch.org/phpwiki/index.php'. Line 4, Position > 11 > > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" > ----------^ > ----- end > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > |
|
From: Steve W. <sw...@pa...> - 2003-12-20 14:12:47
|
It's up as of this morning... I have seen so many Sourceforge-related outages over the last two and a half years that these never phase me anymore. :o) ~swain On Dec 1, 2003, at 3:17 PM, Russ Miller wrote: > I'm hoping someone is aware of this, but phpwiki.org > (http://phpwiki.sourceforge.net/phpwiki/) is down. Error: > > > > > phpwiki-wiki(1.3)/lib/WikiDB/backend/PearDB.php:31: Fatal[256]: Can't > connect to database: wikidb_backend_mysql: fatal database error > > * DB Error: connect failed > * ( [nativecode=Can't create a new thread (errno 11). If you are > not out of available memory, you can consult the manual for a possible > OS-dependent bug] ** mysql://phpwiki:XXXXXXXX@pr-db1/phpwiki) > * > > > Fatal error: Call to a member function on a non-object in > /home/groups/p/ph/phpwiki/htdocs/phpwiki-wiki(1.3)/lib/ > ErrorManager.php on line 191 > > > > > russ > |
|
From: Steve W. <sw...@pa...> - 2003-12-20 14:03:22
|
Time and again, I turn to the Red Bean book, free and online: http://cvsbook.red-bean.com/cvsbook.html It's a great combination of tutorial and cookbook. ~swain On Dec 17, 2003, at 3:55 PM, russ wrote: > I'm not actually a newbie, but I'm afeared this question is. > > I've been following and using PHPWiki for years; I spent a long time > hacking up 1.2.* for personal use. I'm eagerly awaiting 1.4 for a few > installations, and I'm sure some customization and tweaking will > follow. This time, however, I want to do it right. I want to be able > to upgrade as the product changes. I want to be able to isolate and > save my changes. I want the option of submitting my work back to the > project. > > However, I'm not 100% sure how to go about it. I looked into the inner > workings of diff and patch a bit months ago. Is that the place to > start? Does anyone have a pointer to a good reference for someone who > is not a necessarily a coding newbie but is a project newbie? How > about my own code? Should I use source control for that? Any other > best practices I should look into? > > Sorry if this is ramantly off-topic (can't be worse than the > administrivia reply-to thread :), but any pointers (reply-to just me > is fine, too :) would be much appreciated. > > russ > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for > IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys > admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > |
|
From: Bishop <bi...@pl...> - 2003-12-20 00:30:46
|
http://phpwiki.sourceforge.net/phpwiki/PrettyWiki Hey Folks, Last night was full of frustration. My goal was to get a virtualhost PrettyWiki'ed server going with the wiki as its default page, but I was completely unsuccessful before exhaustion claimed me about 0800. I'm hoping someone's done this exact thing: I want to have a centralized phpwiki installation (/var/www/html/phpwiki/ as per http://apt.platypus.bc.ca/~bishop/apt/RPMS.bish/phpwiki-1.3.7-0.20031219.05.rh9.i386.rpm) and use a index.php in the vhost documentroot to start the wiki. So, here's my setup so far: - RH9 + httpd, php, the usual http://apt.platypus.bc.ca/~bishop/apt/RPMS.bish/phpwiki-1.3.7-0.20031219.05.rh9.i386.rpm http://apt.platypus.bc.ca/~bishop/apt/i386/rh9/RPMS.bish/apache-incdirmod-1.4-5.20031208.14.rh9.noarch.rpm (that second one sets up dir-tree inclusion of the httpd.d dir) - /etc/httpd/conf/httpd.d/virtualhost.default.conf: NameVirtualHost *:80 <virtualhost _default_:80> </virtualhost> - /etc/httpd/conf/httpd.d/virtuals/wiki.platypus.bc.ca: (http://cvs.platypus.bc.ca/cgi-bin/viewcvs.cgi/*checkout*/bishop/virtualhosts/virtuals/wiki.platypus.bc.ca?rev=1.1) <VirtualHost *:80> ServerName www.wiki.platypus.bc.ca ServerAlias wiki.platypus.bc.ca ServerAlias www ServerAdmin web...@wi... DocumentRoot /home/wiki/wiki ErrorLog logs/wiki.platypus.bc.ca/error_log CustomLog logs/wiki.platypus.bc.ca/access_log combined UserDir disabled </VirtualHost> <Directory /home/wiki> Order Allow,Deny Allow from All Options +Indexes AllowOverride AuthConfig </Directory> <Directory /home/wiki/wiki> Options +Includes Options +ExecCGI AllowOverride FileInfo </Directory> now, when I hit the URL: /var/www/html/phpwiki/lib/Template.php:21: Warning[2]: fopen("", "rb") - No such file or directory /var/www/html/phpwiki/lib/Template.php:22: Warning[2]: stat failed for (errno=2 - No such file or directory) /var/www/html/phpwiki/lib/Template.php:22: Warning[2]: fread(): supplied argument is not a valid File-Handle resource /var/www/html/phpwiki/lib/Template.php:23: Warning[2]: fclose(): supplied argument is not a valid File-Handle resource /var/www/html/phpwiki/lib/Template.php:21: Warning[2]: fopen("", "rb") - No such file or directory /var/www/html/phpwiki/lib/Template.php:22: Warning[2]: stat failed for (errno=2 - No such file or directory) /var/www/html/phpwiki/lib/Template.php:22: Warning[2]: fread(): supplied argument is not a valid File-Handle resource /var/www/html/phpwiki/lib/Template.php:23: Warning[2]: fclose(): supplied argument is not a valid File-Handle resource /var/www/html/phpwiki/lib/Theme.php:195: Notice[1024]: templates/browse.tmpl: not found /var/www/html/phpwiki/lib/Theme.php:195: Notice[1024]: templates/html.tmpl: not found SO: What I'm thinking, right now, is that I'm not using this as per directions on the bottle. There may be a bug in the code, and indications are that it's near the theming bit, that make a centrally-loated phpwiki installation and vhost configs impossible. Anyone else successfully used a centrally installed phpwiki with replacement 'wiki' files located in other parts of the system? Yours in potential frustration, - bish |
|
From: Zot O'C. <zo...@wh...> - 2003-12-19 23:25:36
|
On Wed, 2003-12-17 at 07:26, Neal Lester wrote: > At 03:02 PM 12/17/2003 +0100, you wrote: > >Well, > > > >not the kind of message that mmakes you happy, I know... I have a > >phpwiki and php 4.3.3. on Apache2. > > > >A klick on "edit" crashes Apache. > > > >Anything known about this? > > I also have a problem where one page (it happens to be the longest page on > a Wiki running under Apache2) is scrambled. > > I reported it to this list previously here: > > http://sourceforge.net/mailarchive/message.php?msg_id=4377589 > That sounds like the digest mode issue. Look back for my posts for a quick tweak. > Neal > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk -- Zot O'Connor http://www.ZotConsulting.com http://www.WhiteKnightHackers.com |
|
From: Sergio T. <ser...@ho...> - 2003-12-19 15:19:05
|
In order for all I/O that moves through PHPWiki to be UTF-8 charset characters (instead of charset=iso-8859-1), is there anything that needs to be done specifically in the PHPWiki code to achieve this, or is it really just a matter of how one configures their Apache httpd server as well as the MySQL backend to PHPWiki? Thanks for any suggestions. Does anyone configure PHPWiki for strict UTF-8 I/O? Sergio _________________________________________________________________ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus |
|
From: Micki K. <mic...@co...> - 2003-12-19 00:01:55
|
Hi Carsten! I'm on phpwiki 1.3.4 (prepping for 1.3.7), with Apache 1.3.27, and php 4.3.0 Thanks, and it's good to hear that the crash is less extreme on newer builds - thanks! Micki At 6:19 PM -0500 12/18/03, Carsten Klapp wrote: >On Thursday, December 18, 2003, at 05:17 pm, Micki Kaufman wrote: > >>Hi folks. >> >>I've got a page with the following line indelicately pasted in by a user: >> >> [ATTENTION :As per the first list above many cases did NOT work. I >>do not know if this is due to the exclude, prefs or both] >> >>it seems that since the user was making use of a colon inside >>square brackets, and without a properly formatted (in this case, >>no) URL, it crashed with a fatal db error. Of course, 300 seconds >>later it's back in business, as set by the connections default in >>php. >> >>Can our esteemed gurus verify this bug, and possibly trap it? >> >>Thanks, >>Micki > > >Hi Micki, > >I tried this out in the SandBox both with new markup and old, on the >PhpWiki server (phpwiki.sf.net/phpwiki) which is running 1.3.7pre. > >There it gives only a PHP Warning message at the bottom of the page. >It's not an ideal response from parsing that particular line but at >least there is no crash. > >What version of PhpWiki, PHP, and Apache (or other http server) are you using? > >Carsten -- Micki mailto:mic...@co... |
|
From: Carsten K. <car...@us...> - 2003-12-18 23:20:26
|
On Thursday, December 18, 2003, at 05:17 pm, Micki Kaufman wrote: > Hi folks. > > I've got a page with the following line indelicately pasted in by a > user: > > [ATTENTION :As per the first list above many cases did NOT work. I do > not know if this is due to the exclude, prefs or both] > > it seems that since the user was making use of a colon inside square > brackets, and without a properly formatted (in this case, no) URL, it > crashed with a fatal db error. Of course, 300 seconds later it's back > in business, as set by the connections default in php. > > Can our esteemed gurus verify this bug, and possibly trap it? > > Thanks, > Micki Hi Micki, I tried this out in the SandBox both with new markup and old, on the PhpWiki server (phpwiki.sf.net/phpwiki) which is running 1.3.7pre. There it gives only a PHP Warning message at the bottom of the page. It's not an ideal response from parsing that particular line but at least there is no crash. What version of PhpWiki, PHP, and Apache (or other http server) are you using? Carsten |
|
From: Micki K. <mic...@co...> - 2003-12-18 23:03:33
|
Hi folks. I've got a page with the following line indelicately pasted in by a user: [ATTENTION :As per the first list above many cases did NOT work. I do not know if this is due to the exclude, prefs or both] it seems that since the user was making use of a colon inside square brackets, and without a properly formatted (in this case, no) URL, it crashed with a fatal db error. Of course, 300 seconds later it's back in business, as set by the connections default in php. Can our esteemed gurus verify this bug, and possibly trap it? Thanks, Micki -- Micki mailto:mic...@co... |
|
From: Norberto M. <nu...@me...> - 2003-12-18 12:32:18
|
Hi Peter et al, [quickly moving the off topic discussion somewhere else]... http://www.cvshome.org is the home of CVS. Please refer to the extensive documentation found there. Cheers, Beto Peter wrote: >Hi, > >please one cvs-question that I never got answered anywhere: > >HOW can i see which modules do exist on a cvs-server after login? > >Is there something like "cvs list modules" > >i did not find anything about that... > >sorry for ot, but i take the chance to jump on that >basic-project-info-thread... > >Thanks for your attention! > >Peter > > >------------------------------------------------------- >This SF.net email is sponsored by: IBM Linux Tutorials. >Become an expert in LINUX or just sharpen your skills. Sign up for IBM's >Free Linux Tutorials. Learn everything from the bash shell to sys admin. >Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click >_______________________________________________ >Phpwiki-talk mailing list >Php...@li... >https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > > > -- Norberto Meijome | numard at meijome dot net "Everything is interesting if you go into it deeply enough." - Richard Feynman |
|
From: Peter <li...@gm...> - 2003-12-18 12:08:03
|
Hi, please one cvs-question that I never got answered anywhere:=20 HOW can i see which modules do exist on a cvs-server after login?=20 Is there something like "cvs list modules" i did not find anything about that... sorry for ot, but i take the chance to jump on that basic-project-info-thread... Thanks for your attention! Peter |
|
From: Arnaud F. <ar...@cr...> - 2003-12-18 07:41:20
|
Right, Templates would be the best. But you can do something more ...
wiki driven :)
Le mer 17/12/2003 =E0 21:16, Carsten Klapp a =E9crit :
> Yes templates would be the best approach. Add a line into=20
> phpwiki/themes/default/templates/top.tmpl to call your menu template:
[...]
> <?php // -*-html-*-
> $s =3D $Theme->getButtonSeparator();
> ?>
> <!-- The menu bar -->
> <?=3D WikiLink(_("RecentEdits"), "button") ?>
> <?=3D$s?><?=3D WikiLink(_("MyPage"), "button") ?>
> <?=3D$s?><?=3D WikiLink(_("AnotherPage"), "button") ?>
> <!-- End menu bar -->
Here, just define the "hard links" to some pages like the RecenChanges,
FindPage, etc.
And add a line like this one to your template :
<?plugin IncludePage page=3D"Menu" quiet=3D1?>
Then, create a wiki page named Menu where you'll just write the
Wikiwords and links you want to have in your menu.
Then you're free to lock the Menu page or not ....
I use this trick to add a "News" box on my wikis. News are taken from
the "!News" section of a wiki page.
--=20
Arnaud Fontaine
Jabber: sh...@ra...
ICQ: 3504789
|
|
From: Carsten K. <car...@us...> - 2003-12-18 00:38:31
|
On Wednesday, December 17, 2003, at 09:02 am, Peter wrote: > Well, > > not the kind of message that mmakes you happy, I know... I have a > phpwiki and php 4.3.3. on Apache2. > > A klick on "edit" crashes Apache. > > Anything known about this? Hallo Peter, This sounds just like the same as the problem with PHP 4.3.x (with Apache 1.x) under Mac OS X, where the httpd server daemon crashes whenever you edit a page or are even just browsing/viewing the OldTextFormattingRules page. (Possibly also when viewing or editing some other page which contains certain old markup rules; exactly which old markup causes the bug to surface we don't yet know). There is some discussion and a few workarounds here in [PhpWiki:KnownBugs] at: http://phpwiki.sourceforge.net/phpwiki/KnownBugs ...under the heading: "EDIT will not work after upgrading to PHP 4.3.0" Let us know whether those workarounds are successful for you (i.e. That is the same problem-bug as you have) or if this might be some other problem. Unfortunately a fix for this bug is still not in sight, but at least we know how to work past it now. Cheers, Carsten |
|
From: Reini U. <ru...@x-...> - 2003-12-18 00:05:31
|
method 1: # remark: always diff old to new # but you want your changes from 1.2 back into cvs...: diff -rbu phpwiki-cvs phpwiki-1.2 > phpwiki-1.2.patch # now you can apply the patches blindly cd phpwiki-cvs; patch -p1 < phpwiki-1.2.patch method 2: or better check the patch file in a editor which can do diff's, such as XEmacs or emacs: C-x 2 M-x ediff-buffers split the window, load the patch and file-wise both files. and see what's different. you can also apply the diff's, but manually. that's preferred ,but needs more time. russ schrieb: > I'm not actually a newbie, but I'm afeared this question is. > > I've been following and using PHPWiki for years; I spent a long time > hacking up 1.2.* for personal use. I'm eagerly awaiting 1.4 for a few > installations, and I'm sure some customization and tweaking will follow. > This time, however, I want to do it right. I want to be able to upgrade > as the product changes. I want to be able to isolate and save my > changes. I want the option of submitting my work back to the project. > > However, I'm not 100% sure how to go about it. I looked into the inner > workings of diff and patch a bit months ago. Is that the place to start? > Does anyone have a pointer to a good reference for someone who is not a > necessarily a coding newbie but is a project newbie? How about my own > code? Should I use source control for that? Any other best practices I > should look into? > > Sorry if this is ramantly off-topic (can't be worse than the > administrivia reply-to thread :), but any pointers (reply-to just me is > fine, too :) would be much appreciated. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |
|
From: Joby W. <joby@u.washington.edu> - 2003-12-17 22:36:43
|
The Sourceforge documents are pretty good, and an easy read. The Cederqvist (CVS Offical Manual) is a bit dense but very informative for an end user. http://www.cvshome.org/docs/manual/cvs-1.11.10/cvs.html jbw Carsten Klapp wrote: > > On Wednesday, December 17, 2003, at 03:55 pm, russ wrote: > >> I'm not actually a newbie, but I'm afeared this question is. >> >> I've been following and using PHPWiki for years; I spent a long time >> hacking up 1.2.* for personal use. I'm eagerly awaiting 1.4 for a few >> installations, and I'm sure some customization and tweaking will >> follow. This time, however, I want to do it right. I want to be able >> to upgrade as the product changes. I want to be able to isolate and >> save my changes. I want the option of submitting my work back to the >> project. >> >> However, I'm not 100% sure how to go about it. I looked into the inner >> workings of diff and patch a bit months ago. Is that the place to >> start? Does anyone have a pointer to a good reference for someone who >> is not a necessarily a coding newbie but is a project newbie? How >> about my own code? Should I use source control for that? Any other >> best practices I should look into? >> >> Sorry if this is ramantly off-topic (can't be worse than the >> administrivia reply-to thread :), but any pointers (reply-to just me >> is fine, too :) would be much appreciated. >> >> russ > > > Hi Russ, > > I think the best way to keep your PhpWikis absolutely up-to-date is > through CVS. > > Learning diff and patch is a very good place to start. Next, learn the > basics of CVS: how to check out a project, how to do diffs with CVS, how > to update files to the latest revisions from the server, and how to > resolve conflicts between modifications of your personal copy with > similar changes newly added to the copy on the server. (Hopefully > conflicts don't happen too often but they are usually pretty easy to fix > with a text editor). > > Even when you make modifications to your local files, CVS can keep your > files up-to-date by automatically merging your own changes with any > changes in the code published/checked in at the SF server, using > built-in diff and patch functions. If there is a conflict between your > mods and a new change on the server, cvs will tell you where the > conflict is. > > Say you don't always want to run "cvs -q up" etc. every day to keep your > PhpWiki code *absolutely* current, that's fine too (and probably a good > idea on a production PhpWiki). In that case CVS is still handy for doing > things like: "cvs diff index.php". Then cvs will display a patch which > shows how your copy of that file differs from that particular revision > of the same file on the SF server. > > Sourceforge has some O.K. docs about how to use CVS. It's been a while > since I first learned CVS, does anyone have a link to a good CVS getting > started tutorial? > > Carsten > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk |
|
From: Carsten K. <car...@us...> - 2003-12-17 21:46:15
|
On Wednesday, December 17, 2003, at 03:55 pm, russ wrote: > I'm not actually a newbie, but I'm afeared this question is. > > I've been following and using PHPWiki for years; I spent a long time > hacking up 1.2.* for personal use. I'm eagerly awaiting 1.4 for a few > installations, and I'm sure some customization and tweaking will > follow. This time, however, I want to do it right. I want to be able > to upgrade as the product changes. I want to be able to isolate and > save my changes. I want the option of submitting my work back to the > project. > > However, I'm not 100% sure how to go about it. I looked into the inner > workings of diff and patch a bit months ago. Is that the place to > start? Does anyone have a pointer to a good reference for someone who > is not a necessarily a coding newbie but is a project newbie? How > about my own code? Should I use source control for that? Any other > best practices I should look into? > > Sorry if this is ramantly off-topic (can't be worse than the > administrivia reply-to thread :), but any pointers (reply-to just me > is fine, too :) would be much appreciated. > > russ Hi Russ, I think the best way to keep your PhpWikis absolutely up-to-date is through CVS. Learning diff and patch is a very good place to start. Next, learn the basics of CVS: how to check out a project, how to do diffs with CVS, how to update files to the latest revisions from the server, and how to resolve conflicts between modifications of your personal copy with similar changes newly added to the copy on the server. (Hopefully conflicts don't happen too often but they are usually pretty easy to fix with a text editor). Even when you make modifications to your local files, CVS can keep your files up-to-date by automatically merging your own changes with any changes in the code published/checked in at the SF server, using built-in diff and patch functions. If there is a conflict between your mods and a new change on the server, cvs will tell you where the conflict is. Say you don't always want to run "cvs -q up" etc. every day to keep your PhpWiki code *absolutely* current, that's fine too (and probably a good idea on a production PhpWiki). In that case CVS is still handy for doing things like: "cvs diff index.php". Then cvs will display a patch which shows how your copy of that file differs from that particular revision of the same file on the SF server. Sourceforge has some O.K. docs about how to use CVS. It's been a while since I first learned CVS, does anyone have a link to a good CVS getting started tutorial? Carsten |
|
From: russ <rl...@rl...> - 2003-12-17 20:55:55
|
I'm not actually a newbie, but I'm afeared this question is. I've been following and using PHPWiki for years; I spent a long time hacking up 1.2.* for personal use. I'm eagerly awaiting 1.4 for a few installations, and I'm sure some customization and tweaking will follow. This time, however, I want to do it right. I want to be able to upgrade as the product changes. I want to be able to isolate and save my changes. I want the option of submitting my work back to the project. However, I'm not 100% sure how to go about it. I looked into the inner workings of diff and patch a bit months ago. Is that the place to start? Does anyone have a pointer to a good reference for someone who is not a necessarily a coding newbie but is a project newbie? How about my own code? Should I use source control for that? Any other best practices I should look into? Sorry if this is ramantly off-topic (can't be worse than the administrivia reply-to thread :), but any pointers (reply-to just me is fine, too :) would be much appreciated. russ |
|
From: Carsten K. <car...@us...> - 2003-12-17 20:16:48
|
Peter wrote:
> Hi,
>
> I would like to have a set of special pages on top of all pages. I do
> it with copying that "header" to all wiki pages. Obviously this is not
> very good, because if I want to change that "menu", I must touch every
> single page I used it...
>
> Is there a better way to get some kind of include("menu") on every
> wikipage??? The menu-pages are wikipages themselves.
>
>
> Thank you very much for your attention!
On Wednesday, December 17, 2003, at 09:29 am, Norberto Meijome wrote:
> Hi Peter,
> why not use templates? start off the default template and edit @ will.
>
> making the menu part of the content of each wiki page is definitely
> the wrong way to go about it.
>
> maybe there is a 'menu' plugin that can create this on parsing? or
> maybe an include plugin (not sure, haven't reviewed all the plugins
> available yet
>
> Beto
Yes templates would be the best approach. Add a line into
phpwiki/themes/default/templates/top.tmpl to call your menu template:
diff -U2 -r1.25 top.tmpl
--- top.tmpl 5 Mar 2003 21:38:15 -0000 1.25
+++ top.tmpl 17 Dec 2003 20:09:13 -0000
@@ -14,4 +14,5 @@
<!-- The top navigation/search bar -->
<div class="toolbar"><?= Template('navbar') ?></div>
+<div class="toolbar"><?= Template('menu') ?></div>
<?php } ?>
Then create a new file menu.tmpl, put your html and php in there,
something like this:
<?php // -*-html-*-
$s = $Theme->getButtonSeparator();
?>
<!-- The menu bar -->
<?= WikiLink(_("RecentEdits"), "button") ?>
<?=$s?><?= WikiLink(_("MyPage"), "button") ?>
<?=$s?><?= WikiLink(_("AnotherPage"), "button") ?>
<!-- End menu bar -->
Carsten
|
|
From: Neal L. <nea...@br...> - 2003-12-17 15:27:44
|
At 03:02 PM 12/17/2003 +0100, you wrote: >Well, > >not the kind of message that mmakes you happy, I know... I have a >phpwiki and php 4.3.3. on Apache2. > >A klick on "edit" crashes Apache. > >Anything known about this? I also have a problem where one page (it happens to be the longest page on a Wiki running under Apache2) is scrambled. I reported it to this list previously here: http://sourceforge.net/mailarchive/message.php?msg_id=4377589 Neal |
|
From: Norberto M. <nu...@me...> - 2003-12-17 14:29:41
|
Hi Peter,
why not use templates? start off the default template and edit @ will.
making the menu part of the content of each wiki page is definitely the
wrong way to go about it.
maybe there is a 'menu' plugin that can create this on parsing? or maybe
an include plugin (not sure, haven't reviewed all the plugins available yet
Beto
Peter wrote:
>Hi,
>
>I would like to have a set of special pages on top of all pages. I do
>it with copying that "header" to all wiki pages. Obviously this is not
>very good, because if I want to change that "menu", I must touch every
>single page I used it...
>
>Is there a better way to get some kind of include("menu") on every
>wikipage??? The menu-pages are wikipages themselves.
>
>
>Thank you very much for your attention!
>
>
>
>
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: IBM Linux Tutorials.
>Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
>Free Linux Tutorials. Learn everything from the bash shell to sys admin.
>Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click
>_______________________________________________
>Phpwiki-talk mailing list
>Php...@li...
>https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>
>
>
--
Norberto Meijome | numard at meijome dot net
"Everything is interesting if you go into it deeply enough." - Richard Feynman
|
|
From: <jw...@fi...> - 2003-12-17 14:11:30
|
Hello again, Here are the patches for the "copypage" functionnality - The modification in editpage.php catches the copypage argument and = forces this page to be chosen as the basis for edition - The modification in Calendar adds the "copypage" argument to the = plugin. This way, when a user clicks on a date, the "empty" wiki page that is = opened contains the same content as the copypage Page e.g. <?plugin Calendar copypage=3DMyChosenExistingTemplatePage?> I hope the patches have been made at the best places in the phpwiki = code, and that you will be able to tweak them into the project code base. Keep me posted! J=E9r=F4me -----Message d'origine----- De=A0: Reini Urban [mailto:ru...@x-...]=20 Envoy=E9=A0: mercredi 17 d=E9cembre 2003 13:30 =C0=A0: J=E9r=F4me WAGNER Cc=A0: php...@li... Objet=A0: Re: [Phpwiki-talk] copypage functionnality please attach your patch to an email or post it at sf.net. we will review it and add it to the current CVS. very good idea indeed! J=E9r=F4me WAGNER schrieb: > I added a small patch to the sources in order to have a "copypage" > functionality : >=20 > When doing an action=3DEdit©page=3DMyPage, >=20 > The resulting textarea is prefilled with the content of MyPage >=20 > This allows, via a patched Calendar plugin for example, to have a = single > prefilled template every time you want to add an entry in the = calendar. >=20 > I'd like to know if there already is such a functionality in the wiki, = if it > interests anyone, and how we could to do add such a thing in the code base. --=20 Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |
|
From: Peter <li...@gm...> - 2003-12-17 13:59:58
|
Well, not the kind of message that mmakes you happy, I know... I have a phpwiki and php 4.3.3. on Apache2. A klick on "edit" crashes Apache.=20 Anything known about this? |
|
From: Peter <li...@gm...> - 2003-12-17 13:53:28
|
Hi,
I would like to have a set of special pages on top of all pages. I do
it with copying that "header" to all wiki pages. Obviously this is not
very good, because if I want to change that "menu", I must touch every
single page I used it...
Is there a better way to get some kind of include("menu") on every
wikipage??? The menu-pages are wikipages themselves.
Thank you very much for your attention!
|
207 messages has been excluded from this view by a project administrator.
