Please Log in or Create an account to join the conversation.
Was able to confirm. That'd be a bug for sure. Have added a bug ticket to see why it's failing.it is imported but additional field not imported
You can't, it's a raw data export/import. Running validation in 99% cases would just cause the import to fail.when i import csv how can i run validation for each field ?
Please Log in or Create an account to join the conversation.
in the past your coding was more stable... :whistle:krileon wrote: Was able to confirm. That'd be a bug for sure. Have added a bug ticket to see why it's failing.
forge.joomlapolis.com/issues/7436
Please Log in or Create an account to join the conversation.
The bug was caused by an additional object column check. The check was to be sure data can only be imported if the object it's importing can hold such data. For custom fields that data doesn't exist as part of the class definition. So when parsing all of this out it doesn't exist as far as this check is concerned and for security purposes cleans it out. None of this is a problem when editing existing rows so it wasn't caught as most of the testing was against an existing row with new row testing just making sure it created the new row.in the past your coding was more stable...
Probably sometime today or early tomorrow.when release new cb? or how can i bug fix?
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
saman2 wrote: friendly bump...new CB not released yet.
Please Log in or Create an account to join the conversation.