User tests: Successful: Unsuccessful:
Follow-up Pull Request after #32448
After updating the article view with the above-mentioned PR, this PR updates all the other views as well to show the component title as H1 when the Menu Title is hidden.
In particular this updates the following views:
In addition, when doing this, I stumbled upon an unused page_subheading param that was present in the 'featured' views and the 'category blog' views. This looks to be an outdated and out of place parameter that was present just in those two views and nowhere else. I don't think nobody has even ever used it.
So this also addresses issue #29586, removing the page_subheading parameter in those views, making them consistent with all the other views as well.
Components title is H2.
Components title is H1 when Menu Title is hidden.
Status | New | ⇒ | Pending |
Category | ⇒ | Front End com_contact com_content com_newsfeeds com_tags Layout Plugins |
Please test @laoneo @bembelimen @brianteeman @simbus82 @Quy
Thanks!
Labels |
Added:
?
|
Title |
|
Title |
|
Category | Front End com_contact com_content com_newsfeeds com_tags Layout Plugins | ⇒ | Front End com_contact com_content com_newsfeeds com_tags Language & Strings Layout Plugins |
Labels |
Added:
?
|
Category | Front End com_contact com_content com_newsfeeds com_tags Layout Plugins Language & Strings | ⇒ | Administration Language & Strings Front End com_contact com_content com_newsfeeds com_tags Layout Plugins |
I have tested this item
I opened the Contact default view. Before applying the patch title was having h2 tag, after patch, it was h1.
I have tested this item
See next comment and review.
I have tested this item
See next comment and review.
This one also needs changes:
joomla-cms/plugins/sampledata/multilang/multilang.php
Lines 856 to 869 in 90ab8c0
would also be modified to include the changes as done in #32550
@AndySDH - working through testing all the scenarios (@himanshu007-creator - will chat in Glip about improving the level of detail for your testing) and found a syntax error that breaks the Blog Category Layout when the patch is applied.
Aside from that, all the other scenarios look to have worked correctly, so will be able to retest quickly when this has been fixed up as I've got all the menu items for the different scenarios saved and ready to go.
Whoops, sorry, thanks for reporting this! It's now fixed.
How did the auto-check not automatically spot this?
@AndySDH, take a look at @infograf768 suggest change needed for the sample data.
#32550 is being worked on concurrently, but it's taking care of the default install. The Sample Data has the same problem that PR is looking to fix, which is that the sample data has J3 parameters not J4 parameters. Just going to see if I can work out what needs to go in there quickly to speed up the change for you.
Once that's also fixed I'll then retest also with a new install + sample data install.
Changes to match up #32550. Part 2.
It stopped letting me add reviews to the code after line 862 for some reason. There's one more line needing adjustment to match up the changes outlined in #32550.
Line 864 - remove show_associations parameter: New line:
. '"link_parent_category":"","show_author":"","link_author":"",'
@AndySDH Ignore this per @infograf768 comment below.
#32550 is marked as merged - so is this ready for testing?
Labels |
Added:
?
|
Category | Front End com_contact com_content com_newsfeeds com_tags Layout Plugins Language & Strings Administration | ⇒ | Administration Language & Strings Front End com_contact com_content com_newsfeeds com_tags SQL Installation Layout Plugins |
Category | Front End com_contact com_content com_newsfeeds com_tags Layout Plugins Language & Strings Administration SQL Installation | ⇒ | Administration Language & Strings Front End com_contact com_content com_newsfeeds com_tags SQL Installation Postgresql Layout Plugins |
I have tested this item
1. Syntax error with Blog Category Layout fixed from previous test, so this part was successful.
#32525 (comment) - Add . '"blog_class_leading":"","blog_class":"",'
before line 859.
#32525 (comment) - Add "link_intro_image":"",
at 860
#32525 (comment) - Add "article_layout":"_:default",
at 862
Labels |
Removed:
?
|
@particthistle Done, thanks!
I have tested this item
Thanks @AndySDH
H1 settings all working.
Changes to related items identified in the multi-language sample data identified in #32550 also now applying successfully.
Concerning subheading: It was used in 3.9 https://issues.joomla.org/tracker/joomla-cms/30422
Concerning subheading: It was used in 3.9 https://issues.joomla.org/tracker/joomla-cms/30422
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/32525.
I'm aware but it was used present only in 1 view (2 if you count Featured view), and absent in all the others. It was wildly inconsistent and I felt it served not much of a purpose. So I thought it made it sense to clean it up and remove it.
Subheading removal: Should it go ahead (I don't know anyone using it, but I'm sure there may be) do we just need to make sure it's listed here: https://docs.joomla.org/Potential_backward_compatibility_issues_in_Joomla_4
If so, add Documentation Required tag for follow up.
I have tested this item
Tested the behavior on all mentioned categories. Thanks @particthistle for helping out earlier.
I've allowed myself to solve the merged conflict and restored the previous test results because the merge after that for resolving the merge conflict was only a code style change.
Status | Pending | ⇒ | Ready to Commit |
RTC
Thanks @richard67
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2021-04-17 15:19:07 |
Closed_By | ⇒ | chmst | |
Labels |
Added:
?
|
Thanks!
@AndySDH So this PR solves that issue #29586 ?