[wp-hackers] Size limit on post.

James Collins james at om4.com.au
Mon May 24 06:59:35 UTC 2010


FYI, the relevant trac ticket is: http://core.trac.wordpress.org/ticket/8553




On 22 May 2010 20:28, Dion Hulse (dd32) <wordpress at dd32.id.au> wrote:

> I'm not entirely sure, But according to google, this should do:
>
>
> [Pcre]
> pcre.backtrack_limit=1000000
> pcre.recursion_limit=1000000
>
>
> (I added the 0 on there too btw)
>
>
> On Sat, 22 May 2010 20:21:58 +1000, Arlen Beiler <arlenbee at gmail.com>
> wrote:
>
>  Well, it didn't work, so I added another 0 to each number and then it
>> worked. Thanks Dion. Also, how do I define this in php.ini?
>>
>> On Sat, May 22, 2010 at 6:18 AM, Dion Hulse (dd32) <wordpress at dd32.id.au
>> >wrote:
>>
>>  Neither. They're the number of times the regular expression library is
>>> able
>>> to backtrace, and the number its allowed to recurse, in a extremely
>>> simple
>>> expression, on a large peice of text, it'll only use very little, when
>>> you
>>> use a large piece of text, with a complex expression, it can often cause
>>> the
>>> backtracing to increase as it attempts to match the longer text.
>>>
>>> Other than trial and error, Its not possible to say what value you'd
>>> need,
>>> or if its even caused by this.
>>>
>>>
>>> On Sat, 22 May 2010 20:14:35 +1000, Arlen Beiler <arlenbee at gmail.com>
>>> wrote:
>>>
>>>  Thanks, I will try that. Is that in bytes or kilobytes?
>>>
>>>>
>>>> On Fri, May 21, 2010 at 9:10 PM, Dion Hulse (dd32) <
>>>> wordpress at dd32.id.au
>>>> >wrote:
>>>>
>>>>  I'd say you're hitting the memory limit/backtrace limit of the Preg
>>>>
>>>>> Regular
>>>>> expressions on your server.
>>>>>
>>>>> wpautop and wptexturize can sometimes hit it with larger posts.
>>>>>
>>>>> Have a look at phpinfo() for pcre.backtrack_limit &
>>>>> pcre.recursion_limit
>>>>> (Report back on their size?)
>>>>>
>>>>> You may be able to add this to your wp-config.php file:
>>>>>
>>>>> ini_set('pcre.backtrack_limit', '100000');
>>>>> ini_set('pcre.recursion_limit', '100000');
>>>>>
>>>>> And see if that helps? You could try upping the limits even further if
>>>>> it
>>>>> doesnt, just to test it.
>>>>> (Note: Those values are what my default install has set, No idea if
>>>>> they're
>>>>> high enough, too high, or what)
>>>>>
>>>>> Cheers
>>>>> Dion
>>>>>
>>>>>
>>>>> On Sat, 22 May 2010 03:48:13 +1000, Arlen Beiler <arlenbee at gmail.com>
>>>>> wrote:
>>>>>
>>>>>  No plugins that hook onto it. It is not there in source view. And
>>>>> there
>>>>>
>>>>>  are
>>>>>> no comments or anything in its place.
>>>>>>
>>>>>> On Fri, May 21, 2010 at 1:07 PM, Brian Layman <bulk at thecodecave.com>
>>>>>> wrote:
>>>>>>
>>>>>>  "probably their"=>"probably there,"
>>>>>>
>>>>>>
>>>>>>> Stupid spell checker...
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: wp-hackers-bounces at lists.automattic.com
>>>>>>> [mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of Brian
>>>>>>> Layman
>>>>>>> Sent: Friday, May 21, 2010 1:04 PM
>>>>>>> To: wp-hackers at lists.automattic.com
>>>>>>> Subject: Re: [wp-hackers] Size limit on post.
>>>>>>>
>>>>>>> How does it look in HTML view?
>>>>>>>
>>>>>>> If this content was originated in something other than WordPress,
>>>>>>> your
>>>>>>> content is probably their with some extra html or CSS that is causing
>>>>>>> issues.
>>>>>>>
>>>>>>> I'd start first with that. What does view source on the page reveal?
>>>>>>>
>>>>>>> -Brian Layman
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> wp-hackers mailing list
>>>>>>> wp-hackers at lists.automattic.com
>>>>>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> wp-hackers mailing list
>>>>>>> wp-hackers at lists.automattic.com
>>>>>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>>>>>>
>>>>>>>  _______________________________________________
>>>>>>>
>>>>>>>  wp-hackers mailing list
>>>>>> wp-hackers at lists.automattic.com
>>>>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>>>>>
>>>>>>
>>>>>>
>>>>>>  --
>>>>> Dion Hulse / dd32
>>>>> Contact:
>>>>>  e: contact at dd32.id.au
>>>>>  Web: http://dd32.id.au/
>>>>>
>>>>> _______________________________________________
>>>>> wp-hackers mailing list
>>>>> wp-hackers at lists.automattic.com
>>>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>>>>
>>>>>  _______________________________________________
>>>>>
>>>> wp-hackers mailing list
>>>> wp-hackers at lists.automattic.com
>>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>>>
>>>>
>>>>
>>> --
>>> Dion Hulse / dd32
>>> Contact:
>>>  e: contact at dd32.id.au
>>>  Web: http://dd32.id.au/
>>> _______________________________________________
>>> wp-hackers mailing list
>>> wp-hackers at lists.automattic.com
>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>>
>>>  _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
>>
>
> --
> Dion Hulse / dd32
> Contact:
>  e: contact at dd32.id.au
>  Web: http://dd32.id.au/
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>


More information about the wp-hackers mailing list