Jump to content

sadlyblue

Members
  • Posts

    305
  • Joined

  • Last visited

Profile Information

  • Location
    Portugal
  • Activity
    Project Owner

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

sadlyblue's Achievements

Newbie

Newbie (1/14)

34

Reputation

  1. Thanks. In our new project we want to keep the carrier id. If anything changes we believe it should behave like the product and other objects. And you just saved me some time trying to solve the range issue.
  2. Just found what might be a bug, and of a file theme in src/PrestashopBundle/Resources/views/Admin/Product (in v1.7.2) The page https://devdocs.prestashop.com/1.7/modules/concepts/hooks/list-of-hooks/ mentions the hooks displayAdminProductsQuantitiesStepBottom, but I've made a module with no success. When checking the hook info, viewed the file and there is no mention to that hook. So, if I change this file to include it, it will be lost my changes on future updates. Also, after finding that this file, it makes me wonder if will we be able to customize backoffice as the old versions allowed (of course many don't use custom back office themes)
  3. We could be doing it the wrong way. But one of the times we had to change in the src was because of the src\Core\Product\Search\urlFragmentSerializer. A store with 2 main categories (Men and Women) both have a sub category with same name (Shirts). In the faceted search, if we picked Shirts as a filter, it would show both categories as selected. To avoid this, we needed to add the category id, and change the unserializeListOfStrings and serialize from the file mentioned, and some other changes.
  4. You can't override the classes in the src folder. The only option is to chages the files in that folder, which gets changed again on updates, and it's not recomended to to either. When I read that prestashop was migrating to symfony I thought it would be possible to use the dependency injection to override behaviours, by creating our own PriceFormatter for example. Not sure its already possible with the structure of prestashop.
  5. Hi, Not sure this is the best place to post this. I would like to continue to develop in Prestashop and maybe contribute to it. But before I decide on that there was a change in 1.7 that left me worried and wanted to get some answers if possible. I already now that the src folder doesn't support overrides. But is this a temporary thing? Will it be available in the future? More and more classes are used from the src folder and sometimes we need to change their behaviour but would also like to be compatible for future upgrades. Also, if other developers have this concern, please share you thoughts and advice on how are you going to work with this. Best regards
  6. I have checked in our theme, and in the default theme, and can't replicate the issue. Tried with a cart rule to apply with and without a code. Also, to apply to all products and only selected products (not sure how you created your cart rule). All combinations worked. Have you tried replicating in a fresh install with the default theme?
  7. Was looking for the same answer. Guess it's another "improvement" in 1.7.
  8. Are warehouses available in 1.7? I installed the 1.7.4.2 and couldn't find the option to activate them. If not. Any plans on when will they be available?
  9. Kind of old post, but still the modules are still missing today. I think this is a wrong move for Prestashop. It's not to "The PrestaShop team has decided to remove these features to simplify PrestaShop's core", because they could make them still available for free as an addon module. This is a "we want to make more money or not care with developing features" move. And this worries me. What will it be next? The email alerts? Banners? Stats? It was bad enough to have part symfony, part not using symfony.
  10. Open the file modules/themeconfigurator/themeconfigurator.php. On line 397, you have: Db::getInstance()->delete(_DB_PREFIX_.'themeconfigurator', 'id_item = '.(int)$id_item); Replace with: Db::getInstance()->delete('themeconfigurator', 'id_item = '.(int)$id_item); Then save the file.
  11. Thanks for the reply, but i was already using Chrome.
  12. Just installed the latest version of Prestashop. When i try to access the carriers tab, the page doesn't load, but no error is given, just keeps loading. In the server processes i check the blockreassurance.php is taking too long to finish (not sure why it would need it here). If i kill it, it spawns again. After a few "kills" it holds on the contact-form.php. Never loading the page to configure the carriers. I have to kill all processes for that user to stop this. Not sure if is a server config problem, but when on this "loop" i can't access other pages either. After killing the processes, other pages work.
  13. I'm having the save problem with v1.6.0.9. Sometimes it times out at 300s. Is there a way to enable the debug when saving a product to check where is it taking too long? If i reload th product, sometimes it saves everything, even after the timeout. Sometimes it doesn't. edit: Just noticed that sometimes it's faster than others. In a matter of minutes, can go from saving fast or slow to the other way around. Don't know if it has anything to do with mysql table lock, or other setting.
  14. I'm having the save problem with v1.6.0.9. We have multishop, but even selecting only one field to change (like the product name) and saving it,it takes forever to complete and sometime it timeout (at 300s). Is there a way to enable the debug when saving a product to check where is it taking too long?
  15. Thanks for the help. It worked great, and is exactly what i was looking for.
×
×
  • Create New...