31 comments found.
How is it possible that you don’t support catalog pricing rules? After all, that’s the basis of promotions, you treat the price set by the catalog pricing rule as not a promotional price – I’m shocked that this scenario isn’t supported.
Catalog pricing rules are supported of course, please make sure you have the latest version of the module and your shop does not have any modifications. I’ve seen shops with changes in the code that you can’t even imagine, fooling the module to treat prices as not promotion ones 
This is weird.
1) Setting a catalog pricing rule for all catalog, 2) The information lands in your module table:
is_specific_price = 0 after setting the catalog price rule and price reindex – it always lands there 0.
First versions of the module had this kind of a bug, because for a general price rule (applied on all the products) PrestaShop does not store this information on a product level. That was fixed long ago.
Hmm, 1.2.8 , Prestashop 8.0.3. Totally weird – in that case.
It may require some investigation, drop us an email so we can check it out.
Okay, i fixed this by truncate gm_omniprice_history and gm_omniprice_index tables – now its working.
but that’s strange – in my opinion you should check the following case:
- all prices are indexed.
and in this case when all prices are already indexed – i.e. the gm_omniprice_history and gm_omniprice_index tables are filled, only now do you throw in the catalog price rule – then in my opinion the table is still is_specific_price = 0 and the module treats that all prices are indexed….so it doesn’t display anything.
in my opinion it’s a bug in the module.
This is an interesting case, but it would require a closer look, so in case of any further problems drop us an email and we’ll check it out.
Another thing – why don’t you consider the option of displaying {$product.regular_price} or at least such an option – when the module has no basis for displaying information.
Having many clients – I know that they interpret the provisions of the Omnibus Act differently and one claims that this price without history is good and another claims completely otherwise (and should be $product.regular_price)
You clients may claim different things, but we have feedback from clients who had it controlled. A product should not be put on promotion right away, this is a false promotion. It should have a regular price for some time, so the module should also have time to notice this price and store it in the history. Also it is forbidden for products to have a “forever” promotion price and never get back to regular price. So we’ll stick to that 
I understand and agree with that, but you should give a choice and the client should decide what to display, however – maybe it’s not a must-have, we can always modify it for the client of the “imaginary lawyer”.
Regards
Recently I added 2nd currency and now I have 2 currencies for 6 shops with around 400 products shared across them.
I noticed that I have the banner only visible for the default currency and not the second one.
So I manually ran the cronjob and it took around 7-8 turns with 1000 batch size to index all prices but the banner did not display in Euro.
I see in your demo that it is working so could you direct me what I’m doing wrong?
Thanks!
In the price history there must be at least two different prices for the message to show up, so after one run (and no changes in prices), the module may only have one price stored in the history.
So basically that’s because I enabled the second currency after the promotion started and there’s no initial record?
Thanks!
Yes, exactly!
Thanks!
How I can solve the multiple run issue, could I schedule a cronjob 1 minute apart?
Sure you can, I even recommned smaller batch size (to make sure there are no timeouts) and more runs.
Thank you!
Jakaś możliwość aby pokazać tekst w paczkach produktów?
can you please update the Changelog on the product page information? thanks (in the changelog when you speak about a module”groupinc module” add also the addon url https://tinyurl.com/yr4lln72)
Changelog updated, thanks
Is possible to choose a list of categories where the label must not be present? We have a category called OUTLET where the prices are always discounted (not a promotion) because products can have some small defects and customer can see the original price of a good version vs the discounted version.
is compatible with PS8.x ?
Yes it is
thank you for the answer is supported also the multistore?
Hello,
Is there any easy fix for:
Message: count(): Parameter must be an array or an object that implements Countable
Location: modules/gm_omniprice/gm_omniprice.php line 622
STACKTRACE #0 modules/gm_omniprice/gm_omniprice.php(622) #1 modules/gm_omniprice/cron.php(25): Gm_OmniPrice->savePrices(true, 39)
Sure, that’s a minor issue, we’ll upload an upgraded version soon.
Thank you! It’s pumping lots of warnings in my logs.
Any new modules soon from you? Really enjoying the two I purchased!
We mostly do custom modules for our customers and the modules are often not general enough for a public sale, but if you have any needs for modules just let us know
W zakładce Moduły na karcie produktu na zapleczu, podejrzeć można zapisaną historię zmian cen produktu, co może być pomocne do analizy tego, jaka cena (i czy w ogóle) powinna się wyświetlać.
Jak wchodzę w zakładkę Moduły na 1.7.8.x Mam tam omniprice i przycisk konfiguruj ale po przyciśnięciu nic się nie dzieje. Nie widać poprzednich cen. W bazie danych w tabeli widać daty i zmianę cen.
“na karcie produktu”
No jestem w karcie produktu i nic tam nie ma.
Prosimy o kontakt przez formularz supportu, tutaj więcej nie da się pomóc.
Nie mam supportu ogólnie pytanie jest proste nie widać tego co Państwo obiecują na stronie produktu. W dokumentacji jest napisane że widać zmiany a ich nie widać. Back office jest dla każdego taki sam więc nie widzę problemu aby to nie działało u mnie a u Państwa działało na 1.7.8.x
A moduł jest na pewno zaktualizowany do najnowszej wersji?
Tak do najnowszej.
Nie mieliśmy jak dotąd zgłoszenia że tego nie widać w wersji 1.7.8, więc musielibyśmy to zobaczyć na żywo, różne czynniki mogą wpływać również na zaplecze Presty, wystarczy jakiś drobny błąd java scriptu jakiegokolwiek pochodzenia żeby zakłócić działanie zaplecza. Prosimy o kontakt mailowy.
Napisałem, proszę kontaktować się na ten mail co podałem ten przypisany do konta służy tylko do kupowania modułów.
Hello,
I have the following error and it started appearing after I switched to multishop:
https://pasteboard.co/4y5hVKd2gyaV.pngHello, thanks for letting us know, we will analyze it.
Hello! Does this module also works with unit price? I am only showing unit price on my product page. Will this work? Thank you!
Hello! It won’t work with unit price by default. Some modifications would be required to retrieve the unit price ratio and calculate the unit price.
Thanks for your answer! Do you think this will require some core changes to the module? Will it be very complicated? I sell products by square metre and have no other option. But if you think it is possible, maybe I should try to make these changes.
PS Dopiero zauważyłem, że jesteście z Polski
The changes may be a bit complicated
Is this module multishop compatible?
I turned on Multishop and the module saves correctly it’s settings but when I want to make a forced reindex it gives me ‘invalid token’ message.
The token has not much to do with Multishop, it should be the same all the time. Maybe you are adding that additional parameter incorectly and the module treats the whole string as a token.
Yes, you’re correct… I’m putting ? instead of &. Sorry for the spam!
The module is compatible with the progressive discount management system provided by the implementation of the European Omnibus law in Italian regulations, which states that ‘In case of progressive discounts, the price to be indicated is the price without any reduction before the first discount applied.’ In practice, in case of progressive discounts, such as sales or Black Friday, where the discount varies from day to day, the module should display the price without any reduction before the first discount applied during the campaign.
Currently not, the module displays price before the current reduction, not the first reduction. But we are considering adding this option in the future.
Thanks for your reply; does the module offers the option to hide some previous price? In this way I can hide the price reductions in case of progressive sales, managing manually.
Sorry, no option like this, it would be hard to manipulate the price history this way.
Does it support multiple languages?
Yes it does.
Dzień dobry, jak dokładnie wygląda hook aby umieścić najniższą cenę w innym miejscu na podstronie produktu? W dokumentacji nic o tym nie ma.
Ok już znalazłem na jakimś forum {hook h=’displayProductPriceBlock’ product=$product type=”after_price”} Tylko teraz on się dodaje z identyczną klasą jak ten poprzedni. Da się to jakoś rozróżnić żeby w CSS jeden schować albo w ogóle go wyłączyć?
{hook h=’displayProductPriceBlock’ product=$product type=”after_price”}
To trzeba zostawić sobie w szablonie tylko jeden, nie powielać go tylko przenieść w inne miejsce. Warto jednak zaznaczyć, że zgodnie z przepisami informacja o poprzedniej cenie powinna być w bezpośrednim sąsiedztwie ceny produktu, a nie gdzieś dalej.
co mogę zrobić aby informacja wyświetlała się w nowym wierszu pod ceną?
Powinna wystarczyć jakąś prosta dodatkowa reguła CSS. Na początek można spróbować zmienić display: inline-block; na display: block; w pliku views/css/gm_omniprice.css
Dziękuję
Cześć, klientowi instalowałem wtyczkę, wszystko zrobione według dokumentacji i, mimo tego nie wyświetla się po obniżeniu cen i promocji szablon Warehouse Co może być przyczyną ?
z góry dzięki za odpowiedź
Aby wyświetlały się ceny muszą być spełnione następujące warunki: 1. Aktualna cena jest ceną promocyjną 2. W historii cen jest zapisana przynajmniej jedna poprzednia cena, różna od aktualnej 3. Z szablonu karty produktu nie został usunięty zaczep displayProductPriceBlock z parametrem type=”after_price” (powinien być domyślnie w każdym szablonie)
Warto też pamiętać, że moduł zapamiętuje w danym dniu cenę tylko raz, aby oszczędzić miejsce w bazie danych.
There’s a strange bug with 1.1.5 and Warehouse theme’s Mega Menu
When I go on a product with visible row from the module all products have the same line under their names in Mega Menu. When you go to another page where the module is not visible this row is not visible.
Warehouse 3.8.7 Module 1.1.5 TB – edge
Also – a side question. Datakick removed a js function displayPrice here: https://github.com/thirtybees/thirtybees/commit/4908ec86b34a2fc3a78ea22508d0cdf42c5855bb
Will this affect this module by any means?
This module has practically no CSS so this effect must be realated to something else, some theme bug or a side effect of something…
In PS 1.6/TB the module uses the displayDiscounts JS function, so it should not be affected by removing displayPrice.
BTW. 1.1.5 had a cleanup bug, so please update to 1.1.6.
Since last few versions the module does not work for me. When indexing I don’t see the table and on save only 1 price is always visible -> the module does not show at any product.
Any advice what to check. Just tried installing 1.0.6 and it works (probably more recent versions will also work, but this is what I got on hand).
Hmm, latest changes were not that big and did not include any changes of the price gathering algorithm. Maybe please contact us by email so we can share some links and screenshots to be able to help you.
Are you planning to add a hook to product list? Because, unfortunately, many owners of shops demand it.
Adding this information to product list should be possible in exactly the same way as it is done on product page, just use the same hook with type=”after_price” parameter and put it in the tpl file responsible for product lists. The reason why it is not there by default is that adding this information would mess the design of the listings, making blocks with promotion products higher then other ones. So help from a frontend developer is required in this case either way to adjust the way it looks on the listing and is strongly dependent on the theme used.
it is working with other themes like AngarThemes? It is one year license or 4ever?
Yes, it is able to work with any theme. Some themes have the required hook removed or hidden, but bringing it back is 5 minutes of work. And it is 4ever
It seems to me that the module is still missing the display of the text “The price has not changed”. , when the price is not discounted or when the module is won fresh to Prestashop and we don’t have historical data and the price was discounted before the module was installed in the product it should automatically take the discounted price if the discount was added before the module was installed. But probably the best option would be to add “The price has not changed” what do you think?
If you say “the price has not changed” then you admit that the promotion is a fake one and the product never had a normal price but is on a discount since forever But if the promotion is added before the module was installed then we have a solution to display the current discounted price as the lowest one, but it’s not offical since we believe it’s not precisely according to the new law. Please contact us directly and we’ll explain what to do.
Thank you for your answer!
