User tests: Successful: Unsuccessful:
Pull Request for Issue # .
Since Joomla 3.6 , JViewLegacy has implemented the method setDocumentTitle https://github.com/joomla/joomla-cms/blob/staging/libraries/legacy/view/legacy.php#L854-L873 which is used to set document title base on site configuration. However, in many views in Joomla code base, we still use manual code, repeating code to set page title. This PR solves it
A real test would be check all views changes by this PR and make sure the document title is not changed before and after patch. However, honestly, I don't think we can expect that kind of test here because it would take much time
So I hope developers can help reviewing the code of the PR and confirm that it is expected changes. If you review code, please help reviewing every file carefully.
None
Status | New | ⇒ | Pending |
Category | ⇒ | Front End com_contact com_content com_finder com_newsfeeds com_tags com_users com_wrapper Libraries |
Title |
|
Labels |
Added:
?
|
no problem just ping me
if you had 200 than yes but 20 changed files is ok
OK. Thanks. I will leave it as how it is, then
I have tested this item
Status | Pending | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-05-14 01:39:23 |
Closed_By | ⇒ | joomdonation |
@joomdonation What is the reason to close this PR?
@n9iels Honestly, a PR which changes multiple files like this would be hard to get testers and proper testings
Also, I was thinking about introduce a new method which set both page title and page meta data (which basically including this block of code as well https://github.com/joomdonation/joomla-cms/blob/0031973e956bc83700140cb905e4a963c195cd45/components/com_content/views/form/view.html.php#L163-L176 )
So I think it is better to close this PR and do proper coding in Joomla 4. Thanks for reviewing the changes though :)
looks good now from a cs persprctive?