Receiving this error "Email field is required for publishing." even though the Email field is not empty and a valid email address. I downgraded to 1.2 and the message went away and the node published as normal. This was introduced in commit: 68f2dca594d57b4c1b4fae97743f456f91979f84 but I can't wrap my head around all the checks that you are doing in the if statement. I will spend some more time with it but I wanted to bring it to your attention.

Thanks for your time.

CommentFileSizeAuthor
#1 required-error]-1084400-.patch1.31 KB2ndmile
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

2ndmile’s picture

2ndmile CreditAttribution: 2ndmile commented
Status: Active » Needs review
FileSize
required-error]-1084400-.patch1.31 KB

Patch Attached - Tested and working on my site

I hope I created the patch correctly as it is my first submitted and still learning git.

2ndmile’s picture

2ndmile CreditAttribution: 2ndmile commented
Status: Needs review » Active

Nope... after further testing my patch allows the field to be blank and still publishes...

DON NOT USE PATCH IN #1

2ndmile’s picture

2ndmile CreditAttribution: 2ndmile commented

Ahhh... there it is. It is not a problem with Required for Publishing but rather with http://drupal.org/project/email which saves the value of the field as $element['#value']['email'] rather than $element['#value']['value'].

So should I submit a patch to them or should we try to come up with a way to make Required for Publishing more ambiguous?

ian_ep’s picture

ian_ep CreditAttribution: ian_ep commented

I think there is a problem with the latest update of Required for Publishing. I too am seeing errors on fields that are filled - both image fields and text fields - and that hitherto have worked fine.

vkareh’s picture

vkareh CreditAttribution: vkareh commented
Assigned: Unassigned » vkareh

I will look into how to make it more generic, basically doing something similar to $element['#value'][$something], where $something is given by some CCK function (if there is such a thing).

vkareh’s picture

vkareh CreditAttribution: vkareh commented
Status: Active » Fixed

This is now fixed in the dev snapshot (6.x-1.x). Please update from the repositories (or wait 12 hours and download) and test.

edit: I created a new release (6.x-1.4), since this is a pretty major issue with the module.

2ndmile’s picture

2ndmile CreditAttribution: 2ndmile commented

Well done... thanks for taking a look at it and fixing it.

I use this module at http://www.kcu.edu

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

ian_ep’s picture

ian_ep CreditAttribution: ian_ep commented
Version: 6.x-1.3 » 6.x-1.4
Status: Closed (fixed) » Needs work

I've just got round to installing 1.4 (after downgrading to 1.2 due to errors with 1.3), and I'm still seeing spurious errors on image fields that are filled. The field in question is also using the 'image-crop' module if that has any bearing on the error. Works fine in 1.2 ...

adriancruz’s picture

adriancruz CreditAttribution: adriancruz commented

I try to install 1.4 and still seeing the error message and remain unpublished even my image field has value/filled. Any idea why it happens? It only happens on image field.