This module works for the Name field (http://drupal.org/project/name) but I have a Field Collection field (http://drupal.org/project/field_collection) and 2 entity references fields (http://drupal.org/project/entityreference) which are all required.
It only forces the Name field to have a value before proceeding to the next step. I can leave field collection fields and entity reference fields blank and it will allow to submit the form. Since these are required fields, the form must have values for these fields before moving to the next step.
Thanks! Andrew
Comments
Comment #1
aaronbaumanIn fact, this module doesn't seem to do any validation between steps, even for core fields.
What's the point of ajaxifying if we're not performing any server-side logic on submit?In fact, server-side validation doesn't even happen on the final submit.
I'm able to submit a node form without filling in any required fields.
This is a serious problem
Comment #2
aaronbaumanComment #3
thijsvdanker commentedPlease review https://www.drupal.org/node/1972616#comment-9502715.
It applies to the master branch!! of this project.
Comment #4
thijsvdanker commentedComment #5
fox_01 commentedi have installed the 7.x-1.0-beta2 version and tried the example module and it stops on not filled required fields. so it works. but i have clientside validation enabled. is this module required here?
Comment #6
Algeron commentedIn case anyone is struggling with getting validation to trigger on fieldable entities, allow me to share a day's worth of frustration and a workaround:
My setup
Issues
Workaround
For reasons that are beyond me, field validation only acts on "simple" fields when the user is on step 1. I was able to restructure the steps in such a way that the first step only had a simple radio button list. I still had to set its #default_value in a hook_form_alter, since neither the field configuration nor the drafted values were sticking.
As for the values that kept disappearing when validation failed: adding the following snippet to my validation function fixed the issue:
Versions
Comment #7
sgurlt commentedThis is a duplication of: https://www.drupal.org/node/1972616
My patch #46 there should fix that.