Error Checking Improvements

[McFateM]

Xpath errors detected indide the batch CSV process are problematic as nearly all errors lead to AJAX failure and report themselves with misleading messages. Paths in the CSV header should be pre-checked before the batch process loop in order to avoid this, and to improve system performance.

[McFateM]

I introduced a new function, icg_csv_import_header_errors, yesterday and it appears to be working properly. From the function header...

/**

• icg_csv_import_header_errors - This is derived from icg_csv_import_batch_item as
• a function to validate Xpaths (CSV header row) before the batch process is started. *
• @param array() $head - XPaths from the structured CSV header row.
• @param array() $controls - Process controls passed from the user interface. Elements mostly
• from $form_state['all_values'] include: *
• @return string|bool|array - An associative array of $head => message errors, FALSE
• if the function failed to build a MODS skeleton, or a valid MODS skeleton string. */

I will close this issue as soon as I have removed the redundant header/xpath checking from the icg_csv_import_batch_item function.

[McFateM]

Redundant header/xpath checking has been removed from icg_csv_import_batch_item and is now provided by the hook_validate_csv_header function found in icg_hooks/icg_hooks.module (and potentially in your own hook). Closing this issue.