After I set the Joomla error reporting to "Simple'. I see that next to every field there is this warning:
I first noticed this issue with CF6.0.4 and it's still showing after updating to CF6.0.5.
Warning: Cannot use a scalar value as an array in ../public_html/libraries/cegcore2/libs/arr.php(71) : eval()'d code on line 1
I first noticed this issue with CF6.0.4 and it's still showing after updating to CF6.0.5.
Hi havex,
Where exactly ? please post a screenshot.
Best regards,
Max
Where exactly ? please post a screenshot.
Best regards,
Max
Hi Max,
This is the screenshot of the multi page form demo.
[attachment=108512_20170522134956_firefox-screenshot-2017-05-22t13-47-14-795z-png.png][/attachment]
I am not sure yet, but it seems this error only occurs with multi-page forms.
This is the screenshot of the multi page form demo.
[attachment=108512_20170522134956_firefox-screenshot-2017-05-22t13-47-14-795z-png.png][/attachment]
I am not sure yet, but it seems this error only occurs with multi-page forms.
Hi,
We are getting exactly the same problem. Is there an answer to this problem, please when we start with "advanced forms" and load multiple sections.
Richard
We are getting exactly the same problem. Is there an answer to this problem, please when we start with "advanced forms" and load multiple sections.
Richard
Hi,
I think that this is a problem with PHP 7.1 - there is a fix for CFv5 posted by user jcmd73 in this post Checking the arr.php it looks as if the same code is used there but at line 71 instead of line 60
Bob
I think that this is a problem with PHP 7.1 - there is a fix for CFv5 posted by user jcmd73 in this post Checking the arr.php it looks as if the same code is used there but at line 71 instead of line 60
Bob
Hi,
OK, we will follow this, but any chance of a Chronoforms update to fix this issue, so we don't have to deal with it on a case by case basis?
Richard
OK, we will follow this, but any chance of a Chronoforms update to fix this issue, so we don't have to deal with it on a case by case basis?
Richard
Hi Richard,
I'm sure that Max will add a fix to a future release. On my part I can't even check the fix as my host isn't yet offering PHP 7,1 :-(
Bob
I'm sure that Max will add a fix to a future release. On my part I can't even check the fix as my host isn't yet offering PHP 7,1 :-(
Bob
I'm getting this error too. I have a form split into partition areas. This error comes up when I add a file field, but it persists even after removing the field. The only way to fix it is to remove the file field and change the form alias to something that hasn't been used yet. Clearing the database cache doesn't help.
I've spent several hours now trying to fix this issue because I need a link and a file upload on my form.
I've spent several hours now trying to fix this issue because I need a link and a file upload on my form.
Sorry comes up when I add a link field, not a file field.
EDIT: Comes up when I add a custom HTML area that contains an <a..> element. The error goes away if I leave the area in, but rename the form's alias. Comes back again if I change the alias back.
EDIT: Comes up when I add a custom HTML area that contains an <a..> element. The error goes away if I leave the area in, but rename the form's alias. Comes back again if I change the alias back.
This topic is locked and no more replies can be posted.