Redirects are not Displayed Properly on ACS AEM Commons Version: 6.10.0

[seer-neil]

Required Information

• AEM Version, including Service Packs, Cumulative Fix Packs, etc: 2024.11.18598.20241113T125352Z-241100 - AEM CaaS
• ACS AEM Commons Version: 6.10.0
• Reproducible on Latest? yes

Expected Behavior

Current Redirects should be displayed on ACS Commons Redirect Manager

Actual Behavior

Current redirects are not displayed on Redirect Manager console. It was working properly since ACS AEM Commons Version 6.7.0

Steps to Reproduce

1. On AEM Cloud as a Service instance (preferably the version in the required information), install the latest ACS AEM Commons Version 6.10.0 together with your AEM CaaS code. This should be the same workflow as your normal AEM CaaS deployment. Make sure to include your current redirects.
2. On Tools > ACS AEM Commons > Redirect Manager
3. View the redirects.

Test Configuration Structure

conf/
    + redirect-manager/
       + <domain> [sling:folder]
           + settings [sling:folder]
              + redirects[acs-commons/components/utilities/manage-redirects/redirects]
                  - redirect_item_1 [acs-commons/components/utilities/manage-redirects/redirect-row]

*** the legacy redirects were made since ACS AEM Commons version 5.4.0 and has been working since ACS AEM Commons 6.7.0

[YegorKozlov]

I can't reproduce it on my local 2024.11.18598.20241113T125352Z-241100 and ACS AEM Commons 6.10.0.
AEM 6.5.22 + ACS 6.10 also works fine for me.

Does it work on your local ?

[seer-neil]

Hi @YegorKozlov , It’s not working on my local environment at the moment. I did test it on a clean local setup before deploying to the cloud instances, but I’m curious about your setup. Did you have your 'legacy' redirects in place before upgrading to ACS AEM Commons 6.10.0? For me, the redirects have been in place since version 5.4.0 and were working fine all the way through 6.7.0.

Right now, my legacy redirects aren’t showing up at all. Would love to hear what you’ve experienced on your end!

[YegorKozlov]

Are you sure you are running 6.10?

Redirect configs now showing up was a bug (#3486) which is fixed in 6.10. I do see it working on my local.

[seer-neil]

Yes. I am aware and have been following this issue for quite some time now.

Totally running ACS AEM Common Version 6.10.0

This is interesting, not sure if I can get something a sample code package or unless I am missing something here. Or maybe check the code commits on this issue board.

Peculiarly, it does work with version 6.7.0 but not after the succeeding releases.

[YegorKozlov]

Do you see the redirects if you access them via the redirect-manager url directly? e.g.

*.adobeaemcloud.com/apps/acs-commons/content/redirect-manager.html/conf/my-site/settings/redirects

I'd like to confirm if it is the configurations not showing up, or something else.

I do have tons of legacy redirects and they are working fine. I deployed 6.10 in AEM CaaS and all seems to be good .

[seer-neil]

@YegorKozlov I don't see any redirects when accessed it directly using the link you provided.
It is technically the configurations not showing up but I do seem them on the crx.

[YegorKozlov]

I tried a few more times and redirect manager worked for me all the time. I did a brand-new setup of the latest aem-sdk-2024.11.18751.20241128T090041 + ACS 6.10.0 and the redirects showed up . I deployed ACS Commons 6.10.0 from Cloud Manager and it worked again.

Is the problem only with legacy redirects? Are you able to create a see new configurations?

Can you upload a redirect configuration that wouldn't show up in your AEM? You can obfuscate the data.

[sravanikancharla455]

@YegorKozlov , I am encountering the same issue. While the problem mentioned in #3486 has been resolved, the redirects created as subfolders (e.g., /conf/my-site/child-site/settings/redirects) are still not appearing. Only the immediate children of the /conf folder seem to be showing up.

@seer-neil

[YegorKozlov]

@sravanikancharla455 Did the /conf/my-site/child-site/settings/redirects structure work in the past? It never occured to me users that could create such deep hierarchies, I designed RM to read configurations as immediate children of /conf.

How deep is your hierarchy?

[sravanikancharla455]

Yes @YegorKozlov, the /conf/my-site/child-site/settings/redirects structure has worked in the past. It was part of our design to organize redirects in a nested hierarchy. The hierarchy we're dealing with is currently up to four levels deep, with some configurations placed further within child-site structures. Would this be an issue with the current implementation, or is there a way to adjust RM to support this deeper nesting?

[YegorKozlov]

@sravanikancharla455 The fix is coming. I have an idea how to supported nested hierarchies.