Members area against Corvid

Ask the community
1

Yeah this is back so i thought id launch a discussion. So during my last couple of projects ive had this thought.
“Man, members area could be great but it is so useless”
So let me try bullet pointing some of my points.

  • The user role permission limitations. you can do it with code. but honestly if i need this feature its faster making a regular page and coding on that instead.

  • The privateMembersData collection it gets data from is read only. BUT can be used with reference fields. BUT not from that collection only from external inserting into it?.. I find this so absurd. i love members have a locked database but why completely ? just make part of the information locked off like owner, update date etc is in all other collections.

  • it just spawns so many pages the second the client touches anything.

  • There is no functionality in it that is done better than what I think most of us can do with corvid and we can do it faster than cleaning up the mess it spawns into the editor.

So this is my take. Ive had a couple clients “work themselves” and always felt that members area was more hassle than enhancement when i entered the site so i thought i would launch a discussion about it.

2 Likes
2

Yes, I agree with you. The member area lacks flexibility and is a pain to customize.

I do believe member management is a cornerstone of any platform, unfortunately, we are limited in what can be customized. So I also end up building my own member system, which I think I should not.

As @code-queen explained, there are many features lacking to have control on the membership process (reset password, change password, roles automation, advance permission system, …)

There is also a strange relationship between CRM contacts and members but it has already been discussed.

That been said, I’ve got to disagree with you regarding the privateMemberData collection. This is used by many apps so I need to remain stable. I’ve not got any issue working with a customMember collection and reference field to privateMemberData (but I imagine some use case are not possible)