-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove cover query for ps1770 #96
Conversation
pablopolyte
commented
Jan 19, 2021
•
edited
Loading
edited
Questions | Answers |
---|---|
Description? | Remove cover query for ps1770 |
Type? | bug fix |
BC breaks? | no |
Deprecations? | no |
Fixed ticket? | Fixes cover image when value is "0" |
How to test? | Please indicate how to best verify that this PR is correct. |
Possible impacts? | Please indicate what parts of the software we need to check to make sure everything is alright. |
Hi @pablopolyte thanks for the PR! Can you give us some context? Why do you suggest to remove the cover query for PS 1770? Is there a change in PS 1.7.7 that requires this? |
It's probably because we're able to get proper cover from .tpl, but I don't see changes related to this |
@matks & @kpodemski it's because I found a bug on the new release of blockwishlist |
@sarahdib ok, if so, this is not a solution, of course this code could be removed by:
|
Hello ! We discovered that with one of the wishlist SQL requests, we could get a The core is able to provide it by itself only if we DO NOT provide this information. As soon as we give a value, even wrong, it does nothing for us: Because of this value zero, it appears that we enter this By leaving the core handling it completely, we get rid of this error. |
@Quetzacoalt91 sure, I understand, make sure to check this PR tho: As without it y'all make sure to edit .tpl inside a module to get cover based on combination added to wishlist, not default one. |
$querySearch->select(' | ||
(SELECT `id_image` FROM `' . _DB_PREFIX_ . 'product_attribute_image` WHERE `id_product_attribute` = product_attribute_shop.`id_product_attribute`) cover_image_id' | ||
); | ||
|
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
I see. Because we can't change the behavior on already released versions of PrestaShop, I guess one workaround could be found on the module side. Would the suggestion above this comment help? ⬆️ |
you can safely remove this query :) to avoid issues with cover:
This should be enough. |
Oh okay ! I didn't get on the last message the changes were needed on the template. Ping @pablopolyte |