since ‎18-12-2014
‎10-12-2019
adobefor
Level 1
Parsys on top of an image adobefor - Adobe Experience Manager Forms
Hi, There is a requirement where parsys should be added on top of an image. It is like a background image with the provision of parsys so that other components can be dragged and dropped on top of it. I am using html5smartimage for image component. But, no clue yet on how I can get the parsys on top of the image. Please help if you find any ideas. Thanks.
459
Views
0
Likes
1
Answers and Comments
listeners involving dam assets adobefor - Adobe Experience Manager
Hi, I have a pathfield via which a dam asset would be selected (say Image). I want to have a listener attached to the pathfield which validates the size of the selected image. For that I would require asset api and resource resolver. By any chance is there a way to have these working inside a listener? I couldn't find any listener using these objects or could it be done? Thanks!
522
Views
0
Likes
1
Answers and Comments
Unable to select the components on a page adobefor - Adobe Experience Manager
Hi, I want to perform a rollout only for the selected components in the page. I notice that I am not able to select any of the components present in the pages using the small checkbox in the component's edit bar. I am not sure why this is happening. All of them are custom components and not OOTB ones. Any solutions to this, please share them. Thanks in advance!
116
Views
0
Likes
0
Answers and Comments
Re: Unable to cancel inheritance individually in rolled out pages adobefor - Adobe Experience Manager
Thanks a ton Sham! I included editContext.getEditConfig().setDeepCancel(false); in the topmost component's JSP. It worked perfectly as I wanted. 🙂
132
Views
0
Likes
0
Answers
Unable to cancel inheritance individually in rolled out pages adobefor - Adobe Experience Manager
I have a header component within which I have wrapped 3 more components.When I roll-out the page, the new page's inheritance lock is such that when I unlock the top most component (i.e, the main header that wraps the remaining), even the ones under that are getting unlocked(inheritance cancelled) which I don't want to happen. Please suggest if there is any way to avoid this without a JSP work around. Please find the code below:
225
Views
0
Likes
2
Answers and Comments
Re: CQ.WCM.select unavailable adobefor - Adobe Experience Manager
I have installed a new instance(5.6.1) to check the component selection's working in geometrixx pages. Even over there, teh selection is not working(verified in both chrome and IE). Please let me know if this is a bug in any case. Thanks!!
140
Views
0
Likes
0
Answers
Re: CQ.WCM.select unavailable adobefor - Adobe Experience Manager
var editBar = this; this.selectBox = new CQ.Ext.form.Checkbox({ // Box label will be set once the actions are retrieved (see: setBoxLabel) boxLabel: CQ.I18n.getMessage("{0} checkbox", ["Edit bar"], "Label of edit bar checkbox"), hideLabel: true, listeners: { check: function(cb, checked) { if (checked) { CQ.WCM.select(editBar, true); } else { CQ.WCM.deselect(editBar, true); } } } }); This is where I am facing the problem of select. The listener gets triggered and enters the 'checked' condition. B...
123
Views
0
Likes
0
Answers
Re: CQ.WCM.select unavailable adobefor - Adobe Experience Manager
[img]freshinstance.png[/img]
139
Views
0
Likes
0
Answers
CQ.WCM.select unavailable adobefor - Adobe Experience Manager
Hi, Is CQ.WCM.select not available in 5.6.1? Also, I see only deselect available in the widgets API (http://docs.adobe.com/docs/en/cq/5-6-1/widgets-api/index.html?class=CQ.WCM) I had doubts when I tried using cq.wcm.select and it didn't work. If so, what is the method that can be used for putting an object into selection? I am using cq version 5.6.1.
310
Views
0
Likes
4
Answers and Comments
Re: Unable to select the components on a page adobefor - Adobe Experience Manager
Hi, Thanks for the reply & yes, they are appearing on the sidekick. However, I just discovered the fix. The EditBar.js has a listener with the following lines of codelisteners: { check: function(cb, checked) { if (checked) { CQ.WCM.select(editBar, true);where 'check' has to be replaced with selectionChanged. Once I tried that, it worked!
184
Views
1
Like
0
Answers
Unable to select the components on a page adobefor - Adobe Experience Manager
Hi, I want to perform a rollout only for the selected components in the page. I notice that I am not able to select any of the components present in the pages using the small checkbox in the component's edit bar. I am not sure why this is happening. All of them are custom components and not OOTB ones. Any solutions to this, please share them. Thanks in advance!
451
Views
1
Like
3
Answers and Comments
Re: Problem with Parsys adobefor - Adobe Experience Manager
As answered, pl use editconfig. Else, you can hover over till you get the green focus on the parsys and rightclick. Click on edit and there you go with the dialog opening. Thanks!
195
Views
0
Likes
0
Answers
Re: Static Reference Rewriter- changes related to MSM adobefor - Adobe Experience Manager
Hi, yes, I had posted 5days back on the same forum. I haven't got it addressed yet. Thanks.
162
Views
0
Likes
0
Answers
Static Reference Rewriter- changes related to MSM adobefor - Adobe Experience Manager
Hi,We have a custom staticreference rewrite transformer component written. Also, the mapping has been made in projectName.xml under/config/rewriter. The functionality was working fine with en_US site redirecting images etc to the static domain. Now that multi lingual sites have been created, the functionality has to be extended to all the sites. As specified, I created new config nodes under config.prod as com.projectName.wcm.rewriter.impl.StaticReferenceRewriteTransformerFactory-UScom.projectNa...
386
Views
0
Likes
3
Answers and Comments
Re: Name field not appearing in Siteadmin adobefor - Adobe Experience Manager
Thanks, that resolved it ! After 2-3 restarts it was working fine. No idea why it was happening. But, it was so only in one particular environment.
106
Views
0
Likes
0
Answers
Name field not appearing in Siteadmin adobefor - Adobe Experience Manager
Hi, While we create a new page via the siteadmin, a dialog pops out with Title and Name text fields. But, for past few days, only the Title field is displayed and not the Name. There has not been any overlay of the siteadmin related JS. No changes in user permissions too. Confused if something was changed accidentally. So, I am unable to figure out what could have probably gone wrong. Any help is much appreciated. Thanks ! [img]Capture.PNG[/img]
124
Views
0
Likes
2
Answers and Comments
Re: Reporting in CQ adobefor - Adobe Experience Manager
Thanks Sham! It was exactly the reason. Along with compreport , there were many other reports under /etc/reports. I went ahead and checked them to find one of them missing jcr:content node. After deleting that report, I am able to see the edit bar in compreport now !
127
Views
0
Likes
0
Answers
Re: Reporting in CQ adobefor - Adobe Experience Manager
Thanks for the help ! Please do let me know their findings.
131
Views
0
Likes
0
Answers
Re: Reporting in CQ adobefor - Adobe Experience Manager
Sure[img]report-auth.PNG[/img]
129
Views
0
Likes
0
Answers
Re: Reporting in CQ adobefor - Adobe Experience Manager
Hi, i verified and I don't see any difference. The only issue I just noticed in a JS error that is occurring only in the non-working instance, Failed to load resource: the server responded with a status of 404 (Not Found) ............:4502/home/users/a/admin.permissions.json?I have provided all the permissions to the admin user through which I am logging in. Yet, it doesn't seem to work and keeps throwing this error. The error is not thrown in the working instance, Thanks.
128
Views
0
Likes
0
Answers
Re: Reporting in CQ adobefor - Adobe Experience Manager
Hi, thanks for the help. The issue is I am able to succesfully run the same report and view the details in the publish instance. When I require to edit the rootpaths etc., I need to edit the same in author instance, publish it so as to make it available in the publ instance to run with the new changes. Hence, I am wondering what is causing it not to display the edit bar in the author instance.
129
Views
0
Likes
0
Answers
Reporting in CQ adobefor - Adobe Experience Manager
The compreport is being used in our application. In my local, I can access it, view the report with all the generated details perfectly. Whereas when it is being accessed from higher environments such as dev and qa, it opens, sidekick is displayed, page layout is displayed, but nothing else happens. There is no sign of a process going on. I checked the permissions for the users and everything is enabled. There is no additional customization done to the component. Please let me know in case of an...
429
Views
0
Likes
12
Answers and Comments
Re: What is the difference between ReplicationActionType.DELETE and ReplicationActionType.DEACTIVATE? adobefor - Adobe Experience Manager
Hi, As I was browsing for an issue related to ReplicationActionType.DEACTIVATE that I am facing, I came across this post,. It would be great if you could see anything that would help me. I am trying to deactivate a page by replicator.replicate(currentSession, ReplicationActionType.DEACTIVATE , pathToDeactivate); This is deactivating the page whereas the node is not getting deleted in the publish instance. Not sure if i am missing anything.
159
Views
0
Likes
0
Answers
Re: Mapping adaptive image to different domain. adobefor - Adobe Experience Manager
Hi, when it comes to staticreferencerewriter, we have been using this in our project. Now, we are expanding to Multi site and hence I am not sure is it will work for different sites. I created different configs with different host patterns. But, it doesn't seem to be working and always ends up taking the last entry in the config. Please let me know how this can be extended for MSM. Thanks.
162
Views
0
Likes
0
Answers
Re: Deactivating a page by replication is not removing the node from publish instance adobefor - Adobe Experience Manager
Thanks for the reply. The property 'cq:lastReplicatedAction','cq:lastModified' etc get changed. The issue is the page is not getting removed from the publish instance.I will look into eventhandler as well.
138
Views
0
Likes
0
Answers
Deactivating a page by replication is not removing the node from publish instance adobefor - Adobe Experience Manager
Hi, I am trying to deactivate a page by the code replicator.replicate(currentSession, ReplicationActionType.DEACTIVATE , pathToDeactivate);.This is deactivating the page in author instance. Also, it invalidates the content in publish but the node doesn't go away from the instance. It is still seen, but, clicking on it takes to 404. I have tried various methods and yet this issue exists. Please let me know if I am missing anything here to delete the node from publ on deactivating.
220
Views
1
Like
3
Answers and Comments
Likes from