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: Philip J. H. <ph...@po...> - 2005-04-27 12:36:45
|
On Wed, 27 Apr 2005 13:10:30 +0800 (SGT), "Charles Corrigan" <ch...@ru...> said: > On Wed, April 27, 2005 12:01, Joel Uckelman said: > > Hmm. There were two people seeing this problem, right? If anyone > > who has direct access to their logs is experiencing this, it > > would be great to hear from you. > > > > Oh, another thing: Does this happen on every page, or just some? > > Do the pages this happens on have anything in common? Can you > > send me a link to a page that does this, so I can put the thing > > into my test wiki? > > Further data points: > 1 - it happens on several different pages - the first page when I go > to the site [a] - whether that first page is the HomePage or > RecentEdits. > 2 - Just hitting refresh does not always resolve the issue, sometimes > shift-refresh is required. > 3 - Once a page is correctly loaded, all subsequent pages normally > load OK. > 4 - it never happens on my local server when I am doing development. > I am based in Singapore and the site above is hosted in California. > 5 - happens in both Firefox and in IE and happens both at home and at > work > > [a] my site is http://www.runegate.org/whitewall/wiki and is running > from the CVS of about 48 hours ago My site behaves similarly to Charles'. While I said earlier that it only happened with HomePage, it looks like it happens with whatever page is loaded first. Once I load any page successfully, all subsequent pages seem to load correctly from then on. So for example, if I start with: http://www.hollenback.net that page doesn't load. Then if I immediately go to: http://www.hollenback.net/index.php/SilverFox that page loads correctly. However going back to http://www.hollenback.net still shows a broken page. It's not until I shift-reload http://www.hollenback.net at that point that HomePage starts working correctly. P. -- Philip J. Hollenback ph...@po... www.hollenback.net |
From: Philip J. H. <ph...@po...> - 2005-04-27 12:23:40
|
Hmmm, now the problem is back. The HomePage loads quickly now, but it still doesn't load completely. I tested the following: konqueror 3.1.4 on fedora core 1 firefox 1.0 on fc1 firefox 1.0 on win2000 ie 6 on win 2000 Results were exactly the same iwth all os/browser combinations: HomePage stops loading at just about the end of the page, on exactly the same character (my last name at the bottom of the page gets truncated to Hollenbac). So whereas loading the HomePage was really slow before and part of the page was cut off, loading HomePage now is pretty fast and less of the page is cut off. Interesting point: this _only_ happens with HomePage. All the other pages load fine. Now that is baffling. P. On Wed, 27 Apr 2005 09:47:28 +0200, "Stefan" <sonstiges@bayern- mail.de> said: > Hello, > > did you solve your problem because it loads within a maximum of 5 > seconds. and other pages within 2 seconds. This seems to be ok. > (Firefox 1.03) > > Regards Stefan > > > Philip J. Hollenback schrieb: > > >I upgraded www.hollenback.net to 1.3.11-rc3 a couple weeks ago. I > >think it was always in my web browser cache since then so I didn't > >notice a big problem until now. > > > >Page load times on a fresh browser are horrible! To demonstrate, > >kill your IE or Firefox, then start a new one and go to > >http://www.hollenback.net. It loads really, really slowly (like 30 > >seconds instead of expected 2-3), and actually craps out before it > >gets done with the page. The rendering just stops, with a broken bit > >of html at the end. > > > >I thought at first this was due to my switch from the Crao theme to > >the shamino_com theme, but I tried switching back and the problem > >persists. Then I thought it was because of the RawHtml plugin and > >images at the bottom of my HomePage, but I removed those and it > >didn't help. > > > >IE always seems to stop rendering the page at the same place, right > >after HelpfulMuttHints. A forced reload (shift-reload) brings up the > >page correctly. Firefox stops rendering the page in a slightly > >different place but basically it does the same thing. > > > >Anybody got any helpful hints here? This is a major problem > >because everyone who goes to my website for the first time will see > >a broken page. > > > >Thanks, > >P. > >-- > >Philip J. Hollenback ph...@po... www.hollenback.net > > > > > > > >------------------------------------------------------- > >SF.Net email is sponsored by: Tell us your software development > >plans! Take this survey and enter to win a one-year sub to > >SourceForge.net Plus IDC's 2005 look-ahead and a copy of this survey > >Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix > >_______________________________________________ > >Phpwiki-talk mailing list Php...@li... > >https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > > > > > > > > > > -- Philip J. Hollenback ph...@po... www.hollenback.net |
From: Yannick L. <Yan...@en...> - 2005-04-27 12:13:20
|
This sounds very similar to the problem that I have been seeing here on = my installation of RC3. Are you also running on IIS 6.0? I found that this = kind of problem only happened in Firefox though. IE always tends to render = the pages completely. In Firefox, I often have to do a shift-refresh. I = have tried to look at memory and debug but did not find anything either. Yannick Thus spake "Philip J. Hollenback": > No, the html is cut off after a tag, the page is not properly closed. >=20 > I tried setting DEBUG=3D2, no better error messages. >=20 > P. Not to belabor the point, but you're positive that there's nothing in = the error log for your web server? The script isn't supposed to end without either 1) closing the html document, 2) printing an error (and even = then the document gets closed), or 3) PHP chokes and spits out something to the server's error log. If one of those things isn't happening, then we = have a unintentional exit point. Aggravating as it is, if it were my installation, at this point I'd = start adding print statements to try to pin down how far execution gets. =20 =20 ______________________________________=20 Yannick Lefebvre=20 eNGENUITY Technologies Inc=20 Senior Technical Specialist Sp=E9cialiste Technique S=E9nior Tel: (514) 341-3874 Ext. 268=20 Fax: (514) 341-8018=20 yan...@en...=20 www.engenuitytech.com=20 4700 de la Savane, # 300=20 Montr=E9al, Qu=E9bec H4P 1T7 Canada=20 ______________________________________=20 Visual. Software. Solutions.=20 =20 |
From: Philip J. H. <ph...@po...> - 2005-04-27 12:10:42
|
I changed my theme back to default. Initially after I did that the pages were failing to load completely. However, the problem seemed to go away an hour later when I checked again (theme still ste to default). So maybe it is theme-related? I'm confused now. I know that at one point I saw the problem under default, Crao, and shamino_com. My gut feeling is there is some sort of memory-related constraint that my wiki is close to, and it is sometimes hitting it. Perhaps since the default themem is simpler it doesn't hit it as often? P. On Wed, 27 Apr 2005 09:47:28 +0200, "Stefan" <son...@ba...> said: > Hello, > > did you solve your problem because it loads within a maximum of 5 > seconds. and other pages within 2 seconds. > This seems to be ok. (Firefox 1.03) > > Regards Stefan > > > Philip J. Hollenback schrieb: > > >I upgraded www.hollenback.net to 1.3.11-rc3 a couple weeks ago. I think > >it was always in my web browser cache since then so I didn't notice a > >big problem until now. > > > >Page load times on a fresh browser are horrible! To demonstrate, kill > >your IE or Firefox, then start a new one and go to > >http://www.hollenback.net. It loads really, really slowly (like 30 > >seconds instead of expected 2-3), and actually craps out before it gets > >done with the page. The rendering just stops, with a broken bit of html > >at the end. > > > >I thought at first this was due to my switch from the Crao theme to the > >shamino_com theme, but I tried switching back and the problem persists. > >Then I thought it was because of the RawHtml plugin and images at the > >bottom of my HomePage, but I removed those and it didn't help. > > > >IE always seems to stop rendering the page at the same place, right > >after HelpfulMuttHints. A forced reload (shift-reload) brings up the > >page correctly. Firefox stops rendering the page in a slightly > >different place but basically it does the same thing. > > > >Anybody got any helpful hints here? This is a major problem because > >everyone who goes to my website for the first time will see a broken > >page. > > > >Thanks, > >P. > >-- > >Philip J. Hollenback > >ph...@po... > >www.hollenback.net > > > > > > > >------------------------------------------------------- > >SF.Net email is sponsored by: Tell us your software development plans! > >Take this survey and enter to win a one-year sub to SourceForge.net > >Plus IDC's 2005 look-ahead and a copy of this survey > >Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix > >_______________________________________________ > >Phpwiki-talk mailing list > >Php...@li... > >https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > > > > > > > > > > -- Philip J. Hollenback ph...@po... www.hollenback.net |
From: Stefan <son...@ba...> - 2005-04-27 07:47:36
|
Hello, did you solve your problem because it loads within a maximum of 5 seconds. and other pages within 2 seconds. This seems to be ok. (Firefox 1.03) Regards Stefan Philip J. Hollenback schrieb: >I upgraded www.hollenback.net to 1.3.11-rc3 a couple weeks ago. I think >it was always in my web browser cache since then so I didn't notice a >big problem until now. > >Page load times on a fresh browser are horrible! To demonstrate, kill >your IE or Firefox, then start a new one and go to >http://www.hollenback.net. It loads really, really slowly (like 30 >seconds instead of expected 2-3), and actually craps out before it gets >done with the page. The rendering just stops, with a broken bit of html >at the end. > >I thought at first this was due to my switch from the Crao theme to the >shamino_com theme, but I tried switching back and the problem persists. >Then I thought it was because of the RawHtml plugin and images at the >bottom of my HomePage, but I removed those and it didn't help. > >IE always seems to stop rendering the page at the same place, right >after HelpfulMuttHints. A forced reload (shift-reload) brings up the >page correctly. Firefox stops rendering the page in a slightly >different place but basically it does the same thing. > >Anybody got any helpful hints here? This is a major problem because >everyone who goes to my website for the first time will see a broken >page. > >Thanks, >P. >-- >Philip J. Hollenback >ph...@po... >www.hollenback.net > > > >------------------------------------------------------- >SF.Net email is sponsored by: Tell us your software development plans! >Take this survey and enter to win a one-year sub to SourceForge.net >Plus IDC's 2005 look-ahead and a copy of this survey >Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix >_______________________________________________ >Phpwiki-talk mailing list >Php...@li... >https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > > > > |
From: Reini U. <ru...@x-...> - 2005-04-27 06:20:03
|
Philip J. Hollenback schrieb: > I upgraded www.hollenback.net to 1.3.11-rc3 a couple weeks ago. I think > it was always in my web browser cache since then so I didn't notice a > big problem until now. > > Page load times on a fresh browser are horrible! To demonstrate, kill > your IE or Firefox, then start a new one and go to > http://www.hollenback.net. It loads really, really slowly (like 30 > seconds instead of expected 2-3), and actually craps out before it gets > done with the page. The rendering just stops, with a broken bit of html > at the end. I remember having that problem at sf.net and some other servers due to some weird apache directive problems. I don't know where it spent its time, but fixing the .htaccess rewriter, proxy settings, and redirector did help. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ http://phpwiki.org/ |
From: Charles C. <ch...@ru...> - 2005-04-27 05:10:39
|
On Wed, April 27, 2005 12:01, Joel Uckelman said: > Hmm. There were two people seeing this problem, right? If anyone > who has direct access to their logs is experiencing this, it > would be great to hear from you. > > Oh, another thing: Does this happen on every page, or just some? > Do the pages this happens on have anything in common? Can you > send me a link to a page that does this, so I can put the thing > into my test wiki? Further data points: 1 - it happens on several different pages - the first page when I go to the site [a] - whether that first page is the HomePage or RecentEdits. 2 - Just hitting refresh does not always resolve the issue, sometimes shift-refresh is required. 3 - Once a page is correctly loaded, all subsequent pages normally load OK. 4 - it never happens on my local server when I am doing development. I am based in Singapore and the site above is hosted in California. 5 - happens in both Firefox and in IE and happens both at home and at work [a] my site is http://www.runegate.org/whitewall/wiki and is running from the CVS of about 48 hours ago regards, Charles PS I have been too busy to do much on PhpWiki recently, otherwise I would spend time on this issue. |
From: Joel U. <uck...@el...> - 2005-04-27 04:02:01
|
> On 04/26/05, Joel Uckelman wrote: > > Thus spake "Philip J. Hollenback": > > > No, the html is cut off after a tag, the page is not properly closed. > > > > > > I tried setting DEBUG=2, no better error messages. > > > > Not to belabor the point, but you're positive that there's nothing in > > the error log for your web server? The script isn't supposed to end > > without either 1) closing the html document, 2) printing an error (and even > > then the document gets closed), or 3) PHP chokes and spits out something > > to the server's error log. If one of those things isn't happening, then > > we have a unintentional exit point. > > Well, this is hosted by a service provider, and they provide a web > interface to manage my account. That web interface has a button that > says, "error logs". Clicking that button supposedly shows the last 300 > lines of the apache error log. The other stuff displayed on that page > looks like the sort of apache errors one would expect. But I can't be > absolutely certain that all my web server errors are showing up on that > page since I don't know what mechanism is used to create it. Hmm. There were two people seeing this problem, right? If anyone who has direct access to their logs is experiencing this, it would be great to hear from you. Oh, another thing: Does this happen on every page, or just some? Do the pages this happens on have anything in common? Can you send me a link to a page that does this, so I can put the thing into my test wiki? > > Aggravating as it is, if it were my installation, at this point I'd start > > adding print statements to try to pin down how far execution gets. > > Can you point me towards the right files to add print statements to? > I'll start doing that. The entry point is index.php. If you see anything at all, then execution is making it into lib/main.php from there. The main() function is at the bottom. Sprinkle some print statements in there and see how far it gets. -- J. |
From: Philip J. H. <ph...@po...> - 2005-04-27 03:39:36
|
On 04/26/05, Joel Uckelman wrote: > Thus spake "Philip J. Hollenback": > > No, the html is cut off after a tag, the page is not properly closed. > > > > I tried setting DEBUG=2, no better error messages. > > Not to belabor the point, but you're positive that there's nothing in > the error log for your web server? The script isn't supposed to end > without either 1) closing the html document, 2) printing an error (and even > then the document gets closed), or 3) PHP chokes and spits out something > to the server's error log. If one of those things isn't happening, then > we have a unintentional exit point. Well, this is hosted by a service provider, and they provide a web interface to manage my account. That web interface has a button that says, "error logs". Clicking that button supposedly shows the last 300 lines of the apache error log. The other stuff displayed on that page looks like the sort of apache errors one would expect. But I can't be absolutely certain that all my web server errors are showing up on that page since I don't know what mechanism is used to create it. > Aggravating as it is, if it were my installation, at this point I'd start > adding print statements to try to pin down how far execution gets. Can you point me towards the right files to add print statements to? I'll start doing that. Thanks, P. -- Philip J. Hollenback www.hollenback.net |
From: Joel U. <uck...@no...> - 2005-04-27 03:03:55
|
Thus spake "Philip J. Hollenback": > No, the html is cut off after a tag, the page is not properly closed. > > I tried setting DEBUG=2, no better error messages. > > P. Not to belabor the point, but you're positive that there's nothing in the error log for your web server? The script isn't supposed to end without either 1) closing the html document, 2) printing an error (and even then the document gets closed), or 3) PHP chokes and spits out something to the server's error log. If one of those things isn't happening, then we have a unintentional exit point. Aggravating as it is, if it were my installation, at this point I'd start adding print statements to try to pin down how far execution gets. |
From: Philip J. H. <ph...@po...> - 2005-04-27 02:35:42
|
No, the html is cut off after a tag, the page is not properly closed. I tried setting DEBUG=2, no better error messages. P. On 04/26/05, Joel Uckelman wrote: > Thus spake "Philip J. Hollenback": > > I just checked the server logs and there isn't anything there. Your > > idea about php running out of memory makes a lot of sense, though. Is > > there any other debugging I can turn on? > > > > Thanks, > > P. > > Hmm. You could try setting DEBUG = 2 in the wiki's config.ini, and see if > any new errors pop up. > > In your browser, check the source of the html returned when a page hangs. > Is it cut off, or properly closed (i.e., does it end with a </html>)? > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Tell us your software development plans! > Take this survey and enter to win a one-year sub to SourceForge.net > Plus IDC's 2005 look-ahead and a copy of this survey > Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > -- Philip J. Hollenback www.hollenback.net |
From: Joel U. <uck...@no...> - 2005-04-27 01:51:51
|
Thus spake "Philip J. Hollenback": > I just checked the server logs and there isn't anything there. Your > idea about php running out of memory makes a lot of sense, though. Is > there any other debugging I can turn on? > > Thanks, > P. Hmm. You could try setting DEBUG = 2 in the wiki's config.ini, and see if any new errors pop up. In your browser, check the source of the html returned when a page hangs. Is it cut off, or properly closed (i.e., does it end with a </html>)? |
From: Philip J. H. <ph...@po...> - 2005-04-27 01:03:45
|
I just checked the server logs and there isn't anything there. Your idea about php running out of memory makes a lot of sense, though. Is there any other debugging I can turn on? Thanks, P. On 04/26/05, Joel Uckelman wrote: > Thus spake "Charles Corrigan": > > I have the same problem but thought it was due to my setups (multiple layers > > of proxies at work, a hardware firewall and a software > > firewall at home). The point where the page-rendering stops is usually roughl > > y the same place, independent of the size of the page. > > I use both Firefox and IE at home and I use IE at work (with an independent c > > onnection to the US, where my website is hosted) > > > > A shift-reload usually fixes the problem for the remainder of the session. > > > > Regards, > > Charles > > The next time that happens, check your web server logs to see if a PHP error > was generated that isn't being displayed. My money is on this being an out- > of-memory problem, and it works the second time because the wiki is able to > fish some of what it needs out of the cache. > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Tell us your software development plans! > Take this survey and enter to win a one-year sub to SourceForge.net > Plus IDC's 2005 look-ahead and a copy of this survey > Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > -- Philip J. Hollenback www.hollenback.net |
From: Joel U. <uck...@no...> - 2005-04-26 23:59:43
|
Thus spake "Charles Corrigan": > I have the same problem but thought it was due to my setups (multiple layers > of proxies at work, a hardware firewall and a software > firewall at home). The point where the page-rendering stops is usually roughl > y the same place, independent of the size of the page. > I use both Firefox and IE at home and I use IE at work (with an independent c > onnection to the US, where my website is hosted) > > A shift-reload usually fixes the problem for the remainder of the session. > > Regards, > Charles The next time that happens, check your web server logs to see if a PHP error was generated that isn't being displayed. My money is on this being an out- of-memory problem, and it works the second time because the wiki is able to fish some of what it needs out of the cache. |
From: Charles C. <ch...@ru...> - 2005-04-26 23:40:11
|
I have the same problem but thought it was due to my setups (multiple layers of proxies at work, a hardware firewall and a software firewall at home). The point where the page-rendering stops is usually roughly the same place, independent of the size of the page. I use both Firefox and IE at home and I use IE at work (with an independent connection to the US, where my website is hosted) A shift-reload usually fixes the problem for the remainder of the session. Regards, Charles > -----Original Message----- > From: Philip J. Hollenback [mailto:ph...@po...] > Sent: 27 April 2005 04:57 > To: php...@li... > Subject: [Phpwiki-talk] really long page loads and incomplete pages with 1.3.11-rc3 > > I upgraded www.hollenback.net to 1.3.11-rc3 a couple weeks ago. I think > it was always in my web browser cache since then so I didn't notice a > big problem until now. > > Page load times on a fresh browser are horrible! To demonstrate, kill > your IE or Firefox, then start a new one and go to > http://www.hollenback.net. It loads really, really slowly (like 30 > seconds instead of expected 2-3), and actually craps out before it gets > done with the page. The rendering just stops, with a broken bit of html > at the end. > > I thought at first this was due to my switch from the Crao theme to the > shamino_com theme, but I tried switching back and the problem persists. > Then I thought it was because of the RawHtml plugin and images at the > bottom of my HomePage, but I removed those and it didn't help. > > IE always seems to stop rendering the page at the same place, right > after HelpfulMuttHints. A forced reload (shift-reload) brings up the > page correctly. Firefox stops rendering the page in a slightly > different place but basically it does the same thing. > > Anybody got any helpful hints here? This is a major problem because > everyone who goes to my website for the first time will see a broken > page. > > Thanks, > P. > -- > Philip J. Hollenback > ph...@po... > www.hollenback.net |
From: Philip J. H. <ph...@po...> - 2005-04-26 20:57:52
|
I upgraded www.hollenback.net to 1.3.11-rc3 a couple weeks ago. I think it was always in my web browser cache since then so I didn't notice a big problem until now. Page load times on a fresh browser are horrible! To demonstrate, kill your IE or Firefox, then start a new one and go to http://www.hollenback.net. It loads really, really slowly (like 30 seconds instead of expected 2-3), and actually craps out before it gets done with the page. The rendering just stops, with a broken bit of html at the end. I thought at first this was due to my switch from the Crao theme to the shamino_com theme, but I tried switching back and the problem persists. Then I thought it was because of the RawHtml plugin and images at the bottom of my HomePage, but I removed those and it didn't help. IE always seems to stop rendering the page at the same place, right after HelpfulMuttHints. A forced reload (shift-reload) brings up the page correctly. Firefox stops rendering the page in a slightly different place but basically it does the same thing. Anybody got any helpful hints here? This is a major problem because everyone who goes to my website for the first time will see a broken page. Thanks, P. -- Philip J. Hollenback ph...@po... www.hollenback.net |
From: Reini U. <ru...@x-...> - 2005-04-26 20:05:19
|
Torsten Bronger schrieb: > I set user authentication to very strict values for our wiki. > Unfortunately, this means that my newsreader is unable to get the > RSS feed from RecentChanges. Is it possible to authenticate via the > URL with some sort of parameters? Or is it possible to exclude the > RSS from the authentication scheme? I need more information, which kind of security and auth you use. For HttpAuth it's easy to use with certain headers. RecentChanges should be viewable, otherwise you will get no rss feed. If you dont want to open that, setup another (action-)page which uses the RecentChanges plugin and point the rss feed to this page. I assume you use ALLOW_ANON_USER = false. Since you don't allow anonymous views why should anonymous rss work then? -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ http://phpwiki.org/ |
From: Torsten B. <br...@ph...> - 2005-04-26 09:49:08
|
Hallöchen! I set user authentication to very strict values for our wiki. Unfortunately, this means that my newsreader is unable to get the RSS feed from RecentChanges. Is it possible to authenticate via the URL with some sort of parameters? Or is it possible to exclude the RSS from the authentication scheme? Thank you! Tschö, Torsten. -- Torsten Bronger, aquisgrana, europa vetus |
From: Reini U. <ru...@x-...> - 2005-04-26 07:46:10
|
Dan, I saw in wikilens that you introduced a seperate category table, and will (already) need a lot of more tables. I thought for 1.3.12, while working on the SemanticWeb, that we could simply enhance the link table with an additional optional column which describes a link relationship. The default would be "LinksTo", for category this would be "CategoryOf", for other things it might be "ClassOf", or any other, when properly handled by any plugin or lib or InterWikiMap entry. I also want to extend certain InterWikiMap entries to define such relations: "PropertyOf", "SubClassOf", "isa", "has", where each of those relations specifies the relation of the current page to the linked pagename. ALTER TABLE $link_tbl ADD relation CHAR(15) NOT NULL DEFAULT "LinksTo" The StructuredData might then be able to query the link table. Metainformation about the links fort certain groups of pages can be queried in a OWL fashion by some new format handlers. I will setup a wikipage for this proposal. http://phpwiki.org/LinkRelationship What I want: * Enrich the links * Easily define PageGroups (lists of pages) * Use StructuredData (acdropdown - static js dropdowns) PageGroups: like "Status" isa:List * Approved * Incorporated * Pending * Proposed * Rejected and any list widget will just get "Status". createWidget("status", "Status") will see that "Status" isa "List" and calls the List() method of the Widget object, storing the result in the relation "status". As plugin like this: <?plugin Widget relation=page ?> e.g. AnyPage: <?plugin Widget status=Status ?> The state of the Status in AnyPage will be internally stored as link, AnyPage => status:Proposed. To explicitly define some relation simply write status:Proposed, which creates no widget. (db: linkfrom=AnyPage,linkto=Proposed,relation=status) But maybe some special relations should be allowed create their widgets automatically. The page "isa:Relation" could define the behaviour if the relations. each isa:<> must have a proper class definition. AnyPage => statusWidget:Proposed will display the widget and not the link, if statusWidget => isa:Widget So the relation (here statusWidget) should search for an internal class, and then for an external pluginname to define its methods. If no special class is found, it will search for a pagename, which may define an isa:<class> link, where a new search or the parent <class> will start. Yet undefined is what will happen with multimethods (multiple isa: links in a page). CLOS handles this just fine, but I'm not sure about our case here, how to define precedence. The link table is not ordered. And CLOS is method centric, we are unfortunately object centric, where multiple inheritance is hard. Categories are a bigger beast, being a container of multiple objects, with its own properties (has:) and methods (search, display, edit, list). I think my proposal will handle all this. What I get: * Every link relation is bound to a pagename, but not necessarily to a revision. ** So widget properties, categories and so on are self-describing and editable. ** Easily define complex relations and inheritance. * Easily extendable to the InterWikiMap syntax: <moniker>:<pagename> where moniker describes a relationship. -- Reini Urban http://phpwiki.org/ http://xarch.tu-graz.ac.at/home/rurban/ |
From: Reini U. <ru...@x-...> - 2005-04-24 17:31:03
|
Torsten Bronger schrieb: > Moreover, USER_AUTH_METHOD must have been "first-only", because > "strict" yielded > > Fatal error: Call to a member function on a non-object in > /export/websites/9/1/sb003732/wiki/lib/WikiUser/PearDb.php on > line 173 > > when I tried to log in as an unauthorised user. thanks, I'll have a look why this appeared. > By the way, what does "Overlage Session data" mean? that's a stupid php session limitation, which we have to workaround in some way or another. internally only. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ http://phpwiki.org/ |
From: Torsten B. <br...@ph...> - 2005-04-24 17:24:02
|
Hallöchen! Reini Urban <ru...@x-...> writes: > [...] > >> P.S.: By the way, the SQL command to create the table "user" >> failed. I had to create "user_dummy" and rename it later. Why? > > Maybe because the tablename user in the mysql database is > reserved. On usenet I found <news:96tnin$1hb4$1...@Fr...>: It looks like this is occurring because there is a built-in function called 'USER' (which returns the current MySQL user name). The parser is obviously getting confused by this. Tschö, Torsten. -- Torsten Bronger, aquisgrana, europa vetus |
From: Torsten B. <br...@ph...> - 2005-04-24 17:17:51
|
Hallöchen! "Charles Corrigan" <ch...@ru...> writes: >> From: Torsten Bronger [mailto:br...@ph...] >> Sent: 24 April 2005 19:43 >> To: php...@li... >> Subject: [Phpwiki-talk] phpwiki-1.3.11_rc3: Login problems >> >> For the editorial collaborative work on a student newspaper, we need >> a Wiki with some sort authentication, i.e., nobody outside should be >> able to read the draft versions. If this is impossible to achieve, >> at least only authorised people must be able to do any changes. >> >> Is this possible with phpWiki? > > Yes. Have a look at the file doc/README.security - with a small > amount of change, it should be possible to do what you want. Thank you, I managed to customise it to what I wanted. I create new users manually directly in the mySQL database. Later, the user sets his password. (Passwords are encrypted so that I don't see them accidentally, but I recommend my users not to use valuable passwords.) Is this a good approach? >> [...] >> >> No I fiddle around with 1.3.11 RC3. While there is a login and >> password facility, I'm unable to login. It always says "Password >> invalid", no matter which login name I try. What's goind wrong? > > Did you create an admin user id and password in the config.ini? Yes, this was not the problem. The breakthrough was getting rid of the table prefix. Some parts of phpWiki wanted to have a table "user", others "PREFIX_user". The only solution was deleting it. Then, two fields in table "user" were commented out in mysql-initialize.sql (e.g. "groupname"), but I needed them for the Db authentication method. Moreover, USER_AUTH_METHOD must have been "first-only", because "strict" yielded Fatal error: Call to a member function on a non-object in /export/websites/9/1/sb003732/wiki/lib/WikiUser/PearDb.php on line 173 when I tried to log in as an unauthorised user. By the way, what does "Overlage Session data" mean? Tschö, Torsten. -- Torsten Bronger, aquisgrana, europa vetus |
From: Reini U. <ru...@x-...> - 2005-04-24 17:02:34
|
Torsten Bronger schrieb: > Hallöchen! > > For the editorial collaborative work on a student newspaper, we need > a Wiki with some sort authentication, i.e., nobody outside should be > able to read the draft versions. If this is impossible to achieve, > at least only authorised people must be able to do any changes. > Is this possible with phpWiki? sure. just set the admin password and allow nobody to edit. more explicit auth is not needed. ALLOW_ANON_USER = falae ALLOW_ANON_EDIT = false ALLOW_BOGO_LOGIN = false ALLOW_USER_PASSWORDS depends on your USER_AUTH_ORDER. ADMIN_USER may always edit. For mysql users only set USER_AUTH_ORDER = "Db" and ALLOW_USER_PASSWORDS = true. For admin only set ALLOW_USER_PASSWORDS = false. > At first I installed v1.2 due to mySQL timeout problems (it's set to > 10 seconds here). I didn't see any reasonable system of > authentication at all, or did I miss it? > > No I fiddle around with 1.3.11 RC3. While there is a login and > password facility, I'm unable to login. It always says "Password > invalid", no matter which login name I try. What's goind wrong? > > I didn't modify the default settings very much. I just changed to > mySQL since our university server doesn't allow to write in the file > system. The table prefix is "phpwiki_", however, "user", "member", > and "pref" don't have prefixes (as said in the docs). Please change your table names to have the same prefixes. And change the DBAUTH config.ini settings for the phpwiki_ prefix. > P.S.: By the way, the SQL command to create the table "user" failed. > I had to create "user_dummy" and rename it later. Why? Maybe because the tablename user in the mysql database is reserved. But then you must have been incredibly stupid to create your tables in the mysql database which I doubt. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ http://phpwiki.org/ |
From: Charles C. <ch...@ru...> - 2005-04-24 14:39:27
|
> From: Torsten Bronger [mailto:br...@ph...] > Sent: 24 April 2005 19:43 > To: php...@li... > Subject: [Phpwiki-talk] phpwiki-1.3.11_rc3: Login problems >=20 > Hall=F6chen! >=20 > For the editorial collaborative work on a student newspaper, we need > a Wiki with some sort authentication, i.e., nobody outside should be > able to read the draft versions. If this is impossible to achieve, > at least only authorised people must be able to do any changes. >=20 > Is this possible with phpWiki? Yes. Have a look at the file doc/README.security - with a small amount = of change, it should be possible to do what you want. > At first I installed v1.2 due to mySQL timeout problems (it's set to > 10 seconds here). I didn't see any reasonable system of > authentication at all, or did I miss it? >=20 > No I fiddle around with 1.3.11 RC3. While there is a login and > password facility, I'm unable to login. It always says "Password > invalid", no matter which login name I try. What's goind wrong? Did you create an admin user id and password in the config.ini? = (Preferably an encrypted password, not plain text). This user id does not appear in the user table and you should be able to log in with = this id. Did you uncomment/enable the auto-create statement? It should be = something like: DBAUTH_AUTH_CREATE =3D "INSERT INTO user SET = passwd=3DPASSWORD('$password'),userid=3D'$userid'" > I didn't modify the default settings very much. I just changed to > mySQL since our university server doesn't allow to write in the file > system. The table prefix is "phpwiki_", however, "user", "member", > and "pref" don't have prefixes (as said in the docs). >=20 > Thank you for any hints! >=20 > Tsch=F6, > Torsten. >=20 > P.S.: By the way, the SQL command to create the table "user" failed. > I had to create "user_dummy" and rename it later. Why? > -- > Torsten Bronger, aquisgrana, europa vetus Regards, Charles |
From: Torsten B. <br...@ph...> - 2005-04-24 11:55:15
|
Hallöchen! For the editorial collaborative work on a student newspaper, we need a Wiki with some sort authentication, i.e., nobody outside should be able to read the draft versions. If this is impossible to achieve, at least only authorised people must be able to do any changes. Is this possible with phpWiki? At first I installed v1.2 due to mySQL timeout problems (it's set to 10 seconds here). I didn't see any reasonable system of authentication at all, or did I miss it? No I fiddle around with 1.3.11 RC3. While there is a login and password facility, I'm unable to login. It always says "Password invalid", no matter which login name I try. What's goind wrong? I didn't modify the default settings very much. I just changed to mySQL since our university server doesn't allow to write in the file system. The table prefix is "phpwiki_", however, "user", "member", and "pref" don't have prefixes (as said in the docs). Thank you for any hints! Tschö, Torsten. P.S.: By the way, the SQL command to create the table "user" failed. I had to create "user_dummy" and rename it later. Why? -- Torsten Bronger, aquisgrana, europa vetus |