LemonStand Forum: form validation [required|optional] not used - LemonStand Forum

I am not sure if it is just me, or because it is happening when extending the product model but I am noticing that if validation is added to a field at all, it becomes required. Furthermore, calling optional on that field's validation does nothing to make it optional.

The following says that it is required.

$product->define_column('x_in_stock_date', 'In Stock Date')->validation();

As well as the following.

$product->define_column('x_in_stock_date', 'In Stock Date')->validation()->optional();

The only way around this is to not use any validation.

$product->define_column('x_in_stock_date', 'In Stock Date')

Updating status to: Unconfirmed

Hi Joe,

I tested your example and had no issues saving the product with the custom field left empty. What kind of validation are you using? Can you share the module code? Feel free to send it in a ticket.

Thank you

Manca, on 11 April 2012 - 03:34 PM, said:

I think it may have been dates.

I went back and looked over it, and it wasn't a required field, but rather that the date wasn't the right format. I had assumed that it would remain optional if I did nothing, and I even tried to explicitly set it to optional. Is there a way to make date, time and any others which may have a specific format to match not cause a fail if blank is matched?

Right now you can't add any validation to a datetime field which should be a bug.

Easy way to test should be, add a new datetime field:

$product->define_column('x_in_stock_date', 'In Stock Date')->validation();

You should see a bunch of errors when trying to edit the value.

It ties in with this other bug:
http://forum.lemonst...eld-not-saving/