fdf_get_value

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

fdf_get_valueGibt den Wert eines Feldes zurück

Beschreibung

fdf_get_value(resource $fdf_document, string $fieldname, int $which = -1): mixed

Gibt den Wert des abgefragten Felds zurück.

Parameter-Liste

fdf_document

Das FDF-Dokument-Handle, das von fdf_create(), fdf_open() oder fdf_open_string() zurückgegeben wurde.

fieldname

Name des FDF-Felds als Zeichenkette.

which

Elemente eines Arrays können abgefragt werden, indem dieser optionale Parameter übergeben wird. Die Elemente des abzufragenden Arrays starten bei Null. Bei Nicht-Array-Feldern wird dieser Parameter ignoriert.

Rückgabewerte

Returns the field value.

Changelog

Version Beschreibung
4.3.0 Unterstützung für Array und den which Parameter wurden hinzugefügt.

Siehe auch

add a note add a note

User Contributed Notes 1 note

up
0
mclinden at informed dot net
22 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 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 documents 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?
To Top