fiddlestix6 Posted August 8, 2014 Share Posted August 8, 2014 Hi, I have very little experience with PrestaShop other than being employed by a small business who employed a website design business to create a website and using it for the past 3 years. I have installed a few modules and use Presta to complete day to day tasks (add, edit products, complete orders etc) the website design business (who built the site then pretty much left us to it with very little support) has since closed and we are having to try our best to maintain our site ourselves. I recently installed the ShopCommander free module in an effort to be able to bulk edit our 2000+ products and realised that it was not what we were after so uninstalled it. Since then, whenever we save a product I get this error. [PrestaShopDatabaseException]Duplicate entry '889-1-0-0-0-0-0-0-1-2014-08-04 00:00:00-2014-08-12 00:00:00' for key 'id_product_2' I have attached a screendump of the error. I am after any advice as to how I can either correct this myself of how I go about getting it fixed. Thanks in advance Melissa Link to comment Share on other sites More sharing options...
bellini13 Posted August 8, 2014 Share Posted August 8, 2014 The error is saying that you already have a specific price recorded for this product. a Specific Price grants a discount to a product to a group of customers, and can be found on the Price tab of each Product. So what I might suggest doing to get past this issue, is to use phpmyadmin (from your control panel) to delete these existing specific price entries. The table name is ps_specific_price, and you can search for id_product equal to number 2 for the product in question. Once this single record is deleted, then try to edit the product again and see what happens. Of course, if you want the specific price to exist, then you would need to add it back Link to comment Share on other sites More sharing options...
fiddlestix6 Posted August 27, 2014 Author Share Posted August 27, 2014 Thanks for your reply, I didn't see it until now though. I found that the error was caused by a sale that we had on some of our products. I deleted the sale (in catalogue price rules) and made a new one and the problem fixed itself. Thanks Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now