Support » Requests and Feedback » Screw MT, look at Textpattern

  • A lot of people have been asking (myself included) for WP to be more MT like, in terms of how certain features are implemented. Well, I have been spending some time playing around with Textpattern and MT is definatelly not the package WP should be “borrowing” ideas from:
    1) Textile integrated with two preview modes, which work very well.
    2) Textpattern’s “sections” looks like the most viable solution to WP lack of static pages. It would also address multiple category issues and only view one category per page questions. Each section can have it’s own look, layout etc.
    3) Individual entry has a different template from the main page. I have found a way around this, but it does not work properly and is not a very elegant.
    4) CSS editor, which is very nice indeed.
    5) Ability to copy a particular template/file to create a copy of it that could be used as a template for a different section.
    6) Auto-closing of comments (1week – 6 weeks).
    7) Forms (templated), while I prefer to use PHP directly … use of tags elimites a lot of headaches when upgrading etc., since tags stay the same even if call syntax changes.
    8) Help is really well done.

Viewing 15 replies - 1 through 15 (of 17 total)
  • Firstly, my this thread is not meant to start a flame war, but is merely a set of suggestions on where WP should be moving in my opinion.
    Secondly, I’ve made WP static pages myself. So you are right it can be easily done, but mod_rewrite is not “easy” and definately not very elegant. Textpattern handles this from within w/o even making users upload a file or ssh to the server.

    i guess it depends on how one designs templates. i follow the model that i used with mt by separating a page into panels. then, within those panels, i use include statements to pull in stuff from other files that control the content of each section in the panel. if i ever need to change a section, all i need to do is edit a particular file without touching the main templates. -type requests is something to think about.

    i can see ways of accomplishing what he wants in 1.2 with parent and child categories.

    Textpattern is neat, but its more of a CMS than a straightforward blogtool. A lot of the people wanting to use WordPress as a CMS might be better off with Textpattern – it would save them a lot of hacking – but I just want to blog so WordPress is the better tool for me. The only features in that list which might be useful in WordPress are the post preview and the comments auto-close, and I think there are already hacks for them anyway.

    I’ll agree with Will’s summary. TXP fro CMS, WP fro blog. Apart from that i like TXP’s section/category options.

    Just curious, what’s the main difference between a CMS and a blog?

    A CMS is a Content Management System…. while a blog is a general purpose journaling system. CMS’s tend to be much more indepth and has more features. Doesn’t make them better, just different. They (CMS’s) tend to have alls kinds of calendars, downloads, articles, forums…. something that runs Yahoo! or Lycos could be called a CMS. PostNUKE, XOOPS, and their like are prime examples. They are general purpose.
    Bolg software is more specialized, and lighter-weight. They also tend to be light weight.
    The decision of blog vs CMS should be based on your needs.

    honestly, i’d prefer wp’s editor. txp’s css editor sucks.

    wordpress css editor is just a text box with a save button.
    how can txp beat that at anything?

    Textpattern also has “just a text box with a save button” – same as WP.
    In addition Textpattern has a handy css editor (a form) to quickly change the css attributes without searching thru, editing & formatting the raw code.

    so how come “txp’s css editor sucks.”! if it does a bit better than WP :O)

    I don’t know, maybe shades can explain – but textpattern does have the same css textbox & save approach as WordPress. ‘Sucks’ isn’t very informative is it?
    Every one has their preferences. I have tried drupal, mambo, wp, txp and others and have settled on WP for traditional blogs & Textpattern for CMS & styled-sections.

    The CSS editing form in Textpattern with all the separate textboxes is kind of dumb, but its not aimed at us, its aimed at people who know nothing about CSS and just want to fiddle with the default 😉
    I can’t understand why anyone would edit CSS online anyway, what’s wrong with Notepad and FTP?

    “… what’s wrong with Notepad …?”
    Where do I start? 😉

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘Screw MT, look at Textpattern’ is closed to new replies.