Wicked007

Make sure that the "Can manage alerts" Moderator permission is active for the user/group ( ACP => Members => Moderators )
 
 

It currently only works in editors (so when you compose new content). It does not apply to custom profile fields, or content titles. The implementation is just a JSON list in HTML which is processed by javascript on submission, so it's not particularly intensive.

As Jordan noted, it's not meant to be a cast iron wall to prevent you from posting specific things, but more a nudge to reconsider. There's just too many ways to get around a word filter to even try stopping it. 
 
@Chris Anderson Nothing is ever feature complete. 🙂 

Sure, there are ways to get around it, however the message still stands to the user that they've been privately warned and then chose to ignore the guidelines. The moderator at that point may or may not want to take action. 😀 

"Most administrators ..."   You may be correct.  And most certainly, 'users' would like on-line and most likely not in any way, want to 'print' a "How To".
But again; there is no "User Manuel" for the user with-out revealing how the innards are configured or can work.  And I would still venture to say that SysOp's & Mod's would appreciate a printed version.
Here is an idea:
How bout we set-up a poll here in our forums and find out if A) a printed manual would be desired, and B) if there should be a separate Manager/ Moderator/ Owner Manual and a separate "User Manual??

I'm going to skip the security part with regards to staying up to date as well as taking backups etc as that's well covered. I wanted to speak a little about the 'community' rather than 'sysadmin' side:
 
I think one of the concerns admins may have with a major version update aside from any third party addons they use (although a good thinking admin will have already spent a few minutes looking for updated versions of these anyway well in advance and likely obtained and tested them) is simply ensuring two things:
1. That the community is informed it is being upgraded, this is really only a concern in most cases if its a large upgrade (say for instance coming from a competitors software or perhaps say a 2x or 3x to 4x upgrade)
2. Providing initial 'helping hands' guides where needed. Only needed really for major changes.
Let me expand on (1) , by this I mean giving the community plenty of notice of this, ideally with some screenshots of the 'new' community and where possible a private test site of it where a few trusted members can post / play with it and give their thoughts. The time factor here is quite important I feel.
To expand a bit on (2) A few simple guides, even if they are just a couple of sentences each such as "how do I now do xyz" or "what happened to xyz" or "where is xyz" , these things can go a long way to help avoid problems provided they are kept simple and straightforward, ideally just a few essential words. Those who need more information will be able to ask or find it easily enough.
I should point out I've not read Matt's guide before I wrote the above (honest) but I expect it will likely touch on these points.

I definitely agree that community management is a practice that requires it's own education.  I've become a certified community manager and there are some amazing concepts grounded in social theory, behavioral analysis, and organizational theory that I never would have known if not for those courses.  
I'm hoping IPS might think about offering something like an IPS University as a place of learning for admins who are looking to professionalize their communities.  
Thanks for sharing your best practice! I definitely agree that having a team and being accountable is important to the well functioning of your community and making measured progress.   
More broadly, I think its all about discipline.  For the beginning years of my community, I did everything myself (because I only needed one person).  But you have to be organized and disciplined.  I keep a "website diary" of all the important changes that I made, my thoughts, and links for things I'd like to investigate in the future.  It's helped me so many rimes to go back and see what I was working on.  

@DReffects2 - I appreciate you've done extensive research as applicable to your situation jurisdiction. We have expended an enormous amount of time and resources aiding our EU clients with GDPR compliance to the best of our abilities and it's our understanding, we've actually done more than most similar platforms. A temporary line has to be drawn somewhere or we're going to end up with, as Matt said, a barrage of half-baked features and checkboxes everywhere. We have consulted with the ICO, our largest EU clients and perused legal resources and are confident that our implementation as of 4.3.3 will help satisfy your compulsory requirements under the GDPR. I know you don't like the "let's wait and see" approach on your remaining potential concerns, but that is in fact a key purpose of the judicial system -- interpreting and providing subsequent guidance on existing regulation.
We are committed to adapting and accommodating as needed, I assure you. We aren't, however, able to go crazy and toss things in based on armchair interpretations. From a layman perspective, a simple checkbox here and there seems easy. From a development perspective - you need to do something with that checkbox. As the contact form, when configured such, is merely an email form, there's nothing to do in the same way there's nothing to do when you actively send someone a traditional email -- you're sending the email because you want to initiate contact. If you wanted a "simple" checkbox on the contact form that's simply sending an email, you then need to provide a mechanism for obtaining consent, store the email address, store the consent, provide a mechanism to withdraw the consent to store the email, etc. None of that is necessary based on reasonable interpretations of the GDPR, so as developers with finite resources, we need to weigh out these requests that amount to a fair amount of development time with limited basis and simply say, if you're super concerned about untested, unchallenged, extreme interpretations for things like this, it's likely best, for your own peace of mind, to simply not use the feature.
I say with confidence that although ultimate compliance with any local, national or international law or regulation is the responsibility of the community owner; 4.3.3 is GDPR friendly. If you feel you need to be more restrictive based on additional member state requirements, interpretations or even personal peace of mind - you can of course disable embeds, disable the contact form, disable spam mitigation, disallow tech support and/or peruse third party solutions. It's my opinion, however, the EU authorities are not intending to cripple the Internet or make it cumbersome, inconvenient and unenjoyable to use; only to hold providers, controllers and processors to task for safeguarding data... and in that regard, it's only a good thing. 
There's a lot of information, opinions and suggestions floating through the comments here and it's difficult to keep track of. We welcome you to engage us via a support ticket for software and corporate specific information and, of course, you may use the client forums to discuss various scenarios, share opinions, tips, etc. 
We appreciate the feedback and participation. Let us know if we can be of further help.

Classifieds plugin is messed up, Tapatalk is not working, Likes are not visible. So there are lot of things to correct.