Hi @designemotions,
This is actually done to prevent errors where content contains these special characters. There is a strict CSV standard, and this result follows that standard.
I might be able to add a hook to overwrite this behavior, but I would strongly suggest you don’t change it.
Can I ask what the use case is?
A company asked me if it is possible to have the file in that format because it is then processed by an application within the company to reprocess the data and automatically generate estimates for customers who fill out the form. Then that format is reworked by an application developed for the need
Thanks
@designemotions ok. Let me get back to you in this!
Hi @designemotions,
I’ve just released version 1.7.5 for you. It contains a few new hooks for you to change the behavior of the CSV.
The hooks are:
– gfexcel_renderer_csv_delimiter -> default: ,
– gfexcel_renderer_csv_enclosure -> default: "
– gfexcel_renderer_csv_line_ending -> default: PHP_EOL
– gfexcel_renderer_csv_use_bom -> default: false
– gfexcel_renderer_csv_include_seperator_line -> default: false
You can add something like this to your functions.php:
// changes CSV delimiter to a semicolon
add_filter('gfexcel_renderer_csv_delimiter', static function() {
return ';';
});
Please let me know if this helps you out enough.
Closed due to inactivity. If you need any more help, please let me know.
