Classifieds for TYPO3

Classifieds on your own website are an alternative to marketplace platforms

Clubs, regional portals and community websites sometimes need a classifieds section: members list second-hand items, neighbors offer services, organizations broker donations in kind. The kleinanzeigen extension brings this functionality straight into TYPO3, without sending users off to Facebook Marketplace, eBay or national classifieds sites such as Marktplaats, leboncoin or Gumtree. Users create ads in the frontend, other users find them through categories and search, and the editorial team keeps control over approval and moderation.

The use case is narrow. Anyone who needs a full marketplace with payments, a rating system and buyer protection is better served by a specialized solution. For community portals with 50 to 500 active ads at a time, however, the extension is a solid tool that keeps users on your own platform.

Typical use cases are club portals, regional platforms and internal exchanges

The most common scenario is the club portal. A sports club, a church congregation or a community group gives members a place to sell, give away or swap used items. The classifieds section is a community feature that brings visitors back to the website again and again. The categories stay manageable: sports equipment, clothing, furniture, miscellaneous.

The second scenario is regional platforms and city portals. A municipal website or a local news portal runs a classifieds section for the region. Residents advertise apartments for rent, babysitting or the services of local tradespeople. Moderation sits with the editorial team, which approves ads before they go live.

The third scenario is internal exchanges in companies or universities. On the intranet, employees offer office furniture, bicycles or sublets. The classifieds extension runs on the internal TYPO3 instance and is visible to logged-in users only. Universities also use the feature for textbook exchanges, where students sell or swap course literature among themselves.

The technical architecture relies on Extbase records with frontend input

The extension is built on TYPO3’s Extbase/Fluid framework. Ads are stored as domain records in a dedicated table. Each record contains title, description, price (optional), category, contact details and images. Categorization runs through TYPO3 system categories or a dedicated category field.

Three plugins are available in the frontend: a list view with filters and search, a detail view for individual ads and an input form for new ads. The input form requires a frontend login (fe_users), so only registered users can create ads. Images are uploaded via FAL (File Abstraction Layer) and validated server-side for size and file type.

Moderation works through an approval flag in the backend: new ads stay hidden by default until an editor publishes them. Alternatively, automatic approval can be switched on, which can make sense for trusted communities.

Search runs as a simple LIKE-based database query on title and description. For portals with more than 500 active ads, adding ke_search or a dedicated search index is recommended to improve search performance and relevance. Sorting can be configured by date (newest first) and by price (ascending or descending).

Common problems are spam, image optimization and expiry management

Problem one: spam ads. Every public input form attracts spam. Without protective mechanisms, the listings fill up with irrelevant entries within weeks. The fix: mandatory frontend login, honeypot fields in the form, an optional CAPTCHA and approval-based moderation. Combined, these measures bring spam down to near zero.

Problem two: image optimization. Users upload photos straight from their smartphones, often at 4 to 8 MB per image. Without server-side compression and resizing, the site slows down and storage runs short. The fix: define a maximum image size in the extension configuration (recommended: 1,200 px wide, 80% JPEG quality) and cap uploads at 5 MB in the PHP configuration.

Problem three: expiry management. Outdated ads that have been online for months make the listings useless. The fix: an automatic expiry date (recommended: 30 to 90 days) and a reminder email to the author before the ad is archived. This requires a scheduler task configuration.

One more topic comes up regularly: how sellers and interested buyers get in touch. The simplest solution shows the seller’s email address on the detail page. That works, but it exposes the address to spam crawlers. The better solution is a contact form on the detail page that forwards the message to the seller without revealing their email address.

The extension has no confirmed support for current TYPO3 versions

kleinanzeigen was developed for older TYPO3 versions and has no official support for v12 or v13. In a migration, the question is whether to adapt the extension or replace it with a custom-built solution. For portals with an active classifieds section, Gosign recommends a rebuild on the current Extbase API that migrates the existing data and tailors the functionality to the portal’s specific requirements. The effort is typically 5 to 10 working days for core functionality with list view, detail view, frontend input and moderation.

The advantage of a rebuild over patching the old extension: the database structure can be optimized for the actual requirements, the frontend templates use current Fluid features, and responsive behavior is designed in from the start. Gosign migrates existing ad data into the new structure automatically, so no active content is lost.