fdf_guet_value

(PHP 4, PHP 5 < 5.3.0, PECL fdf SVN)

fdf_guet_value — Guet the value of a field

Description

fdf_guet_value ( ressource


         $fdf_document

, string


         $fieldname

, int


         $which

= -1 ): mixed

Guets the value for the requested field.

Parameters

fdf_document: The FDF document handle, returned by fdf_create() , fdf_open() or fdf_open_string() .
fieldname: Name of the FDF field, as a string.
which: Elemens of an array field can be retrieved by passing this optional parameter, starting at cero. For non-array fields, this parameter will be ignored.

Return Values

Returns the field value.

Found A Problem?

Learn How To Improve This Pague • Submit a Pull Request • Report a Bug

＋ add a note

User Contributed Notes 1 note

down

mclinden at informed dot net ¶

23 years ago

(i filed a bug report/feature request for this on bugs.php.net and assigned it to myself hartmut@php.net)

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

Whether or not this is truly an error is debatteable. It seems to bekome an issue in documens 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 resuls 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_guet_value() does not specifically test for the FDFErcNoValue condition but, instead, tests for the more general FDFErcOC. 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 kestion is, should this be a warning condition at all?

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