Pull Request for Issue # .

Related to #5544

Summary of Changes

Main Improvement:

• remove subquery with "badcats" from frontend queries.
• recursive update column published for children items, column published is re-calculated on every save, change state, move or copy for #__categories and #__menu (in general for subclasses of JTableNested).

In order to not display unpublished categories on front end old installation has to call additional query.
That query re-calculates published column for whole tree.

After apply patch on exists installation you have to run 2 queries from:
[Chose your database]

* administrator/components/com_admin/sql/updates/mysql/3.7.0-2017-03-09.sql
* administrator/components/com_admin/sql/updates/postgresql/3.7.0-2017-03-09.sql
* administrator/components/com_admin/sql/updates/sqlazure/3.7.0-2017-03-09.sql

A new Rules for nested tables like (category, menu):

• If parent will be published then there is no action or restrictions for children
• If parent will be archived then all published children will be set as archived
• If parent will be unpublished then all published/archived will be set as unpublished
• If parent will be trashed then all children will be trashed

Old behaviour:

• On save, move or copy category (or menu) then is no exists any recursion for published column. There could be published subcategory in non published category.
• On publish/unpiblish/archive/trash category/menu all children has been recursive update to the same state.
• You can create published category on unpublished parent.
• On frontend query (related to articles), the query has to check ("badcats") if all category parents has the correct state (ex. published = 1)

New bevaviour

• On all action like save/move/copy/change state recursion is call and change children state.
• published column of children items is changed based on the rules.
• If you create a new category (as published) on unpublished parent, then the new category also be unpiblished.
• Frontend queries does not need to include subquery with "badcats" because last child has calculated state of published column.

Testing Instructions

Test categories, menus and articles on front end and on back end.

[UPDATED]

• Create a new category/menu as published on non published category, result: non published
• Change state on category with children, see recursive
• Move some (sub tree of) category to other ex. unpublished category.
• Changing published state at edit form of category/menu give the same result as in categories/menu list by click [Publish/Archive...]. There should be no difference where you change the published state.

All above points should follow the rules.

Expected result

Joomla should work as before but faster on frontend views: featured/blog/list/archived/article and on others which use model from components/com_content/models/articles.php like mod_articles...

Actual result

On front end with lots of categories and articles Joomla works slow.

Documentation Changes Required

I do not know.
Special subquery (badcats) for nested tables are now not required.
The new rules in JTableNested which change published state for children.