Large number of form elements results in PHP warnings, then breakage
Permalink Browser Info Environment
I'm building a survey form. When I get past a certain number of form elements, I start getting PHP warnings and eventually get to the point that no more elementscan be added to the form. The warnings seem to start around 31-32 elements. I presently have 47 elements and can add no more.
Warning: preg_match_all() [function.preg-match-all]: Compilation failed: regular expression is too large at offset 76837 in /home1/laserwor/public_html/updates/concrete5.6.2.1_updater/concrete/libraries/3rdparty/urlify.php on line 208
Warning: Cannot modify header information - headers already sent by (output started at /home1/laserwor/public_html/updates/concrete5.6.2.1_updater/concrete/libraries/3rdparty/urlify.php:208) in /home1/laserwor/public_html/updates/concrete5.6.2.1_updater/concrete/core/libraries/view.php on line 957
Warning: preg_match_all() [function.preg-match-all]: Compilation failed: regular expression is too large at offset 76837 in /home1/laserwor/public_html/updates/concrete5.6.2.1_updater/concrete/libraries/3rdparty/urlify.php on line 208
Warning: Cannot modify header information - headers already sent by (output started at /home1/laserwor/public_html/updates/concrete5.6.2.1_updater/concrete/libraries/3rdparty/urlify.php:208) in /home1/laserwor/public_html/updates/concrete5.6.2.1_updater/concrete/core/libraries/view.php on line 957
Type: | Discussion |
---|---|
Status: | Resolved |
Also: at first it was only printing the error messages in the form design tool. Now it's printing them all over the web page that visitors can see.
That is an issue that I didn't test....
Seems to me it looks like some kind of memory bounds thingy....
I did stumble on such kind of problem on another project, but I can't recall what the solution for this was...
I need to check this...
Best,
Corretje
Seems to me it looks like some kind of memory bounds thingy....
I did stumble on such kind of problem on another project, but I can't recall what the solution for this was...
I need to check this...
Best,
Corretje
Okay, I fixed it. I put the fix into the 5.6.3.1 folder rather than the 5.6.2.1 folder. The Concrete5 update downloaded but was never installed, so the system was using the other folder.
Is this fixed in 5.6.3.1 or do I need to reapply the patch?
Is this fixed in 5.6.3.1 or do I need to reapply the patch?
Great! I don't no if they fixed it. I did mention it..
http://www.concrete5.org/marketplace/addons/formidable/forums/preg_...