Menu
▾
▴
phpwiki-talk
|
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: Reini U. <ru...@x-...> - 2005-05-06 10:08:19
|
Philip J. Hollenback schrieb: > Hi Everyone, > > So I'm still experiencing this problem of pages not loading all the way. > I just tested a few minutes ago and it's still occuring. > > Again, there are no errors in my apache logs and I can't troubleshoot > much further because this is a hosted setup. > > I've seen this connecting from several different locations and with > several different browsers. I've had other people in different cities > check my page and they've seen the same problems. > > But others on this list have replied that they have gone to > www.hollenback.ent and everything looks fine. > > The one suggestion I got was to sprinkle some print statements into the > phpwiki code to see where it is dying. I guess I will try that... does > anyone else have any ideas? Don't use printf, use echo instead. There's some problem with print and output buffering I didn't care to report at the php-dev list yet. Any printf in any plugin, template, code will eventually bypass the buffering, thus fooling the http headers. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ http://phpwiki.org/ |
|
From: Philip J. H. <ph...@po...> - 2005-05-06 14:53:52
|
I followed your suggestion and used echo. I've found that placing echo " "; anywhere in the program execution before the call to this->Request in function WikiRequest in lib/main.php causes the pages to output fully. Of course my website now looks like crap because this causes a bunch of php warnings to be printed after all the regular output. Still, that's better than it taking forever to load and cutting off the pages. So it seems like my phpwiki is sitting around waiting for some output which never finishes? Then it eventually times out and dumps what it does have? That would explain both the long load delay and the end of my wiki pages being cut off. I haven't yet begun to dig into the Request function in lib/Request.php to see if I can isolate this further. Any phpwiki developers care to hazard a guess what might be going on here? P. On Fri, 06 May 2005 12:10:00 +0200, "Reini Urban" <rurban@x- ray.at> said: > Philip J. Hollenback schrieb: > > Hi Everyone, > > > > So I'm still experiencing this problem of pages not loading all the > > way. I just tested a few minutes ago and it's still occuring. > > > > Again, there are no errors in my apache logs and I can't > > troubleshoot much further because this is a hosted setup. > > > > I've seen this connecting from several different locations and with > > several different browsers. I've had other people in different > > cities check my page and they've seen the same problems. > > > > But others on this list have replied that they have gone to > > www.hollenback.ent and everything looks fine. > > > > The one suggestion I got was to sprinkle some print statements into > > the phpwiki code to see where it is dying. I guess I will try > > that... does anyone else have any ideas? > > Don't use printf, use echo instead. There's some problem with print > and output buffering I didn't care to report at the php-dev list yet. > > Any printf in any plugin, template, code will eventually bypass the > buffering, thus fooling the http headers. > -- > Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ > http://phpwiki.org/ -- Philip J. Hollenback ph...@po... www.hollenback.net |
|
From: Philip J. H. <ph...@po...> - 2005-05-24 19:07:21
|
Hmmm, I haven't made any progress debugging this. Has anyone else come up with anything? Current status is my website works ok if I put that echo statement in the code. However, the piles of big red error boxes at the bottom of every page are really freaking ugly. P. On Fri, 06 May 2005 10:53:33 -0400, "Philip J. Hollenback" <ph...@po...> said: > I followed your suggestion and used echo. I've found that placing > > echo " "; > > anywhere in the program execution before the call to this->Request in > function WikiRequest in lib/main.php causes the pages to output fully. > > Of course my website now looks like crap because this causes a > bunch of php warnings to be printed after all the regular output. > Still, that's better than it taking forever to load and cutting off > the pages. > > So it seems like my phpwiki is sitting around waiting for some output > which never finishes? Then it eventually times out and dumps what it > does have? That would explain both the long load delay and the end of > my wiki pages being cut off. > > I haven't yet begun to dig into the Request function in > lib/Request.php to see if I can isolate this further. Any phpwiki > developers care to hazard a guess what might be going on here? > > P. > > On Fri, 06 May 2005 12:10:00 +0200, "Reini Urban" <rurban@x- > ray.at> said: > > Philip J. Hollenback schrieb: > > > Hi Everyone, > > > > > > So I'm still experiencing this problem of pages not loading all > > > the way. I just tested a few minutes ago and it's still occuring. > > > > > > Again, there are no errors in my apache logs and I can't > > > troubleshoot much further because this is a hosted setup. > > > > > > I've seen this connecting from several different locations and > > > with several different browsers. I've had other people in > > > different cities check my page and they've seen the same problems. > > > > > > But others on this list have replied that they have gone to > > > www.hollenback.ent and everything looks fine. > > > > > > The one suggestion I got was to sprinkle some print statements > > > into the phpwiki code to see where it is dying. I guess I will > > > try that... does anyone else have any ideas? > > > > Don't use printf, use echo instead. There's some problem with > > print and output buffering I didn't care to report at the php-dev > > list yet. > > > > Any printf in any plugin, template, code will eventually bypass the > > buffering, thus fooling the http headers. -- Philip J. Hollenback ph...@po... www.hollenback.net |
|
From: Reini U. <ru...@x-...> - 2005-05-24 19:24:40
|
sorry. not yet. but it's high priority on my todo list. > Hmmm, I haven't made any progress debugging this. Has anyone else come > up with anything? > > Current status is my website works ok if I put that echo statement in > the > code. However, the piles of big red error boxes at the bottom of every > page are really freaking ugly. > > P. > > On Fri, 06 May 2005 10:53:33 -0400, "Philip J. Hollenback" > <ph...@po...> said: >> I followed your suggestion and used echo. I've found that placing >> >> echo " "; >> >> anywhere in the program execution before the call to this->Request in >> function WikiRequest in lib/main.php causes the pages to output fully. >> >> Of course my website now looks like crap because this causes a >> bunch of php warnings to be printed after all the regular output. >> Still, that's better than it taking forever to load and cutting off >> the pages. >> >> So it seems like my phpwiki is sitting around waiting for some output >> which never finishes? Then it eventually times out and dumps what it >> does have? That would explain both the long load delay and the end of >> my wiki pages being cut off. >> >> I haven't yet begun to dig into the Request function in >> lib/Request.php to see if I can isolate this further. Any phpwiki >> developers care to hazard a guess what might be going on here? >> >> P. >> >> On Fri, 06 May 2005 12:10:00 +0200, "Reini Urban" <rurban@x- >> ray.at> said: >> > Philip J. Hollenback schrieb: >> > > Hi Everyone, >> > > >> > > So I'm still experiencing this problem of pages not loading all >> the way. I just tested a few minutes ago and it's still occuring. >> > > >> > > Again, there are no errors in my apache logs and I can't >> > > troubleshoot much further because this is a hosted setup. >> > > >> > > I've seen this connecting from several different locations and >> with several different browsers. I've had other people in >> > > different cities check my page and they've seen the same problems. >> > > >> > > But others on this list have replied that they have gone to >> > > www.hollenback.ent and everything looks fine. >> > > >> > > The one suggestion I got was to sprinkle some print statements >> into the phpwiki code to see where it is dying. I guess I will >> try that... does anyone else have any ideas? >> > >> > Don't use printf, use echo instead. There's some problem with >> > print and output buffering I didn't care to report at the php-dev >> list yet. >> > >> > Any printf in any plugin, template, code will eventually bypass the >> buffering, thus fooling the http headers. > -- > Philip J. Hollenback > ph...@po... > www.hollenback.net > > > > ------------------------------------------------------- > This SF.Net email is sponsored by Yahoo. > Introducing Yahoo! Search Developer Network - Create apps using Yahoo! > Search APIs Find out how you can build Yahoo! directly into your own > Applications - visit > http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk -- Reini Urban http://phpwiki.org/ http://xarch.tu-graz.ac.at/home/rurban/ |
|
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: 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: 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-05-05 13:01:21
|
Hi Everyone, So I'm still experiencing this problem of pages not loading all the way. I just tested a few minutes ago and it's still occuring. Again, there are no errors in my apache logs and I can't troubleshoot much further because this is a hosted setup. I've seen this connecting from several different locations and with several different browsers. I've had other people in different cities check my page and they've seen the same problems. But others on this list have replied that they have gone to www.hollenback.ent and everything looks fine. The one suggestion I got was to sprinkle some print statements into the phpwiki code to see where it is dying. I guess I will try that... does anyone else have any ideas? If anyone on the list could go to www.hollenback.net and see if the bottom of the HomePage is cut off or not, I would appreciate it. Thanks, P. On Wed, 27 Apr 2005 08:36:38 -0400, "Philip J. Hollenback" <ph...@po...> said: > 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. -- Philip J. Hollenback ph...@po... www.hollenback.net |
|
From: Robert C. J. <ro...@ar...> - 2005-05-05 13:09:46
|
At 9:01 on 5 May 2005, Philip J. Hollenback <ph...@po...> wrote: > If anyone on the list could go to www.hollenback.net and see if the > bottom of the HomePage is cut off or not, I would appreciate it. I just went there. It took about 20 seconds to load. It looks like it's all there. Nothing obviously broken. These were the bottom two lines on the page: -----8<----- * Linux on the Toshiba Portege 610CT or the Fujitsu N3010 Lifebook Owner: PhilHollenback Last edited on April 28, 2005 3:34 pm by PhilHollenbac -----8<----- Firefox 1.0.3 on Win98SE -- Rob Croson (ro...@ar...) Member of the Pegasus Mail and Mercury/32 Beta Test Teams Pegasus Mail and Mercury/32 Portal: http://email.arcm.com Visit the MailWiki: http://email.arcm.com/wiki |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X