Import Problem - double import

Another observation is the the configuration of thge import is not saved properly.

I made an assignment of a csv column to a field, but this assignment was not saved with the configuration.

Please attach your CVS I'll test.

Scenario: Empty js_res_record, js_res_record_values, js_res_record_categories, js_res_import, js_res_import_rows

I imported the attached CSV (4 records) into a TYPE with a TEXT field.

The CSV has 4 columns: NO --> unique Number Category --> category informartion Title --> Title File --> Text field in TYPE

After IMPORT it shows:

It should say 4 new Articles inserted and not updated, since the type was empty and did not have any prior records.

When checking the record_values table it only shows 1 record (from article 4), the first 3 records for field FILE were not created.

"Indexing" in js_res_record fieldsdata did only happen for the last inserted record.

When importing the same file again, it creates another 4 records and is not ignoring (updating) the existing 4 records.

See attached CSV file, exported from Excel as Windows CSV. Workbook21

Since the import process provides a "ctime" field, it should also provide an "expiration_time" field.

Speaking of date fields, the datetime field is also lacking the import feature. I would suggest to expect as default date "YYYY-MM-DD" and add the " 00:00:00", before storing, if the csv data does not have the time information.

Another usefull feature would be a recording of created ID's (or a logfile in general) to provide an option to UNDO the import in deleting all the created records.

Sackgesicht Another usefull feature would be a recording of created ID's (or a logfile in general) to provide an option to UNDO the import in deleting all the created records.

Such a thing created in DB js_res_import in crossids column. It is JSON.

I'll check the other issues on import later.

Sergey Such a thing created in DB js_res_import in crossids column. It is JSON.

nothing is created here in my setup under crossids column....

Sackgesicht Since the import process provides a "ctime" field, it should also provide an "expiration_time" field.

Good point. I remember I have mentioned something similar in another topic.
IMHO, all minimum core infos/fields should be available during import.

If import soes not finish with success it might fail to write that data into import table. Does your import go through without error or interaption?

Sergey If import soes not finish with success it might fail to write that data into import table. Does your import go through without error or interaption?

No error.

Did you try the import with requested and attached file? Did it properly create the record values on your side? Does it show the articles created under "New articles inserted" in the final page? What happends on second import?

Here import is not working as expected under different scenarios (New installation, existing installation, PHP 5.5 to PHP 7)

I wrote very extensive answer to this question withh al the explanations. But fail to save. I was logged out.

So shortly you cannot use . in column name. Change NO. to NO.

Sergey So shortly you cannot use . in column name. Change NO. to NO.

I changed it and the import is running better now. Exceptions like "No . in header" should be detected by the parser, giving a warning and not proceeding to Step 2, otherwise defective records will be created by the import script.

I have a complete empty Cobalt installation and import 4 records. In the final page it says, 4 articles updated. It should show 4 new articles inserted.

Now i used the same csv file and added 1 article. After importing it shows :

This is wrong, it should say 5 processed , 1 new article inserted and 4 articles updated. The import itself was correct.

Another thing, the import setting should remember the field settings. It only remembers the title, category and unique number.

Sackgesicht Exceptions like "No . in header" should be detected by the parser, giving a warning and not proceeding to Step 2, otherwise defective records will be created by the import script.

Fixed.

Sackgesicht This is wrong, it should say 5 processed , 1 new article inserted and 4 articles updated. The import itself was correct.

I also noticed this problem. I'll check it later.

Sackgesicht Another thing, the import setting should remember the field settings. It only remembers the title, category and unique number.

For me it remembers averything. Including all fields configurations.

Sergey For me it remembers averything. Including all fields configurations.

But not for TEXT fields, since it does not have the onImportForm function. See Github issue #85

Text field have those methoods on parent class in components/com_cobalt/library/php/fields/cobaltselectable.php. This is parent class for checkbox, radio, select, listautocomplete and multiselect.

Please check repeated import with TEXT field. It does not remember the setting.

If I add

    public function onImportForm($heads, $defaults)
    {
        return $this->_import_fieldlist($heads, $defaults->get('field.' . $this->id));
    }

to TEXT field, then it remembers it.

I have updated parent class for text field. It should work now.

Sergey I also noticed this problem. I'll check it later.

Still not working.. it does not distinguish between updated and created.

But this is exactly what is called.

public function onImportForm($heads, $defaults)
{
    return $this->_import_fieldlist($heads, $defaults->get('field.' . $this->id));
}

this is what you can find in text field parent plass.

it is refering to the problem in distinguishing between update and new record. Please check 13 comment here where you mentioned that you are aware of it and will check it later. Not about the text field.

Sackgesicht it is refering to the problem in distinguishing between update and new record

I've fixed this problem for next update.