datakick

Glad I could help, fortunately integrating krona is not very hard, with most modules it can be done in hour or two. I'll add support to Send to a Friend Module v2.0.1 later this week. Are there any other community modules that would be good candidates for integration?

@movieseals said in [Free Module]Revws - Product Reviews: If we use the free module, will the paid version will merge itself seamlessly or is it a separate install? It's just a separate branch of revws module - you can install it the same way you would upgrade revws module to newer version. Simply upload zip and that's it, you won't loose any data or configuration. Every piece of code that's in free version is also in premium version.

@movieseals did you update from older version? If so, you'll need to reset the module (so the new hook get registered). Just make sure you reset only the parameters. If you reset everything, you'd loose price alerts data

That's weird. I'd really need access to your server to investigate further. At this point, it can be 1) the override code is not triggered (overrides are disabled, or maybe class_index.php is corrupted). You could check this by editing override file, and add some die('override is triggered') somewhere at the beginning of postProcess function. 2) the google captcha has been broken. That's not very likely. If this is the case, there's not much you can do until google fixes it 3) this is not an automated spam, but someone is posting the comments manually. Again, not very likely, but who knows I can't think of anything else

Well, on front end everything looks ok. So the issue is probably with override. Please check that there is override installed for ContactController. Also, make sure that both "Disable non thirty bees modules" and "Disable all overrides" are set to NO.

what's your website? I can't see any captcha at https://www.rampagesport.eu/

I've also integrated my own Price alert module

@movieseals here's support for wishlist module, if you want to use it, you'll need to download it from my github repository, branch krona. I'll create a pull request, but I'm not 100% sure it will be integrated. Krona module is a community module, and I'm not sure if TB maintainers would want to reference community module from core module. This integration creates 3 actions: wishlist created product added to wishlist wishlist sent by email Of course, you don't need to use all 3 of them https://github.com/getdatakick/blockwishlist/commit/134d757379bf385028a4eb7c674ae3d27b0c8205

@movieseals if you could make a list of modules / or built-in features / that should be integrated with krona, I could try to add support for them in my spare time

what captcha module are you using?

Hi everyone, I've just released first paid version of revws module - you can read more about it's functionality in one of the previous post. At the moment I only sell it on my own website, but I'm figuring how to add this to official thirtybees store. The development of this premium module is not finished yet - I plan to add additional functionality such as rewards for reviews, posting reviews to facebook, automated backups,... But don't worry, if you purchase module now you'll get all future updates for free. PS: you can test the paid module functionality on my demo account

@movieseals I'm afraid there isn't an easy way. Those third party modules will have to implement couple of hooks in order to communicate with krona module. With the small tb community this probably won't happen anytime soon. I'm really sad that this module is not ported to vanilla ps16, because the adoption rate by merchants would be much higher. And with that might come the support by third-party modules.

@colorful-ant try this ``` $content = strip_tags($post->content); $pos = strpos($content, ' ', 160); $meta = substr($content, 0, $pos); ... 'meta_description' => $meta ``` This will strip HTML tags from post, and take max 160 characters. It does not break words - meta description can, and usually will be, a bit shorted than 160 characters.

I've just release new version 1.0.18 Enhancements sanity checks - detect problems with module configuration - report missing email translations etc. improve review creation experience for multiple criteria - there is now a slide effect between criteria drilldowns - links from review list to product / customer microdata - emit information about worst and best ratings fix translations [nl, de, es, ru] dedicated data export / import page (extracted from settings) multiple bugfixes microdata - render aggregated ratings within review list microdata - incorrect calculation of average ratings MyReviews page - fix bug with missing product information

Thanks @nickon for the feedback. I would put the revws subscribe block UNDER the ps/tb thank you block. So that the user is not confused I can't change position of subscribe block - this is decided by theme itself, I just render the content. You would need to modify your theme and move hook placement to some better position. When clicking on the subcribe button I would change the button to “thank you for subscribing” Good idea The checkbox of the email subscription should be on gdpr module where I could check/uncheck the consend I see what I can do about this. Unfortunately it might not be possible, as prestashop's official gdpr module expects every module to have only one consent. In revws case, there are actually two consents, each for specific area of functionality. One is for review authoring (permission to use provided data when someone write a review), the second needs to be given when user create an account, so we can communicate with them.

According to upgrade process you have to Go to your modules directory and DELETE all of your stats module except statsdata and statsmodule. Also delete the modules graphnvd3, gridhtml, pagesnotfound, and sekeywords.

@nickon Someone switched consent mode to Not required, so that's the reason why consent checkbox was not displayed. The module can be access from Catalog > Product reviews

Hi everyone, some of you may already know this - I'm going to release a paid version of revws module with ask for review by email functionality (and then a couple more features). I've just started testing it on my demo account, and I wanted to ask you for your help and feedback. If you are interested in this functionality, please try it. There are these areas to test Consent management with all the GDPR stuff it's important to be nice and friendly. That's why I added support for consent with sending review requests. You can choose one of these consent levels: - no consent required - newsletter subscription is considered consent - either newsletter subscription or explicit consent - explicit consent When you choose one of the explicit consent levels, then you will get a consent checkbox on Account creation page, and also additional request on Order confirmation page (but only if we don't have consent yet) Also, you customers can unsubscribe from receiving further email requests, so that should help with compliance as well. Order list There are many options to specify for which orders (and when) email requests should be sent. For example, you can define min and max order age, order state, or how long to wait after merchandise was shipped. To make things easier to understand I added a list of all orders. This list is displaying a stage in which each order is. So you can easily check and see what is going on, why some review requests are not being sent, etc... Emails And of course there are review request emails. You can, obviously, start review process from there. You can also unsubscribe from further review requests. And, to make things a bit more user friendly, there is auto-logging functionality as well.

@luv thanks for reporting this. This is a known bug, and it's already fixed in upcoming version

I was suggesting to use different approach than attribute groups. Attributes are used to generate product combinations. Each combination must have an record in db -- and that's not possible with this many options. Customization, on the other hand, is something completely different. It gives your customers option to customize the product when they order it. I think this is what you want.

Disallow this page using robots.txt, google will eventually stop indexing it.

If these attributes don't have impact on quantity on stock, or on price, then it doesn't really need to be an attribute in the first place. You should have a look at some customization modules, for example https://addons.prestashop.com/en/combinaisons-customization/6638-advanced-customizations.html

If the tbupdater is meant only for those native thirtybees modules, then it makes sense to fix these. It could be a lot of work, though, as someone would have to go through all of them. If, in the future, you plan to use tbupdater module to install / update third party modules (for example community modules from tb store), than this could be a big problem. I've seen many modules that allow user to uploads images (or other files) and stores them somewhere in module's directory. It's not realistic to expect that module developer will fix this. I'm afraid we'll need to choose the lesser evil here. The replace method would keep module code clean, but module updates might result in loss of file-data. The merge method can result in quite a mess in the module directory, with outdated / unused files everywhere. But the module will still work in 99% of the time (unless it does some dangerous *.php autoloading), and no data will be lost. But we definitely need to decide which algorithm to use, and use it both in tbupdater, and in manual module update in core

I checked this - when we manually upload module zip file from backend, its content is merged with the existing module directory. However, when module is updated using tbupdater module, the old module directory is completely deleted and replaced by content from zip package. Although the tbupdater approach sounds like a much better way to me (definitely more predictable and maintainable), I'm afraid it breaks backward compatibility - any module that stores some data to its own directory will be affected by this. Maybe the best solution would be some mixed approach - replace all code files (*.php, *.tpl , *.js , *.html , *.css ) , but keep binary data (images, etc). Also, it would be nice if the same algorithm were used for both manual installation and tbupdater

More information regarding translations. At the moment revws module is translated to bg, cs, de, es, nl languages (only partially) txt Translation 'bg': 156 strings translated [ 62.15% ] Translation 'cs': 251 strings translated [ 100% ] Translation 'de': 170 strings translated [ 67.73% ] Translation 'es': 235 strings translated [ 93.63% ] Translation 'nl': 170 strings translated [ 67.73% ] It would be amazing if you guys could help me complete these translations, or add support for another language. There are few ways to do this: 1) normal prestashop translation process - just translate everything in your thirtybees backoffice, and then send me .php file 2) download and edit language json file from github. If language does not exists yet, download en.json and rename it to your .json. When you done, send me json file via email 3) if you know how to work with git, then clone revws repository and make changes directly there. Then create pull request I personally prefer editing strings directly in json file, as I don't have too much confidence in prestashop backend translator tool.