Hi @alexanderbailey I believe you are using the free version, we have tested this header manipulation function in our local, its working fine.
Here I am sharing a working video https://drive.google.com/drive/folders/1FsxSjLPuIVEyFXlH8snwVQp9Z9DrQSsX. Can you please check this and share the issue you are facing in the screen record?
Hi @riswanasmack. Correct, I was using the free version.
It looks like you are using field names (e.g. “post_title”, “post_name”) when you do it in your screen recording rather instead of headers from the CSV.
In my scenario, I was importing a CSV which included “Street”, “City”, “State”, “Postal code”, “Country” headers, which I wanted to concatenate to a single ACF field “Address” when importing. I tried using things like “{Street}, {City} {State} {Postal code}, {Country}” but ended up with nothing in the ACF “Address” field after import.
Maybe I could have made the address concatenation work during import if I had created extra ACF fields for each of the CSV columns and then used the field names for each field? I can see the value creating excess fields for a routine (repeating) import, however, I was just doing a one-time import to migrate data from an old (dead) plugin to an ACF-based solution.
I did some more testing. Header manipulation works for me with WP Core Fields but doesn’t work with ACF fields. (If I recall correctly, ACF fields get saved after the post is saved and so content of the ACF fields might not be available in time for header manipulation?)
@alexanderbailey Thank you for the details. We tested the header manipulation using the CSV header only. I can assure this works well with ACF fields aslo.
Here is detailed video https://drive.google.com/drive/folders/1FsxSjLPuIVEyFXlH8snwVQp9Z9DrQSsX
If you share a screen record and sample CSV from your end, that would be helpful.
I think your test is ambiguous because “post_title” and “ID” are both WP core fields as well as headers in your CSV. Without looking at your plugin’s code, my guess is that the core fields are getting “post_title” and “ID” values from the CSV and then header manipulation for the ACF field is manipulating the values from the WP core fields instead working directly with the values from the CSV.
Here’s a one-line sample from the data I was importing:
https://alexanderbailey.com/bb_use/gigpress-export-for-Ultimate-CSV-XML-Importer.csv
See if you can concatenate the address-related fields into a your ACF “text” field, for example:
{Street}, {City} {State} {Postal code}
Sorry if I’m being obtuse!
PS. I’m pretty sure that I was also trying concatenate CSV columns in the WP core post_title field, e.g., {Date}: {City}: {Artist} from my CSV but the plugin would throw an alert to the effect of “Post Title is required”.
@alexanderbailey Thank you for your input. We noticed there is an issue, and now it has been fixed. Here is demo video in the fixed pack
https://drive.google.com/file/d/1XmUbCC1yzOlkS7qC02wozqpLnjAVJ1RZ/view?usp=drive_link
We will update this pack in the next version, if you need the fixed pack immediately, please connect with our support team
I’m glad if I was able to help you find and fix an issue. Thank you for making the plugin!
Thank you for your contribution @alexanderbailey . We consider this as resolved, if you require any assistance, please feel free to create a new thread.
