Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Pages: 1
#1 2008-11-18 21:14:43
- lee
- Member
- From: Normandy, France
- Registered: 2004-06-17
- Posts: 831
Membership capability?
Do the Devs envisage TxP having built in membership capability?
At it’s basic level I’m talking about a system where each user (public not admin) can be granted a range of privileges, letting you define with precise control what each user is permitted to do on the front end.
Last edited by lee (2008-11-18 21:15:02)
Offline
Re: Membership capability?
Lee,
I don’t know exactly what you need…but for a solution that isn’t built-in there’s amember
I think jstubbs is using that on some of his TXP sites. Might acomplish what you need for now.
—
Tom
Offline
Re: Membership capability?
lee wrote:
Do the Devs envisage TxP having built in membership capability?
We do not have any plans in that direction.
Offline
#4 2008-11-19 08:34:03
- lee
- Member
- From: Normandy, France
- Registered: 2004-06-17
- Posts: 831
Re: Membership capability?
wet wrote:
We do not have any plans in that direction.
Who is we? Is that we the core developers? We the community?
What dictates which features get developed?
Offline
Re: Membership capability?
lee wrote:
wet wrote: We do not have any plans in that direction.
Who is we? Is that we the core developers?
As far as this question relates to my previous answer: Yes.
We the community?
I do not know which plans members of the community have with regard to memberships.
What dictates which features get developed?
Nothing dictates the development of features.
A mixture of factors enables the introduction of features: Fun, gut feeling, useful parts of paid projects which core developers re-integrate into the core, a frequent request which serves a broader audience, contributed code, compatibility.
Offline
Pages: 1