View Issue Details

IDProjectCategoryView StatusLast Update
0008016OXID eShop (all versions)1.01. Products (product, categories, manufacturer, promotions etc.)public2026-11-01 19:27
Reportermario_lorenz Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
Product Version7.5.1 
Target Version7.6.0 
Summary0008016: FrontendController::getListDisplayType() falls back to infogrid, which Apex has no template for
Description$_aListDisplayTypes is hard-coded to ['grid', 'line', 'infogrid'], and every value that is not in this list is replaced by 'infogrid'. Apex only ships widget/product/listitem_grid and listitem_line, and its theme.php restricts sDefaultListDisplayType to line|grid.

As a result, both ldtype=infogrid (old Flow/Wave links that are still indexed, especially in migrated shops) and any arbitrary ldtype value (bot probing) render a category or search list where every article box throws a "template not found" exception. One log entry with a full stack trace is written per article box, which quickly adds up to hundreds of MB.
Steps To Reproduce1. Use Apex as the active theme.
2. Open any category with ?ldtype=infogrid, or with ?ldtype=foo.
3. Check oxideshop.log: there is one "template not found" error per article.
Additional InformationExpected:
- Unknown or unsupported types fall back to sDefaultListDisplayType. If that is not valid either, they fall back to the first supported type.
- Ideally, the allowed types come from the active theme (for example a theme setting, or the constraints of sDefaultListDisplayType) and are not hard-coded in the core.
- The invalid value is not written into the session.

Side note: ArticleListController::getArticleListDisplayType() and ViewConfig::getNrOfCatArticles() read ldtype from the session without any validation.
TagsNo tags attached.
ThemeApex
BrowserFirefox
PHP Version8.4
Database VersionNot defined

Activities

There are no notes attached to this issue.