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: Von S. M. \(Max\) <M.E...@rl...> - 2007-08-30 07:08:20
|
Hello,=20 Thanks for your assistance,=20 I did try this but it had no effect whatsoever. I have managed get some signs of life out of it now (the problem seemed to stem from the authentication settings) - once I said to use encryption things did appear.=20 However, ever attempt to log into the Admin area automatically resets the admin password in an encrypted format (i.e. unreadable) so basically everytime I access the admin area, it seems I have to reuse passencrypt.php and hard code a new entry into the config.ini ... This is really rather annoying.=20 Aside from that small issue, it seems to work ...=20 Thank you,=20 Max.=20 -----Original Message----- From: php...@li... [mailto:php...@li...] On Behalf Of Reini Urban Sent: 29 August 2007 21:42 To: Discussion on PhpWiki features, bugs, development. Subject: Re: [Phpwiki-talk] Installation Problems. Von Seibold, MEA (Max) schrieb: > Hello, > =20 > I just subscribed here. I suspect that this is a common/annoying=20 > question so forgive me. I hope that I am posting this in the correct place. > =20 > Basically I am having a very hard time getting phpwiki-1.3.14=20 > installed on Solaris 10. > =20 > I am running Apache2 and MYSQL with PHP5 Compiled from source. > =20 > I moded the mysql create script with the name "phpwiki" and have=20 > created the database following the instructions given. > =20 > When I load the index.php page all I get is a blank white screen. Hi Max, The first step when loading directly from index and a blank screen is usually to disable the logic in index.php: //if (@is_dir(SCRIPT_FILENAME) or realpath(SCRIPT_FILENAME) =3D=3D realpath(__FILE__)) include(dirname(__FILE__)."/lib/main.php"); > Are there any guides/docs available a little more comprehensive than the=20 > ones included with the download that anyone could point me at? > =20 > DATABASE_TYPE =3D ADODB > DATABASE_PREFIX =3D phpwiki_ > DATABASE_DSN =3D=20 > mysql:wikiusername:wikiuserpassword@the_computers_hostname/phpwiki > =20 > DATABASE_DIRECTORY =3D /www/phpwiki/pages > DATABASE_DBA_HANDLER =3D db64 > =20 > =20 > I have also encrypted the password with passencrypt.php and entered this=20 > in the config/config.ini file. > =20 > =20 > Could anyone help? > =20 > =20 > Thanks, > =20 > =20 > =20 > Max. > =20 >=20 >=20 > ------------------------------------------------------------------------ >=20 > ------------------------------------------------------------------------ - > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ >=20 >=20 > ------------------------------------------------------------------------ >=20 > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk --=20 Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ ------------------------------------------------------------------------ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Phpwiki-talk mailing list Php...@li... https://lists.sourceforge.net/lists/listinfo/phpwiki-talk |
From: Harold H. <ha...@ha...> - 2007-08-30 04:03:16
|
I'm running phpwiki 1.3.13 (I think, by looking at the installed file names... Does the version show up somewhere on a wiki page?). Anyway, I'm trying uploads again. It now separates uploads by user. When I do an upload, it ends up in the directory uploadsharold . The link formed on the page is * [Upload:harold/HarrisAmsg1-0601.pdf] . So, did I miss something in config? THANKS! Harold -- FCC Rules Updated Daily at http://www.hallikainen.com - Advertising opportunities available! |
From: Reini U. <ru...@x-...> - 2007-08-29 20:41:34
|
Von Seibold, MEA (Max) schrieb: > Hello, > > I just subscribed here. I suspect that this is a common/annoying > question so forgive me. I hope that I am posting this in the correct place. > > Basically I am having a very hard time getting phpwiki-1.3.14 installed > on Solaris 10. > > I am running Apache2 and MYSQL with PHP5 Compiled from source. > > I moded the mysql create script with the name "phpwiki" and have created > the database following the instructions given. > > When I load the index.php page all I get is a blank white screen. Hi Max, The first step when loading directly from index and a blank screen is usually to disable the logic in index.php: //if (@is_dir(SCRIPT_FILENAME) or realpath(SCRIPT_FILENAME) == realpath(__FILE__)) include(dirname(__FILE__)."/lib/main.php"); > Are there any guides/docs available a little more comprehensive than the > ones included with the download that anyone could point me at? > > DATABASE_TYPE = ADODB > DATABASE_PREFIX = phpwiki_ > DATABASE_DSN = > mysql:wikiusername:wikiuserpassword@the_computers_hostname/phpwiki > > DATABASE_DIRECTORY = /www/phpwiki/pages > DATABASE_DBA_HANDLER = db64 > > > I have also encrypted the password with passencrypt.php and entered this > in the config/config.ini file. > > > Could anyone help? > > > Thanks, > > > > Max. > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > ------------------------------------------------------------------------ > > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ |
From: Von S. M. \(Max\) <M.E...@rl...> - 2007-08-29 12:17:37
|
Hello,=20 =20 I just subscribed here. I suspect that this is a common/annoying question so forgive me. I hope that I am posting this in the correct place. =20 Basically I am having a very hard time getting phpwiki-1.3.14 installed on Solaris 10.=20 =20 I am running Apache2 and MYSQL with PHP5 Compiled from source.=20 =20 I moded the mysql create script with the name "phpwiki" and have created the database following the instructions given.=20 =20 When I load the index.php page all I get is a blank white screen.=20 =20 Are there any guides/docs available a little more comprehensive than the ones included with the download that anyone could point me at?=20 =20 DATABASE_TYPE =3D ADODB DATABASE_PREFIX =3D phpwiki_ DATABASE_DSN =3D mysql:wikiusername:wikiuserpassword@the_computers_hostname/phpwiki =20 DATABASE_DIRECTORY =3D /www/phpwiki/pages DATABASE_DBA_HANDLER =3D db64 =20 =20 I have also encrypted the password with passencrypt.php and entered this in the config/config.ini file.=20 =20 =20 Could anyone help?=20 =20 =20 Thanks,=20 =20 =20 =20 Max.=20 =20 |
From: Sabri L. <sab...@gm...> - 2007-08-24 21:37:59
|
On 8/23/07, Reini Urban <ru...@x-...> wrote: > > Sabri LABBENE schrieb: > > Hi Reini and all, > > I have some issues with not supported characters by wysiwyg charset. > > What happens is that some users sometimes copy some text from other text > > editors and paste it into wysiwyg edition area. The copied text can > > contain some characters that are not part of ISO 8859-1 charset. When > > opening a page that contains such characters with wysiwyg the text after > > the unknown character is not shown. > > I choosed ISO 8859-1 as a charset for wikiwyg conversion because it is > > understandable by all web browsers and is a standard in web > applications. > > - Should we support additional charsets? > > We should detect/choose it (optionally) and convert it. > Or tell the user to use our native charset and how to convert it. > (iconv or use some sort of save as...) You think about popups? I like it. We can ask the user whether he wants to do a conversion to our native charset. This have to happen only if we detect that the user content is in a different charset. I Don't know how to do that yet. I also didn't understoot the 'save as' solution. However, I think it is not a good idea to force user to save his wiki page at any time durin the edition. He should keep the freedom of doing it whenever he wants. > - May be skip the unknown characters and continue the display? Not > > really good because there is some data loosing ! > > > > what do you think? > > Cheers, > > There are mostly two types of pasted formats: rtf and ansi (text/plain) > in the clipboard. From notepad you get ansi (the windows version of > latin1. almost the same, but different). > From word, wordpad, outlook at el. you'll get rtf, with formatting. > This is what the user wants usually. > > I have to investigate if it's possible to get the source charset from > rtf to convert it automatically. If possible. I doubt it. > We'd need some dropdown to choose the source charset within the editor, > which converts it into the wiki charset, which is usually latin1 or utf-8. The problem I described in my previous message is that - Some characters in wiki pages are part from wiki charset (utf-8). - Those characters are not part of ISO 8859-1 charset which is used in wysiwyg edition mode. - When you open the wiki page in wysiwyg edition mode, the display stops at the unknown character (unknown for ISO 8859-1) These characters are usually introduced into the wiki page by copy from the clipboard. The classical edition textarea accept those chars since they are in utf-8. If you save the page, they will be part of it and they will be displayed without problem if you view the wiki page. The problem only appears when you edit the page with wysiwyg editor. I just want to remind that ISO 8859-1 was used to solve the accented characters issue some time ago and I believe it is suitable for wysiwyg editor html content. There's a libtextcat library which can detect the language and/or > charset of the source automatically. > I maintain it for cygwin. Good. Let's assume that we guessed in which charset user data is. This is what I propose: - Tell user that his data is not compatible with our native charset. - We will then propose to him to convert his content to our native wysiwyg charset (ISO 8859-1). Otherwise, his page will not be viewed correctly. What do you think.? -- Sabri. |
From: Reini U. <ru...@x-...> - 2007-08-23 06:59:37
|
Sabri LABBENE schrieb: > Hi Reini and all, > I have some issues with not supported characters by wysiwyg charset. > What happens is that some users sometimes copy some text from other text > editors and paste it into wysiwyg edition area. The copied text can > contain some characters that are not part of ISO 8859-1 charset. When > opening a page that contains such characters with wysiwyg the text after > the unknown character is not shown. > I choosed ISO 8859-1 as a charset for wikiwyg conversion because it is > understandable by all web browsers and is a standard in web applications. > - Should we support additional charsets? We should detect/choose it (optionally) and convert it. Or tell the user to use our native charset and how to convert it. (iconv or use some sort of save as...) > - May be skip the unknown characters and continue the display? Not > really good because there is some data loosing ! > > what do you think? > Cheers, There are mostly two types of pasted formats: rtf and ansi (text/plain) in the clipboard. From notepad you get ansi (the windows version of latin1. almost the same, but different). From word, wordpad, outlook at el. you'll get rtf, with formatting. This is what the user wants usually. I have to investigate if it's possible to get the source charset from rtf to convert it automatically. If possible. I doubt it. We'd need some dropdown to choose the source charset within the editor, which converts it into the wiki charset, which is usually latin1 or utf-8. There's a libtextcat library which can detect the language and/or charset of the source automatically. I maintain it for cygwin. -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ |
From: Sabri L. <sab...@gm...> - 2007-08-22 23:54:04
|
Hi Reini and all, I have some issues with not supported characters by wysiwyg charset. What happens is that some users sometimes copy some text from other text editors and paste it into wysiwyg edition area. The copied text can contain some characters that are not part of ISO 8859-1 charset. When opening a page that contains such characters with wysiwyg the text after the unknown character is not shown. I choosed ISO 8859-1 as a charset for wikiwyg conversion because it is understandable by all web browsers and is a standard in web applications. - Should we support additional charsets? - May be skip the unknown characters and continue the display? Not really good because there is some data loosing ! what do you think? Cheers, -- Sabri. |
From: Zac E. <zac...@me...> - 2007-08-20 16:08:18
|
hello. I'm trying to determine why the upload plugin isn't working as described. I have two phpwiki instances. a 1.2.1 and a 1.3.14 here's an example File successfully uploaded. Upload:ZacElston/z1-image.gif (http://psiwiki//uploads/ZacElston/z1- image.gif) in the 1.3.14 ( UpLoad.php,v 1.25) version the uploaded files get written to a uploads$user/$file dir as opposed to uploads/$user/$file which is what the wiki reports it should be. thus the inline request of [Upload:ZacElston/z1-image.gif] fails in the 1.2.1 (UpLoad.php,v 1.19) install it just writes to the root phpwiki dir with a filename of uploads$user$file the errors (1.3.14) listed on the upload are as follows. where should phpwiki-upload.log be located? It's not accepting the phpwiki root or the plugin dir lib/plugin/UpLoad.php (In template 'body' < 'html'):264: Warning: The upload logfile is not writable. so in both cases it looks like the file isn't getting the initial ./ uploads/ directory prepended to the name on write. is this a config option somewhere? thanks -zac |
From: Alexander T. <di...@0-...> - 2007-08-17 06:00:20
|
>> With that out of the way, I'll explain my trouble with HttpAuth in the >> hope that someone can enlighten me. I'm using PhPWiki 1.3.14, and have >> Apache configured to require a password with .htaccess and .htpasswd >> files. I successfully authenticate to Apache, but PhPWiki does not >> consider me authenticated, and asks me to login when I try to upload a >> file for example. One unusual thing about this hosting environment, which >> is a possible cause, is that /tmp is not writeable, so I have to configure >> any temp file locations manually. >> >> Here are the configuration parameters from the user auth section of my >> config/config.ini: >> >> ALLOW_ANON_USER = true ALLOW_ANON_EDIT = true ALLOW_BOGO_LOGIN = false >> ALLOW_USER_PASSWORDS = false >> >> USER_AUTH_ORDER = "HttpAuth" >> >> PASSWORD_LENGTH_MINIMUM = 6 >> >> USER_AUTH_POLICY = strict >> >> ;ENABLE_USER_NEW = false ENABLE_PAGEPERM = false Reini> If you choose HttpAuth, phpwiki does not do any auth session handling, Reini> all this is done within apache, and therefore you have a apache Reini> problem. phpwiki just checks for the typical vars for PHP_AUTH_USER Reini> or REMOTE_USER (in case of cgi) I just checked and REMOTE_USER has the correct value, while PHP_AUTH_USER is empty. I don't have control over the Apache configuration on this machine, is there something I can do with the phpwiki configuration to support this case? Thanks, Alex -- https://savannah.gnu.org/projects/libcvs-spec Access CVS through a library. PGP: ID: 0x23DC453B FPR: 42D0 66C2 9FF8 553A 373A B819 4C34 93BA 23DC 453B I am not expendable, I am not stupid, and I am not going. - Avon |
From: Reini U. <ru...@x-...> - 2007-08-16 06:26:06
|
Alexander Taler schrieb: > Hi, I have recently installed phpwiki and am having some trouble with httpauth. > Unfortunately my first line of inquiry, the documentation on the website, is > not available to me. For several weeks I have received no response from the > webserver for URLs such as > > http://phpwiki.sourceforge.net/phpwiki > > I've tried a few different browsers from various locations on the internet, so > I don't think this is my problem. Are others having the same problem? It's > kind of important because all the search engines are returning links to such > URLs. Yes, it's broken again and seems to be an issue with the squid cache. I just reverted back to the 1.2.x version. I'll import parts of the content into this version. > With that out of the way, I'll explain my trouble with HttpAuth in the hope > that someone can enlighten me. I'm using PhPWiki 1.3.14, and have Apache > configured to require a password with .htaccess and .htpasswd files. I > successfully authenticate to Apache, but PhPWiki does not consider me > authenticated, and asks me to login when I try to upload a file for example. > One unusual thing about this hosting environment, which is a possible cause, is > that /tmp is not writeable, so I have to configure any temp file locations > manually. > > Here are the configuration parameters from the user auth section of my > config/config.ini: > > ALLOW_ANON_USER = true > ALLOW_ANON_EDIT = true > ALLOW_BOGO_LOGIN = false > ALLOW_USER_PASSWORDS = false > > USER_AUTH_ORDER = "HttpAuth" > > PASSWORD_LENGTH_MINIMUM = 6 > > USER_AUTH_POLICY = strict > > ;ENABLE_USER_NEW = false > ;ENABLE_PAGEPERM = false If you choose HttpAuth, phpwiki does not do any auth session handling, all this is done within apache, and therefore you have a apache problem. phpwiki just checks for the typical vars for PHP_AUTH_USER or REMOTE_USER (in case of cgi) > Finally, for the record, the reason I have chosen http auth is because it is > the only mechanism that protects uploaded attachments. When using the other > authentication methods attachments may be downloaded without authentication. > Would you like me to report this as a bug? I know of this problem and temp. protected uploads-only with http auth, the rest with LDAP in my case. I'm already working on a transparent http auth login page, so that we get rid of the client auth dialog and have a beautiful, transparent and global HttpAuth solution via httpauth.js -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ |
From: Alexander T. <di...@0-...> - 2007-08-15 23:10:14
|
Hi, I have recently installed phpwiki and am having some trouble with httpauth. Unfortunately my first line of inquiry, the documentation on the website, is not available to me. For several weeks I have received no response from the webserver for URLs such as http://phpwiki.sourceforge.net/phpwiki I've tried a few different browsers from various locations on the internet, so I don't think this is my problem. Are others having the same problem? It's kind of important because all the search engines are returning links to such URLs. With that out of the way, I'll explain my trouble with HttpAuth in the hope that someone can enlighten me. I'm using PhPWiki 1.3.14, and have Apache configured to require a password with .htaccess and .htpasswd files. I successfully authenticate to Apache, but PhPWiki does not consider me authenticated, and asks me to login when I try to upload a file for example. One unusual thing about this hosting environment, which is a possible cause, is that /tmp is not writeable, so I have to configure any temp file locations manually. Here are the configuration parameters from the user auth section of my config/config.ini: ALLOW_ANON_USER = true ALLOW_ANON_EDIT = true ALLOW_BOGO_LOGIN = false ALLOW_USER_PASSWORDS = false USER_AUTH_ORDER = "HttpAuth" PASSWORD_LENGTH_MINIMUM = 6 USER_AUTH_POLICY = strict ;ENABLE_USER_NEW = false ;ENABLE_PAGEPERM = false Finally, for the record, the reason I have chosen http auth is because it is the only mechanism that protects uploaded attachments. When using the other authentication methods attachments may be downloaded without authentication. Would you like me to report this as a bug? Thanks, Alex -- https://savannah.gnu.org/projects/libcvs-spec Access CVS through a library. PGP: ID: 0x23DC453B FPR: 42D0 66C2 9FF8 553A 373A B819 4C34 93BA 23DC 453B I am not expendable, I am not stupid, and I am not going. - Avon |
From: Reini U. <ru...@x-...> - 2007-08-15 08:46:25
|
RubyCon schrieb: > Thanks for your quick reply. :-) > > Your solution works. No errormessage and the database gets data. > > Thank you for your nice wiki Glad I could help you. It's just no "my" wiki, I just happen maintain it now. It's the collaborate work of dozens of developers and people sending patches. -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ |
From: RubyCon <dm...@ik...> - 2007-08-15 07:42:10
|
Thanks for your quick reply. :-) Your solution works. No errormessage and the database gets data. Thank you for your nice wiki -- View this message in context: http://www.nabble.com/Re%3A-Wrong-table-in-mysql_initialize.sql---tf4269624.html#a12157830 Sent from the phpwiki-talk mailing list archive at Nabble.com. |
From: Reini U. <ru...@x-...> - 2007-08-15 06:48:37
|
RubyCon schrieb: > Sorry, I searched in the wrong direction. Forget my 1. posting .. I'm sorry. > The error still appears: > ib/WikiDB/backend/PearDB.php:1059 Error: WikiDB_backend_PearDB_mysql: fatal > database error > > * DB Error: value count on row > * (INSERT INTO accesslog > (time_stamp,remote_host,remote_user,request_method,request_line,request_uri,request_args,request_time,status,bytes_sent,referer,agent,request_duration) > VALUES (1187156181,'xxx.xxx.xxx','-','GET','GET /quicky/ > HTTP/1.0','/quicky/','','15/Aug/2007:07:36:21 0200',200,7800,'','Mozilla/5.0 > (Windows; U; Windows NT 5.1; de; rv:1.8.1.6) Gecko/20070725 > Firefox/2.0.0.6',1,2147881984711) [nativecode=1136 ** Column count doesn't > match value count at row 1]) > > What is going wrong here ? PHP Version is 5.1.6 , MySQL is 5.0.22 on > Scientific Linux 5. Ok, your system looks sane, just european. The error is the request_duration as 1,2147881984711 It should be 1.2147881984711 Know problem with PEAR DB quoting. ? should be escape floats with , // duration problem: sprintf "%f" might use comma e.g. "1,201" in european locales The fix is function setDuration ($seconds) { // Pear DB does not correctly quote , in floats using ?. e.g. in european locales. // Workaround: $this->duration = strtr(sprintf("%f", $seconds),",","."); } in Request.php -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ |
From: RubyCon <dm...@ik...> - 2007-08-15 05:57:08
|
Sorry, I searched in the wrong direction. Forget my 1. posting .. I'm sorry. The error still appears: ib/WikiDB/backend/PearDB.php:1059 Error: WikiDB_backend_PearDB_mysql: fatal database error * DB Error: value count on row * (INSERT INTO accesslog (time_stamp,remote_host,remote_user,request_method,request_line,request_uri,request_args,request_time,status,bytes_sent,referer,agent,request_duration) VALUES (1187156181,'xxx.xxx.xxx','-','GET','GET /quicky/ HTTP/1.0','/quicky/','','15/Aug/2007:07:36:21 0200',200,7800,'','Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6',1,2147881984711) [nativecode=1136 ** Column count doesn't match value count at row 1]) What is going wrong here ? PHP Version is 5.1.6 , MySQL is 5.0.22 on Scientific Linux 5. If you need more infos feel free to ask Thanks -- View this message in context: http://www.nabble.com/Re%3A-Wrong-table-in-mysql_initialize.sql---tf4269624.html#a12156931 Sent from the phpwiki-talk mailing list archive at Nabble.com. |
From: Reini U. <ru...@x-...> - 2007-08-14 20:45:37
|
RubyCon schrieb: > I just installed a new and fresh phpwiki 1.3.14 (timestamp July 1th 12:15.) > Everything works fine except an errormessge at the end of each page: pear > ... mysql .. access_log something-wrong table_rows > > The following patch fixes the problem. > > ---cut here--- > *** schemas/mysql-initialize.sql 2007-08-14 21:03:16.000000000 +0200 > --- schemas/mysql-initialize.sql.orig 2007-07-01 12:11:27.000000000 +0200 > *************** > *** 130,138 **** > remote_user VARCHAR(50), > request_method VARCHAR(10), > request_line VARCHAR(255), > - request_uri VARCHAR(255), > request_args VARCHAR(255), > request_file VARCHAR(255), > request_time CHAR(28), > status SMALLINT UNSIGNED, > bytes_sent SMALLINT UNSIGNED, > --- 130,138 ---- > remote_user VARCHAR(50), > request_method VARCHAR(10), > request_line VARCHAR(255), > request_args VARCHAR(255), > request_file VARCHAR(255), > + request_uri VARCHAR(255), > request_time CHAR(28), > status SMALLINT UNSIGNED, > bytes_sent SMALLINT UNSIGNED, > > ---cut here--- Please always do diff old new, not new old. I looked for 10 minutes for the sequence request_uri request_args request_file request_time, but could not find it. What a stupid mysql do you have? Or a pear or adodb bug? lib/WikiDB/backend.php is okay. Just the order is different. I also wonder now what request_file should do here. Seems not to be used at all. |
From: Sabri L. <sab...@gm...> - 2007-08-14 20:25:51
|
On 8/14/07, Reini Urban <ru...@x-...> wrote: > > 2007/8/14, Sabri LABBENE <sab...@st...>: > > I've seen several times the bug you've recently fixed (Unknown modifier > ? At any page save) in my wiki. Unfortunately, I can't find a scenario that > makes the bug easily reproducable. Thus, I can't check if your fix solves my > problem. > > Do you have any idea how to reproduce the bug ? > > Yes, in your preferences save a page like Page/* > in "Get an email notification at changes of the following pages:" > and store your email. > > Then edit any page and voila, you get the warning. ok I see. Your patch has fixed my problem. Thanks a lot. --Sabri. |
From: RubyCon <dm...@ik...> - 2007-08-14 20:09:34
|
Hello, I just installed a new and fresh phpwiki 1.3.14 (timestamp July 1th 12:15.) Everything works fine except an errormessge at the end of each page: pear ... mysql .. access_log something-wrong table_rows The following patch fixes the problem. ---cut here--- *** schemas/mysql-initialize.sql 2007-08-14 21:03:16.000000000 +0200 --- schemas/mysql-initialize.sql.orig 2007-07-01 12:11:27.000000000 +0200 *************** *** 130,138 **** remote_user VARCHAR(50), request_method VARCHAR(10), request_line VARCHAR(255), - request_uri VARCHAR(255), request_args VARCHAR(255), request_file VARCHAR(255), request_time CHAR(28), status SMALLINT UNSIGNED, bytes_sent SMALLINT UNSIGNED, --- 130,138 ---- remote_user VARCHAR(50), request_method VARCHAR(10), request_line VARCHAR(255), request_args VARCHAR(255), request_file VARCHAR(255), + request_uri VARCHAR(255), request_time CHAR(28), status SMALLINT UNSIGNED, bytes_sent SMALLINT UNSIGNED, ---cut here--- Now everything works fine. But a very nice wiki I'm still testing but it looks good Thanks -- View this message in context: http://www.nabble.com/Wrong-table-in-mysql_initialize.sql---tf4269441.html#a12151392 Sent from the phpwiki-talk mailing list archive at Nabble.com. |
From: Reini U. <ru...@x-...> - 2007-08-14 17:41:50
|
2007/8/14, Sabri LABBENE <sab...@st...>: > I've seen several times the bug you've recently fixed (Unknown modifier ? At any page save) in my wiki. Unfortunately, I can't find a scenario that makes the bug easily reproducable. Thus, I can't check if your fix solves my problem. > Do you have any idea how to reproduce the bug ? Yes, in your preferences save a page like Page/* in "Get an email notification at changes of the following pages:" and store your email. Then edit any page and voila, you get the warning. |
From: Sabri L. <sab...@st...> - 2007-08-14 11:46:16
|
Hi Reini and all, I've seen several times the bug you've recently fixed (Unknown modifier = ? At any page save) in my wiki. Unfortunately, I can't find a scenario = that makes the bug easily reproducable. Thus, I can't check if your fix = solves my problem. Do you have any idea how to reproduce the bug ? Thanks for your help, -- Sabri. =20 |
From: Reini U. <ru...@x-...> - 2007-08-12 16:06:44
|
Sacha Schär schrieb: > Greetings to Austria and many thanks for all your help! > As far as I can tell the wiki works now, _after_ applying the SQL patch > above! Ah, good. > (from your other mail) > > FYI: The fix for this error is in lib/upgrade.php > > > > function CheckDatabaseUpdate() { > > global $DBAuthParams, $DBParams; > > After fixing this, ?action=upgrade dies at the following check: > check for mysql LOCK TABLE privilege ...lock_tables_priv missing. > The DB Admin must run mysql_fix_privilege_tables > > > Is 'mysql_fix_privilege_tables' some file or action that is provided > with PHPWiki? I can not find anything like that. > If it is something only the host provider can do, how should I instruct > him? This error says that it seems that wikiuser has no privileges to LOCK tables. Your provider has to grant you LOCK TABLE privileges for your own databases, best done with mysql_fix_privilege_tables. However if you CAN edit pages, you don't need this and the upgrade check is wrong. > Can I savely run the wiki now or should I fix the problem above first? > PS: One minor glitch: Seemingly, I can no longer login into the wiki as > 'SachaSchär'. Is this because of the umlaut? Anyway, no real problem, > I'm just curious... Hmm, that depends on many other things. If the new database has a different default locale, it will lead to those effects. -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ |
From: <sac...@gm...> - 2007-08-12 15:34:39
|
Greetings to Austria and many thanks for all your help! > Does the wiki work? > > > ...(snipped some text) > > [nativecode=1054 ** Unknown column 'cached_html' in 'field list']) > > We still seem to need 'cached_html' > Strange, this should have been there since 1.3.11. Try > > ALTER TABLE page ADD cached_html MEDIUMBLOB; > > But I rather believe upgrade fails in mysql_list_fields(). As far as I can tell the wiki works now, _after_ applying the SQL patch above! (from your other mail) > FYI: The fix for this error is in lib/upgrade.php > > function CheckDatabaseUpdate() { > global $DBAuthParams, $DBParams; After fixing this, ?action=upgrade dies at the following check: check for mysql LOCK TABLE privilege ...lock_tables_priv missing. The DB Admin must run mysql_fix_privilege_tables Is 'mysql_fix_privilege_tables' some file or action that is provided with PHPWiki? I can not find anything like that. If it is something only the host provider can do, how should I instruct him? Can I savely run the wiki now or should I fix the problem above first? -Sacha PS: One minor glitch: Seemingly, I can no longer login into the wiki as 'SachaSchär'. Is this because of the umlaut? Anyway, no real problem, I'm just curious... |
From: Reini U. <ru...@x-...> - 2007-08-12 14:35:14
|
Reini Urban schrieb: > Greetings to Basel. > Sacha Schär schrieb: >> lib/WikiDB/backend/PearDB.php:1059 Error[256]: >> WikiDB_backend_PearDB_mysql: fatal database error >> >> * DB Error: syntax error >> * (DESCRIBE [nativecode=1064 ** You have an error in your SQL >> syntax; check the manual that corresponds to your MySQL server version >> for the right syntax to use near '' at line 1]) >> * >> >> lib/upgrade.php:472 Notice[8]: Undefined variable: DBParams > > This error is not fatal. > mysql session.sess_id sanity is not so important in your case. FYI: The fix for this error is in lib/upgrade.php function CheckDatabaseUpdate() { global $DBAuthParams, $DBParams; -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ |
From: Reini U. <ru...@x-...> - 2007-08-12 13:08:55
|
Greetings to Basel. Sacha Schär schrieb: > Thank you for the quick reply! I did not receive this email. So I just > copied the text from the archieves, thereby probably creating a new > thread... sorry. > > > > Oops, upgrade error. I forgot something. > > Best is to use your phpMyAdmin with the following snippet: > > > > ALTER TABLE accesslog CHANGE remote_host VARCHAR(100); > > > > <enter> // this may fail. > > Failed indeed: > > #1064 - You have an error in your SQL syntax; check the manual that > corresponds to your MySQL server version for the right syntax to use > near 'VARCHAR(100)' at line 1 > > > > ALTER TABLE link ADD relation INT DEFAULT 0; > > CREATE INDEX link_relation ON link (relation); > > > > <enter> // this is required. > > This worked! > > > And then optionally again ?action=3Dupgrade to fill in the relations. A mailer error. I meant ?action=upgrade of course ... > This failed, seemingly, 3Dupgrade is an unknown action in my setup: > > ...(snipped some text) > [nativecode=1054 ** Unknown column 'cached_html' in 'field list']) > * > > lib/main.php:873 Notice[1024]: 3Dupgrade: Unknown action > > > I tried ?upgrade instead. With this, the migration went further as > before, but still failed: > > Upgrading this PhpWiki > check for necessary database updates - SQL > db version: we want 1030.14 > db version: we have 0 > Backend type: mysql > check for table session ...OK > check for table pref ...OK > check for table member ...OK > Rebuild entire database to upgrade relation links ... OK > check for table accesslog ...OK > check for table rating ...OK > check for new session.sess_ip column ... SKIP > check for mysql session.sess_id sanity ... > Fatal Error: > > lib/WikiDB/backend/PearDB.php:1059 Error[256]: > WikiDB_backend_PearDB_mysql: fatal database error > > * DB Error: syntax error > * (DESCRIBE [nativecode=1064 ** You have an error in your SQL > syntax; check the manual that corresponds to your MySQL server version > for the right syntax to use near '' at line 1]) > * > > lib/upgrade.php:472 Notice[8]: Undefined variable: DBParams This error is not fatal. mysql session.sess_id sanity is not so important in your case. > lib/WikiDB/backend/PearDB.php:1151 Warning[2]: mysql_list_fields() [<a > href='function.mysql-list-fields'>function.mysql-list-fields</a>]: > Unable to save MySQL query result > > lib/WikiDB/backend/PearDB.php:1152 Warning[512]: > /home/httpd/vhosts/scanita.net/httpdocs/phpwiki/lib/WikiDB/backend/PearDB.php:1152 > Table 'spice_phpwiki.' doesn't exist > > > (spice_phpwiki is the name of the DB as well as the name of the admin user) > > Is there a bug in upgrade.php or do you think there is a problem with my > settings? Both. A bug in upgrade and an intermediate mysql schema. Thanks for using DEBUG to get the failing upgrade lines. I can fix it now. Does the wiki work? > ...(snipped some text) > [nativecode=1054 ** Unknown column 'cached_html' in 'field list']) We still seem to need 'cached_html' Strange, this should have been there since 1.3.11. Try ALTER TABLE page ADD cached_html MEDIUMBLOB; But I rather believe upgrade fails in mysql_list_fields(). -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ |
From: <sac...@un...> - 2007-08-12 07:36:51
|
Thank you for the quick reply! I did not receive this email. So I just copied the text from the archieves, thereby probably creating a new thread... sorry. > Oops, upgrade error. I forgot something. > Best is to use your phpMyAdmin with the following snippet: > > ALTER TABLE accesslog CHANGE remote_host VARCHAR(100); > > <enter> // this may fail. Failed indeed: #1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'VARCHAR(100)' at line 1 > ALTER TABLE link ADD relation INT DEFAULT 0; > CREATE INDEX link_relation ON link (relation); > > <enter> // this is required. This worked! > And then optionally again ?action=3Dupgrade to fill in the relations. This failed, seemingly, 3Dupgrade is an unknown action in my setup: ...(snipped some text) [nativecode=1054 ** Unknown column 'cached_html' in 'field list']) * lib/main.php:873 Notice[1024]: 3Dupgrade: Unknown action I tried ?upgrade instead. With this, the migration went further as before, but still failed: Upgrading this PhpWiki check for necessary database updates - SQL db version: we want 1030.14 db version: we have 0 Backend type: mysql check for table session ...OK check for table pref ...OK check for table member ...OK Rebuild entire database to upgrade relation links ... OK check for table accesslog ...OK check for table rating ...OK check for new session.sess_ip column ... SKIP check for mysql session.sess_id sanity ... Fatal Error: lib/WikiDB/backend/PearDB.php:1059 Error[256]: WikiDB_backend_PearDB_mysql: fatal database error * DB Error: syntax error * (DESCRIBE [nativecode=1064 ** You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1]) * lib/upgrade.php:472 Notice[8]: Undefined variable: DBParams lib/WikiDB/backend/PearDB.php:1151 Warning[2]: mysql_list_fields() [<a href='function.mysql-list-fields'>function.mysql-list-fields</a>]: Unable to save MySQL query result lib/WikiDB/backend/PearDB.php:1152 Warning[512]: /home/httpd/vhosts/scanita.net/httpdocs/phpwiki/lib/WikiDB/backend/PearDB.php:1152 Table 'spice_phpwiki.' doesn't exist (spice_phpwiki is the name of the DB as well as the name of the admin user) Is there a bug in upgrade.php or do you think there is a problem with my settings? -Sacha |