ronnyfm

Adobe Experience Manager

Adobe Campaign Classic

Adobe Campaign Standard

Adobe Experience Platform

Adobe Analytics

Adobe Audience Manager

Adobe Target

Adobe Experience Cloud

Adobe I/O Cloud Extensibility

Adobe Advertising Cloud

Marketo

Magento

Adobe Creative Cloud

Adobe Document Cloud

Workfront, an Adobe company

since

‎10-12-2019

Level 3

Re: AEM 6.5 issue - Adobe Experience Manager

I agree, but even using the dependecy returned by depfinder, cq-dam-commons 5.12.54 com.day.cq.dam providedI am getting the same exception.

1.4K

Re: targetingconfig.json issue - Adobe Experience Manager

Not solved in fact. After a restart, the issue comes back. Reproducible at least from 6.4.3 up to 6.5. I am suspecting that I am missing something in the templates, but not sure what yet.

6.2K

Re: targetingconfig.json issue - Adobe Experience Manager

Thanks, I solved by installing 6.4.4 service pack. Still not sure what in the nosamplecontent caused the issue.

6.2K

Re: targetingconfig.json issue - Adobe Experience Manager

Update: Issue happens using the nosamplecontent, that is the difference between the instances. I am going to setup a nosamplecontent locally to debug further.

6.2K

Re: targetingconfig.json issue - Adobe Experience Manager

Thanks, but we are not using the built-in Target functionality.

6.2K

Re: targetingconfig.json issue - Adobe Experience Manager

Additional info:AEM 6.4.3The page uses an Editable Template. I have also the same policies applied on both environments.

6.2K

targetingconfig.json issue - Adobe Experience Manager

Hi,Does anyone know what paths are affected when requesting http:///content/mysite.targetingconfig.json URL?I have the same content and code locally and on my development server? However in the dev server I get this exception:"Unable to load targeting config for page {}".The message comes from /libs/cq/gui/components/authoring/editors/clientlibs/sites/page.js$.get(Granite.HTTP.externalize(pagePropsUrl)) .done(function(data){ self.forceLocation = data["forceLocation"]; self.pageAmbits = data["amb...

6.5K

AEM 6.4 /api/screens-dcc/devices/stati WARNING - Adobe Experience Manager

28.02.2019 12:46:00.026 *WARN* [127.0.0.1 [1551375960022] GET /api/screens-dcc/devices/stati HTTP/1.1] com.adobe.granite.rest.impl.ResourceAdapterFactory Unable to handle adaptable com.adobe.cq.screens.impl.rest.DevicesStatiResourceHi, does someone know how to get rid of this message?

11.3K

Re: Allow URLs without extension to bypass the dispatcher - Adobe Experience Manager

For example:/test -> it doesn't work/test.html -> it does workApache 2.2.15 and Dispatcher version is 4.2.2

1.1K

Allow URLs without extension to bypass the dispatcher - Adobe Experience Manager

Hi,We have redirects with Sling Mappings, but some of them are redirects without extension. Therefore the dispatcher is blocking these requests.What are recommended ways to fix this?Vanities are working fine, since I am using the vanitiy_url section. And redirects with extension as well, the extensionless and with trailing slash are the problem.Thanks.

1.2K

Re: AEM 6.2 to 6.4 upgrade : Issue with iparsys - Adobe Experience Manager

Reviewing, we are having CSS issues with some components, the dialog is in the DOM but with CSS rules that prevent it to be displayed:element { position: absolute; z-index: 11000; visibility: visible; left: -10000px; top: 20px; width: 800px; }I am still researching why some of them have such rules applied.

6.0K

Re: AEM 6.2 to 6.4 upgrade : Issue with iparsys - Adobe Experience Manager

Sure Scott, but the first phase is the upgrade step, before then moving to the latest features.I am aware that Classic UI is deprecated, but we need to ensure that we can perform the upgrade without affecting current site, or at least to know that by fixing a couple of configurations or lines of code will suffice to get the iparsys working fine.

6.0K

Re: AEM 6.2 to 6.4 upgrade : Issue with iparsys - Adobe Experience Manager

Hi, we are facing something similar, did this happen to you using either 6.4.0, 6.4.1 and 6.4.2? Does this happen also using Classic UI?

6.0K

Re: Dispatcher: Apache unable to start. - Adobe Experience Manager

Yeah, I sometimes forget to document all differences when selinux appears to be an issue, but I was with the latest dispatcher version, latest Apache 2.4.6 and latest RHEL. After solving this issue, I also had to fix permissions for the docroot, though I applied the commands found in the Installation guide. I solved by following the solution found here: centos7 - CentOs 7 & SELInux: User cant write in the Webroot of Apache - Server Fault

1.6K

Re: Dispatcher: Apache unable to start. - Adobe Experience Manager

Thanks. I was able to solve it running the following command:sudo chcon -t httpd_sys_script_exec_t /etc/httpd/modules/mod_dispatcher.so

1.6K

Dispatcher: Apache unable to start. - Adobe Experience Manager

Hello, I am facing a weird issue installing a dispatcher for an author instance. The configuration for the author is based in a previous installation that I know it works fine. Now back to this project, the dispatchers for the publish instances are working fine. They do have the same httpd version, same RHEL version, same dispatcher module (I even copied the same .so from the working dispatchers). But Apache is unable to start and I do not have many useful info, since Apache doesn't write to the...

5.1K

Responsive grid inside a responsive grid - Adobe Experience Manager

Hello, is it possible to have a responsive grid component inside another? The goal is to have, for example, an image component with "Drag components here" over the image that allow to put add a text, button or any other component for further customization.AEM version 6.3, responsive layout enabled. Looking at we retail, I note that the hero image and similar components offer the possibility to add a title and other options but in a single dialog.

1.5K

Re: Not able to login in AEM Publish instance - Adobe Experience Manager

Another reason that could cause this issue is if there is a reindexing process running, such like the one suggested here: Performance tuning tips | 6.x that does affect /oak:index/nodetype. Running this will prevent pretty much any other operation in the publish instance, though it will be able to render content.

8.1K

Re: Including com.fasterxml.jackson dependency - Causing errors - Adobe Experience Manager

Hi,Did you try the export bundle as I suggest in a previous post?

3.8K

Re: Including com.fasterxml.jackson dependency - Causing errors - Adobe Experience Manager

What the error.log say when the bundle stops? If all dependencies are resolved, there could be another reason for the bundle error.

3.8K

Re: Importing the SocialUtils using @Reference annotation causing servlet status is unsatisfied - Adobe Experience Manager

Did you solve this issue?

752

Re: Not able to login in AEM Publish instance - Adobe Experience Manager

How did you solve the issue?

8.1K

Re: Multidomain and dispatcher invalidation issue - Adobe Experience Manager

Thank you! Apache rules did the trick.

1.1K

Multidomain and dispatcher invalidation issue - Adobe Experience Manager

This is the issue.I have followed the guide in the official documentation. Additionally, I created a virtual host for invalidation_only though that was not explicitly in the docs, but I found that as a recommendation in this forum.What is happening is:I have /content/sitea and /content/siteb.I send the invalidation request for /content/siteb but in the dispatcher logs what I see is:Touched /var/www/html/content/sitea/.statIf I request /content/siteb/test.html, I get the test.html correctly and t...

1.5K

Re: Disable Discovery Service - Adobe Experience Manager

Well, that didn't solve the issue. The only workaround was to increase timeouts in the configuration.

1.2K

Re: Disable Discovery Service - Adobe Experience Manager

Second screenshot

1.1K

Re: Disable Discovery Service - Adobe Experience Manager

Screenshot.

1.1K

Disable Discovery Service - Adobe Experience Manager

I am facing this WARN message that slows down the instance. For some reason the cluster change event keeps updating and changing. Is there a way to disable this service or configuration for a single instance that is not in a cluster? Already tried removing the default localhost topology URL.org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler checkForLocalClusterViewChange/.run: time since local instance last wrote a heartbeat is 669667ms (heartbeatTimeoutMillis=300000, heartbeatInt...

2.7K

Re: Unable to start AEM - equestLogin=1 10.05.2017 10:43:46.521 *ERROR* [pool-6-thread-1] org.apache.sling.commons.scheduler.impl.QuartzScheduler No discovery avail - Adobe Experience Manager

¿Do you mean running a command via oak-run-*.jar? Do you have a sample command for that? Thanks.

1.1K

Re: Unable to start AEM - equestLogin=1 10.05.2017 10:43:46.521 *ERROR* [pool-6-thread-1] org.apache.sling.commons.scheduler.impl.QuartzScheduler No discovery avail - Adobe Experience Manager

Any sucess? Facing same error since a couple of days ago. Not sure what happened. I already tried by deleting /repository/index. No luck, same result. The instance, eventually starts up, but after some time it is unresponsive.

1.1K

Likes given to

User

Count

Likes from

User

Count

Guidelines

Cookie preferences