Membership Pro and the new GDPR regulations

Tuan. If my membership secretary gets a phone call from a member and updates via the backend we have no record of the change. If she could do all her work through the frontend that would then trigger the email that would work for me.

mike,

Would this be of any use to you? I've just installed it and it seems a plausible solution to being able to document end-user changes that occur with their accounts: extensions.joomla.org/extension/clients-...ension_limitstart=36 / www.richeyweb.com/development/joomla-plu...-e-privacy-directive

Regards,

Is it possible to define the order in which this item is displayed? I should display it before payment information, at the end of custom fields.

Unfortunately, it's not possible. If you want to change it, you will need to customize the code. Take a look at the file , change this block of code to the the position you want:

For your need, just move it below this line:

Once the change is done, please move the change to PATH_TO_TEMPLATE/html/com_osmembership folder so that the change won't be lost when you update to future releases of the extension

Regards,

Tuan

Hello Tuan,
Could you advise what setting I need to change to have best compliance with GDPR (in Membership Pro and in Events Booking?) For example, I still want people to be subscribed to an Acymailing lis when they join/subscribe, but especially with Events, I think I need a 'subscribe me' button so that the person knows and agrees to her/him being on the list. Should it be a 'custom field' for the front-end Form, as a radio btton or checkbox? If so, what should be the values codings? And should we Not use the auto-subscribe options in the Events/Membership settings?

Thanks, Robin

Just want to update that we answered the questions via support tickets. For Membership Pro, see membershipprodoc.joomservices.com/basic-setup/gdpr

For Events Booking, see eventbookingdoc.joomservices.com/basic-setup/gdpr

Regards,

Tuan

Thank you for all the good work.
I have a few issues
There is a need for a "required" switch of the privacy policy. The reality is that it will take many months to get all members to agree, and in the meantime admin cannot update the data base without being "required" to click the box. This defeats the point.of recording acceptance. So I need to be able to choose when the acceptance is "required".
Next, I need to have the releavant field data in the export data base. I need to be able to sort this list and find who has not agreed so that I can target follow up. I cannot do this unless the fields are listed.
Thirdly I need to be able to transfer in data from CB where the current data is held. I cannot do this without a field identity in the data base.
My solution on this at the moment is to use custom fields because the new features you have made are just too inflexible.
I am on the point of a major membership upload from CB, but holding off until some of these issues are settled. I do not want to have to go through the database and make complex manual changes to a large number of records.

Hi Tuan,

There is still an important GDPR rule that I think is still missing and would be welcome ASAP (better if fixed by May, 25 ... The GDPR call us to privide a direct easy way to DELETE AN ACCOUNT to a given member ...

I think we need a button at MemebrshipPro profile view that could allow a member to delete his subscription or even better, to delete his subscription and his linked joomla! user account at once ...

I can survive some days more by using the FREE Delete My Account add-on that deletes the Joomla! user account but that's not perfect as it leaves the subscription entry orphaned.

I would like to hear your toughts about that, too

Waiting your feedback,
best.
_gabriel

That delete account feature should be handled by Joomla core, not Membership Pro

There is an already effort in Joomla core repo for that feature. I will attempt to spend my time to help getting that feature added to Joomla core in 3.9.0 (which helps with GDPR requirement)

For now, please use the Delete My account plugin which you mentioned. If you want, you can go to Membership Pro -> Configuration, set Delete user's subscription when account deleted config option to Yes

By doing that, when account deleted, all subscription related to the account will be deleted, too

Regards,

Tuan

I dont think there is a legal need to provide that a subsciber can delete their own records.
The GDPR introduces a right for individuals to have personal data erased. The right to erasure is also known as ‘the right to be forgotten’.
Individuals can make a request for erasure verbally or in writing.
So it can be done by admin on request.
The requirement only is that it shall be done if asked.