Skip to main content
Topic: ElkArte 1.1.4 - Release announcement (Read 1428 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Re: ElkArte 1.1.4 - Release announcement

Reply #15
Once I put some text in there it seems everything is back to working as expected. I was hoping elkart was going to supply a Privacy Notice though.

Re: ElkArte 1.1.4 - Release announcement

Reply #16
The box fails to save on mine as well, even with text in the file. The workaround is checking a similar box in registration settings. 

Re: ElkArte 1.1.4 - Release announcement

Reply #17
I want to force all users to accept the new registration agreement the next time they login. Checking this box and saving has no effect, ie...saving unchecks the box.

[attach type=image]6003[/attach]
This is intended.
The idea is that when you do an edit that requires you to force your users to accept the agreement then you select it.
The reason behind the design is that if you for example want to fix a typo in the text it is not necessary to force all the users to accept the privacy policy again.
So, any time you make a change you are "asked" to select the option only if you really want the users to accept the new agreement.
Bugs creator.
Features destroyer.
Template killer.

 

Re: ElkArte 1.1.4 - Release announcement

Reply #18
Once I put some text in there it seems everything is back to working as expected. I was hoping elkart was going to supply a Privacy Notice though.
TBH I don't think we can write a privacy policy that suites all the needs, that's why I refrained from adding one.
What we can "easily" do is try to document how the data are used and stored, but the actual policy is something that is currently up to the owner of the site.
For example if you have backups, if you have addons, for how long you intend to keep the records, what you do with deleted accounts, if you have more people that can access the data, etc.
All of these should be likely taken in consideration, and since I'm not a lawyer and don't have enough money to consult one for writing a legal document, then I'm in your same boat.
If you have any suggestion, please open a topic and start drafting a generic policy for anybody to have a boilerplate to work on. ;D
Bugs creator.
Features destroyer.
Template killer.

Re: ElkArte 1.1.4 - Release announcement

Reply #19
I think we got some problems with this button as it did not stay selected after we as admin have chosen it in the settings.
[ ] Force all members to accept this new version of the privacy policy at the next visit to the forum.

When I select it again, I was taken to https://elkarte.sch.my/index.php?action=admin;area=regcenter at the browser url but the same page is still showing with the above button unselected.

Selecting it again will drive me back to https://elkarte.sch.my/index.php?action=register;sa=privacypol where I (as the admin) now have to accept the privacy policy.

I am all confused. Or is this intended? ;D

Re: ElkArte 1.1.4 - Release announcement

Reply #20
I think we got some problems with this button as it did not stay selected after we as admin have chosen it in the settings.
[ ] Force all members to accept this new version of the privacy policy at the next visit to the forum.

When I select it again, I was taken to https://elkarte.sch.my/index.php?action=admin;area=regcenter at the browser url but the same page is still showing with the above button unselected.

Selecting it again will drive me back to https://elkarte.sch.my/index.php?action=register;sa=privacypol where I (as the admin) now have to accept the privacy policy.

I am all confused. Or is this intended? ;D
 
 Same.  Shouldn't the box save if there is an edit?  If so, there was a hiccup here... ;)

Re: ElkArte 1.1.4 - Release announcement

Reply #21
Maybe read the messages posted in this topic? :P
Bugs creator.
Features destroyer.
Template killer.

Re: ElkArte 1.1.4 - Release announcement

Reply #22
TBH I don't think we can write a privacy policy that suites all the needs, that's why I refrained from adding one.
What we can "easily" do is try to document how the data are used and stored, but the actual policy is something that is currently up to the owner of the site.
For example if you have backups, if you have addons, for how long you intend to keep the records, what you do with deleted accounts, if you have more people that can access the data, etc.
All of these should be likely taken in consideration, and since I'm not a lawyer and don't have enough money to consult one for writing a legal document, then I'm in your same boat.
If you have any suggestion, please open a topic and start drafting a generic policy for anybody to have a boilerplate to work on. ;D

OK, thanks. I do understand that. What I really don't understand is the whole GDPR thing. A few questions remain. Do we have to keep a visible link to the Privacy Policy on our website? Do we have to give users the ability to download their data that we have. Do we have to give users the ability to delete their account? I currently do not have any of those 3 things working.

And if you think this GDPR thing is bad wait until you see what they are up to next:

European Union prepares to wreck internet with new copyright law

Re: ElkArte 1.1.4 - Release announcement

Reply #23
May I ask where you are from, @b4pjoe? @Ruth and me worked for weeks on our privacy policy, maybe we can give you some answers. Here's a translated view of my privacy policy. Please keep in mind that this privacy policy is not made or controlled by a lawyer, it may not be perfect, maybe not 100% legal.  ;)  But I did my very best.

Do we have to keep a visible link to the Privacy Policy on our website?

The privacy policy along with your registry agreement and your impressum must be always visible and easy to find! A single click to reach these documents is required. Links in your footer are perfect!

Do we have to give users the ability to download their data that we have.

Users may want to know what data you collected. You must give them an overview of the collected data in an electronic form, as an excel file for example. But you can wait till they ask you for it, and you still have a decent amount of time to provide this data.

Do we have to give users the ability to delete their account?

Sure. But they have already, or not? Users can delete their account in their profile. At least they can apply for it and you have to confirm it.


Re: ElkArte 1.1.4 - Release announcement

Reply #25
The update worked perfect with my test forum. :)

Just one question: Where can I find the privacypolicy.txt ?
I got the message that it's not writable and want to change it.
ElkArte version: 1.1.5 / Theme: BeSocial / PHP 7.2.7

Re: ElkArte 1.1.4 - Release announcement

Reply #26
privacypolicy.txt should be in the forum root.  If not, create it manually and give it read/write permissions.   ;)

Re: ElkArte 1.1.4 - Release announcement

Reply #27
May I ask where you are from, @b4pjoe? @Ruth and me worked for weeks on our privacy policy, maybe we can give you some answers. Here's a translated view of my privacy policy. Please keep in mind that this privacy policy is not made or controlled by a lawyer, it may not be perfect, maybe not 100% legal.  ;)  But I did my very best.

Do we have to keep a visible link to the Privacy Policy on our website?

The privacy policy along with your registry agreement and your impressum must be always visible and easy to find! A single click to reach these documents is required. Links in your footer are perfect!

Do we have to give users the ability to download their data that we have.

Users may want to know what data you collected. You must give them an overview of the collected data in an electronic form, as an excel file for example. But you can wait till they ask you for it, and you still have a decent amount of time to provide this data.

Do we have to give users the ability to delete their account?

Sure. But they have already, or not? Users can delete their account in their profile. At least they can apply for it and you have to confirm it.

Thanks for the link. I had found a privacy policy online and modified it to fit what I think I need. Very similar to yours. Creating a link o it and registration agreement are easy enough to link but I have no idea how I would go about gathering the data if a user requests it.

I am in the USA but I do have members on my forum that are from the EU.

Re: ElkArte 1.1.4 - Release announcement

Reply #28
privacypolicy.txt should be in the forum root.  If not, create it manually and give it read/write permissions.   ;)

Thank you, the privacypolicy.txt is now in the forum root. :)
ElkArte version: 1.1.5 / Theme: BeSocial / PHP 7.2.7

Re: ElkArte 1.1.4 - Release announcement

Reply #29
I think what I mean was the behaviour of that button that causes the jump to another tab button and the change of displayed url, after selecting it again it displays the privacy policy page. That is really weird to me and other than what you tried to explain, the effects are more like bugs.