EasyPopulate 4.0 Support Thread

[chadderuski]

It's 9 ... I edited the post to fix it... too early

Deleting should be no different.

[Kevin205]

Hi Kevin,

No. But there is a work around that I don't suggest except for new installs. You can list the product TWICE. The first time in it's existing category, with v_status = 9 (request a delete product), and then again in the target category with v_status = 1 for normal active.

So what happens is the product is first deleted and then re-added to the store. Note that this breaks the product_id, and that may affect things like your sitemap, feeds, etc.

I know, I am trying to inject coffee to myself also.

Since you mentioned you do not recommend except for new installs. You can list the product TWICE

If you are deleting products from table first (v_status = 9), and then adding new products to a different category via (v_status = 1). Whys is it that the product ID is broken? Why should it? Product ID should be deleted in the tables. Aren't they?


Please excuse me if I asking dumb questions like that.

ps. By product IDs i meant v_products_model.

[chadderuski]

This would be a pretty useful tool. (Not that it already isn't)

I can only imagine there will be instances that you add 100s of products by mistake to a category. And then you have to delete them from one category and add them to the correct one!

This is ONE of the many potential screw-up that can occur, and the reason I always ALWAYS recommend doing a database backup with Dr. Byte's Backup MySQL tool before doing any import.

I've been using EP for 8 years, and even with MY coded version, I still do a DB backup before an import.

[chadderuski]

I know, I am trying to inject coffee to myself also.

Since you mentioned you do not recommend except for new installs. You can list the product TWICE

If you are deleting products from table first (v_status = 9), and then adding new products to a different category via (v_status = 1). Whys is it that the product ID is broken? Why should it? Product ID should be deleted in the tables. Aren't they?


Please excuse me if I asking dumb questions like that.

ps. By product IDs i meant v_products_model.

when you browse your store, look at your URL. It is made up of category ID's and your product's ID, NOT the model. So if you feed google, bing, or some other place, you will throw a wrench in your bot's indexing ...

Hope that makes sense.

[Kevin205]

OK now I understand. My #1 rule is to always make backups.

What my concern is when you populate the database with 100s of records and in a month or two after adding hundreds more, then if the category name has to be changed for any reason whatsoever, manufacturer definitions, management decision to change location and or mistakes or any other reason, then this is something that has to get done and backups will not help. The product tree has to be changed. Search engine bots, SEO and etc. could be re-established.

As long as the action of deleting a series of products with v_status = 9 (request a delete product), and then adding the same series of products in the target category via v_status = 1, does not interfere with database integrity. I would not care about bots or indexing.

Do you think the above action might damage the database integrity itself?

[chadderuski]

OK now I understand. My #1 rule is to always make backups.

What my concern is when you populate the database with 100s of records and in a month or two after adding hundreds more, then if the category name has to be changed for any reason whatsoever, manufacturer definitions, management decision to change location and or mistakes or any other reason, then this is something that has to get done and backups will not help. The product tree has to be changed. Search engine bots, SEO and etc. could be re-established.

As long as the action of deleting a series of products with v_status = 9 (request a delete product), and then adding the same series of products in the target category via v_status = 1, does not interfere with database integrity. I would not care about bots or indexing.

Do you think the above action might damage the database integrity itself?

I see no reason for the databases to suffer. Although you may want to optimize your databases if you delete *hundreds* of item, etc. as these are not physically deleted from the database (only marked as deleted) until you do so.

[Kevin205]

So how would you physically delete them?

[chadderuski]

So how would you physically delete them?

From zencart admin: Tools > Store Manager > Optimize Databases

[Razzinator]

I can download "Full" and turn right around and import it back. But if I open with Calc and save file unedited I get this error msg.

No model field in record. This line was not imported

[Kevin205]

From zencart admin: Tools > Store Manager > Optimize Databases

Chad - Thank you for all the help.