AEM 6.5 Bulk Editor Pathbrowser Inactive for Tags when Pages Do Not Have Equal Set of Tags

[joeobar]

Hello,

Since initially creating this post I created a case with Adobe support as this may be a bug.  Let me know which is the appropriate channel and I will close the redundant one.  

In 6.2 we were able to select multiple pages and then properties to allow bulk editing.  The path browser option to select tags was active regardless of the values of the currently selected tags for the pages.  The common tags were displayed and any new tag selected was added to the tag set for each of the pages.  

In 6.5 the behavior has changed as the path browser option is inactive unless the tag sets are equal across the selected pages.  

There does seem to be a work around - uncheck one of the pages and then recheck.  This results in the path browser button being active. 

How can we allow the behavior of 6.2 in 6.5 without the work around? 

[Vijayalakshmi_S]

Hi @joeobar,

I tried reproducing this in my local AEM 6.5.0.

Though the tag field is editable upon removing one page from selection and including it back, associating new tag will not be persisted upon "Save & Close" (No input on cq:tags field in POST request)

It should have been an intentional behavior(Not allowing to edit/disabled tagfield/not persisting the data even if it editable in the UI) when the tags are not exactly/completely equal in the selected pages. 

Given that you already raised a Support ticket, you can get this affirmed from Engineering team. 

[jetate]

Have you had any success in resolving this issue? I've seen another post which referenced the parameter allowBulkEdit which I already have set to true on the main Tags property as well as another custom tags property, but neither are actually allowing for bulk editing of pages unless the existing page tags match. It seems like this is something that should be allowed but has been broken by design based on the disabling of the property.

[dtbayer11_]

Hey all,

I found this thread while looking into the same issue - using AEMaaCS ver.2022.9.8722.20220912T101352Z-220800. The symptoms are the same down to the letter. Has there been an update, resolution, or walkaround?