Author instance package manager not pointing to correct URL

[Gokul2011]

Hi All,

Please guide on this issue 

Once login to Author instance welcome.html and tried to click Packages link on left side of welcome screen.

After clicking , the URL points to http://localhost:4502/crx/packmgr.html: 404 Not found

Actually it needs to point to http://localhost:4502/crx/packmgr/index.jsp

In log files we are getting same and throwing 404 error.

In /etc/map/http we are not able to see any folders for configuration.

Where to map the URL for Package manager in login page? 

[smacdonald2008]

What version of CQ are you using? 

[Sham_HC · Accepted solution]

Log to CRXDE Lite 

• browse to /libs/cq/core/content/welcome/features/packages and Make sure that
  • sling:resourceType is set to sling:redirect
  • and sling:target is /crx/packmgr/
• Similarly Browse to /libs/crx/core/content/welcome/core/crx/features/packages Make sure that
  • sling:resourceType is set to crx/core/components/welcome/feature
  • sling:target is /crx/packmgr/

[Gokul2011]

Hi Sham,

All the settings in CRXDE is fine as you suggested.

[Gokul2011]

CQ 5.5

CRX 2.3.32

[smacdonald2008]

Does this URL bring up Package Manager:

http://localhost:4502/crx/packmgr/index.jsp

[Sham_HC]

Might be browser cache. Clear the cache Or use private window of firefox & verify.

[Ove_Lindström]

Have you removed the index.html from the list of things to try when looking at a /-ending url?

[Gokul2011]

Yes when manually trying the URL it is working fine..

[Gokul2011]

Hi Ove,

Can you please explain it clearly . Where to remove index.html from home URL? 

[Gokul2011]

Hi Sham,

Tested in IE in private browsing , once clicked on packages it is pointing to

http://localhost:4502/libs/cq/core/content/welcome/features/packages.html    --- 404 error

[Sham_HC]

Seems like you have /crx node under the repository root folder directly. If yes, try moving it to temp folder and check the link.

[maheshgundre]

Hi Gokul,

Have you checked the bundle which is related to CRX Package manager?

If not check that bundle, try to reload the bundle

(Might be that bundle is giving problem)

Thanks,

Mahesh

[Adobeaspirant]

Same issue in AEM6.3