AEM 6.4.3 siteadmin : new page dropdown is disabled | Community
Skip to main content
K
karanmahi
Level 4
February 4, 2019
Solved

AEM 6.4.3 siteadmin : new page dropdown is disabled

  • February 4, 2019
  • 8 replies
  • 1617 views

In AEM 6.4.3, We are running automation script, and when we access a page directly on the browser to create "new page under that path", we are noticing that new page dropdown is completely disabled. We are seeing similar behavior on we-retail pages, for example (http://localhost:4502/siteadmin#/editor.html/content/we-retail/us/en/men.html). That new page dropdown becomes "enabled again only when I select some hierarchy on the left side or any pages on the right side". but since I will be calling the page directly from an automation script, we cannot touch the site admin. This used to work on 6.3. How can we get this working in 6.4.3?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by smacdonald2008

I am seeing the New Page show up. Click on We Retail and then try. You should see New Page enabled as shown below.

2nd - to everyone reading this. In 6.4 - Classic UI is depreciated. I talked with the Team team and they recommend that everyone on 6.4 - you should be using TOUCH UI to perform operations like Creating new pages.

8 replies

smacdonald2008
smacdonald2008
Level 10
February 4, 2019

This is a new issue - i have never seen. I am checking with the team.

smacdonald2008
smacdonald2008
Level 10
February 4, 2019

The team replied there is not much we can do on our end as Classic UI is now depreciated in this version of AEM.

Gaurav-Behl
Gaurav-Behl
Level 10
February 4, 2019

works for me on 6.4.3.  If it doesn't work for you, then there must be some error in console log or error.log/conflicts due to your code customization.

You may validate it on a fresh instance.

K
karanmahiAuthor
Level 4
February 4, 2019

Hi Gaurav,

1. I have tested this on a vanilla 6.4 instance with 6.4.3 service pack only, nothing else (no custom code). Still same issue.

2. When you hit this page in your browser http://localhost:4502/siteadmin#/content , just click on new page dropdown(don't click anywhere else.) Does this scenario work for you? I have tried on different machines, every time seeing the same issue.

3. We have only service pack 6.4.3. Seeing the same issue even without this service pack i.e on 6.4 vanilla. Can you please confirm your packages on 6.4 vanilla?

Gaurav-Behl
Gaurav-Behl
Level 10
February 4, 2019

Correct. Look out for errors/warnings. I don't think this is a showstopper, you could still move the root page from /crx/de or find another workaround.

AEM 6.4.3

core components 2.2.2

acs commons 3.19

acs tools 1.0.2

smacdonald2008
smacdonald2008Accepted solution
Level 10
February 5, 2019

I am seeing the New Page show up. Click on We Retail and then try. You should see New Page enabled as shown below.

2nd - to everyone reading this. In 6.4 - Classic UI is depreciated. I talked with the Team team and they recommend that everyone on 6.4 - you should be using TOUCH UI to perform operations like Creating new pages.

smacdonald2008
smacdonald2008
Level 10
February 5, 2019

Touch UI -

Y
Adobe Employee
Yann_IckAdobe Employee
Adobe Employee
February 6, 2019

Hello,

This is an issue with the very initial loading of the SiteAdmin. Once you start navigating in the left tree, the actions button are properly updated.

I guess the sample URL you provided had a mistake, and the real one to test would be without the editor.html:

http://localhost:4502/siteadmin#/content/we-retail/us/en/men.html

This is really impacting when using automated unit tests, like with Selenium, and you could probably add some navigate and select steps to work-around the problem.

But the issue can be fixed by adding one single line to this file:

/libs/cq/ui/widgets/source/widgets/wcm/SiteAdmin.js

1436                            } catch (e) {

1437                                //console.log("error:" + e);

1438                            }

1439                        }

                            admin.checkActions();

1440                        admin.unmask();

1441                    }

1442                });

1443            },


It is not recommended to make any change directly under "/libs", so you need to implement this within an overlay (overlaying SiteAdmin.js under /apps).

Terms & ConditionsAccessibility statement

Loading footer...