Warning: Compilation failed: regular expression too large at offset 0 in /var/www/html/terrapin/core/core.template.php on line 531

is the message I get when trying to access *particularly long* posts.

Is this a limit of php and/or RegExp generally? or a configuration issue? has anyone a clue?

TIA
ward

Just contributing some information I found.

It appears there is some kind of upper limit on the size of regular expressions in PHP.  Some sources discussing or confirming this.  Most of the sources were discussing things like ban lists, so it might be something like an IP Ban list or Blacklist causing this.

thanks—this is interesting, I’ve run into the

“Cannot modify header information - headers already sent by “

message too, before.

But I don’t have any IP addresses banned, yet. So it must be some regular expression(s) used to manage those particular blacklists, and they are very large, rather than just the fact that it was an IP banning issue.

Interesting that it would crop up mainly in the context of managing banned IPs—spam is really overwhelming in so many ways! but probably it is some 256k limit or something?

The “cannot modify header” warning is simply caused by the other error.  When the first error is taken care of, the second will go away on its own.

I don’t think the issue is really particular to IP banning or anything; rather banning routines simply tend to run very large regular expressions and thus would be more likely than other operations to hit this limit (whatever it is).

Hopefully the developers will have some more concrete ideas than I do! [grin]

Based on the line number that regex is the one that is replacing the contents of an EE tag with a special marker.  How big is this template of yours?  It would seem to be quite a large template or tag to cause memory to run out.

Same error :(

Not blacklists, nor banned IP

The template is short (no more than 20 lines, but embedding other templates), and uses the {exp:weblog:category_heading} and {exp:weblog:entries} tags.

It started crashing calling one specific category for which a long article was recently inserted.

Finally I discovered that removing the {exp:filter_html} solved the problem.

Maybe it helps.