I have a query with a (custom) field for which a formatter is used. The correct formatter is used in the Views, but the default formatter is used in the VDE. Does the field need a special callback?
It concerns a field from countries.module.
I tested a normal value-list field with Key and Value, This is OK.
Another custom field even causes the following crash (where \xC4\x81ori is the code for UTF-8 strings):
PDOException: SQLSTATE[HY000]: General error: 1366 Incorrect string value: '\xC4\x81ori"...' for column 'data' at row 1: INSERT INTO {views_data_export_object_cache} (eid, updated, data) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2); Array ( [:db_insert_placeholder_0] => 27 [:db_insert_placeholder_1] => 1299769354 [:db_insert_placeholder_2] => O:4:"view":29:. ......

Comments

johnv’s picture

Update on the issue: the PDOException only occurs with 'Export batch = Yes' (obviously, since it is inserting into views_data_export_object_cache)
With 'Export batch = No', also for the second Field type, only the default formatter is used.

johnv’s picture

Update on the issue:
- the PDOException only occurs with 'Export batch = Yes' (obviously, since it is inserting into views_data_export_object_cache)
- With 'Export batch = No', also for the second Field type, only the default formatter is used.
- I get a lot of errors when changing the view:
Notice: Undefined variable: header in template_preprocess_views_data_export_msoffice_header() (line 290 of ..\theme\views_data_export.theme.inc). (10 times, once for each line on the page?)
Notice: Undefined variable: output in template_preprocess_views_data_export_msoffice_body() (line 255 of ...\theme\views_data_export.theme.inc). (only one time)
Notice: Undefined variable: header in template_preprocess_views_data_export_msoffice_body() (line 258 of ...\theme\views_data_export.theme.inc). (about 50 times)

johnv’s picture

Title: Why is proper field formatter not used (for some fields)? » PDOException: SQLSTATE[HY000] on batch export
Status: Active » Closed (works as designed)