Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 31 2019 21:04
    joerghoh commented #1732
  • Jan 31 2019 21:02
    joerghoh commented #1732
  • Jan 31 2019 19:40
  • Jan 31 2019 01:58
    badvision review_requested #1738
  • Jan 31 2019 01:58
    update-changelog[bot] commented #1738
  • Jan 31 2019 01:58
    badvision opened #1738
  • Jan 31 2019 01:54

    badvision on Renovator_bugfixes

    #1737 - Added additional asset … (compare)

  • Jan 31 2019 01:43
    badvision opened #1737
  • Jan 30 2019 15:26
    kwin opened #1736
  • Jan 30 2019 15:14
    kwin synchronize #1735
  • Jan 30 2019 15:10
    update-changelog[bot] commented #1735
  • Jan 30 2019 15:10
    kwin opened #1735
  • Jan 30 2019 14:00
    kwin edited #1733
  • Jan 30 2019 12:48
    mauryamanoj opened #1734
  • Jan 30 2019 12:31
    kwin opened #1733
  • Jan 30 2019 00:35
    davidjgonzalez commented #1715
  • Jan 29 2019 23:56
    badvision commented #1715
  • Jan 29 2019 21:55
    badvision milestoned #1732
  • Jan 29 2019 21:55
    badvision labeled #1732
  • Jan 29 2019 21:55
    badvision labeled #1732
Wim Symons
@wimsymons
@DanaAnthony Take a look at https://adobe-consulting-services.github.io/acs-aem-commons/features/versioned-clientlibs/index.html MD5 Enforcement. It will return 404 if the client lib has been changed on another publish instance. Clients having cached the resource won’t see this during deploy. New clients will fail on those resources during deploys. Refreshing the page would render them the correct resource (after deploy is finished). Not 100% foolproof but it does the job. Other option could be to make your load balancer sticky. That way html and css/js will come from the same publish instance.
DanaAnthony
@DanaAnthony
Neither of those really works for me, @wimsymons - we did at one time have sticky load balancers and moved away from it, and the MD5 enforcement is a reasonable idea except the 404 seems like it would be too site breaking when it occurred.
DanaAnthony
@DanaAnthony
we're working on blue/green setup and I think once that's in place this problem will be moot, but in the interim I was hoping for a simple operations thing we can do to 'fix' / update the number being used as the sling selector that's basically ignored anyway but just serves to make browsers/CDN update their cached files
Sridhar Reddy
@sridredd

When we were using ACS Commons 3.9 version, after applying Named Transform Image Servlet , quality of the image was reduced when compared it with the original image.

After updating ACS Commons to 3.17, on applying named transform image servlet Quality(Sharpness) of the image is same as that of the original image for NEWLY UPLOADED IMAGES,

Issue is with the already existing images, on applying named transformed servlet, quality(sharpness) is reduced i,e quality of the already existing images is not maintained after updating it to the later version.

We tried to re-run the DAM asset workflow for the already existing images, but quality was not maintained on applying named images transform servlet

Sridhar Reddy
@sridredd
Hi @cmrockwell, we cleared dispatcher cache and checked it, but no luck. we have updated ACS commons latest version, and on applying the image transform servlet, quality is not same as original image. but if i download the same image from DAM and upload it again and on applying image transform servlet sharpness is maintained.
DanaAnthony
@DanaAnthony
Is there a recommended approach for updating from using Dynamic RTE Configuration (deprecated) classic dialogs to touch ui dialogs?
Rajashekar Donthi
@rajashekar63
Hi All when i am trying to run first time "mvn -PautoInstallPackage clean install" getting error like
The project com.adobe.acs:acs-aem-commons-content:3.17.1-SNAPSHOT (/Users/raj/Documents/acs-aem-commons/content/pom.xml) has 2 errors [ERROR] Unresolveable build extension: Plugin com.day.jcr.vault:content-package-maven-plugin:0.0.24 or one of its dependencies could not be resolved: Failed to read artifact descriptor for com.day.jcr.vault:content-package-maven-plugin:jar:0.0.24: Could not transfer artifact com.day.jcr.vault:content-package-maven-plugin:pom:0.0.24 from/to adobe-public-releases (https://repo.adobe.com/nexus/content/groups/public/): Connect to repo.adobe.com:443 [repo.adobe.com/192.147.130.162] failed: Connection refused (Connection refused) -> [Help 2] [ERROR] Unknown packaging: content-package @ com.adobe.acs:acs-aem-commons-content:[unknown-version], /Users/raj/Documents/acs-aem-commons/content/pom.xml, line 19, column 16
Can anyone help me please.
ankurvashisht
@ankurvashisht

Hi All,

I am facing issue with ACS Commons Bulk Work flow manager (https://adobe-consulting-services.github.io/acs-aem-commons/features/bulk-workflow-manager/index.html).

When I am running DAM Update Asset workflow using ACS commons bulk workflow manager. And, facing below error[1] from Scene7 step. Everything is working fine if I run the DAM Update Asset workflow on individual asset without ACS commons bulk workflow manager.

I have made "acs-commons-bulk-workflow-service" user a member of administrator group.

Can someone please help.

[1]com.adobe.granite.workflow.WorkflowException: Dynamic Media asset upload failed. Please contact your system administrator./content/dam/aaa.psd
at com.day.cq.workflow.compatibility.CQWorkflowExtProcessProxy.execute(CQWorkflowExtProcessProxy.java:68)
at com.adobe.granite.workflow.core.util.WEPProxyHolder.execute(WEPProxyHolder.java:42)
at com.adobe.granite.workflow.core.job.JobHandler.process(JobHandler.java:272)
at org.apache.sling.event.impl.jobs.JobConsumerManager$JobConsumerWrapper.process(JobConsumerManager.java:500)
at org.apache.sling.event.impl.jobs.queues.JobQueueImpl.startJob(JobQueueImpl.java:291)
at org.apache.sling.event.impl.jobs.queues.JobQueueImpl.access$100(JobQueueImpl.java:58)
at org.apache.sling.event.impl.jobs.queues.JobQueueImpl$1.run(JobQueueImpl.java:227)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.Exception: java.lang.Exception: Upload failed, unable to find Scene7 job handle
at com.day.cq.dam.scene7.internal.impl.Scene7InternalUploadServiceImpl.uploadPost(Scene7InternalUploadServiceImpl.java:478)
at com.day.cq.dam.scene7.impl.process.Scene7UploadProcess.upload(Scene7UploadProcess.java:524)
at com.day.cq.dam.scene7.impl.process.Scene7UploadProcess.execute(Scene7UploadProcess.java:324)
at com.day.cq.workflow.compatibility.CQWorkflowExtProcessProxy.execute(CQWorkflowExtProcessProxy.java:66)
... 9 common frames omitted

Luc Rochefort
@Lrochefort
Hi there!
Do anyone knows when the next version of ACS Commons will be released?
3.17.0 was released in May, and I'm eagerly awaiting for a fix (1301) on the Tag Creator.
Jake Tracey
@jaketracey_gitlab
Hi all!
I'm trying to get the twitter component working and it won't seem to refresh a feed
Gary
@GL369
Hi (me again)...trying to use the Data Importer (ACS 3.16.0) to add dc:title to a small sample (60 assets). The objective is to add the current filename to the dc:title field so the business can sort in AEM UI. Currently dc:title is blank for all the assets. I am using the xlsx format with just path & dc:title for the 60 files and getting the following error: 2018-08-07 23:31:35 Value for key dc:title can't be put into node: 8UKM248U976999_3.psd java.lang.IllegalArgumentException: Value for key dc:title can't be put into node: 8UKM248U976999_3.psd at org.apache.sling.jcr.resource.internal.JcrModifiableValueMap.put(JcrModifiableValueMap.java:458) at org.apache.sling.jcr.resource.internal.JcrModifiableValueMap.put(JcrModifiableValueMap.java:47) at com.adobe.acs.commons.mcp.impl.processes.DataImporter.populateMetadataFromRow(DataImporter.java:269) at com.adobe.acs.commons.mcp.impl.processes.DataImporter.updateMetadata(DataImporter.java:243) at com.adobe.acs.commons.mcp.impl.processes.DataImporter.lambda$null$1(DataImporter.java:201) at com.adobe.acs.commons.fam.impl.ActionManagerImpl.withResolver(ActionManagerImpl.java:204) at com.adobe.acs.commons.fam.impl.ActionManagerImpl.runActionAndLogErrors(ActionManagerImpl.java:166) at com.adobe.acs.commons.fam.impl.ActionManagerImpl.lambda$deferredWithResolver$0(ActionManagerImpl.java:158) at com.adobe.acs.commons.fam.impl.TimedRunnable.run(TimedRunnable.java:84) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: javax.jcr.nodetype.ConstraintViolationException: No matching property definition: dc:title = 8UKM248U976999_3.psd at org.apache.jackrabbit.oak.jcr.delegate.NodeDelegate.setProperty(NodeDelegate.java:522) at org.apache.jackrabbit.oak.jcr.session.NodeImpl$35.perform(NodeImpl.java:1377) at org.apache.jackrabbit.oak.jcr.session.NodeImpl$35.perform(NodeImpl.java:1364) at org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:208) at org.apache.jackrabbit.oak.jcr.session.ItemImpl.perform(ItemImpl.java:112) at org.apache.jackrabbit.oak.jcr.session.NodeImpl.internalSetProperty(NodeImpl.java:1364) at org.apache.jackrabbit.oak.jcr.session.NodeImpl.setProperty(NodeImpl.java:352) at org.apache.sling.jcr.resource.internal.JcrModifiableValueMap.put(JcrModifiableValueMap.java:455) ... 13 more
Luc Rochefort
@Lrochefort
@davidjgonzalez Hi! Do you guys have any plans for the next release? When can we expect to get it?
david g.
@davidjgonzalez
@Lrochefort will cut it today - have to run some errands, but there is a one last PR want to have someone look at to see if we can get it in
@GL369 i susepct that its the always annoying issue with dc:title (and dc:description) where the property type isnt matching up .... depending on how that property is created in AEM, it might be a String or String[] ... my guess is your XLSX has it set to String but the property type in the JCR is String[] ... so it can't figure out how to write that value in... you could try updating your XLSX to match the property type in the JCR and that should would (though im not 100% sure how Data Importer handles "corner" cases like this)
david g.
@davidjgonzalez
@Lrochefort 3.17.2 is released.. should be on repo.adobe.com tomorrow or the day after (depending on when that team promotes it)
sorry for the wait :(
Evan Roper
@roperev_twitter
This may not be the correct place to ask, but I'm getting the following error message when trying to install acs-commons 3.17.2 on AEM 6.3.1.2:
Could not Install Package
"javax.jcr.nodetype.ConstraintViolationException: OakConstraint0001: /home/users/system/acs-commons[[rep:AuthorizableFolder]]: No matching definition found for child node remote-assets-service with effective type [nt:folder]"
I tried creating the named folder in crxde, however received another 409 (Conflict) error (same error message)
Ronald Diemicke
@RonaldDiemicke_twitter
Hey folks - not sure if anyone is around, but I'm trying to get the client libs versioning up and running but running into some issues where I'm following the documentation on the site, but it doesn't work - wondering if anyone has some pointers, suggestions or a better tutorial on how to get this to work.
Luc Rochefort
@Lrochefort
@davidjgonzalez thanks a lot!
Luc Rochefort
@Lrochefort
@roperev_twitter I'm getting the same error on 6.2

Could not Install Package

"javax.jcr.nodetype.ConstraintViolationException: OakConstraint0001: /home/users/system/acs-commons[[rep:AuthorizableFolder]]: No matching definition found for child node remote-assets-service with effective type [nt:folder]"

I tried both acs-aem-commons-content-3.17.2.zip
and acs-aem-commons-content-3.17.2-min.zip
@davidjgonzalez can you install on 6.4?
Gary
@GL369
Hi - what's the difference between the two zips? min and no-min? And is it recommend to uninstall previous versions? I am on 6.4 - 3.16.0?
Justin Edelson
@justinedelson
@Lrochefort it looks like something is awry with 3.17.2. @davidjgonzalez will probably have to respin
you don't need to uninstall previous versions
@RonaldDiemicke_twitter you should probably create a GitHub issue describing what you are doing, what you expect to be happening, and what isn't happenin
Luc Rochefort
@Lrochefort
@justinedelson any news on this?
I know that version 3.17.1-SNAPSHOT was installing properly
Justin Edelson
@justinedelson
@Lrochefort 3.17.4 is now up on GitHub. David is working on getting it promoted to repo.adobe.com
david g.
@davidjgonzalez
Thanks @justinedelson should be all set on GH/Bintray — hope it hits repo.adobe.com tomorrow
sathishkumar
@sathishtb_twitter
How to activate syslog appender? After configuring host and port in SyslogAppender in OSGi, syslog will be activated automatically?
sindhugondela
@sindhugondela
Hi. i'm not sure if this is the right place to ask this. but when i ran the pattern detector on my 6.3 project, it showed too many acs-commons issues. example: "2018-07-31T17:28:20.755Z [SUSPICION] The pattern=ECU/extraneous.content.usage was found by detector=ContentAccessDetector with id=ba0d1fb144f0aad47d8391b0e95dfc9056ba7d85dd4553da04ec4d06163ec070 message="Cross-boundary override of internal marked path /libs/granite/ui/components/foundation/form/field referenced at /apps/acs-commons/components/authoring/search-pathbrowser". More info at=https://www.adobe.com/go/aem6_ECU". should i just ignore them while we upgrade from 6.3 to 6.4. NOTE: i have latest version installed (ACS AEM Commons 3.17.4)
Justin Edelson
@justinedelson
@sindhugondela there are some bugs in the current pattern detector version which produce these false positives. you should contact DayCare for information on an update to the pattern detector
sindhugondela
@sindhugondela
@justinedelson Thank You!
Justin Edelson
@justinedelson
there was a legitimate problem reported by PD fixed in 3.17.2 - Adobe-Consulting-Services/acs-aem-commons#1420
(not super-relevant for your question since you have 3.17.4 installed, but more of an FYI)
ajaykpaul
@ajaykpaul
Dear All, not sure if this is the right forum to ask it but Adobe AEM ships with 1.4 version of com.day.commons.osgi.wrapper.fop
which is a derivative of original apache FOP. However, how Apache has upgraded this jar file to 2.3 version with bug fixes.
could this be added with ACS commons ?
Justin Edelson
@justinedelson
probably not... that's really something which should be done in AEM proper
Eshan Kumar
@EshanKumar
I have been facing issues in building project because Adobe's maven repo is giving 502 response to download requests of acs-aem-commons-bundle-3.17.0, anybody facing similar issue since last few hours?
Justin Edelson
@justinedelson
@EshanKumar I think that issue is fixed now. if you are still seeing it, please report it to Daycare