Im using automatic nodetitles along with some other fields with validation in a specific content type. This content type is meant for anonymous users. When a user submits and the fields are not complete, it shows the validation errors. However, it always shows the title field error message last, and out of the regular sorted order of all of the fields on the Manage Fields page for this content type. I even changed the order of the title fields to the beginning and the error message still shows up last. I even went into the database and changed the ids and field_ids of this field to see if that worked. The validation error message still shows up last. Any advice would be greatly appreciated.

I would be happy to send anyone at least a $50 paypal donation or check if you can help solve this issue.

Thanks,
Dan

CommentFileSizeAuthor
#2 Screen shot 2012-09-12 at 10.04.26 AM.png36.9 KBdandolino
#3 Screen shot 2012-09-12 at 10.04.26 AM.png36.9 KBdandolino
Screen shot 2012-08-23 at 6.19.52 PM.png97.41 KBdandolino

Comments

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Closed (won't fix)

I don't see why this should be related to automatic nodetitles.

dandolino’s picture

dandolino commented
Status: Active » Closed (won't fix)
StatusFileSize
new Screen shot 2012-09-12 at 10.04.26 AM.png36.9 KB
dandolino’s picture

dandolino commented
Status: Closed (won't fix) » Active
StatusFileSize
new Screen shot 2012-09-12 at 10.04.26 AM.png36.9 KB

I set up the automatic nodetitle so that it uses this pattern

[node:field-title-of-story-2]

$year = '[node:field_year_memory]';
if (empty($year)){
return false;
} else {
return ', [node:field-year-memory:year]';
}

The only thing is I have title show up first visually on the form, but it looks like it gets processed last (see devel load snapshot attached). Then, the "title" field validation error always comes up last. I would be very happy to donate if you could kindly help me.

Thanks
Dan

dandolino’s picture

dandolino commented

closed. I used Clientside Validation module instead, and issue is taken care of.