ID: 22803
Updated by: [email][/email]
Reported By: [email][/email]
-Status: Assigned
+Status: Closed
Bug Type: FDF related
PHP Version: 5CVS-2003-03-20 (dev)
Assigned To: hholzgra
New Comment:

This bug has been fixed in CVS.

In case this was a PHP problem, snapshots of the sources are packaged
every three hours; this change will be in the next snapshot. You can
grab the snapshot at [url][/url].

In case this was a doentation problem, the fix will show up soon at

In case this was a website problem, the change will show
up on the site and on the mirror sites in short time.

Thank you for the report, and for helping us make PHP better.

Previous Comments:

[2003-03-20 04:48:11] [email][/email]

user contributed not on fdf_get_value()
by mclinden at informed dot net

The default behavior for the FDF Toolkit is to return an FDFErcNoValue
for the FDFGetValue when the field exists but has no value.

Whether or not this is truly an error is debateable. It seems to become
an issue in doents created by Acrobat 5 when optional fields are
included in a form with required fields since the default behavior
seems to be to populate the HTTP_FDF_DATA with the results of the
FDFNextFieldName enumerator, which would include the fields which have
no value.

This would not be a problem except that the PHP function
fdf_get_value() does not specifically test for the FDFErcNoValue
condition but, instead, tests for the more general FDFErcOK. If this
value is not the result of the error code, the system issues warnings
(the display of which could be turned off), but the broader question
is, should this be a warning condition at all?

Put another way, should a return of FDFErcNoValue for FDFGetValue be
considered an event worth generating a warning?


Edit this bug report at [url][/url]