Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
Adriano Faria Posted July 12, 2015 Posted July 12, 2015 It depends on your needs.I really don't care, how IPS gonna solve it backend wise, but the settings should be similar to the given profile field permission settings, like:a) show on register page yes/nob) birthdate ist required or notc) show on profile page yes/no...Best. No, it depends on how IPS does things. It is as it is. They won't change this, honestly. There's no sense in make this as a custom field.I'm with IPS on this. I see this kind of request since 2010. Ok, it's totally required for you or your board; it can be required for the type of your content, but it isn't for all the other clients/boards. That's why this and several other things are better if made as a plugin. Now you don't like 3rd party plugins, well that's up to you. You just can't wait that every tiny request from everybody will be added just because they don't like 3rd party resources.Keep up with requests. Who knows...
Myr Posted July 13, 2015 Posted July 13, 2015 I'd appreciate it being built in. We have a site that has a fair few teenagers mixing with adults and we use the age on the profile as an indicator for proper behavior.
Joel R Posted July 17, 2015 Posted July 17, 2015 Use the Rules application by @Kevin Carwile to create custom data field for the profile, then rules to only open certain forums / permissions for different age-based groups
CheersnGears Posted November 11, 2015 Author Posted November 11, 2015 On 7/11/2015, 12:03:55, Lindy said: It's on the roadmap. No ETA. When you said no ETA, I kinda thought that it might at least make it into 4.1. It seems to have fallen off the road map.
Management Lindy Posted November 12, 2015 Management Posted November 12, 2015 5 hours ago, CheersnGears said: When you said no ETA, I kinda thought that it might at least make it into 4.1. It seems to have fallen off the road map. It's still there - I promise. It's just part of a larger function now. It shouldn't be much longer.
CheersnGears Posted November 12, 2015 Author Posted November 12, 2015 okay good. 4.1 is sooooo close to being usable for me, I'm looking at making the move in the next month or so once a critical bug I experienced is fixed.
Management Lindy Posted November 12, 2015 Management Posted November 12, 2015 5 minutes ago, CheersnGears said: okay good. 4.1 is sooooo close to being usable for me, I'm looking at making the move in the next month or so once a critical bug I experienced is fixed. I know you have quite a setup. Let us know when you're ready and if you need help.
Guest Posted February 3, 2016 Posted February 3, 2016 Just bumping to see if there's any resolution to this for v4.1.7 ??
SJ77 Posted February 3, 2016 Posted February 3, 2016 10 hours ago, SMCAust said: Just bumping to see if there's any resolution to this for v4.1.7 ?? would very much like this option as well.
Management Lindy Posted February 3, 2016 Management Posted February 3, 2016 I expect we'll target this in 4.2.
Myr Posted December 23, 2017 Posted December 23, 2017 On 2/3/2016 at 3:17 PM, Lindy said: I expect we'll target this in 4.2. Eh. How about in 4.3? Our site has an age range from 14 to 86 and according to Google, we're oddly even across all age groups. We want to cover ourselves and protect our members so we need to have a functioning birthday system. Right now it appears that these systems don't tie together very well as far as setting a birthday goes: COPPA/Registration/Profile Completion/GDPR requirements. In 4.2.6, You cannot use COPPA and Profile Completion at the same time. This is just plain silly. If COPPA is on, trigger an extra dialog. Force filling out the birthday field. In 4.2.6, if you have COPPA off and you set "Birthday" as a required field in profile completion, it only requires the year. It accepts the current year and ignores month and day. I'm pretty sure infants aren't posting on the forums, so that's ridiculous. Between COPPA and GDPR, website operators would be in some trouble collecting data if you are under 13 or 16. This should be addressed somehow. Setting a minimum age requirement? requiring month,day and year to be filled out. In 4.2.6, the system allows you to edit the birthday when you edit the profile and does no checks at all on it. (Though if you profile completion on and they change birthday year to not telling, it does trigger profile completion again) Can we also get a built in user setting to let the member display their birthday or age or both on the Calendar? Given GDPR, just displaying birthdays on the calendar without getting permission seems like it violates the law. We've manually added a custom field to do this, but I'd rather have it built in so we don't have to maintain modifications and plugins.
CheersnGears Posted June 11, 2018 Author Posted June 11, 2018 On 6/5/2018 at 11:36 AM, Aldro said: 4.3.3 and still nothing They resolved it a different way. Instead of doing it at profile creation, you can put it in the profile completion process and make it required.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.