trench999

Re: CQ 5 Rich Text Editor with Cut and Copy Plugin Added - Adobe Experience Manager 15-10-2015

Support is saying this is known defect and is scheduled for the next release. I would encourage everyone who want to get this fixed to enter a support ticket to rally for a fix. This is a pretty basic feature in an RTE. As bad as the RTE is, we need to make sure that the functionality it has does work.

137

launch Rich Text Editor on Drop - Adobe Experience Manager 15-10-2015

I see an event that fires for placing a component in a parsys. Does anyone have a snipped of code that can be used to open the dialog immediately when that event is fired?

179

Re: Open richtext editor on drop/place - Adobe Experience Manager 15-10-2015

I did find that Andy Power offers a solution at http://andypowell.org/category/cq5/Here is the listener function:function(path, definition) { var dialogConfig = CQ.WCM.getDialogConfig(definition.dialog); dialogConfig.success = function(form, action){ CQ.Util.reload(CQ.WCM.getContentWindow()); }; dialogConfig.failure = function(form, action){ var resp = CQ.HTTP.buildPostResponseFromHTML(action.response); CQ.Ext.Msg.alert(response.headers[CQ.HTTP.HEADER_MESSAGE]); }; var dialog = CQ.WCM.getDialog(...

183

Open richtext editor on drop/place - Adobe Experience Manager 15-10-2015

I see component "placement" events in the widget API. Has anyone setup components to open the dialog based on that event?

221

Re: Your Thoughts - Comparing CQ5 with Wordpress - Adobe Experience Manager 15-10-2015

This is difficult question to answer without knowing the full extent of your needs. Essentially these are two very different platforms. For simple structured, repeating content WordPress meets the need very well on many levels. The level of market saturation alone makes WordPress a good choice for sites that are basic. AEM is an enterprise content and marketing platform with an architecture to handle complex and wide publishing and distribution workflows. The authoring experience is fundamentall...

373

Re: Default component content in template components - Adobe Experience Manager 15-10-2015

Thanks, but we should not have to extend a component every time we want some default text. This is is not conducive to author experience. What other alternatives are there?

1.1K

Re: Default component content in template components - Adobe Experience Manager 15-10-2015

No worries. It was seem like if you had some content or a reference in a cq:include tag then that would server as a parameter in the instantiation of the component instance. eg.

1.1K

Re: Default component content in template components - Adobe Experience Manager 15-10-2015

No, I am doing this with the snippet above. I am trying to setup "placeholder" or default text on the text component I have setup already on the page.

1.1K

Re: Default component content in template components - Adobe Experience Manager 15-10-2015

Thanks, Scott. This is not directly related to what I want to do, but I had not seen the boiler plate option before. I can push default components on page as you suggest or directly embedded in the template jsp. The issue is adding default content for a given cq:include. It would be best to have an attribute that allows direct injection of the placeholder text and even better we would have a reference attribute that could pull content from a /content node. Where do we add such requests?

1.1K