datakick

There is bug indeed. To fix it, modify file /modules/blocknewproducts/blocknewproducts.php and change line ~308 from foreach ($caches as $template => $cacheId) { Tools::clearCache(Context::getContext()->smarty, $template, $cacheId); } to foreach ($caches as $template => $cacheId) { Tools::clearCache(Context::getContext()->smarty, $this->getTemplatePath($template), $cacheId); }

Today I've released new version 1.0.15 - this one brings in some GDPR nonsense. You can newly choose to display consent checkbox on review submission form, if you think it's necessary. It's probably not, but better play it safe than be sorry. It also integrates with official prestashop GDPR complience module. That's not probably very interesting for you thirtybeerers. But in case you are running ps17 somewhere, or if you have bought ps16 version, you can use it to export and delete user data.

Here are official guidelines from ps how to make community modules GDPR compliant @SnowyCat / @lesley - will thirtybees GDPR module be compatible with these hooks? It would be very unfortunate if it wasn't, as all ps16 modules who implements these guidelines couldn't be used on thirtybees

All right. I'll implement csv data export and data deletion into my modules. Once you guys have GDPR module ready I'll integrate these features with your hook(s)

@lesley thanks. I hoped that the consent won't be necessary. So I guess there will have to be two new hooks that core (or GDPR module) will trigger. One hook for data deletion, and one for export. These hooks should probably receive customer id and customer email as input parameters, so modules could find the data accordingly. The deletion functionality is quite straightforward, export is more tricky. Will it be sufficient if module returned associated data as one big string blob?

I know next to nothing about the upcoming GDPR sh*t, so I wanted to ask more knowledgable people on this forum if there's anything I need to change in my modules to make them GDPR compliant. I have two modules that I believe could be affected - revws module that collects product reviews, and price alert that notifies your customer when prices drops below some threshold. Both these modules collect personal information, specifically email addresses. So, do I need to add some sort of consent on form, or will this be covered by some generic site-wide consent? Also, do I need to implement some hook to delete user's data, say hookEuropeanBureaucracy? Is there anything else I need to worry about? I would really like to have some sort of GDPR compliant badge on my modules :)

Because perk is considered sale of digital service, every EU-based patreon will be charged VAT according to his country. That shouldn't be a problem for businesses, as most merchants are VAT payer, so they can deduct this charge back. This only negatively impacts patreons without VAT number.

I've released new version 1.0.14 -- added support for Multiple languages. You can now choose to display only reviews written in visitor's language. This settings is recommended for any shop using multiple languages feature: it will reduce the noise on your product page, displaying only information relevant to each visitor it will have SEO benefits - no duplicate content between different language versions Of course, you can disable this feature and keep displaying all reviews regardless of language. This can be useful in case you haven't collected many reviews yet.

@rubben1985 said in Landing pages: I already said once that CMS and landing pages is the biggest hole That is very interesting information for us, developers. Although I'm not sure if it's really so requested feature - when I did the poll about what free module to develop, nobody suggested this functionality. ...which is a shame, I'd love to work on something like this. That's exactly in my wheelhouse...

Another minor release 1.0.13: ability to trigger review dialog using url parameter named postreview, ie: https://www.domain.com/en/home/my-awesome-product/?post_review. Same parameter is used by @SLiCK303 's send review request module. This change shouldn't affect integration with this module at all added support to choose layout (left and right columns) for MyReviews section check module version now display release notes

It seems like the problem is that the module prefixed namespace of stripe library with ThirtyBeesStripe, but the prefixer program didn't replace references inside Util.php - it tries to use unprefixed class Stripe\Customer instead of ThirtyBeesStripe\Stripe\Customer You can try to modify file modules/stripe/vendor/stripe/stripe-php/lib/Util/Util.php, edit function convertToStripeObject, and add this ThirtyBeesStripe prefix to all objects in $types array, and also on line 117. But obviously this needs to be fixed on different level - paging @mdekker

Error code won't help us, it's encrypted using your server's key. You'll need to paste it to Advanced Parameters > Logs > Decrypt an exception message to get plain version. Then you can decide if it's safe to post it here

@30knees said in CSV Import killer app features list: Take a look at the @datakick module. It's very capable! Thanks for the shout-out! Unfortunately my module can import only XML files at the moment, CSV support will come soon.

This is indeed nice feature, but I'm afraid the implementation won't be trivial. First of all, quantity on hand for packs can't be just some virtual number calculated in php. There are numerous places in core (and in hundreds of modules) that expects quantity information to be stored in stock_available database table. It's not possible to fix them all. So, to implement this, we would need some synchronization mechanism that would keep data in stock_available table in sync - whenever quantity of child item is modified, we'd need to update pack quantity as well. I'm afraid it will be very hard to keep these in sync, even if we used database triggers.

seriously guys, why should we even care? This is one request per hour, and that's definitely wont hurt your server - just compare it with one page load of average visitor - that's like 20-30 requests and hundreds of sql requests. If you ask me, this cron service is one of the nicest gesture prestashop as a company ever did. Granted, it's not perfect and it's very buggy - but hey, we can say the same about ps codebasem and we are using it daily. This service removes barrier to entry significantly, as it allows for scheduled tasks out of the box. There are many merchants who doesn't understand how cron works. and software shouldn't force them to learn about it.

@vincentdenkspel do you have SPF and DKIM set up properly? My suggestions is to outsource sending emails to third party service, such as mailgun (I personally have great experience with them). You could: create a dedicated subdomain for transactional emails, such as mail.yourdomain.com (you can still send emails from [email protected] using this subdomain). Don't send any other email using this subdomain (for example, if you have mailchimp, create another subdomain for it) sign up for mailgun, or other similar service for transactional email. set up SPF and DKIM dns records for this subdomains (they'll guide you) use their smtp service to send emails from your server. Alternatively, you can set up email server on your vps as an email relay - your local email server will forward emails to mailgun smtp server. This will help in case mailgun smtp is down (very unlikely, but it happens) These service providers are very good at delivering emails. They know all in and outs, and it really shows. They employ special algorithms, such as email validation, advances queuing, and scheduling, they have fallback mechanism for bounced emails, etc... in short, they make recipient's email servers very happy, and thus gradually increasing your mail reputation.

@bocua try it and let us know

I've released a new version 1.0.12. This version http requests uses CSRF security token to protect against cross site request forgery attacks. It's a very important from security point of view, so revws module won't be abused for sending spam. CSRF is good enough protection against most of the dumb/blind bots. But I plan to implement captcha as well, so even more sophisticated bots won't have a chance added option to check (automatically or manually) for new version of the module added support page with links to this forum topic as an official discussion board (so hopefully that will bring in some prestashop users), and a few other links to modules that cooperate with revws - @SLiCK_303 's send review request, @wakabayashi krona module, and of course my very own datakick module.

@slick_303 you are right, it's the same action from database perspective. Both actions will mark review as deleted. The difference is not what happened, but who has performed the action. When it's review author, the action is Delete review. When it's administrator, the action is Reject review. This distinction is important, so I know what emails to send. Regarding real delete - I plan to implement filtering into backoffice review list. The list will, by default, hide all delete reviews. But it will still be possible to show them. So this will partly solve this nuisance. And after that, I'll maybe implement real delete function. But it has very low priority.

The looks amazing

I've released new version 1.0.11. This version brings better integration with datakick and krona modules. And it also let you import yotpo reviews

@manisch this really seems like some data integrity problem caused by botched data import. I'd guess data from different tables were incorrectly paired, possibly referencing non-existing documents. I could have a look at your data to confirm this, but it probably won't help you much. It would be hard to fix the data in place - it's probably better to do the import again.

@cassim said in Setup mail delivery + modules: And you think this will work. Or will that just show if they have open for that port. ? that's just verifies whether port 25 is open or not. It should display this: Trying 104.199.96.85... Connected to in.mailjet.com. Escape character is '^]'. 220 in.mailjet.com ESMTP Mailjet

@cassim than it's most probably your server configuration fault. You should contact your hosting provider, and ask whether they block ports 25 and 465. Alternatively, if you have ssh access, you can connect to your server and try running command telnet in-v3.mailjet.com 25

@cassim have you tried to set up the same smtp configuration in some email client, say thunderbird? If it's not possible to send email with this configuration even from thunderbird, then it's an issue with mailjet. - you have either used wrong server, username, password, or encryption method. - if you are sure you've entered the right connection info, then contact mailjet support - problem must on their side. If you can send email using this configuration from thunderbird, then it's an issue with your server configuration. For example, there may be some firewall blocking communication with stmp server.