View Issue Details

IDProjectCategoryView StatusLast Update
0006542OXID eShop (all versions)1.01. Products (product, categories, manufacturer, promotions etc.)public2022-01-28 11:50
Reporteravalue Assigned To 
Status resolvedResolutionwon't fix 
Product Version4.10.2 / 5.3.2 
Summary0006542: page title is used instead of category title
DescriptionIn flow's list template found under

Line 35

the SEO title is used to display the category name. This causes side-effects as SEO addons can modify the page title for seo optimization – but you do not want to display the meta title as category name.

So in my opinion, better use [{$actCategory->getTitle()}] to get the title of the category, not the SEO title of the page in h1 tag.
Steps To Reproduce1. change the seo title of the category with any available seo addon
2. you will see the title is used inside an h1 tag
TagsSolution Provided
BrowserGoogle Chrome
PHP Version5.6
Database VersionNot defined



2016-11-18 09:54

administrator   ~0011871

The $oView->getTitle() in both application/views/flow/tpl/page/list/list.tpl (line 35) and application/views/flow/tpl/layout/base.tpl(line 11) call application/controllers/alist.php::getTitle() method. This method returns the active category's title value.
1. Can you give an example or a situation where these two must differ.
2. What do you actually mean by SEO Title?


2016-11-18 10:06

reporter   ~0011872

1. For example you have a SEO manager and he wants to optimize the page title (<title> tag) but the h1 heading on the page itself should NOT change. This is actually impossible with that theme.

The Method getTitle() implemented in alist.php is meant to return the page title (<title> tag) not the visible title of a Category as there is "oxCategory->getTitle()" for it.

2. <title> tag in meta informations


2016-11-18 10:23

administrator   ~0011873

Thank you for the information. I am changing the severity to a feature request.


2017-05-19 14:10

reporter   ~0012097

I created a pull request for this issue:


2022-01-28 11:50

administrator   ~0013538

The pull request was once done and then reverted, because it caused side-effects. If this should still be implemented, the change must be more sophisticated. Please see pull request.
In any case: This won't be fixed or changed for flow anymore. Also since the value comes from the controller, you can easily change what it would return anyway.