Using Adobe Experience Manager (AEM), I'm trying to overlay the cq/searchpromote/components/search component.
I have copy/pasted the folder and my search.jsp is working as it should with new functionality.
My dialog won't work. It still reads from the original default component. The naming and path are the same so I believe it should work.
What could be the issue?
Related
Is there any way to customize IonSelect component, or to create some custom component which contains search box inside (on top of) it?
There is one ionic component IonSelectable for angular and this is exactly what I need in react typescript as well.
Here is link to installation and example: https://www.npmjs.com/package/ionic-selectable for this component. Here is also a link to github repo: https://github.com/eakoriakin/ionic-selectable.
Here is the picture how it looks like, and it is pretty amazing:
Does anyone know if something same/similar already exist for react typescript? Or, is there any one to create/solve this?
I have lately installed a Google Tag Manager plugin on our Shopware store, the problem is that it is only implemented on the Responsive theme.
We have created another theme, which is derived from Responsive but has another name.
How can I make the plugin work for this theme as well (or instead)?
Thanks!
Try adding protected $injectBeforePlugins = true; in your theme's Theme.php file.
I am working on creating a component with both a dialog and a design_dialog. In the design_dialog, I am using a pathfield widget to allow a designer to select a root path. In the dialog, I am trying to use another pathfield widget to allow the author to select a page under the path that was selected by the designer in the design dialog. (Basically I am trying to set the rootPath property of the widget in the dialog to equal the path the designer chose in the design_dialog.) It seems like it should be something simple to do, but I'm having no luck. Any help or pointers would be greatly appreciated.
Adobe AEM uses ExtJS for the widgets (in Classic mode).
Here is a resource to get you started:
http://docs.adobe.com/docs/en/cq/5-6-1/developing/widgets.html
Here is the API doc:
http://docs.adobe.com/docs/en/cq/5-6/widgets-api/index.html
And maybe have a look at this: http://labs.sixdimensions.com/blog/2014-04-07/cq-dialog-dynamically-generate-rootpath/
I am creating a new template and then a page from SCRATCH in CQ5. But I can't find the option to add my own CSS/images/JS to the page.
I mean a place to add/upload the actual files.
All the tutorials I've seen talk only about creating a template based on an existing template. Is there any tutorial on how to create the page from scratch ?
Your CSS and JavaScript go into nodes under /etc/designs/[your project's name]/clientlibs. (Ordinarily, you would set the page property cq:designPath of your content's home page to be /etc/designs/[your project's name] to point to this.) It's common practice to set up a subfolder of clientlibs called default, where your general-purpose style sheets and JavaScript go; you can set up other clientlibs for special-case script and style sheets. The simplest way to incorporate your script and style sheets into your page template is the <cq:includeClientLib> JSP tag.
The Adobe docs on clientlibs will also be useful to you, and explains how to use the tag.
#David , thanks for your answer, but for now, I got a better way to add and then use external files using WebDAV with CQ5.
The basic integration of WebDAV with CQ5 application is mentioned in this page
I am new in CQ5 and I would like seek help on how will I be able to add a new custom console in my CQ instance. If you guys can give me a walkthrough or a reference which I can use. I'm trying to search for answers but I failed to get one.
You can customize the login and welcome screens by copying the relevant code in /libs/cq/core/content, /libs/cq/core/components, /libs/wcm, etc. to the corresponding /apps node(s), just the same way you would customize an ordinary content-handling component. Some references in the CQ5 docs:
http://dev.day.com/docs/en/cq/current/deploying/configuring_cq.html#Removing%20CQ%20Sign%20Out%20Links
http://dev.day.com/docs/en/cq/current/developing/customize_siteadmin.html