Item tracking improvements

[elit0451]

Details

This PR's purpose is to begin the process of integrating the functionality of the Nexu package directly into Umbraco 9.
The whole feature request can be found here.
@dawoe had already worked on 5/8 of the items on the TODO List for v8, and this PR migrates those to v9.

More specifically:

• Tracked references on Content items;
• Even if a parent item is not used, indicate on the info tab that one or more of the underlying items (descendants) is being used;
• Warn an editor when deleting a Media item that is being used;
• Warn an editor when deleting a Content item that is being used;
• Warn an editor when unpublishing a Content item that is being used.

This PR also adds the last 3 features from the list, related to warning the user when performing listview bulk actions:

• Warn an editor when deleting a Media item that is being used, using the listview bulk delete action;
• Warn an editor when deleting a Content item that is being used, using the listview bulk delete action;
• Warn an editor when unpublishing a Content item that is being, used using the listview bulk unpublish action.

Tests

• Have the SK installed
  • Check if media item references are shown correctly on the info tab
    • ex: Umbraco Campari Meeting Room image has a reference to Home
  • Check if content item references are shown correctly on the info tab
    • ex: Blog node has a reference to Home
  • Check that it is indicated on the info tab when underlying items are used (both for Content and Media)
    • ex: Design folder shows "One or more of this item's descendants is being used in a content item."
  • Check that when you try to delete a media item that is in use, you get a warning
    • ex: Before deleting Umbraco Campari Meeting Room image, you should get a warning
  • Check that when you try to delete a content item that is in use you get a warning
    • ex: Before deleting Blog node, you should get a warning
  • Check that when you try to unpublish a content item that is in use, you get a warning
    • ex: Try unpublishing Biker Jacket node should show a warning
  • Check that when trying to bulk delete Media items, you will only be warned about the items used in relations
    • ex: Click a Media folder and select used, unused, or both used and unused items and verify that the delete warning will show correctly
  • Check that when trying to bulk delete Content items, you will only be warned about the items used in relations
    • ex: Click a Products > Child Items and select used, unused, or both used and unused items and verify that the delete warning will show correctly
  • Check that when trying to bulk unpublish Content items, you will only be warned about the items used in relations
    • ex: Click a Products > Child Items and select used, unused, or both used and unused items and verify that the unpublish warning will show correctly
• Create your own references and verify the above ⬆️
• You can also modify some media/member types and reference content or media items to get the full set of references ("Used in Documents", "Used in Members", "Used in Media") displayed in the info tab.
• Experiment with pagination (p.1):
  • For info-tab, set ex: vm.contentOptions.pageSize = 5 in umbtrackedreferences.component.js loadContentRelations()

        function loadContentRelations() {

            vm.contentOptions.pageSize = 5;

            return trackedReferencesResource.getPagedReferences(vm.id, vm.contentOptions)
                  . . .
        }

• Experiment with pagination (p.2):
  • For listview, set ex: vm.mediaOptions.pageSize = 5; in umbtrackedreferenceslistview.component.js checkMediaListViewUsage()

        function checkMediaListViewUsage() {
            var ids = vm.selection.map(s => s.id);
          
            vm.mediaOptions.pageSize = 5;

            return trackedReferencesResource.checkLinkedItems(ids, vm.mediaOptions)
                  . . .
        }

---

Update:

• This PR also includes the functionality mentioned in V9: Displaying descendants in use as part of item tracking #12039 and V9: Prevent delete or unpublish of items that have references #12047

[bjarnef]

@nielslyngsoe shouldn't this be busy as in commit message "rename busfy to busy"?
https://github.com/umbraco/Umbraco-CMS/blob/v9/contrib/src/Umbraco.Web.UI.Client/src/views/users/user.controller.js#L377

Here it is busy:
https://github.com/umbraco/Umbraco-CMS/blob/v9/contrib/src/Umbraco.Web.UI.Client/src/views/users/views/users/users.controller.js#L339

Besides that I can't see the vm.enableUserButtonState or vm.enableUser() function is being used in user.html - only vm.enableUserButtonState and vm.enableUsers() in users.html

[elit0451]

I've renamed busfy to busy but will let @nielslyngsoe answer the other question 😊

[nzdev]

This query would benefit from an index on ChildId, IsDependency on RelationDto

[bergmania]

Good point.. Will create task for that

[elit0451]

RelationRepository.GetPagedEntitiesForItemsInRelation is not used as the logic has been moved to a different repo but we will create the indexes as they are still useful for the use case 👍

[elit0451]

The new place where we are making a similar query is TrackedReferencesRepository.GetPagedItemsWithRelations(). When testing we didn't see major improvements adding the indexes. Can you perhaps elaborate on the reasons for your suggestion? 🙂

[elit0451]

Thanks both for the suggestions! 💪 Most of them, together with additional fixes can be found in #12146