DataMapper doesn’t do anything with repopulating forms, why would a repopulation issue be related to DataMapper?

As far as I have seen, DataMapper doesn’t run CI’ FormValidation rules by calling run(), it calls the rule function directly instead. This causes the FormValidation library not to store the _field_data array, which in turn, disables set_value() ability to repopulate the form.

I’m not saying it’s wrong, I just want to find a workaround to deal with this.

DataMapper doesn’t do form validation at all.

It does pre-save validation of object properties. And yes, some of the validation rules are borrowed from the form validation library. But that doesn’t mean it is the same as form validation.

If you want to populate your forms from DataMapper objects, just use the object properties directly. If you need default values for new objects, add a method to your model that sets them when not exists(), and call that method before you load the view. Alternatively, you can call it from __construct() (and probably clear() as well) to do it automatically.

WanWizard - 04 December 2011 04:54 AM

DataMapper doesn’t do form validation at all.

That’s confusing, taking into account what says here: http://datamapper.wanwizard.eu/pages/validation.html

I don’t think that page says any different from what I just wrote, nor does it say it does something with forms.

What exactly is confusing?

You say that DataMapper doesn’t do any form validation at all, but the user guide says it does, so that’s confusing to me. Please explain a bit better (and thank you for your patience)

No, the user guide says that DataMapper provides object property validation.

It runs validation rules on the object properties before you save the object (i.e. INSERT or UPDATE the record). It is not about POSTed variables at all, forms or form variables are not mentioned on that page.

It only says that DataMapper is “borrowing some of the existing functionality from the CodeIgniter Form Validation library.” which means that for example DataMapper doesn’t provide it’s own valid_email() method, but instead calls the method in the form validation library.