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. |