slack
Hi,
I've just installed dokuwiki on Kubuntu 7.10 and for the most part it's working fine, except that very large pages (in the realm of 20,000 words, but text only) aren't being parsed -- the wiki source just seems to be dumped unformatted (although the usual header and footer is still output). I can divide the page into two smaller pages which are both rendered properly, so as far as I can tell there isn't a problem with the wiki source, it's just a matter of the page size.
Is this a deliberate limit? Is there some configuration option somewhere that tells it the maximum page size to parse?
I'll attach a screenshot to show you what I mean.
Thanks for your help.
Dan
chi
Increasing the max_memory_limit in your php.ini should help with this.
slack
Thanks for your suggestion, Chi.
I've tried increasing memory_limit from 128M to 512M and I still get the same result. Could it really take more than half a gig to mark up 20,000 words of text? max_execution_time is 30 seconds and it never takes that long to run.
Any other thoughts?
jm-zz
I had the same problems with big tables.
Perhaps there is a troubleshoot because of too much plugins (love them....). Perhaps like chi write, by server parameters it is possible to improve this behavior ?
___> test on a fresh DokuWiki install without plugins, your page.
___> Explore your php.ini ... and find the good parameters. Perhaps you server is quite low hardware ?
andi
Check your webserver error log, it should tell you what goes wrong. You might be hitting some PCRE limit somewhere.
slack
jm_zz: I am not using any plugins (I've only just installed dokuwiki). The "server" I'm using is just my laptop, 512mb ram, 1.7ghz Pentium. I really don't think it ought to be struggling with this. I have looked through my php.ini (which I haven't changed from the default kubuntu package apart from increasing the memory it's allowed to use) but nothing has leapt out at me. I tried to attach it, but I get "invalid attachment file" from the forum. I could copy-paste it if it's important.
andi: Nothing is appearing in my error log. Which I'd expect, because the entire page is being output, albeit not marked up -- and therefore it seems more likely that it is dokuwiki that is "giving up" somehow and dumping its source as an error mechanism, rather than this being a problem at the level of PHP or my web server. At least, that's my guess.
slack
I can't copy-paste either, as there is a limit on post length.
andi
can you email me the source of your page? andi at splitbrain dot org
slack
Sent. Let me know if you don't receive it.
andi
Haven't got anything yet. What was your subject line? Maybe it got caught in the spam filter.
slack
Subject: Source of dokuwiki page.
slack
Date: Tue, 19 Feb 2008 09:37:45 +1100
Subject: Source of dokuwiki page.
andi
nothing. could you please send it again or upload it somewhere?
andi
The devel version is somewhat cleverer in catching the error :-). Here is what I get:
A PCRE backtrack error occured. Try to increase the pcre.backtrack_limit in php.ini
Just follow the advice ;-)
slack
Great, it sounds like you've tracked down the problem.
Could you tell me what you needed to increase pcre.backtrace_limit to in order for it to work? I've tried increasing it a thousandfold and I get the same result.
I'm editing apache's main php.ini file -- that's the relevant one, isn't it? I haven't added a php.ini to dokuwiki.
Thanks for your help.
slack
Can anybody actually get this page to parse by increasing the size of pcre.backtrace_limit? If so, could you let me know a value that works for you? The source is still at
http://home.silencescape.net/~slack/broken-page.source
If not, then this would seem to be a bug that gobbles all available memory for some reason.
grahack
Hi,
First, after few attempts, I managed to parse your page BUT without the '**' formatting in the first line, and this without touching php.ini (in fact there is no pcre thing in my basic xampp install). This doesn't solve your problem but I found this to be quite interesting.
Then, I don't understand
I haven't added a php.ini to dokuwiki
slack
Grahack,
Thanks, that's really useful. At least this confirms my suspicion that this is some sort of bug rather than just me not having configured my server properly. I should be able to submit a useful bug report now.
By "I haven't added a php.ini to dokuwiki" I just meant that I hadn't added a separate PHP configuration file to the site -- I was just trying to track down exactly which PHP config file it was that was determining the PCRE limit. I assume a site-specific one would have overridden the default Apache one.
Thanks for your help.