Join us as we take a look into the immediate future at what the next version of Textpattern after 4.7.3 is likely to resemble.

Ask anyone new to Textpattern what its one deficiency is compared to the competition, and the answer is usually “Where are the Themes?” We finally have an answer to that.

We are currently working on what will finally become Textpattern CMS 4.5.

With the recent release of Textpattern CMS 4.2.0 a number of significant enhancements have been made. Since we love to share, we thought we’d give a rundown of the main features and what they mean for you and your sites.

As almost nothing is made to last forever, articles may carry an expiry date/time in the upcoming Textpattern 4.0.7 release.

In the upcoming Textpattern 4.0.7 release, the default page template will contain a sample two-level navigation menu with the first level built by a list of sections while the second level menu is run by a list of article titles within the active section.

For those that just went… “Tag what?!”, the tag parser is the part of Textpattern that interprets the txp tags in your carefully crafted forms and pages. This is the first of two articles discussing the parser changes in the upcoming TXP 4.0.7 version (no, not next week/month).

So, it’s been over a month since we moved in at our new code repository, we already acquainted ourselves to the place and added a few new features to what will then become Textpattern 4.0.7. I thought I’d explain one of these upcoming features in greater detail: plugin order.

During May this year, some kind soul drew our attention to the fact that Textpattern lacks an official JavaScript library as part of its distribution package.

If you’re an assiduous reader of this blog, you probably remember that I announced it several months ago. All my comments about the implementation in that post remain valid.

Due to the excellent work by Arif Widianto, Textpattern CMS is available in Bahasa Indonesian starting just now.

Last December showed a number of reports from different users that some spam-bots and/or (so-called) ‘SEO-Tools’ had been adapted for Textpattern CMS and some users were receiving automated spam to their sites.