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

lat9:

One of those was a good guess!:D

To insert a product via import, you'll need to have both the v_products_id and v_products_model fields present in the to-be-imported CSV. Set the products_id value to 0 (not blank) and the products_model to the new product's unique model number.

And the guess I didn't make. ;-)

Works perfectly when you do that!

Just a quick question before I go much deeper. Is there an option to add/update categories or deos the category structure need to be in place before the file is imported?

There's no separate handler for categories at this time. When you import a product, the category structure will be created if it doesn't already exist.

lat9:

There's no separate handler for categories at this time. When you import a product, the category structure will be created if it doesn't already exist.

That doesn't seem to be working. I tried adding a new product to a category that didn't exist and it gave an error.

[*] Product not inserted at line number 2, no match found for categories_name (Rich).

Hmm, I'll need to investigate further ...

lat9:

Hmm, I'll need to investigate further ...
... v1.3.0-beta1 is available for download from the DbIo's GitHub repository. This version (to be released as v1.3.0) contains the changes necessary for the automatic generation of products' categories on a Products import.

Note that there's a new configuration value available: Configuration->Database I/O Manager Settings->Products: Auto-Create Categories?. The setting defaults to No; set the value to Yes for the auto-generation.
.

Installing it now. I'll let you know if I find any issues. Thanks!!

Still getting the error. I downloaded, copied the admin files, and set the config setting. Same message:

Product not inserted at line number 2, no match found for categories_name (Rich).

From the debug log:

2017-04-21 09:34:49: importProcessField (--special--, categories_name, 0, Media^Aqueous^Inkjet Paper^Innova Paper^Rich)
2017-04-21 09:34:49: Products::importAddField (--special--, categories_name, Media^Aqueous^Inkjet Paper^Innova Paper^Rich)
2017-04-21 09:34:49: [*] Product not inserted at line number 2, no match found for categories_name (Rich).

I can email you the full debug log if you PM me with your email. Anything I can do just let me know.

Did you change that new configuration setting? It defaults to "No" (i.e. categories not auto-created).

lat9:

Did you change that new configuration setting? It defaults to "No" (i.e. categories not auto-created).

Yes, I set it to "yes"

badarac:

Yes, I set it to "yes"
PM sent.

lat9:

PM sent.

Reply email sent

Creating a category named Rich, with parent_category_id 34

Amazing what a difference saying "Yes" makes :cool:

badarac:

Creating a category named Rich, with parent_category_id 34

> 
> Amazing what a difference saying "Yes" makes :cool:
... Yes!:P

The issue that @badarac found was that I had the wrong value in the conditional checking to see whether (Yes) or not (elsewise) the categories are to be auto-created.  Its correction has been posted to the GitHub repository but is not included in the -beta1 version.

In the DbIo exported dB header..... Where would I put "dealer Pricing"? the MSRP retail price is going into the "v_products_price" column.
Do I need to or better yet, CAN I make another column for the Dealer pricing?

I have TWO picture FOLDERS to FTP/upload to the site. (/large_/001-00122.jpg) and (/small_/001-00122.jpg)

What SHOULD I do for the two different size photos for each product...? How do I set that up ?

Thanks,
MrRogue
)

MrRogue:

In the DbIo exported dB header..... Where would I put "dealer Pricing"? the MSRP retail price is going into the "v_products_price" column.
Do I need to or better yet, CAN I make another column for the Dealer pricing?

I have TWO picture FOLDERS to FTP/upload to the site. (/large_/001-00122.jpg) and (/small_/001-00122.jpg)

What SHOULD I do for the two different size photos for each product...? How do I set that up ?

Thanks,
MrRogue
)
The DbIo gives you the opportunity to import and export ***all ***database fields for a product. If you've installed the MSRP plugin, for example, any additional fields defined by that plugin will automatically be available for export (and import).

If you create a database field for the dealer pricing, you can manipulate the value using the DbIo but you'll need other code modifications to actually use that value for any display or processing.

Regarding the images, you'll need Image Handler 4 to manage the various sizing of those images. Zen Cart uses a base image name (recorded in the database) and then looks for that name in the various folders; IH4 extends that processing.

I've just submitted v1.3.0 to the Plugins for review, providing changes for the following issues (identified by their GitHub issue number):

#94: Enable a handler to totally control an import
#98: Add (optional) category-creation during a "Products" import
#99: Correct the plugin's initialization for "early adopters".
#100: Manage date_added/last_modified fields during a "Products" import
#102: Display all DbIo option settings on the Database I/O Manager page

I'll post back when it's available for download there.

lat9:

I've just submitted v1.3.0 to the Plugins for review, providing changes for the following issues (identified by their GitHub issue number):

#94: Enable a handler to totally control an import
#98: Add (optional) category-creation during a "Products" import
#99: Correct the plugin's initialization for "early adopters".
#100: Manage date_added/last_modified fields during a "Products" import
#102: Display all DbIo option settings on the Database I/O Manager page

I'll post back when it's available for download there.
DbIo v1.3.0 is now available for download: https://www.zen-cart.com/downloads.php?do=file&id=2091

And yet another great plugin by lat9 :cheers: !!

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.

frank18:

And yet another great plugin by lat9 :cheers: !!

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.
:oops:Thanks for the report, @frank18, I'll get that logged and included in the next release.