Database I/O Manager (DbIo) Plugin [Support Thread]

[boomy]

Double post ..sorry

[boomy]

The following warnings/errors were generated by the above action:


Data record at line #2 not imported. Column count (42) less than header column count (43)

[lankeeyankee]

That means your database tables don't match. One has 42 columns and the other has 43. So you need to compare the tables to see what the missing column is. I believe your new database has the extra column based on the message.

[lat9]

@boomy, you don't mention your PHP or DbIo version, but ...

... after an import is completed, there's a dbio log file generated with the same name as your input csv; that .log file (also accessible from the DbIo console) will identify what were considered errors.

[lat9]

The following warnings/errors were generated by the above action:


Data record at line #2 not imported. Column count (42) less than header column count (43)

That message implies that your import-CSV file identifies 43 columns in the header row (the first row) but only 42 rows in data.

[lat9]

And yet another great plugin by lat9 !!

Found one little snag when testing on a local dev install (1.5.5e): I omitted to make the YOUR_ADMIN/dbio folder writable and of course my test export file was not created.

In case the YOUR_ADMIN/dbio folder is not writable then DbIo should give a warning in the admin when attempting to export to that folder, would avoid some raising of the eyebrows.

I guess that test could be done during the install process of DbIo.

I've got the change for this issue staged on the plugin's GitHub repository; it will be included in the plugin's 1.3.1 release.

[Johnies]

1.5.5e / 1.3.0 - "Products: Auto-Create Categories on Import?" option set to "true". I created a custom product template to match the fields in an Easy Populate CSV from an old OSCommerce site I'm updating. I tested it by exporting the sample data and found a couple of problems.

Under the "v_categories_name" heading, all that's listed is a '1' for each product. However; under the v_products_status heading, instead of the expected "Active" or "Inactive", it has the category hierarchy for each product, separated by a caret --> Women^Bottoms^Jeans^Image Gallery.

Template creation is pretty straight forward so it's likely a bug but if there's a way to resolve it I'd appreciate the help.

[lat9]

1.5.5e / 1.3.0 - "Products: Auto-Create Categories on Import?" option set to "true". I created a custom product template to match the fields in an Easy Populate CSV from an old OSCommerce site I'm updating. I tested it by exporting the sample data and found a couple of problems.

Under the "v_categories_name" heading, all that's listed is a '1' for each product. However; under the v_products_status heading, instead of the expected "Active" or "Inactive", it has the category hierarchy for each product, separated by a caret --> Women^Bottoms^Jeans^Image Gallery.

Template creation is pretty straight forward so it's likely a bug but if there's a way to resolve it I'd appreciate the help.

Hmm, it sounds like (somehow) the v_categories_name data and the v_products_status data got reversed (note that the products_status will show either 0 or 1, not "Inactive" or "Active") in the export.

Would you share, via image, the configuration of the template that you've set up ... that might help me to reproduce the issue.

[Johnies]

Hmm, it sounds like (somehow) the v_categories_name data and the v_products_status data got reversed (note that the products_status will show either 0 or 1, not "Inactive" or "Active") in the export.

Would you share, via image, the configuration of the template that you've set up ... that might help me to reproduce the issue.

Thanks for the info. Shows how observant I am ...I forgot that zen cart used 1's and 0's for active/inactive. Here's an image of the template.

Attachment 17308

No clue what would cause the category and status details to swap so I appreciate any help you can offer. ~Johnie

[lat9]

I don't know what you attached, but the forum software found it "unacceptable". Please give it another try.