datakick

@nickon awesome, please try this one and let me know if it works.

@nickon I'll add the js code, hopefully it will work. I don't have these themes, though, so I can't test it.

@mockob that's hard since I can't reproduce it on my end. I've tested it on android, ipad, windows phone, in chrome-devtool phone simulator,... and it works everywhere just fine. I've added one more touchevent and css rule to prevent screen scrolling/swiping, but that's all I can do at the moment. Here's latest version of module with these tweaks

@nickon not really what I meant. The html markup isn't that important, what's important is how the tab switching is implemented. It can be as simple as assigning 'active' class to li element. But more commonly it will use some jquery plugin. Or maybe some proprietary javascript code.

@mockob yes, unfortunately this is very theme-related. It's really up to theme designer to decide how to render tabs, and how to switch between them. I could add some code that will fix this problem on community theme (and maybe on many other themes that use the same mechanism), but it's not guaranteed that it will work on all themes.

@movieseals that's a lot of modules, I'm quite surprised. Usually 1.6 modules are working without problems. Maybe the culprit is somewhere else. Does you dev server have the same configuration as your production one? For example, do you use the same PHP version, or mysql settings? You could install vanilla prestashop 16 on your dev server and then try to install these modules there, to check if it's environment problem, or if it's really 30bz related. If this is problem with thirtybees, I could have a look at these modules for you, is you wish. For developers it's a bit easier to spot the problem. PM me if you need my help.

@vincentdenkspel thank you for this resource, its indeed very interesting read. Yes, I plan implement something very similar to this breakdown

Very simple yet brilliant idea. Kudos.

@MockoB and @30knees - I've tested the touch events on iPad and android, and it works just fine for me. Could you please re-test? Maybe your device has old version of javascript cached, or something like that. I've fixed the problem with NaN - this one reproduced only on ios devices. Also, here's new version that adds rich snippet support. It can be disabled, so you will be able to use json module to emit microdata. One more thing - I've moved Product reviews menu item under Catalog. That's probably the best place for this.

@zimmer-media said in I'm going to create a free module: If I have at least 2 criteria, where do I recognize the different rating. Eg rating for quality, rating for criterion 2, rating for criterion 3, etc at the moment the only place where you can see it is when you edit review, admin in back office, customers on front. I'm still thinking about the best way to display this info to visitors. Together with some review filtering, and possibly some overall statistics.

@nickon said in I'm going to create a free module: It should be easy I think All it should take is that module lets you pick a template and you display it in a generic block That's the thing about software development - nothing is easy, if you want to do things properly :) I can't just hack this in, there are multiple questions, and each one of them will have consequences that needs to be taken care of. For example - where should we save store review? There is already a db table with reviews, let's store it there. But what about product_id column? It can't be null, database won't allow it. Eh, I can surely save 0 there, to distinguish between product and store reviews. But now it's not really product id, is it? I can no longer safely use inner join in selects... Well, I can live with that... ...after few hours of implementing... Great, I can now create store review. But when I save store review, it sends wrong email. Email says that I've reviews some product. And product title is empty, and image is missing... why? Well, the notification mechanism that watches changes in product reviews kicked in, obviously, since I have saved the store review as a product review... To fix this, I will have to add couple exceptions to the code - in case the review is for product do this, otherwise to that. That's not good, I don't like it... I wonder, what else will not work? I should have created a separate table for the store reviews... and a separate model to handle changes. Oh crap, let's rewrite this sh*t... ..... And this is only a question about how to save review. There are others, for example review criteria - we can't reuse current criteria, as they can be associated with specific product categories or even with specific products. This would be really big feature. I might implement this in the future, if you guys want it badly, but at the moment it's not on the table. Sorry. Also, if I ever implement this, I'll probably make it a bit more generic, so we could have a reviews for different entities - products, store, brands, or even customers (might be useful for marketplaces to rate sellers)

@mockob said in I'm going to create a free module: also when I rate the product when I choose stars they are not colored yellow. should be fixed now, however I could only test it on my old windows phone running ie :) could you please verify it works on normal device as well?

@mockob I've just re-tested it and I thing that caching bug was fixed. There is one thing that may have confused you - when you create a review, it's not approved by default. Until it's approved, you are the only one who can see it in the list (so you can edit/delete it). But it's not actually counted in total reviews you see on product/product listing. As shown on this image:

@MockoB you are right, the caching problem was still there. Here's new version

I wonder how accurate builtwith.com data are - they track ~576 sites

@lesley said in 19 Patron ?!: We are seeing between 50-100 installs That's surprisingly high number, congrats! How many of those are production servers, though? That's the more important metric

@cassim my module has mass-update functionality. That's what you want.

my module has mass-update functionality that could be used for this. You can try it, there's 14 day free trial period

@mockob what bugs in particular?

New version is available - this one fixes bugs you guys reported, and also adds integration with email automation module and my very own import/export module. You can test it on my demo account. Note that I'll release email automation module sometimes next week if I have enough time finish the UI. Datakick list Datakick export reviews to xml

@pedalman what are you trying to achieve? If you want to disable the whole address validation functionality, then you need to do following steps: 1 - don't load google api library - get rid of following lines from AdminOrderController $apiKey = (Configuration::get('TB_GOOGLE_MAPS_API_KEY')) ? 'key='.Configuration::get('TB_GOOGLE_MAPS_API_KEY').'&' : ''; $protocol = (Configuration::get('PS_SSL_ENABLED') && Configuration::get('PS_SSL_ENABLED_EVERYWHERE')) ? 'https' : 'http'; $this->addJS($protocol.'://maps.google.com/maps/api/js?'.$apiKey); 2 - get rid of actual geolocation javascript call. Edit file <admin>/themes/default/template/controllers/orders/helpers/view/view.tpl and remove everything related to geocoder. For example, you can replace line var geocoder = new google.maps.Geocoder(); with var geocoder = (window.google ? new google.maps.Geocoder() : { geocode: function(address) { console.info("Automatic geocoding was disabled: "+address.address); } }); Now, if you want to make this whole functionality on demand, that will add a lot of complexity. You would need to add some preference so tb users could actually choose if they want this functionality on demand, or keep it as it is now if it's on demand, then you'll need edit order page, add some button, bunch of javascript that will dynamically and asynchronously load the google library, and once the library is loaded then initialize it with api key, and perform the actual geo call... This is a lot of work. And I wouldn't expect guys on core team to implement this, as it really doesn't bring any actual value to merchants. It doesn't fix any bug, it doesn't provide new functionality,...

@krystian I'm afraid this is something that devs here won't help you with, as it's related to ps17. 30bz is a fork of ps16, with no trace of symfony code in it. You'll probably have to raise an issue on ps forum, or on symfony framework.

@krystian, are you using thirtybees? NumberToLocalizedStringTransformer is part of symfony framework...

@nickon I'm actually working on this feature, it will be released soon. It will be a standalone module though, one that you will have to install alongside revws module. The ultimate goal of this new module is to let you set up various email automation flows, such as review requests or abandoned cart reminder. But that's in the far future - at the beginning only review requests will be supported. I agree with @wakabayashi that the emails should have opt-out / unsubscribe functionality, and they will have. Customers will be able to opt-out from the whole functionality (no more review requests). There will also be an option for merchants to decide whether to send review requests for products we have already sent request for in the past. And also some other options, such as how many review request can be sent concurrently (default only one active request per customer), etc... These kind of settings, unsubscribe functionality, and tracking email opens/clicks will be shared with other flow types, that's one of the reason I wanted to separate this functionality from the review module

I have a question regarding rewards for reviews - what type of rewards are possible? All I can think of is loyalty points, but I'm sure there are other types of compensation.