You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Piwigo offers the possibility to synchronize image metadata (exif,iptc) into database fields. One can sync fields from iptc to database fields. It's enabled with the following config example:
// use_iptc: Use IPTC data during database synchronization with files
// metadata
$conf['use_iptc'] = true;
// use_iptc_mapping : in which IPTC fields will Piwigo find image
// information ? This setting is used during metadata synchronisation. It
// associates a piwigo_images column name to a IPTC key
$conf['use_iptc_mapping'] = array(
'date_creation' => '2#055',
'author' => '2#080',
'name' => '2#005',
'comment' => '2#120'
);
When uploading images with the admin interface, this works fine.
With the community-upload plugin mechanism, these fields will end up empty, most of the time. Why? Because the the image-upload form offers 3 text inputs for "name", "author" and "description". These fields are written to the database, after the image was uploaded and saved, therefore it overwrites the values taken from the iptc fields.
The following patch only submits fields containing user input, so the metadata is only overwritten when the user enters text into these fields.
Piwigo offers the possibility to synchronize image metadata (exif,iptc) into database fields. One can sync fields from iptc to database fields. It's enabled with the following config example:
When uploading images with the admin interface, this works fine.
With the community-upload plugin mechanism, these fields will end up empty, most of the time. Why? Because the the image-upload form offers 3 text inputs for "name", "author" and "description". These fields are written to the database, after the image was uploaded and saved, therefore it overwrites the values taken from the iptc fields.
The following patch only submits fields containing user input, so the metadata is only overwritten when the user enters text into these fields.
The text was updated successfully, but these errors were encountered: