datakick

I've just released new version 1.0.9 which includes couple of bugfixes, and 2 new features: Verified purchase - review has new boolean field named verified_buyer. This will be set to true if customer really purchased product associated with review. This is determined at the time of review submission - there must exists already shipped order. This means that reviews submitted before product purchase will not be marked as verified. Administrator can check/uncheck this field from back-office. Verified purchases are highlighted in review list. Criteria breakdown - If you use multiple review criteria, you can now show them on review list. You can choose on of the 3 ways to display criteria breakdown. Don't show criteria breakdown at all -- this is current behavior, only average ratings is shown Show criteria on top, in single line separated by divider Show criteria on right side

@movieseals the idea behind blackhole bad bots mechanism is really very clever. It shouldn't be hard to implement this as a tb module.

@chandra I believe this is CCC bundle

@chandra that one's not generated by my module

@chandra sorry about that, I forgot to remove code that forces new css regeneration. Please edit file revws.php and delete line #464: $data .= time(); You can safely delete all revws-**.css files from cache directory. The easiest way is to clear cache from Advanced Parameters > Performance

@drmasterchief that's correct behaviour. These rows are linked using id_reference column - there should be only one active row for each id_reference. Every non-active row in this table represents a historical state / settings, and are linked to from orders / invoices. So, even if you change your shipping rates, your orders are not affected.

@Luv verified purchase / buyer will be in upcoming version of the module. I've already implemented it, but I want to test it a little bit longer, because this release requires database change. You can test it on my demo account - front / back

Since I have a little bit of a free time this week, I decided to implement another feature to this module. Since version 1.0.8 you can change star color from settings page.

I've released new version 1.0.7 - this is a bugfix - I've forgot to include txt email templates to previous module builds. This resulted in not sending emails.

@Troy-Roberts if the popup does not show, there's probably some javascript error. Could you send me url of your shop so I can have a look? Regarding emails - do you have email templates translated to your language(s)?

@slick_303 I didn't have smarty cache enabled before. When I enabled it, it started doing exactly the same weird behaviour you've reported before. With the fix it seems to be working.

@SLiCK_303 I may have found the problem with smarty cache. Could you please try it on your end to verify it's working - simply change line ~326 in revws.php from return $this->display(__FILE__, 'product_list.tpl'); to return $this->display(__FILE__, 'product_list.tpl', $this->getCacheId() . '|' . $productId); Then clear cache. Let me know if that helped

@SLiCK_303 - I've added zip file to release. Regarding php 7.xx - I couldn't reproduce this issue. Everything seems to be working ok on my 7.0.11. What version exactly do you have?

I've just released a new version 1.0.6 - this one get rid of inline styles we have discussed with @zimmer-media. This version introduces breaking change - if you copied front.css file to /themes/<yourtheme>/modules/revws/revws.css and modified it, it will no longer be used. To make changes to CSS, please create file /themes/<yourtheme>/modules/revws/views/templates/front/css-extend.tpl and enter your css changes here. Content of this file will be appended after content of file /modules/revws/views/templates/front/css.tpl. CSS priority rules will make sure definitions in css-extend.tpl file will have priority over default values from css.tpl file. You might have notices that the css file(s) has .tpl extension - that's right, this is normal smarty template, we just generate css instead of html markup. Generated css file is stored in you theme cache directory. Example of how to extend CSS styles - create file css-extend.tpl with following content to have your stars in red color .revws-grade-on path { fill: red; stroke: red; }

@zimmer-media said in [Free Module]Revws - Product Reviews: Despite the great module, you will be devalued by these many additional inline styles by Google. Google doesn't care at all if we use inline styles or css. What is important for them is page load and render time. And very often web pages with inline-styles only can easily beat css powered ones. Simply because there's no need for additional css fetch, and browser can start rendering the page even before it is completely downloaded and parsed. That's not possible if page contains css. But, obviously, inline styles impact page size, and that in turn impact load time. So it will have some negative effect. In our case we are talking about two inlines styles per star: style="padding-left:2px;padding-right:2px" and style="stroke-width:50". So we have extra payload of 325 bytes per review. If we have 20 products block on page, we will have to transfer extra 6k. But since everyone is using gzip, this will be greatly reduces to ~1k (gzip is great for repeating texts). With current speed of internet, this amount of extra data won't even register. We are talking about microseconds here. Compare it with size of all the retina images you have on your page... I agree it would be nice if I didn't have to emit these to page. Why don't I use css here? That's because we couldn't adjust theme from settings page. For example, star size option (and in the future fill and stroke colors, spacing,...). If these properties were hardcoded in css, we couldn't change them from ui. For example, try change star size with your revwspaddi class in place. It will not scale nicely, as 2px padding is too small for large stars. My module is targeted to ordinary users/merchants, not power users who knows how css works. And with that comes the price :) Note: maybe in the future I'll add some option to dynamically generate css files when theme options are changes in settings. But at the moment it has very little priority.

@pedalman I'm not really sure if you had the same problem @SLiCK_303 is experiencing. But I'll test the module on php 7.1 anyway.

@hubbobubbo you can map everything during import. You can also clean up data during import, if need be. I've just use this way to import yotpo reviews without any problems. Just ping me if you need any help setting up import. I can prepare import definition on my demo account, so you can have a look how it's done.

@nickon there isn't one. You need to install my module, and create a new list from scratch. Or you can try it on my demo account

@hubbobubbo thanks for letting me know. revws module is integrated with my data import/export module. So, if you can get your current review data into XML format (or CSV - you can transform it to XML using this tool, then you can easily use my module for import.

Thanks @SLiCK_303 for investigation. I'll try to reproduce the problem on my side. I'm not sure if this is bug in the module, though. What tb version do you use?

@hubbobubbo what review module do you use currently?

@nickon you can install my module and create list that matches your criteria. Once you are satisfied, you can add &debug-mode=1 the the url and my module will tell you the query it used to retrieve the data. That could help you a bit.

I've released version 1.0.5 added support for krona module ability to choose where you want to render review average (product extra / product buttons / nowhere) render review placeholder in product block if no review exits - you can use this to align block height for product with and without reviews some refactoring to make module migration easier

@wakabayashi - singlestore... but I can't reproduce it anymore as well, so maybe that was just some glitch in the matrix :) Anyway, do you think it would be possible to pass action label and message during registration? At the moment only action key is passed, and user have to manually enter labels for all actions.

@wakabayashi said in Planned Free Module: Loyalty Points: Have you already checked, if the hooks are working for you? I've just submitted integration with your module -- this version is still officially not released, I'd like to test it (and possibly extend) a little bit more. You can donwload this version from github if you wish to test it. I've encountered one problem - revws module registers 3 actions. They were all saved correctly to tb_genzo_krona_action table, but only the last action was saved to tb_genzo_krona_action_shop table. You should definitely check this issue.