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: Reini U. <ru...@x-...> - 2006-08-14 22:42:18
|
Mici Maci schrieb: > I tried to set the CHARSET in the config.ini to > 1) utf-8 > 2) iso-8859-2 > The 1) gone wrong because of a failed sql select. > [There's a mysql in the background.] the sql query > string should not contain utf encoded characters. of course you have to tell your database to accept utf-8. ALTER TABLE page DEFAULT CHARACTER SET utf8_general_ci; ALTER TABLE version DEFAULT CHARACTER SET utf8_general_ci; ALTER TABLE session DEFAULT CHARACTER SET utf8_general_ci; what we just do is telling the client talking to the database which charset we use for the transport. config.ini: CHARSET=UTF-8 => PearDB_mysql.php: SET NAMES 'utf8'; http://dev.mysql.com/doc/refman/5.0/en/charset-connection.html > The number 2) was wrong because htmlspecialchars... So I > wrote a htmlspecialchars_workaround() function, that > checks the third argument (which is the requested charset), > and if it's 8859-2, it makes a few simple string replacement. > [<, > and & is enough to replace to "<", ">" and > "&"...] > It calls the original htmlspecialchars in other cases. > Now I can use iso-8859-2 in the config.ini, and Wiki > seems to work. Of course I have had to append > _workaround to all occurances os htmlspecialchars > in the original code. Brrrr! Ugly and impossible to > maintenance but maybe works... It's under testing > now. 8-) Well, why not. "_workaround" might be a bit too long though. > Why don't use PhpWiki developers their own html > escaper function?? htmlspecialchars() has more > disadvatages than advantages, because it keeps > the usable character set small, so excludes lots > of people from lots of nations to join the project... because you are the first with such an exotic eastern charset (czech and polish also) which is not supported by such a basic function. that tells us, that we seriously lack a lot of users. of course we accept any workaround function. > Reini Urban <ru...@x-...> írta: > >> Reini Urban schrieb: >>> Mici Maci schrieb: >>>> thanks for your answer but it's not so easy. PhpWiki >>>> uses htmlspecialchars() to masq strings, and PhpWiki >>>> passes a third argument to it containing the charset >>>> name. htmlspecialchars() does not know about latin2, >>>> it gives warnings. >>>> >>>> lib/XmlElement.php...: 502: Warning: htmlspecialchars(): >>>> charset `iso-8859-2' not supported, assuming iso-8859-1 >>>> >>>> lib/XmlElement.php...: 170: Warning: htmlspecialchars(): >>>> charset `iso-8859-2' not supported, assuming iso-8859-1 >>>> >>>> These two lines (502 and 170) are giving the message >>>> but lots of times in a page request. What's wrong? May >>>> I upgrade or reconfigure php to work, or the >>>> htmlspecialchars() function needs a workaround in >>>> PhpWiki? >>>> >>>> [phpwiki-1.3.12p3] >>>> [php-4.4.2-1.1] >>> Oje! >>> http://www.mantisbt.org/mantis/bug_view_page.php?bug_id=6624 >>> >>> So you have to convert to UTF-8 and bite into the bullet. >>> Note, that UTF-8 is not officially supported and not > included. >>> I posted a patch to the sf.net patch area, which should > get around most >>> issues. But since UTF-8 strings are asciiz-safe it is > not so harmful to >>> work without proper UTF-8 support in all string > functions. (preg_match, >>> strlen, ...) >> BTW: If you do have mbstring loaded in your php it's very > easy. >> Simply set >> mb_internal_encoding('UTF-8'); >> somewhere ("lib/config.ini") and set >> >> mbstring.func_overload in the php.ini or .htaccess to 7 >> >> .htaccess: >> php_value mbstring.func_overload 7 >> >> The hugepatch comes from the fact, that not all servers > support mbstring >> and strlen's are different in UTF-8 land. >> We do support now, input from UTF-8 land (e.g. MS IE), but > convert this >> input to our charset. -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ |
From: Mici M. <mm...@fr...> - 2006-08-14 16:56:46
|
Hi, I tried to set the CHARSET in the config.ini to 1) utf-8=20 2) iso-8859-2 The 1) gone wrong because of a failed sql select. [There's a mysql in the background.] the sql query string should not contain utf encoded characters. The number 2) was wrong because htmlspecialchars... So I wrote a htmlspecialchars_workaround() function, that checks the third argument (which is the requested charset), and if it's 8859-2, it makes a few simple string replacement. [<, > and & is enough to replace to "<", ">" and "&"...] It calls the original htmlspecialchars in other cases. Now I can use iso-8859-2 in the config.ini, and Wiki seems to work. Of course I have had to append _workaround to all occurances os htmlspecialchars in the original code. Brrrr! Ugly and impossible to maintenance but maybe works... It's under testing now. 8-) Why don't use PhpWiki developers their own html escaper function?? htmlspecialchars() has more disadvatages than advantages, because it keeps the usable character set small, so excludes lots of people from lots of nations to join the project... mm. Reini Urban <ru...@x-...> =EDrta: > Reini Urban schrieb: > > Mici Maci schrieb: > >> thanks for your answer but it's not so easy. PhpWiki > >> uses htmlspecialchars() to masq strings, and PhpWiki > >> passes a third argument to it containing the charset > >> name. htmlspecialchars() does not know about latin2, > >> it gives warnings. > >> > >> lib/XmlElement.php...: 502: Warning: htmlspecialchars(): > >> charset `iso-8859-2' not supported, assuming iso-8859-1 > >> > >> lib/XmlElement.php...: 170: Warning: htmlspecialchars(): > >> charset `iso-8859-2' not supported, assuming iso-8859-1 > >> > >> These two lines (502 and 170) are giving the message > >> but lots of times in a page request. What's wrong? May > >> I upgrade or reconfigure php to work, or the > >> htmlspecialchars() function needs a workaround in > >> PhpWiki? > >> > >> [phpwiki-1.3.12p3] > >> [php-4.4.2-1.1] > >=20 > > Oje! > > http://www.mantisbt.org/mantis/bug_view_page.php?bug_id=3D6624 > >=20 > > So you have to convert to UTF-8 and bite into the bullet. > > Note, that UTF-8 is not officially supported and not included. > >=20 > > I posted a patch to the sf.net patch area, which should get around most=20 > > issues. But since UTF-8 strings are asciiz-safe it is not so harmful to=20 > > work without proper UTF-8 support in all string functions. (preg_match,=20 > > strlen, ...) >=20 > BTW: If you do have mbstring loaded in your php it's very easy. > Simply set > mb_internal_encoding('UTF-8'); > somewhere ("lib/config.ini") and set >=20 > mbstring.func_overload in the php.ini or .htaccess to 7 >=20 > .htaccess: > php_value mbstring.func_overload 7 >=20 > The hugepatch comes from the fact, that not all servers support mbstring=20 > and strlen's are different in UTF-8 land. > We do support now, input from UTF-8 land (e.g. MS IE), but convert this=20 > input to our charset. > --=20 > Reini Urban > http://phpwiki.org/ http://murbreak.at/ > http://helsinki.at/ http://spacemovie.mur.at/ >=20 > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D1= 21642 > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > =0A=0A________________________________________________________________ Iratkozzon fel szakmai h=EDrlevel=FCnkre =E9s nyerje meg =D6n a 3 db k=E9ny= eztet=F5 wellness h=E9tv=E9ge egyik=E9t! kattintson ide: http://www.dashofer.hu/origo/?wa=3DCEMORI0632 |
From: Reini U. <ru...@x-...> - 2006-08-14 11:25:05
|
ecocode schrieb: > * Reini Urban <ru...@x-...> wrote: > | Ok, > | so try installing the latest pear DB library and put the pear library > | path in front of INCLUDE_PATH in config.ini. This will override our version. > | AUTH_USER_FILE_STORABLE will not work though. > > Done that, > > but still have the same error :-/ > the error seems to be _in_ pear DB Please report this upstream at the pear folks. I'd like to have that fixed also. -- Reini Urban |
From: Reini U. <ru...@x-...> - 2006-08-14 11:23:53
|
Reini Urban schrieb: > Mici Maci schrieb: >> thanks for your answer but it's not so easy. PhpWiki >> uses htmlspecialchars() to masq strings, and PhpWiki >> passes a third argument to it containing the charset >> name. htmlspecialchars() does not know about latin2, >> it gives warnings. >> >> lib/XmlElement.php...: 502: Warning: htmlspecialchars(): >> charset `iso-8859-2' not supported, assuming iso-8859-1 >> >> lib/XmlElement.php...: 170: Warning: htmlspecialchars(): >> charset `iso-8859-2' not supported, assuming iso-8859-1 >> >> These two lines (502 and 170) are giving the message >> but lots of times in a page request. What's wrong? May >> I upgrade or reconfigure php to work, or the >> htmlspecialchars() function needs a workaround in >> PhpWiki? >> >> [phpwiki-1.3.12p3] >> [php-4.4.2-1.1] > > Oje! > http://www.mantisbt.org/mantis/bug_view_page.php?bug_id=6624 > > So you have to convert to UTF-8 and bite into the bullet. > Note, that UTF-8 is not officially supported and not included. > > I posted a patch to the sf.net patch area, which should get around most > issues. But since UTF-8 strings are asciiz-safe it is not so harmful to > work without proper UTF-8 support in all string functions. (preg_match, > strlen, ...) BTW: If you do have mbstring loaded in your php it's very easy. Simply set mb_internal_encoding('UTF-8'); somewhere ("lib/config.ini") and set mbstring.func_overload in the php.ini or .htaccess to 7 .htaccess: php_value mbstring.func_overload 7 The hugepatch comes from the fact, that not all servers support mbstring and strlen's are different in UTF-8 land. We do support now, input from UTF-8 land (e.g. MS IE), but convert this input to our charset. -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ |
From: Reini U. <ru...@x-...> - 2006-08-14 11:13:33
|
Mici Maci schrieb: > thanks for your answer but it's not so easy. PhpWiki > uses htmlspecialchars() to masq strings, and PhpWiki > passes a third argument to it containing the charset > name. htmlspecialchars() does not know about latin2, > it gives warnings. > > lib/XmlElement.php...: 502: Warning: htmlspecialchars(): > charset `iso-8859-2' not supported, assuming iso-8859-1 > > lib/XmlElement.php...: 170: Warning: htmlspecialchars(): > charset `iso-8859-2' not supported, assuming iso-8859-1 > > These two lines (502 and 170) are giving the message > but lots of times in a page request. What's wrong? May > I upgrade or reconfigure php to work, or the > htmlspecialchars() function needs a workaround in > PhpWiki? > > [phpwiki-1.3.12p3] > [php-4.4.2-1.1] Oje! http://www.mantisbt.org/mantis/bug_view_page.php?bug_id=6624 So you have to convert to UTF-8 and bite into the bullet. Note, that UTF-8 is not officially supported and not included. I posted a patch to the sf.net patch area, which should get around most issues. But since UTF-8 strings are asciiz-safe it is not so harmful to work without proper UTF-8 support in all string functions. (preg_match, strlen, ...) -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ |
From: ecocode <ec...@ec...> - 2006-08-14 08:23:22
|
* Reini Urban <ru...@x-...> wrote: | | Ok, | so try installing the latest pear DB library and put the pear library | path in front of INCLUDE_PATH in config.ini. This will override our version. | AUTH_USER_FILE_STORABLE will not work though. Done that, but still have the same error :-/ the error seems to be _in_ pear DB -- Eco http://www.ecocode.net * Life is wonderful with Emacs and Perl * |
From: Mici M. <mm...@fr...> - 2006-08-14 06:28:04
|
Hi, thanks for your answer but it's not so easy. PhpWiki uses htmlspecialchars() to masq strings, and PhpWiki passes a third argument to it containing the charset name. htmlspecialchars() does not know about latin2, it gives warnings. lib/XmlElement.php...: 502: Warning: htmlspecialchars(): charset `iso-8859-2' not supported, assuming iso-8859-1 lib/XmlElement.php...: 170: Warning: htmlspecialchars(): charset `iso-8859-2' not supported, assuming iso-8859-1 These two lines (502 and 170) are giving the message but lots of times in a page request. What's wrong? May I upgrade or reconfigure php to work, or the htmlspecialchars() function needs a workaround in PhpWiki? [phpwiki-1.3.12p3] [php-4.4.2-1.1] --=20 mm. Reini Urban <ru...@x-...> =EDrta: > [redirected to the mailing list, I hate the tracker] >=20 > SourceForge.net schrieb: > > Read and respond to this message at:=20 > > https://sourceforge.net/forum/message.php?msg_id=3D3865587 > > By: mmaci > >=20 > > Hi, > >=20 > > I'm interested in making a hungarian site driven by PhpWiki. But there's a > > probleme: our national charset contains two additional characters to iso-8859-1, > > "o and "u (the long versions of =F6 and =FC), that is only found in iso-8859-2. > > These chars are frequent in hungarian, and it's impossible to leave them or > > interchange them with latin1 chars. It would real ugly. The other thing is > > that I have to use these characters in WikiNames, but current version of PhpWiki > > does not support it. Xxx=F3=E1Yyy is ready (latin1 chars are usable), but if I > > change =F3=E1 to "o, it fails, and square brackets does not help. The [] creates > > a link, but "o and "u is viewd as & #337 ; and & #369 ; . Could You please > > help me how to solve the probleme? Is it a big work to add latin2 support into > > PhpWiki? >=20 > Normally it should work out of the box when you > define('CHARSET', 'iso-8859-2'); > (or define it in the config.ini) > and your php supports it (via iconv) in the pcre functions. > mbstring should not be needed afaik. latin-2 is single-byte. >=20 > > I promise I'll gift the project with a hu.po file if iso-8859-2 will be ok... > > Now there's nothing to it. >=20 > Personally I'd rather prefer a cool layout in a new template, but we=20 > accept hungarian also :) > --=20 > Reini Urban > http://phpwiki.org/ http://murbreak.at/ > http://helsinki.at/ http://spacemovie.mur.at/ > =0A=0A______________________________________________ Dobd fel a napod, dobd fel a vide=F3id! http://videa.hu |
From: Robert B. <rob...@gm...> - 2006-08-14 04:15:55
|
Good question. Since the host is Linux, it would appear to be gdbm. b On Aug 13, 2006, at 4:00 PM, Reini Urban wrote: > SourceForge.net schrieb: >> By: elkhornbob >> I've searched the forum for anything on this, but found nothing. >> I'm getting messages from PHP like the one below when making edit >> changes to >> a page. Any advice on what I need to do to stop this? (The edits >> are being >> saved ok, strangely.) >> Warning: dba_insert(FrontPage,a:3:{s:9:"fromlinks";a:5:{s: >> 21:"PhpWikiAdministrat >> ion";i:1;s:12:"ReleaseNotes";i:1;s:8:"TestPage";i:1;s: >> 19:"TextFormattingRules";i >> :1;s:13:"RecentChanges";i:1;}s:7:"tolinks";a:10:{s: >> 11:"WikiWikiWeb";i:1;s:12:"Ho >> wToUseWiki";i:1;s:11:"AddingPages";i:1;s:7:"SandBox";i:1;s: >> 14:"RecentVisitors";i >> :1;s:13:"RecentChanges";i:1;s:11:"MostPopular";i:1;s: >> 12:"ReleaseNotes";i:1;s:21: >> "PhpWikiAdministration";i:1;s:9:"WeavaTeam";i:1;}s:8:"pagename";s: >> 9:"FrontPage";} >> ) [function.dba-insert]: Cannot replace in >> /www/nwfish.info/subdomains/www/phpwiki/lib/dbalib.php on line 126 > > The page content is saved, but the link updates not. > This is a backend problem with dba. Which backend do you use? > berkeley or gdbm? |
From: Reini U. <ru...@x-...> - 2006-08-13 22:59:22
|
SourceForge.net schrieb: > By: elkhornbob > > I've searched the forum for anything on this, but found nothing. > > > I'm getting messages from PHP like the one below when making edit changes to > a page. Any advice on what I need to do to stop this? (The edits are being > saved ok, strangely.) > > Warning: dba_insert(FrontPage,a:3:{s:9:"fromlinks";a:5:{s:21:"PhpWikiAdministrat > ion";i:1;s:12:"ReleaseNotes";i:1;s:8:"TestPage";i:1;s:19:"TextFormattingRules";i > :1;s:13:"RecentChanges";i:1;}s:7:"tolinks";a:10:{s:11:"WikiWikiWeb";i:1;s:12:"Ho > wToUseWiki";i:1;s:11:"AddingPages";i:1;s:7:"SandBox";i:1;s:14:"RecentVisitors";i > :1;s:13:"RecentChanges";i:1;s:11:"MostPopular";i:1;s:12:"ReleaseNotes";i:1;s:21: > "PhpWikiAdministration";i:1;s:9:"WeavaTeam";i:1;}s:8:"pagename";s:9:"FrontPage";} > ) [function.dba-insert]: Cannot replace in > /www/nwfish.info/subdomains/www/phpwiki/lib/dbalib.php on line 126 The page content is saved, but the link updates not. This is a backend problem with dba. Which backend do you use? berkeley or gdbm? |
From: Reini U. <ru...@x-...> - 2006-08-13 17:41:47
|
[redirected to the mailing list, I hate the tracker] SourceForge.net schrieb: > Read and respond to this message at: > https://sourceforge.net/forum/message.php?msg_id=3865587 > By: mmaci > > Hi, > > I'm interested in making a hungarian site driven by PhpWiki. But there's a > probleme: our national charset contains two additional characters to iso-8859-1, > ő and ű (the long versions of ö and ü), that is only found in iso-8859-2. > These chars are frequent in hungarian, and it's impossible to leave them or > interchange them with latin1 chars. It would real ugly. The other thing is > that I have to use these characters in WikiNames, but current version of PhpWiki > does not support it. XxxóáYyy is ready (latin1 chars are usable), but if I > change óá to ő, it fails, and square brackets does not help. The [] creates > a link, but ő and ű is viewd as & #337 ; and & #369 ; . Could You please > help me how to solve the probleme? Is it a big work to add latin2 support into > PhpWiki? Normally it should work out of the box when you define('CHARSET', 'iso-8859-2'); (or define it in the config.ini) and your php supports it (via iconv) in the pcre functions. mbstring should not be needed afaik. latin-2 is single-byte. > I promise I'll gift the project with a hu.po file if iso-8859-2 will be ok... > Now there's nothing to it. Personally I'd rather prefer a cool layout in a new template, but we accept hungarian also :) -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ |
From: Reini U. <ru...@x-...> - 2006-08-13 08:22:59
|
ecocode schrieb: > * Reini Urban <ru...@x-...> wrote: > | > | ecocode schrieb: > | > I'm new to phpWiki. I just installed it, but I can't get rid of these > | > notices which appear on every page... The wiki seems to work however. > | > (I've installed version 1.3.12p3) > | > > | > This is the notice : > | > > | > lib/pear/DB/common.php:1295: Notice: Only variable references should be > | > returned by reference > | > | Yes, please this file at line 1295: (untested) > | > | => return &$row; > | > | This is unfortunately an external library, not our code. > | I'll update it for the next release. > > that doesn't work ... > it even makes everything worse, since the wiki doesn't work anymore... Ok, so try installing the latest pear DB library and put the pear library path in front of INCLUDE_PATH in config.ini. This will override our version. AUTH_USER_FILE_STORABLE will not work though. -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ |
From: ecocode <ec...@ec...> - 2006-08-13 00:27:42
|
* Reini Urban <ru...@x-...> wrote: | | ecocode schrieb: | > I'm new to phpWiki. I just installed it, but I can't get rid of these | > notices which appear on every page... The wiki seems to work however. | > (I've installed version 1.3.12p3) | > | > This is the notice : | > | > lib/pear/DB/common.php:1295: Notice: Only variable references should be | > returned by reference | | Yes, please this file at line 1295: (untested) | | => return &$row; | | This is unfortunately an external library, not our code. | I'll update it for the next release. that doesn't work ... it even makes everything worse, since the wiki doesn't work anymore... -- Eco http://www.ecocode.net * Life is wonderful with Emacs and Perl * |
From: Reini U. <ru...@x-...> - 2006-08-12 22:51:20
|
Hi, ecocode schrieb: > I'm new to phpWiki. I just installed it, but I can't get rid of these > notices which appear on every page... The wiki seems to work however. > (I've installed version 1.3.12p3) > > This is the notice : > > lib/pear/DB/common.php:1295: Notice: Only variable references should be > returned by reference Yes, please this file at line 1295: (untested) => return &$row; This is unfortunately an external library, not our code. I'll update it for the next release. |
From: charles.wicksteed <cha...@wa...> - 2006-08-12 22:34:52
|
Reini, or anyone else who has admin access to the PhpWiki SourceForge area, In case you don't know, there's still a problem with the Wiki at http://phpwiki.sourceforge.net/phpwiki/ It redirects to http://phpwiki.sourceforge.net/phpwiki/phpwiki-1.2/ then: http://phpwiki.sourceforge.net/phpwiki/phpwiki-1.2/phpwiki-1.2/ etc forever until the browser detects the looping (I'm using Firefox). This seems to happen to all pages, eg http://phpwiki.sourceforge.net/phpwiki/SteveHuff -> http://phpwiki.sourceforge.net/phpwiki/phpwiki-1.2/ and loops. (I have a proxy server where I can see the logs). Noted at 22:00 GMT on 12 August. Charles Barnet, North London, UK. |
From: ecocode <ec...@ec...> - 2006-08-10 06:36:26
|
Hi, I'm new to phpWiki. I just installed it, but I can't get rid of these notices which appear on every page... The wiki seems to work however. (I've installed version 1.3.12p3) This is the notice : lib/pear/DB/common.php:1295: Notice: Only variable references should be returned by reference Any idea ? Thanks -- Eco http://www.ecocode.net * Life is wonderful with Emacs and Perl * |
From: Reini U. <ru...@x-...> - 2006-08-07 22:41:04
|
Matt Brown schrieb: > > Reini Urban wrote: > >> We know that we need at least 16MB for 1.3.x. >> This was described analysed in great detail at the sf.net page which >> does not work now. > > Any chance that you have an offline copy somewhere that you could send > to me? Backup attached. >> Reduce memory limits - in decreasing order of gained memory: >> >> DATABASE_TYPE=dba >> USECACHE=0 >> ENABLE_USER_NEW=false >> WIKIDB_NOCACHE_MARKUP = true > > OK, I'll check these out. Thanks. In the src are at certain functions also numbers for timings from the latest profiler run. But no memory results, these are only from the feature matrix. I have much more results locally. -- Reini |
From: Matt B. <ma...@ma...> - 2006-08-07 21:44:47
|
Reini Urban wrote: > We know that we need at least 16MB for 1.3.x. > This was described analysed in great detail at the sf.net page which=20 > does not work now. Any chance that you have an offline copy somewhere that you could send to me? > Reduce memory limits - in decreasing order of gained memory: >=20 > DATABASE_TYPE=3Ddba > USECACHE=3D0 > ENABLE_USER_NEW=3Dfalse > WIKIDB_NOCACHE_MARKUP =3D true OK, I'll check these out. Thanks. -- Matt Brown ma...@ma... Mob +64 21 611 544 www.mattb.net.nz |
From: Reini U. <ru...@x-...> - 2006-08-07 20:49:31
|
Matt Brown schrieb: > Hi, > > I'm having trouble with the PHPwiki Debian package and memory usage. In > particular the package doesn't work with the default memory limit that > PHP4 has in Debian (8MB), which is also the default memory limited > shipped with PHP4. > > Have other people run into this problem? namely that PHPwiki will not > run with small amounts of memory? > > Are there any techniques that can be used to reduce PHPwiki's memory > usage so that it will work with an 8MB memory limit? We know that we need at least 16MB for 1.3.x. This was described analysed in great detail at the sf.net page which does not work now. Reduce memory limits - in decreasing order of gained memory: DATABASE_TYPE=dba USECACHE=0 ENABLE_USER_NEW=false WIKIDB_NOCACHE_MARKUP = true -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ |
From: Matt B. <ma...@ma...> - 2006-08-07 10:33:59
|
Hi, I'm having trouble with the PHPwiki Debian package and memory usage. In particular the package doesn't work with the default memory limit that PHP4 has in Debian (8MB), which is also the default memory limited shipped with PHP4. Have other people run into this problem? namely that PHPwiki will not run with small amounts of memory? Are there any techniques that can be used to reduce PHPwiki's memory usage so that it will work with an 8MB memory limit? -- Matt Brown ma...@ma... Mob +64 21 611 544 www.mattb.net.nz |
From: Reini U. <ru...@x-...> - 2006-08-06 14:53:01
|
I disabled the default 1.3.x version of the sf.net homepage over at http://phpwiki.org/ resp. http://phpwiki.sorceforge.net/phpwiki/ due to yet unknown technical problems. I've linked it to the 1.2.x version instead and locked all the default pages. The default version (1.3.12p2 and p3) worked fine for some time without any change from our side, until sf.net changed something in their webserver configuration, which probably causes a loop somewhere. This would explain the recent mysql troubles also. php for example has again gdbm and db4 enabled. Unfortunately they don't offer apache or squid logs for performance reasons to nail this down. I cannot reproduce this problem on any of my servers. We did run out of soft quotas (100MB), but after deleting some of leftovers it still doesn't work. (96MB) local user rurban: 4.2M phpwiki group: 78M If someone will offer a new home for the webservice, current and demo versions, we would be very happy. It will produce some traffic. It will be about 80MB. Downloads and nightly tarball still from sf.net. Our admins would need ssh access. Unfortunately my webserver in the university network is no longer reliable, so I cannot host it. -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ |
From: Jacob R. <jac...@gm...> - 2006-08-04 05:18:15
|
Ok, that got me further. Now I have a new error: lib/WikiDB/backend/PearDB.php:34: Fatal[256]: Can't connect to database: wikidb_backend_mysql: fatal database error * DB Error: connect failed * ( [nativecode=Access denied for user: 'jjrael@localhost' (Using password: YES)] ** mysql://jjrael:XXXXXXXX@localhost/jjrael_phpwikidb) * lib/pear/DB/common.php:300: Notice[8]: Only variable references should be returned by reference lib/WikiDB/backend/PearDB.php:34: Fatal[256]: Can't connect to database: wikidb_backend_mysql: fatal database error * DB Error: connect failed * ( [nativecode=Access denied for user: 'jjrael@localhost' (Using password: YES)] ** mysql://jjrael:XXXXXXXX@localhost/jjrael_phpwikidb) * I think I need to change the password for the mysql dB. How do I do that? jr > Date: Mon, 31 Jul 2006 18:27:50 +0200 > From: Reini Urban <ru...@x-...> > Subject: Re: [Phpwiki-talk] how to access data when phpwiki is dead? > To: php...@li... > Message-ID: <44C...@x-...> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Jacob Rael schrieb: > > Hello, > > > > A few years ago I set up phpwiki on my personal site. My site provider > > kept changing things on me like adding phpsuexec. I would hack the > > code to get things to work but I began migrating data away from the > > site. > > > > Today, I wanted to view my site to get some info and when I attempted > > to log in (I am pretty sure my password is correct), I get: > > > > Fatal error: Cannot instantiate non-existent class: file_passwd in > > /home2/jjrael/public_html/phpwiki/lib/WikiUserNew.php on line 2122 > > Problem: > Your pear doesn't contain the File_Passwd library. > > Workaround: > config/config.ini: > INCLUDE_PATH = "/home2/jjrael/public_html/phpwiki/lib/pear" > > 2nd Workaround, if the first doesn't work. > ENABLE_USER_NEW = false > > > > I have ssh access to my site but I don't know what to do. At this > > point, I only need to read my old data. > > -- > Reini Urban > http://phpwiki.org/ http://murbreak.at/ > http://helsinki.at/ http://spacemovie.mur.at/ > -- Jacob Rael jac...@gm... |
From: Reini U. <ru...@x-...> - 2006-07-31 16:27:47
|
Jacob Rael schrieb: > Hello, > > A few years ago I set up phpwiki on my personal site. My site provider > kept changing things on me like adding phpsuexec. I would hack the > code to get things to work but I began migrating data away from the > site. > > Today, I wanted to view my site to get some info and when I attempted > to log in (I am pretty sure my password is correct), I get: > > Fatal error: Cannot instantiate non-existent class: file_passwd in > /home2/jjrael/public_html/phpwiki/lib/WikiUserNew.php on line 2122 Problem: Your pear doesn't contain the File_Passwd library. Workaround: config/config.ini: INCLUDE_PATH = "/home2/jjrael/public_html/phpwiki/lib/pear" 2nd Workaround, if the first doesn't work. ENABLE_USER_NEW = false > I have ssh access to my site but I don't know what to do. At this > point, I only need to read my old data. -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ |
From: Jacob R. <jac...@gm...> - 2006-07-31 14:49:58
|
Hello, A few years ago I set up phpwiki on my personal site. My site provider kept changing things on me like adding phpsuexec. I would hack the code to get things to work but I began migrating data away from the site. Today, I wanted to view my site to get some info and when I attempted to log in (I am pretty sure my password is correct), I get: Fatal error: Cannot instantiate non-existent class: file_passwd in /home2/jjrael/public_html/phpwiki/lib/WikiUserNew.php on line 2122 I have ssh access to my site but I don't know what to do. At this point, I only need to read my old data. jr -- Jacob Rael jac...@gm... |
From: Dan M. <Mic...@ve...> - 2006-07-28 06:42:43
|
William Leader wrote: > Dan, > I have seen the same behavior when a page has an inline image (like > this: [http://someurl.to/a/picture.jpg] ) in the wiki text on my wiki. I > don't know if my problem is related, but when I find a page that does > what you describe, I am still able to go to the edit page, and remove > the inline image by adding edit to the url. > > http://dan.martins.wiki/index.php/HomePage?action=edit > > Good luck, > -Will > > Dan Martin wrote: > >> I have seen this question raised in forums but have yet seen no good >> answer. I upgraded to Fedora 5, which upgraded me to Apache 2.2.2 and >> libphp 5.1.4. Now I get a totally blank page when trying to load >> index.php. configurator.php and passencrypt.php load and show just fine. >> >> Viewing the source of the page shows nothing, not even a set of <html> >> tags. It behaves the same whether being viewed from IE or Firefox. >> >> I upgraded to phpwiki 1.3.12p3 but no change. >> >> Thanks for the suggestion. I tried it, but got no change in the behavior. I also tried on a virgin wiki setup and by renaming the data dir (I use File for the database.) All of these give the same result. Dan |
From: Dan M. <Mic...@ve...> - 2006-07-27 12:14:49
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=us-ascii" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> William Leader wrote: <blockquote cite="mid...@k2..." type="cite"> <pre wrap="">Dan, I have seen the same behavior when a page has an inline image (like this: [<a class="moz-txt-link-freetext" href="http://someurl.to/a/picture.jpg">http://someurl.to/a/picture.jpg</a>] ) in the wiki text on my wiki. I don't know if my problem is related, but when I find a page that does what you describe, I am still able to go to the edit page, and remove the inline image by adding edit to the url. <a class="moz-txt-link-freetext" href="http://dan.martins.wiki/index.php/HomePage?action=edit">http://dan.martins.wiki/index.php/HomePage?action=edit</a> Good luck, -Will Dan Martin wrote: </pre> <blockquote type="cite"> <pre wrap="">I have seen this question raised in forums but have yet seen no good answer. I upgraded to Fedora 5, which upgraded me to Apache 2.2.2 and libphp 5.1.4. Now I get a totally blank page when trying to load index.php. configurator.php and passencrypt.php load and show just fine. Viewing the source of the page shows nothing, not even a set of <html> tags. It behaves the same whether being viewed from IE or Firefox. I upgraded to phpwiki 1.3.12p3 but no change. </pre> </blockquote> <br> </blockquote> I backrevved PHP to php-5.0.5 and at least got an error to show up -<br> <br> <b>Fatal error</b>: Call to a member function get() on a non-object in <b>/share/goodnews/lib/WikiUser.php</b> on line <b>140<br> <br> The only other thing I can think to do is downgrade apache to 2.0.xx, but that would involve installing a whole slew of supporting libraries, and I just don't want to mess with it. It is too bad, and I wish someone from the PhpWiki project would take some interest in this problem, but I just don't want to fool with it anymore.<br> <br> </b> </body> </html> |