Extension released: Social Brag module

Go to Extension page

Purpose
Customers are the best advocates. Customers proudly telling their friends about your product is the best advertising you can ever get. With that in mind, this extension makes it easy for customers to share your products in their social networks.

When customers finish their purchases, then on the success page, this module invites them to share on Facebook, Twitter or Email that they just bought your product!

Installation v 2.8

• Download the .ocmod file from the marketplace.
• Upload the file from

  Code: Select all

  OpenCart Admin > Extensions > Extensions Installer

• Go to

  Code: Select all

  OpenCart Admin > Extensions > Modifications

  , and click

  Code: Select all

  Refresh

Screenshots
Settings:

On Success Page after checkout:


Frequently Asked Questions

1. Which product is shown in the module? The most expensive product in the order.
2. I have a non-English site, or need to change the text of the module for another reason No problem! Just go to module settings

   Code: Select all

   OpenCart Admin > Extensions > Extensions > Modules > Edit Social Brag Module

   . There, you can provide the exact text, separately for each active language.
3. I have a non-English site, or need to change the text of the share button for another reason No problem! Just go to module settings

   Code: Select all

   OpenCart Admin > Extensions > Extensions > Modules > Edit Social Brag Module

   . There, you can provide the exact text for the share button, separately for each active language.
4. When I click the Share button to share with Facebook, I get an error! You need to create a Facebook app, and add the ID at

   Code: Select all

   OpenCart Admin > Extensions > Extensions > Modules > Edit Social Brag Module

5. How do I get the Facebook App ID? Log in at Facebook Dev portal. Select Add a New App from the Apps menu at the top. Fill out Display Name, Namespace, choose a category and click Create App. Go to Settings page and click on Add Platform. Choose website and enter in the new screen your website url in App Domains and Site URL fields. They should match with your website domain. Publish the app, and copy the App ID.
6. Does this extension work with my theme? It has been developed for OpenCart Default theme, and should work with most themes that use the same structure.
7. Does this extension work with Journal 2 theme? Yes!
8. Does this extension work with OpenCart 3.x? Yes!
9. I have an idea. Great! Post it as a reply to this.
10. I am having a problem with this extension. Please go to the extension page and click Get Support

Maybe a great module .. but I cannot see any GDPR compatibility!

OSWorX wrote: ↑

Wed Jun 13, 2018 3:59 pm

Maybe a great module .. but I cannot see any GDPR compatibility!

When it comes to the brass tacks, GDPR is about:

1. Minimizing the data collected, and not collecting data not relevant to the declared purpose.
2. Transparency with respect to what data are collected and what uses they are put to.
3. Control over personal data, including ability to remove such data.

This extension does not "collect" or store any consumer data.

In order to post on Facebook or Twitter, the user has to "authenticate" themselves. In order to send an email to "a friend", the user has to provide the email. But this is used only for sending the email, not stored. All of these functions should be covered by your store (and Facebook App)'s Privacy Policy.

I am not sure what, if anything, this extension can or should do towards GDPR compatibility.

You forgot that sending Emails from a Website to another person through a form (invite, recommend, etc.) is forbidden in some countries.
The website owner gets then punished if a reciever of such an email goes to court - because count as Spam.

Keep that in mind and inform about in the module.

OSWorX wrote: ↑

Wed Jun 13, 2018 6:02 pm

sending Emails from a Website to another person through a form (invite, recommend, etc.) is forbidden in some countries...because count as Spam.

I am not aware of this. Can you please point to any specific provisions and/or cases so that I can inform myself?

Either way, it's not part of EU-wide GDPR.

Also, please note that the message is sent from the customer's email address, not from the store's.

OC2PS wrote: ↑

Wed Jun 13, 2018 6:15 pm

I am not aware of this. Can you please point to any specific provisions and/or cases so that I can inform myself?

The net is full of articles about that and descisions - mainly Germany because their law is very restrictive in some points.

For example:
https://drschwenke.de/abmahnungsrisiko- ... heckliste/
https://www.bkwendler.de/index.php?acti ... zeln&id=17
https://www.repalogic.com/cms/40-tell-a ... date-.html

And a decision which may have a great impact for the next years:
https://www.online-und-recht.de/urteile ... -20150709/

While some of them talk at the beginning about Amazon, the decisoins are valid for all 'tell-a-friend' modules and functions.

And even when you send the email in the name if the sender, the reciever has to agree to recieve such emails (see GDPR which touch that in such a case).
And the server (mailserver) of the webshop is sending the emails, a user who know how to read mail headers, can see that.

You are 'only' the vendor of such a module, but finally it is your duty to inform that using such a module can lead to some 'unwanted side effects' ..

I went through the link you posted (courtesy of Google Translate), and based on it, I feel comfortable that the store owners would be well-protected since this module allows one "send" per purchase. It appears nowhere but on the order "success" page. I feel even more comfortable with it, because this exact implementation is also available at amazon.de

That said, as per your suggestion, I am adding a warning for potential customers of the extension in the description.

Further, I'll consider providing the admin an option to turn off the "email" function.

Well, I know you and trust you.
But such modules or functions have a long history at courts - specially in Germany.
The decisions you mention are mainly based on those functions at Amazon, but have an affect on all modules providing such functions.

And in one of the links is also a solution presented, Lawyers think that it will be okay: do not use the website internal mail function.
Instead use the mail system of the user who wants to share: use the mailto href
Therefore the website owner will never get in touch with any email address and cannot fetch it (if he wants ..).

Thanks, I'll consider changing the implementation of the mail function from `mail()` to `mailto:`