Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

trench999
trench999
Offline

Badges

Badges
18

Accepted Solutions

Accepted Solutions
4

Likes Received

Likes Received
6

Posts

Posts
79

Discussions

Discussions
3

Questions

Questions
76

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by trench999
Customize the badges you want to showcase on your profile
xtype Selection dropdown width - Adobe Experience Cloud 15-10-2015
We are finding a lot of usability issues with the default width of dialog widgets. We have been using:anchor="" width="160"...for various other components including text inputs and color pickers. This does not work for selection dropdown.

Views

444

Likes

0

Replies

0
Re: xtype Selection dropdown width - Adobe Experience Manager 15-10-2015
Thanks. This was a good clue, but does not work in a tabpanel > panel > fieldset dialog.xml config

Views

575

Likes

0

Replies

0
Running Update Asset workflow on existing assets - Adobe Experience Manager 15-10-2015
We had to add a rendition recently and would like to rerun Update Asset or a similar workflow to regenerate all the assets. What is the best way to do this?

Views

345

Likes

0

Replies

0
Re: Allowing <thead> in RTE - Adobe Experience Manager 08-09-2017
HI All,I have tried the above solution but seems that its only generates element but not element in the table.Has anyone found out any solution to include ?Thanks,Mayur

Views

1.3K

Likes

0

Replies

0
Re: Width of selection xtype - Adobe Experience Manager 15-10-2015
What I mean to say is try with 100% of anchor. If you observe any change in width of the the selection field, adjust anchor value to yours 150 px. To verify it, create a field of xtype textfield below or on above of it. Give width 150px to the textfield and compare with selection xtype.http://dev.day.com/docs/en/cq/5-6/widgets-api/index.html?class=CQ.form.Selectionhttp://dev.day.com/docs/en/cq/5-6/widgets-api/index.html?class=CQ.Ext.layout.AnchorLayout

Views

339

Likes

0

Replies

0
Re: Launch node url rewrites - Adobe Experience Manager 15-10-2015
Which version of aem? How did you promoted & what is status of launch?Technically if promote was successfully, launch pages will move the content back into production and url will be converted. From your description looks like you have missed some part OR permission issue in workflow package and promote is not succesful. All the issue reported so far are addressed & in fact we internally use it. I won;t rule out the fact there may be niche case it might have broken, i would encourage to engage w...

Views

192

Likes

0

Replies

0
Re: nodes checked in, checkout out - what is this? - Adobe Experience Manager 15-10-2015
It is used during versioning of node http://www.day.com/specs/jcr/2.0/15_Versioning.htmlYogesh

Views

494

Likes

0

Replies

0
Re: How to show available componets for page? - Adobe Experience Manager 15-10-2015
One thing to watch out for is where in the node hierarchy you put your configs. If you put one specific component in a column control versus template level you end up inadvertently losing all other components. We put all our design configs at the template region level.

Views

159

Likes

0

Replies

0
Re: Docs: wrong link for missing info - Adobe Experience Manager 15-10-2015
The link for the 6.1 documentation is:http://docs.adobe.com/docs/en/aem/6-1/author/page-authoring/working-with-page-versions.html#Restoring PagesWe've updated the link at:http://docs.adobe.com/docs/en/aem/6-1/author/page-authoring/managing-pages.html#Deleting a PageHope that helps and thanks for letting us know.

Views

460

Likes

0

Replies

0
Re: Migrating 5.6.1 ACLs to 6.1 - Adobe Experience Manager 15-10-2015
Keep in mind that the change Joerg is describing has absolutely nothing to do with ACLs. This is only for users and groups node names/path. The link between an ACL and a user/group was always done through the principal name.Any code which assumed that the path to a user or group was derivable from the username was buggy and likely to fail on any CQ/AEM version. The only change now is that this code will always fail. Which IMHO is actually much better

Views

253

Likes

0

Replies

0
Likes given to