Hello,
is there a way to limit the registration per IP to avoid spam (manually registrations with fake emails)?
If a user has registered one account, he will not be able to register a second one with the same IP (optionally for X time)
Hmm, interestingly enough, it works on my site, you'll need to take everything in //convoe.com/vendor/convoe/_cnvo.register.js and make your own file and replace it, you don't really have to remove it completely. This is because I have hot-linking blocked as far as assets goes.
Facebook
<iframe src="//www.facebook.com/plugins/like.php?href=https%3A%2F%2F YOUR FACEBOOK URL HERE &width&layout=button_count&action=like&show_faces=false&share=false&height=21&appId=135888533251344" scrolling="no" frameborder="0" style="border:none; height: 21px; overflow: hidden; width: 105px;" allowTransparency="true"></iframe>
Twitter
<a href="https://twitter.com/TwitterUsername" class="twitter-follow-button" data-show-count="true" data-dnt="true">Follow @TwitterUsername</a>
<script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script>
The +1 widget will be available online somewhere, I don't use Google +, it's awful. Change TwitterUsername and YOURFACEBOOKURL to your own, the facebook one already includes the https part.
Updated to support IPS 4.0.12.1 latest patch (some groups and members changes). Tested again with 0.7.2 NodeBB and 4.0.12.1 IPS.
In fact, there is a schema validation built upon Hibernate JPA, so if something is wrong with DB - it will fail at startup with no data corruption.
Well, there are language files in /public/language. The GDPR text is, as far as I remember, sourced from a few of these entries (the language files are JSON files with a prase identifier, and translation). So if you want to change the wording, you would have to modify these files in your clone of the repo.
Not sure if this is the "best way" since they might be overwritten when you pull the next version (could someone with more knowlede than me confirm this?) but that's a git issue that you should be able to handle once you get to updating.
For example, I see three entries in the file "/public/language/en-US/register.json" that start with "gdpr_". There are probably others but this is a good place to start. Just search those language files for the exact wording.
Also note that to chnag eit you would have to change all of the languages, but if english only is enough for you, that is easier.
