Dave_Hughes

Re: Client code for cq:layout=auto - Adobe Experience Manager

Thank you, Scott. That's unfortunate, but it's an answer.

384

Re: Client code for cq:layout=auto - Adobe Experience Manager

Thanks Scott. Do you know what the turn around time is for this type of request?

373

Re: Client code for cq:layout=auto - Adobe Experience Manager

Thanks, but I am familiar with setting the cq:layout to editbar. My question is specifically about setting the layout to auto. The documentation describes auto as "The choice is left to the client side code". I interpret this as meaning that the choice between editbar and rollover is made at page render time, determined by some client code (JSP/JavaScript/something else?). I am looking for an example or documentation for the "client code" that would dictate which layout to use.EDIT: you beat me ...

382

Client code for cq:layout=auto - Adobe Experience Manager

I would like to use cq:layout="auto" in my component's edit config. https://docs.adobe.com/docs/en/cq/5-5/developing/components/edit_config.html#cq:layoutThe documentation states that auto allows the client code to determine if it should be editbar or rollover, but I can't find any documentation or literature on how to achieve this. Could anybody provide sample code or links to help? Thanks!

849

Re: Submitting a message to the AEM 5.6.1 Inbox (graceful workflow process step failure) - Adobe Experience Manager

*bump*

1.5K

Submitting a message to the AEM 5.6.1 Inbox (graceful workflow process step failure) - Adobe Experience Manager

Hello,We have implemented a custom workflow process step to perform an operation against an integration. The particulars aren't important.Currently, if an error occurs when we call the integration, we throw a workflow exception. This causes the step to be retried (10 attempts), after which the workflow is halted and a the exception is sent to the AEM inbox (/inbox) as a FailureItem.We wish to change this behaviour so that the process step is tried only once. We wish to make it a graceful failure...

1.6K

Re: Dispatching a request from a workflow process (5.6.1) - Adobe Experience Manager

Thank you again, Kunal. I had already searched for the source of SlingRequestProcessorImpl for setStatus, and found none; I did, however, overlook the calls to sendError, which I suppose my wrapper also needs to implement, in order to set status code. Once again, thank you.

552

Re: Dispatching a request from a workflow process (5.6.1) - Adobe Experience Manager

kunal23 wrote... I guess you used the RequestResponseFactory service to get the dummy request, response objects for sending a request to the SlingRequestProcessor. The request, response objects this service creates are just mock objects and they do not have any implementation of setStatus and getStatus methods. To get the status of the response you can create your own response class implementing the HTTPServletResponse interface. In the setStatus method you can set the value passed in the method...

500

Re: Dispatching a request from a workflow process (5.6.1) - Adobe Experience Manager

Another excellent response, thank you so much.

496

Re: Create Page Option appears to be null and not available in AEM - Adobe Experience Manager

Happy to help. I've seen several other individuals trip over this before as well. I'm not sure how it is that the problem is so common, as it seems to require that a user delete/renames a node that they should not, but it does seem to happen alarmingly frequently. I'd love to see Adobe make the Projects and Site Admin interfaces more durable, so they don't just fail silently under these conditions.

1.8K

Re: Create Page Option appears to be null and not available in AEM - Adobe Experience Manager

I'm not familiar with the newer projects interface, but I've experienced a similar issue with the older Site Admin (/siteadmin).The issue that I've experienced seems to occur if any piece of content (at least top-level content, possibly even nested content) becomes "corrupt", by missing it's jcr:content child node. If this is the same problem, you should be able to explore the repository with CRXDElite (/crx/de/index.jsp#/content) and either add the missing jcr:content nodes, or delete any conte...

1.7K

Re: Dispatching a request from a workflow process (5.6.1) - Adobe Experience Manager

Thank you, kunal23. That was exactly what we were looking for in order to process the internal sling request. Is there any way to determine the response code? By logging the response output stream, I was able to determine that my initial attempt resulted in a 404 (because I included the query string in the request path, rather than breaking out to a params map), but it does not appear possible to determine the response code from the response object. Any tips?Also, I retrieve a ResourceResolver f...

496

Dispatching a request from a workflow process (5.6.1) - Adobe Experience Manager

Hello,We are creating a simple workflow process to automate a process that would generally be executed by a content manager. The process is to click a button on the Page tab of the Sidekick. The button is provided by ClayTablet (an integrated translation platform), but this is a superfluous detail; the important part is that the button results in a GET request to a path/servlet on the current author environment.We've tried a few approaches:urlcaller process (out of the box) to make the HTTP requ...

1.3K

Re: AEM6 Instance Start Times - Adobe Experience Manager

I've encountered this with 5.6.1 as well. The initial startup will take upwards of 20 minutes, with restarts (without system reboot) starting in 1-2 minutes.

482

Re: Setting allowed children on triple nested parsys - Adobe Experience Manager

I've finally resolved this. The key was that the conditions component had to be a container (component defined with property cq:isContainer="{Boolean}true"). Setting this property not only made the allowedComponents work as expected, it also allowed the updatecomponentlist event listener to be registered on the component (https://helpx.adobe.com/experience-manager/kb/HowToDefineComponentListDynamically.html).

401

Re: Execute Dialog Validation on Activation (AEM 5.6.1) - Adobe Experience Manager

Bump. Nobody has dealt with the same problem? No suggestions?

317

Re: Execute Dialog Validation on Activation (AEM 5.6.1) - Adobe Experience Manager

Hi Jitendra. Thank you for responding.We do not enforce manual review. Even if we did, the intent would be to review copy (text) and layout; it is unlikely that a manual reviewer would detect issues with misconfigured properties, unless there was a visual discrepancy. As mentioned, we currently have a replication preprocessor which automatically runs a set of validation rules on the page properties prior to replication, cancelling the activation if any property fails the validation. We would lik...

318

Re: Execute Dialog Validation on Activation (AEM 5.6.1) - Adobe Experience Manager

One suggestion from StackOverflow: http://stackoverflow.com/a/34160564/3192139This suggestion is to include a hidden field in the dialog for each and every component, which would set a property (eg, isComplete) on the component's node when the dialog is opened and saved. Since the save will only succeed if validation is successful, the property will only be set when the validation rules have passed. The activation preprocessor could then iterate over all nodes under a page and ensure that the pr...

322

Execute Dialog Validation on Activation (AEM 5.6.1) - Adobe Experience Manager

Originally asked on StackOverflow: http://stackoverflow.com/questions/34145668/execute-dialog-validation-on-activation-aem-5-6-1AEM/CQ5 (5.6.1) appears to have a deficiency in how content validation works in the out-of-the-box product.Though component dialogs have a mechanism for validation, the validators only get executed when the dialog is open. The problem is that a component can be added to a page, and without opening the component's dialog, the page can be activated with the unconfigured c...

644

How To Define Component List Dynamically - Adobe Experience Manager

https://helpx.adobe.com/experience-manager/kb/HowToDefineComponentListDynamically.htmlThe instructions in that Knowledge Base article do not seem to work with AEM 5.6.1. I have raised DayCare ticket #80287 about that.Is there a way to achieve the same in 5.6.1? Can the allowed components for a parsys be dynamically defined, so instead of using a design to specify the allowed components, the components themselves can control what may be placed in them?

175

Disable 'delete' in context menu of embedded component - Adobe Experience Manager

We have a component (conditionsContainer) that is only ever used by embedding it in other components. We would like to disable the context menu for this conditionsContainer component, so that it cannot be removed. Currently, we prohibit deletion of the conditionsContainer component with the use of a beforedelete event listener that returns false. For obvious UX reasons, however, we would like to remove the ability to click delete. Using the edit bar (which can be customized without a delete butt...

465

Re: Setting allowed children on triple nested parsys - Adobe Experience Manager

A few weeks later, I'm reviving this thread.The link that bsloki provided appears to be the opposite of what I'm trying to achieve. The gist (which is associated with http://www.citytechinc.com/us/en/blog/2013/02/limitations_of_the_cq_parsys.html) seems to create a parsys that can be nested in another parsys, but simply inherits the allowed components from the parent parsys.Perhaps that approach could be modified, changing the cellSearchPathModifier function to search deeper than the out of the ...

449

Re: Allowed components for a parsys do not apply when the parsys is loaded from absolute path - Adobe Experience Manager

As an aside, this isn't a major impediment. By taking a slightly different approach, I am able to work around this by adding a dialog to the "sandwichTypesConfig" component (which is actually an extension of parsys, not a foundation/components/parsys). The dialog allows me to add children to the parsys, without the sidekick recognizing the children as allowed.I am still seeking input from others, however. Please weigh in with your thoughts on the original question.

432

Allowed components for a parsys do not apply when the parsys is loaded from absolute path - Adobe Experience Manager

I've recently built a new tool for managing a certain type of system-wide configuration; we'll call it the Sandwich Types Config Tool. This tool resides under the Tools section (/etc).The initial implementation stored the configuration under the tool itself (the tool is an instance of a "sandwichTypesTool" page component, which includes a "sandwichTypesConfig" parsys for adding Sandwich Type components to). In an effort to decouple the tool and the configuration, I chose to move the "sandwichTyp...

842

Storing a component property under a different node - Adobe Experience Manager

I am building a tool under the Tools/Misc admin (/etc) for managing a particular custom configuration. This tool has some characteristics/constraints that I wish to satisfy:I would like to build this page with a custom component for the input of the configuration, so that the Content Managers responsible for this configuration has a consistent experience between using this tool and authoring content.I would like to decouple the tool and its data, so that the tool may be included in and deployed ...

340

Re: TagInputField widget with custom template - Adobe Experience Manager

I suspected that this may require a custom extension to the widget, and you have confirmed this for me. Thanks again, Praveen.

271

Re: TagInputField widget with custom template - Adobe Experience Manager

Thanks edubey,I had not noticed the displayTitles property. Thank you for pointing me to that. I have now tried it, and unfortunately, it only applies to the "current tags" field, not the tag picker panel (which is arguably more important in this case).I have learned, however, that retrieving the title from a tag object escapes (actually, replaces with a space) colons and slashes. As we are trying to use the tag's title for CSS media queries, having colons and slashes removed was problematic. Fo...

265

TagInputField widget with custom template - Adobe Experience Manager

I have used the "tags" xtype on a component dialog, but I would like to render the tag picker with a slightly different template. Rather than displaying the tags' titles, I'd like to display the name.Is this possible? From the docs, I've tried to use the tpl config option, but I can't get it working.Help, please? Thank you.

486

Re: DropTarget for Component Embedded in Page (AEM 5.6.1) - Adobe Experience Manager

*bump*This is still unresolved. Cross-posted on stackoverflow: http://stackoverflow.com/questions/30516922/cqeditconfig-not-applying-outside-of-parsys

484

Re: DropTarget for Component Embedded in Page (AEM 5.6.1) - Adobe Experience Manager

Pawan, thanks for your response.By "not accepted", I mean that the image cannot be dropped on the component. WCM shows the not allowed image as you hover over the component that you want to drop the image on. It looks the same as when you try to drag a component from the Sidekick to a parsys that does not allow that component type.--I tried adding the node to the editConfig, but it made no difference. We actually removed that recently, because it was set to the wrong resourceType and changed th...

432

Likes from

User

Count

Learn

Documentation

Community

Support

Resources

Adobe account

Adobe