Buy Now
Sign in

Warning: Cannot use a scalar value as an array

havex , May 22 2017, 09:40
H
havex 64
May 22 2017, 09:40 #368437
After I set the Joomla error reporting to "Simple'. I see that next to every field there is this warning:

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.
admin 29
May 22 2017, 13:31 #368464
Hi havex,

Where exactly ? please post a screenshot.

Best regards,
Max
H
havex 64
May 22 2017, 13:54 #368468
Hi Max,

This is the screenshot of the multi page form demo.

Firefox_Screenshot_2017-05-22T13-47-14.795Z.png

I am not sure yet, but it seems this error only occurs with multi-page forms.
Attachments
Firefox_Screenshot_2017-05-22T13-47-14.795Z.png
Firefox_Screenshot_2017-05-22T13-47-14.795Z.png
(17.37 KiB)
1270 Downloads/Views
R
richarddhill 19
June 09 2017, 10:13 #369153
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
GreyHead 64
June 09 2017, 13:04 #369163
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
ChronoForms technical support
If you'd like to buy me a coffee or two, thank you very much
R
richarddhill 19
June 09 2017, 13:24 #369168
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
GreyHead 64
June 09 2017, 15:10 #369175
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
ChronoForms technical support
If you'd like to buy me a coffee or two, thank you very much
healyhatman 9
June 19 2017, 01:54 #369544
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.
Web developer at SkySpider.com.au - I DO NOT work for ChronoEngine!
Donations: paypal.me/healyhatman
Professional Work: kamron@skyspider.com.au
Custom CF / CC Plugins and Extensions: skyspider.com.au/store
healyhatman 9
June 19 2017, 02:06 #369545
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.
Web developer at SkySpider.com.au - I DO NOT work for ChronoEngine!
Donations: paypal.me/healyhatman
Professional Work: kamron@skyspider.com.au
Custom CF / CC Plugins and Extensions: skyspider.com.au/store