You are not logged in.
We get many requests for new features. While there are plenty of subjective reasons for choosing or rejecting features, here are a few tips that might help.
The features that are most likely to make it in to Textpattern are:
The features likely to be rejected or ignored are:
I’d really like feature XYZ to be added, how can I help?
By far the best thing you can do is write the code yourself, or find someone to do it for you. The dev team will be in a much better position to evaluate the potential benefits and drawbacks of a new feature if they have the code sitting in front of them. (The dev team members themselves work this way: when one team member wants a new feature added, he’ll produce a patch and send it to the others for evaluation).
It’s in our best interest to encourage submissions. But once we add something to the core, we’ll have to maintain it, fix bugs, and support it. For that reason, we’re most likely to accept patches that:
What’s a patch? I still want feature XYZ, dammit!
If you’re submitting a feature request, or have read someone else’s and would like to see it added to Textpattern, here are some things you can do to help improve its chances:
Things people often do that won’t help at all, and might make it harder to follow the discussion:
In addition to Dean’s post, I would suggest the Texbook Feature Request Page to see some of the big next project, and as a place to draft in detail Feature Requests after a consensus on it is obtained on this forum.
If you hesitate between a plugin request and a core (as in native) Textpattern request, Texbook Plugins vs Core is a good reading too.