I'm relatively new with working with Prestashop and I cannot fix one problem.
After deleting one combination for a product new default combination doesn't want to save and therefore the price showing on the website is not correct.
Any ideas how to fix it?
Thanks!
It might be possible that the combination that you have deleted is a default combination, you can try the following steps to set another default combination.
Open table ps_product_attribute and filter the rows with product ID of the product you want to edit. You will see a column default_on in this table, just edit it to 1 for the combination you want to set as default.
Experienced exactly the same problem (Prestashop 1.6.23) - the default product combination did not want to save.
In debug mode received an error stating the "default_on" field was already set for this product.
Solved it by opening the database table "ps_product_attribute" and searched via the product ID. Deleted the old combinations manually (which were not displayed at the back-end anymore and not in use). Then I was able to set the default combination again.
Sidenote: in our Prestashop setup (with a custom theme) the price was showing as 0 EUR (front-end) before getting the default combination to save again.
Related
I installed an add-on for bulk action (called ba_importer v 1.1.24), I upload an Excel file with my data and create a group of products.
I can set the categories' tree or manually add ID of main categories and associated. I tried with no luck to use the tree features (like Home/Products/etc) and so I use all the ID of main category and all the associated. The result is a product with the correct categories set, but with no specific price from the customer group linked to a category.
I tried to edit a single product, remove all categories and set it one by one (set one, save, set one, save etc.) and then the specific price from the group linked to a category appears to the product.
Is there a better solution? I'm thinking about make a personal PHP page that reads an Excel file and sets all the information about the product, but I'm scared to face the same problem with the specific price.
There is no such thing as "category-related specific price",
if you have specific prices tied to customer groups , these are created as a result of the add/update product action with ps_specific_price DB entries having id_group with your restricted ID.
It is likely that the bulk module acts directly with DB queries to speed up things and bypasses this operation, I've seen this behaviour with those kind of modules in the past.
Since you are talking of a paid add-on, I would definitely seek help from the developer.
Right now I am trying to update a field for a lot of products using SQL on Volusion but I can't seem to get it right.
I am trying to update the Package Type to UPS Package for every product but when I update it this way, it just adds another option on the drop down list titled the exact same thing
https://i.imgur.com/MhPmRIJ.png
I imagine what I should be doing is changing things around so that instead of updating every product I'm making every product choose UPS Package from the existing menu? If I manually change a product to UPS Package (correctly) then export all product data the field is displayed as just a '2' on the spreadsheet, but I also can't just put a '2' in on the mass update.
Thanks in advance
1:
Its the space before the SET value that is causing this, which you would need in order to keep this on the same line (otherwise this becomes products_joinedSET). This was a correction made to any SQL that can be run in a store that was made back in mid November. So any queries with a SET value will need a line break in order to remove that space between the table name and the SET.
UPDATE Products_Joined
SET Package_Type = 'UPS Package' WHERE ProductPrice = '0'
Of course, if you want to change ALL your products to UPS Package and have products that are more than $0.00 then you'll need to remove WHERE ProductPrice = '0'
The products list is dynamically generated while running purchase request. While change the cost or qty it shows the following error, What need to do to modify the record?
Finally I fond the answer for it. I made one of the required field(UOM) in order line. So that only this happens.
I have been working on a completely new store (Prestashop 1.6) using the information from my old store (Prestashop 1.5) and now that I am just finishing the last details (and since I don't want to mess things up), I want to know if someone already did this.
My old store is up and running and sales have continued since the last time I have started working on my new store (like two months ago).
Keeping all the information updated (new users, sales, etc.) how can I export directly from my database from Prestashop 1.5 to 1.6?
I've noticed that there are paid modules that does that (a lot actually) but I want to do it manually. I'm just not sure what should I do, which tables can I "copy/paste" and whatsoever.
Any kind of help would be much appreciated.
Thanks a lot!
Ahh... isn't it wonderfull when you find the answer to your very own question? :D
Ok, so actually this is even easier than I though! :)
And for anyone that might have this same doubt, here's what I did:
FIRST OF ALL, BACKUP ALL YOUR DATABASES!!!
Now that you have finished your BACKUP (did I mentioned that you MUST BACKUP ALL YOUR DATABASES?), you do this:
On your old prestashop database, you select these tables (I use phpmyadmin for that):
ps_address
ps_cart
ps_cart_product
ps_connections
ps_connections_source
ps_customer
ps_customer_group
ps_customer_message
ps_customer_thread
ps_guest
ps_message
ps_orders
ps_order_carrier
ps_order_detail
ps_order_detail_tax
ps_order_history
ps_order_invoice
ps_order_invoice_payment
ps_order_payment
ps_order_state
ps_order_state_lang
After that, you select "export" and save that file.
Then, you go to your new prestashop database (DON'T FORGET TO BACKUP...) and you delete those tables mentioned above (ONLY THOSE ONES, MAKE SURE YOU ARE INDEED SELECTING THE RIGHT ONES).
Now you have to import the file you exported from your old prestashop (not the entire backup, obviously... only the file that you exported with those tables selected)!
After import the tables, you will now have to recreate come columns. Now this is a VERY important step, and if you don't do it correctly, your store will NEVER work! (if you don't know how to do this, ask a professional to do it for you or simply buy a module to export and import your stuff)
Add column "mobile_theme" to "ps_cart" as tinyint(1) and 0 as default
Add column "id_lang" to "ps_customer" as int(10) and NULL as default
Add column "date_upd" to "ps_customer_message" as datetime
Add column "mobile_theme" to "ps_guest" as tinyint(1) and 0 as default
Add column "mobile_theme" to "ps_orders" as tinyint(1) and 0 as default
Now, I am not sure if these columns were added after I install some module or theme, but anyway if later you try to install some module or theme and some error appear regarding a column, you just have to remove that column and proceed to installation, and it will create the column again.
this is unfortunately only partly working. Prestashop alters a lot more in the table structure as you can see in the
/install/upgrade/..
files. It worked for me to import these tables and then run the upgrade script again. Of course you need to set the older Prestashop version in
config/settings.inc.php
Don´t forget to copy COOKIE_KEY (in config/settings.inc.php) from your old store to new one, for your customers login in new store.
I am not able to remove the "new products", "specials", "our stories", "contact us" modules from the index page in Prestashop. Please, will any one tell me how to do it?
Thank you....
Check the database. In ps_hook table identify which id_hook these modules are attached to. Simply find e.g. row where name is displayHome and remember id_hook. Then look at ps_module table and identify modules ids which you are about to get rid of. At last check ps_hook_module table and find if there are rows where your id_module and id_hook match. If so just delete these rows.
If you don't find such matches, simply delete (and make an backup) of the modules from Prestashop installation folder/modules.
If this won't work these modules are only cached or you wrongly identified the modules you have uninstalled.
The case where uninstalled modules are not unhooked from Prestashop DB ps_hook_module table is important bug. Check if there isn't an override of Module->uninstall() function, which could cause such an situation.