[5.2] Deprecate WebApplication::$JComponentTitle

[HLeithner]

Summary of Changes

Deprecate the legacy parameter $JComponentTitle from WebApplication. This should have been done when the variable has been created. Sadly it has been missed.

Testing Instructions

No test needed

Link to documentations

Please select:

• Documentation link for docs.joomla.org:

• No documentation changes for docs.joomla.org needed

• Pull Request link for manual.joomla.org:

• No documentation changes for manual.joomla.org needed

[brianteeman]

I have tested this item ✅ successfully on 247c409

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/43304.}

[ChristineWk]

J 5.2.0-alpha1-dev
Code Review

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/43304.}

[ChristineWk]

I have tested this item ✅ successfully on 247c409

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/43304.}

[Quy]

RTC

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/43304.}

[wilsonge]

The usage in mod_title goes back to at least joomla 1.6 and I suspect earlier (

joomla-cms/administrator/modules/mod_title/mod_title.php

Line 13 in 83939b8

$title = &JFactory::getApplication()->get('JComponentTitle');

). Whilst it definitely belonged in AdministratorApplication and not WebApplication, I think this needs better docs than just deprecated because core isn’t using it, we don’t know what plugins or admin modules might be using this from days gone old. Such as what is the correct method for plugins etc to set a page title. I believe when production made the rule of 2 major versions deprecation the deprecation also had to include a replacement method

[HLeithner]

Replacement is set or get title Form the document AS documented in the deprecation.

[laoneo]

Should you then not fallback to the document title here https://github.com/joomla/joomla-cms/pull/43304/files#diff-a35dff7f70b05500db42e3f582368ededb2d2477bbc955142c16a0038e184a6cR40, when this should be the replacement?

[HLeithner]

Should you then not fallback to the document title here https://github.com/joomla/joomla-cms/pull/43304/files#diff-a35dff7f70b05500db42e3f582368ededb2d2477bbc955142c16a0038e184a6cR40, when this should be the replacement?

We do this when the variable gets removed in 7.0

joomla-cms/libraries/src/Toolbar/ToolbarHelper.php

Line 55 in 42c57d6

$app->getDocument()->setTitle($title);

Until then we have to use the variable because we can't (or don't do) intercept when someone sets the JComponentTitle by hand in the application.

So yes in 7.0 we have to use document->getTitle() in the module.

[laoneo]

I think this should be done now as fallback, something like:

$data['title'] = isset($this->getApplication()->JComponentTitle) ? $this->getApplication()->JComponentTitle : $this->getApplication()->getDocument()->getTitle();

[HLeithner]

since this is only used for mod_title and only in combination with the toolbar::title function it's something which would be a behavior change which could be unexpected. ex. if your want to remove the title for you extension $app->JComponentTitle = ''; or null worked the last 15 years. If you change this now you can remove the variable and functionality directly and would have the same effect.

Extension developer have to set it in $doc->setTitle();.

only a thought I have I didn't proofed if this is a usecase

[laoneo]

As it is an isset() check, '' or null would still work, as long as the variable exists.

[HLeithner]

As it is an isset() check, '' or null would still work, as long as the variable exists.

I'm sorry but that's wrong

[laoneo]

True, null is not covered

[pe7er]

Thanks @HLeithner !