Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: What features would you take from ExpressionEngine
Destry wrote:
…Although it may seem like I’m not a happy camper, the opposite is true. (…) But that doesn’t mean development should be complacent and not improve handling of what exists. There’s room for it. (…)This topic—granular content and Txp’s reasonably good ability to handle it—needs communicated outward, and now is the time, because people out there are tuned-in to anything “adaptive” and “responsive” with respect to CMSs. Up to now, nobody has really demonstrated that very well, though there was never really the focus on adaptative content before like now either. I think we’ll be seeing an article in the magazine on Txp’s chunking abilities, eventually.
Yes, communicating the possibilities of txp is really a good point! And the right time. Looking forward for the article.
Btw, Zanza, when are you writing something for the magazine? Maybe something on those content type work-arounds? ;)
Honored by your proposal, Destry. I need to wait to have something useful to say, though. I’m having spare time for txp-playing, lately… But, who knows? Those articles are inspiring…
Offline
Re: What features would you take from ExpressionEngine
Zanza wrote:
Destry wrote:
Btw, Zanza, when are you writing something for the magazine? Maybe something on those content type work-arounds? ;)
Zanza wrote: Honored by your proposal, Destry. I need to wait to have something useful to say, though. I’m having spare time for txp-playing, lately… But, who knows? Those articles are inspiring…
I second Destry’s proposal re article.
PS I think that with the imminent release of TxP 4.5 and certainly by 4.5.5, That it is timely for a updated book on Textpattern Solutions …
If there are any inspired authors out there.
…. texted postive
Offline
Re: What features would you take from ExpressionEngine
Thinking about it, the only two plugins I’d really ever want to see assimilated into core are custom fields and contact forms really (though it could be argued that forms can be more appropriately handled by wufoo or machform so even that isn’t essential)). Maybe some better multi languages support.
Everything else is best served by plugin authors themselves. Though I agree with gocom that orphaned plugins can be a problem sometimes, but that’s not unique to Textpattern.
Offline
Re: What features would you take from ExpressionEngine
philwareham wrote:
Though I agree with gocom that orphaned plugins can be a problem sometimes, but that’s not unique to Textpattern.
I agree that all CMSes that rely on plugins can find themselves with orphans. But I think with ours there is a greater likelihood judging from the date that most plugins were last modified. It does cause me worry to rely on them.
Is there a possibility, or desire, to have plugins that work with 4.5 > be listed in a central repository? It would be on a voluntary basis by the plugin developer, but seeing theirs listed in such a repository would give greater confidence that there is a care and feeding regime on their part.
Furthermore: Should a crucial plugin go orphaned is said plugin free to be updated/modified by another developer?
…. texted postive
Offline
Re: What features would you take from ExpressionEngine
bici wrote:
Should a crucial plugin go orphaned is said plugin free to be updated/modified by another developer?
Plugins are licensed under the GPL as long as they are making function calls to and share data structures with Textpattern and therefore inherit its license. This precondition applies to almost any plugin.
Thus any user of these plugins has the “legal permission to copy, distribute and/or modify the software.”
Offline
#42 2012-09-15 23:46:39
- masa
- Member
- From: Asturias, Spain
- Registered: 2005-11-25
- Posts: 1,091
Re: What features would you take from ExpressionEngine
wet wrote:
There is no overkilll in Textpattern. Articles are where our user-editable content lives, that’s why we have permissions set up the way they are. Looks like a perfect fit.
I agree with Robert.
It’s what I’ve been doing for years. You just set aside some “invisible sections” such as client-quotes, footers, addresses etc. named accordingly, place snippets as separate ‘articles’ in there and pull them in where needed.
Think of ‘articles’ as any kind of content.
Offline