Got an idea!
What about this?
All of the subscribers are still webusers but there is a separate table of what each webuser is subscribed to. What do you think of that?
-
MODX Staff
- 12,272 Posts
Try managing 5000 subscribers. Don’t think it’s a good idea.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
-
MODX Staff
- 10,725 Posts
Ryan, why not? I’m personally for avoiding redundancy in data as much as possible. Can you explain why managing 5000 usernames/password/email address combinations is any less complex than managing 5000 web users?
-
MODX Staff
- 12,272 Posts
Let me clarify... if you have web users that are actually doing things on the site, then definitely not, especially if you’re going to get more than a few hundred subscribers... just a lot of extra bloat and makes managing "real" webusers incredibly tedious. Imagine trying to locate a specific user to make a change among 25, 50 or even 1000 pages of web users.
Take my Dad’s business for example. There’s an inhouse list of more than 7000 newsletter subscribers that definitely should not be in the webuser database as there are 5 other "real" potential webusers for the site/applications I’m planning on building. I just don’t want the clutter and extra complexity of extra groups in the main system.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
-
MODX Staff
- 10,725 Posts
That’s what groups and roles are for (though agreed we need better management of users by groups and roles), and having to duplicate data structures and logic for an additional entity seems like another kind of bloat. If you think about it, these should never get in the way of each other from a management stand-point, but from a data stand-point it just makes more sense to me to keep one consolidated list of users, regardless if they are subscribers or content editors or application end-users. Consider someone who collects thousands of subscribers and then wants to create a special section of the site for those subscribers down the road. Oh boy, now they need two passwords to manage their subscription data vs. their user profile for their special content.
So go with webusers for the user info?
Hmmm,
IMO the NewsLetter system should also allow users to login and unsubcribe from the news letter.