Undefined Offset (datetime) in form

(Kieran@parracity) #1

Hi guys,


Just updated a form that was working fine.



Deleted one field and added two. Updated the bodycopy so it isn't referencing the old field keyword, but the new ones instead.

Getting this error twice:


    PHP Notice
    File:	[SYSTEM_ROOT]/core/assets/form/form_question_types/form_question_type_datetime/form_question_type_datetime.inc	Line:	273
    Message:	Undefined offset: 1


??
(Ashish Karelia) #2

Hi,
When are you getting this error? On form load or when viewing the submissions?

Also what Matrix version are you on?



Ash

(Kieran@parracity) #3

Hi Ashish,


v4.10.1

On viewing the form.

(Kieran@parracity) #4

go to:
http://www.parracity.nsw.gov.au/live/my_home/parking__and__transport/parking/ParkingMeterEnquiry

if it helps



Then do a /_nocache

(Ashish Karelia) #5

Hi,
This is very strange (without a backtrace of the error) as to why this particular function is called on printing the form initially.

I can surely see the error occurring but can't figure out why just looking at the code. Matrix is getting unexpected value where the error is being raised from.

Is the settings on the DateTime Question filed set up properly? (may be a screen shot of what it looks like?)



If the issue is critical and if you are Squiz Client then I'd say raise a support ticket for someone in Squiz to have a look at it and resolve the issue asap.



Ash

(Kieran@parracity) #6

These are the 2 screen shots of the only date/times in the form.

9uTVh.gif1186x815


If0vJ.gif1186x815




The email is set to just output the form submission.



I deleted a select field and added the 2 check box list fields.

(Ashish Karelia) #7

Hi,
I gave it a try with the settings you provided but it is not doing anything funny. what is still strange is execution path reach the functions (which is causing error) on the first form load.

There is surely something funny going on. And it is very difficult to determine without debugging.



Sorry for not being of much help here but I reckon this is farthest I help.



Ash

(Kieran@parracity) #8

It's your date/time field allow blank bug with client side validation on, still in effect.
Temporarily solved.