Jump to content

bcarron

Members
  • Posts

    29
  • Joined

  • Last visited

Profile Information

  • First Name
    Blaise
  • Last Name
    Carron

Recent Profile Visitors

392 profile views

bcarron's Achievements

Newbie

Newbie (1/14)

  • Dedicated Rare
  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

4

Reputation

  1. Which index? You mean ID product/combination IDs? Unfortunately, I can't use profiling for that since it's an API call and not a standard page. However I found out that if I empty the ps_order_detail table, the long wait time is reduced to about 15 seconds but I couldn't find any difference between the table from the upgraded shop and the one from a fresh 1.7 shop.
  2. I probably was not very clear but I am talking about the upgraded 1.7 shop, the upgrade to 1.6.1.24 from 1.6.1.1 worked perfectly and the products / stocks / combinations were all working nicely with it. I didn't think of that, thank you so much for your help! The page produced a "Lock wait timeout exceeded" error. I increased the timeout and now the page eventually loads, but it takes forever (over 8 minutes)... Strangely the "Stocks" page works fine with the fresh 1.7 shop where data was copied with your script. I can increase quantities and everything, but I can't see combinations on the product pages and I can't make a new product with combinations. This is all very confusing...
  3. You're right, I kind of glossed over it since it was only warnings and I couldn't find them. I just got the message a the end of the upgrade: Database upgrade OK Warning detected during upgrade. The full log is 22762 lines long (I've attached it to this post) and by searching it more thoroughly I could not find any warnings except these: [INTERNAL] /var/www/tms17/vendor/ircmaxell/random-lib/lib/RandomLib/AbstractMcryptMixer.php line 75 - Function mcrypt_module_open() is deprecated [INTERNAL] /var/www/tms17/vendor/ircmaxell/random-lib/lib/RandomLib/AbstractMcryptMixer.php line 76 - Function mcrypt_enc_get_block_size() is deprecated [INTERNAL] /var/www/tms17/vendor/ircmaxell/random-lib/lib/RandomLib/AbstractMcryptMixer.php line 77 - Function mcrypt_enc_get_iv_size() is deprecated [INTERNAL] /var/www/tms17/vendor/ircmaxell/random-lib/lib/RandomLib/AbstractMcryptMixer.php line 86 - Function mcrypt_module_close() is deprecated Yes the page where you can edit quantities and see movements (other tab) in the back office. The settings for stock in the product settings page of backoffice? I can't really see any relevant settings except enabling stock management (which is indeed enabled). Debug mode is enabled but the "Stocks" page is using the API to populate a Vue view so the page itself is loading but the content does not load, a popup appear with "Internal Sever Error". Since the page itself loads, I don't get any debug information. Can't find anything useful in the php/apache logs either. From the Symfony toolbar, I can see that the AJAX request that provoque the error 500 is this one: admin/index.php/api/stocks/?_token=XXX&order=product&page_size=30&page_index=1 The log from Apache : [14/Nov/2019:11:50:17 +0100] "GET /admin/index.php/api/stocks/?_token=XXX&order=product&page_size=30&page_index=1 HTTP/1.1" 500 117784 "XXX/admin/index.php/sell/stocks/?_token=XXX" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.120 Safari/537.36" I have a fresh 1.7 shop where I tried to play around with new products and changing quantities. That's where I noticed that 1.7 does not use ps_stock anymore and "depends_on_stock" in ps_stock_available is set to 0 by default instead of 1. I also noticed that ps_stock_mvt now uses ps_stock_available id for its id_stock despite still being called id_stock. I don't think that this is my problem though, since I emptied the ps_stock_mvt table to test if it had an influence. PS17 upgrade log copy.txt
  4. That's a great idea, I have done the process again and the new shop running 1.6.1.1 with copied data from the old shop worked fine. Then I upgraded that shop to 1.6.1.24 in order to use php 7.1 for the upgrade to PS 1.7. I thought it might be the reason why the upgrade to 1.7 failed, and it was the case, this time the upgrade was able to finish successfully with warnings detected during upgrade. On that shop, I can still see the combinations on the product page but the stocks page is not working, the page is displayed but the content loads forever until I get an Internal Server Error popup. I checked the tables for ps_stock, ps_stock_available and ps_stock_mvt, the tables are similar between a fresh 1.7 shop and the updated one. The only differences I could find are that 1.7 does not use ps_stock anymore and "depends_on_stock" in ps_stock_available is set to 0 by default instead of 1 (both of which are normal since there is no ASM in 1.7). I tried removing all entries from stock and setting all stocks in ps_stock_available to 0 but I still can't load the page. Since I get no error message it is hard to understand why the query hangs just on the Stocks page but I have noticed that this page is using the BO API instead of querying the DB directly. I know that this is not really related to your script but do you know of any other tables that are involved in the stock management? Once I copy that shop to a fresh 1.7.6.1 shop, I can't even see the combinations on the product's pages.
  5. I have quite a lot of products so that kind of service is expensive. Furthermore, I don’t mind doing it myself if possible, I have a background in computer science (unfortunately I don’t know the inner workings of PS that much though). I don’t mind using the new “Stocks” interface from 1.7. However, I tried the procedure I outlined and while the shop is now working in 1.7, I have a lot of issues with product stocks and specially product combinations. The existing combinations are not displayed in the product page and I can’t even create combinations with new products. I wonder if this is due to the way product combination stocks were stored in ASM and are now conflicting with the new way stocks are managed.
  6. Hi musicmaster, this script looks great! Does it work with advanced stock management? Unfortunately, I can't use the 1-click upgrade (or the manual process) to upgrade my shop since it always fail when updating the database. Therefore, I have to somehow copy the data between shops on 1.6.x before upgrading a clean shop to 1.7.x and copy the data again to a clean 1.7.x shop... Your script seems perfect for that but I am worried that since I use advanced stock management in my 1.6.x shop I will have problems in 1.7.x even by only copying business tables.
  7. I am still using 1.6.1.x branch, is it now possible to migrate to 1.7.x using the 1-click upgrade? Is it even advisable at this point? It has been some time now that 1.7 is out and I would like to get some of the new features, what do you guys think? Thanks!
  8. Well I just wanted to know if someone had done it before and had a proper answer but of course I will try it myself But I am pretty sure it will reset all quantities to 0. I just tried to enable multistore on my test server running 1.6 and when you share quantities between the shops, it reset everything to 0 which is quite painful... I will have to make a script to convert everything I guess.
  9. Hi guys, I am contemplating moving to 1.7 now with the 1.7.3 release. But I use the advance stock management on all my products, I don't mind going back to the standard stock management but what will happen to my stock if I do the upgrade? Will the products and current quantities be converted to standard stock management or will I lose all my stock? Thanks!
  10. I have the same problem, only about 2/3 of my orders are reported in Google Analytics... I'd like to disable the PS stats to accelerate my website but I can't since GA is not accurate. I've seen people who have done it, is there something specific to do to ensure that all transactions are registered?
  11. What happens to the database when I add quantities to a product using ASM and depends on stock? Which tables are modified? Since I use ASM, I can't modify ps_stock_available directly right? I have to also modify ps_stock and add a movement in ps_stock_mvt, but how exactly should I do that?
  12. I was wondering if it was possible to modify the quantities in stock using the web service when the products uses both ASM and depends on quantity from the stock. I haven't been able to either modify the stock available directly or the quantities in stock or even add a stock movement. Can someone explain to me exactly what happens in the DB when you increase / decrease stock in the back office? Is it possible to modify the quantity of products available to order from the web service? Even if you don't know for the web service, I would be very grateful if someone can really explain how the ASM / depend on stock feature works in the DB. Thank you
  13. I know this is old but I had this issue and for people looking to resolve this, you should use filter[id]=[2|3|8] instead of filter[id]=[2,3,8].
×
×
  • Create New...