news (tx_news) for TYPO3

tx_news is the extension no TYPO3 project can do without

tx_news by Georg Ringer has been installed more than 5.6 million times via Packagist (as of September 2026). That figure alone is impressive, yet it understates how central the extension is. tx_news is not just a news plugin but the foundation for blogs, magazines, newsrooms, event listings, staff directories and every other kind of structured, chronological content in TYPO3. From a single, actively maintained codebase it delivers categories, tags, media assets, SEO fields (canonical, OpenGraph, Schema.org), pagination and import/export. If you publish editorial content in TYPO3, there is no way around tx_news.

Gosign has configured, extended and migrated tx_news in hundreds of projects, from Fluid templates and custom ViewHelpers to complete migrations from tt_news. The extension is a fixed part of every TYPO3 setup we deliver.

Typical use cases range from the corporate blog to the press archive

The most common scenario is the corporate blog or online magazine. Editors maintain articles in the TYPO3 backend with title, teaser, body text, categories, tags and media. The list view shows teasers with images, and the detail view shows the full article. SEO fields such as meta description, canonical URL and OpenGraph image are maintained per article. A typical installation holds 100 to 5,000 articles and grows by 2 to 10 articles per week.

The second scenario is press releases for investor relations and corporate communications. Listed companies and large groups publish mandatory disclosures in the press section of their website. tx_news provides the chronology, the categorization (ad hoc disclosure, quarterly report, executive appointment) and downloads for attached PDFs. The archive keeps announcements from ten years ago easy to find.

The third scenario is event listings and calendars. With the add-on extension eventnews, also by Georg Ringer, entries get start and end dates, a location and an organizer, which turns tx_news into a simple event calendar. For associations, cultural institutions and education providers, that is often enough, and a specialized event extension such as sf_event_mgt is not needed. tx_news only reaches its limits once registration, attendee management or ticketing come into play.

The technical architecture keeps data, configuration and presentation strictly apart

tx_news stores articles as Extbase records in the table tx_news_domain_model_news. Every record contains mandatory fields (title, datetime, type) and optional ones (teaser, body text, author, tags, categories, media, related news). Relations to categories and tags run through MM tables, which keeps filtering fast.

Configuration happens in TypoScript: template paths, sorting, pagination, category filters, the PID of the detail page and SEO settings. The extension ships an extensive set of TypoScript constants that covers most configurations without custom code. For custom requirements, such as a homepage slider showing the three latest news items, ViewHelpers are available for use in Fluid templates.

The Fluid templates for list, detail, category and date menu can be overridden via TypoScript paths. In practice, teams copy the default templates into their own site package and adapt the HTML structure and CSS classes to the corporate design. This separation allows extension updates without overwriting your own customizations.

Performance is good when the configuration is right: the list view uses the TYPO3 page cache, and the detail view caches per article UID. Performance only becomes an issue beyond 10,000 articles combined with complex category filters and full-text search. In those cases, a search index via ke_search or Solr is the better route.

Common problems involve SEO configuration, performance and the tt_news migration

Problem one: missing or incorrect canonical URLs. Without the right configuration, the same article is reachable via several URLs: the category path, the archive path and the direct link. Google indexes every variant as a separate page, which leads to duplicate content. The fix: set the detail page PID explicitly and point the canonical URL in the TypoScript settings to the detail page. The newscanonical extension addresses this problem as well.

Problem two: performance drops with large news archives. When the list view has to scan 5,000+ articles, database query times rise. The fix: category-based restrictions in the TypoScript configuration, pagination with a maximum of 20 articles per page and database indexes on the category relations.

Problem three: migrating from tt_news. The legacy extension tt_news has not been compatible with TYPO3 since v8. Moving the data to tx_news requires a field mapping (tt_news_cat to sys_category, marker templates to Fluid templates) and a URL redirect strategy so that existing Google rankings survive. Gosign uses AI-assisted template analysis for this: our tooling reads the old marker templates, identifies the fields in use and generates Fluid templates that produce the same output.

tx_news fully supports TYPO3 v12 and v13

Georg Ringer maintains tx_news actively and ships a compatible version promptly after every TYPO3 LTS release. The current 14.x series supports TYPO3 v13 and v14 in parallel, and the 13.x series covers v12 and v13. When upgrading from v10 or v11 to v12, breaking changes mainly affect custom ViewHelpers, which need to move to the current Fluid API, and TypoScript configurations that the new TypoScript parser in v12 no longer accepts. tx_news has supported site sets since version 12.1, but they can only be used from TYPO3 v13 on. The record structure stays stable, so no data migration is needed. Gosign typically upgrades tx_news as part of the TYPO3 core upgrade and checks custom templates, ViewHelpers and TypoScript overrides for compatibility along the way. For projects with extensive customizations (custom fields, in-house ViewHelpers, integrations with third-party systems), we draw up a compatibility matrix before the upgrade that documents every dependency and gives a realistic estimate of the migration effort. AI-assisted code analysis speeds up this process considerably by pinpointing every place in the project that API changes affect.