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
swaroop srinivasan
@ssriniv2
I have a customer on AEM 6.4.3 and they are using ACS commons Report Builder bundle. They say they are using a user assigned to the administrator group, but they are not able to see the 'Edit' button when viewing list of reports
As shown in image below
image.png
Is this a known issue, or is there a way where we can set the permission on this
bhaveshkaloni
@bhaveshkaloni
We are upgrading AEM from 6.3 to 6.5..multifields are not saving the values in repository.
we are using granite fields in multifields with latest acs-aem-commons package
bhaveshkaloni
@bhaveshkaloni
@davidjgonzalez please help on above query
Brendan Robert
@badvision
Multifield is an AEM feature, not an ACS Commons one, at least in the sense that we've deprecated the multifield widget in ACS Commons in favor of the product version.
e.g. have you tried the GraniteUI multifield instead?
Brendan Robert
@badvision
@MatWrz , @boswellt -- AFAIK you can still include ACS Commons in your packages. Nothing in the package manager has changed in AEM for a very long time. However, there are some pros and cons to consider when deploying ACS Commons as part of your code package. If you're doing a lot of development it can be a tad disruptive to have all the OSGi services in ACS Commons (and anything depending on them) restarting during deployment, etc. Not to mention if you have multiple packages/bundles for your project then you might want to deploy ACS Commons separately as well to decouple things. Packaging the ACS Commons bundle in your project makes small projects easier to install in new environments since you only deploy one package and you're done. However, over time that might not be necessarily useful in the long run. It's really up to you to decide which works best for your project, etc.
swaroop srinivasan
@ssriniv2

Hi,

I am an AEM support consultant and I am working on an issue raised by WYNDHAM WORLDWIDE OPERATIONS, INC.

They are trying to publish some property-overview pages to Preview environment by using Bulk Workflow Manager, but they are not getting the updated content on Preview environment and also would like to see whether the content structure is created on Preview publisher environment or not.

Can you please let me know how they can get this issue addressed by the ACS team?

Siddhartha
@siddama_gitlab
Which version of ACS_AEM_COMMONS is best compatible and bug-free for AEM 6.4
Sathish Balan
@sathish-git
Hey guys, I've found an issue with the dtm implementations even in the latest version of acs commons, i know a fix and i know dtm is no longer supported but i believe there are still some customers like us for example still using DTM. Thoughts?
niksvers
@niksvers

Hey guys,

Query:
I'm new to using ACS Commons in a project and was wondering if there's way I can restrict/filter what I want to install from ACS Commons.

Example:
For example, I want to install the OSGi bundle & certain resources under '/var/acs-commons/reports', but not other resources such as : '/apps/cq/core/content/nav/tools/acs-commons'. Is there a way to do this?

Background:
I'm installing ACS Commons via maven as a subpackage. I think the best would be if such filters could be added under the maven POM tag where one can specify what to path(s) to install from the subpackage. Kind of like a way to override the filters specified in the ACS Commons package itself.

Sathish Balan
@sathish-git
Hi @niksvers , I think the best way to do what you want to do is to build the ACS Commons packages by yourself (Have to be careful with this) after modifying the filters. With that said, why would you want to do this? I'd always recommend installing the whole thing even if you don't want to use some of the features.
Rosario Hettiarachchige
@Ros95_gitlab

Hi all,
I migrated the project I'm working on from version 6.2 to version 6.5 of AEM. So I installed the the acs commons v. 4.3.2, previously v. 3.6.2.
Unfortunately, I found a bug in saving and showing the data of the multifield fields of type acs-commons-nested = "JSON_STORE" in page properties.
Do you also find bugs in this regard? In case what you did to solve them?

Thank you,
Rosario

niksvers
@niksvers

@sathish-git Hello Sathish, apologies for my late response.

There are certain things installed with ACs Commons package that effects the UI, for example : '/apps/cq/core/content/nav/tools/acs-commons'. This adds new options for authors/admins who don't need to have access to such options(in the current project at least).

I guess for this specific scenario I could remove read rights for the user groups that shouldn't be able access the mentioned options, but there could be more things like this that gets installed with ACS Commons that I might not be aware of.

Yeah, modifying filters & building ACS Commons separately does seem like a 'hacky' way, probably better to not go that way. :)

sindhugondela
@sindhugondela
Hi All,
we are implementing AEM Assets and doing a huge migration of assets upto 15TB. we used s3 ingestor to add assets from an s3 bucket to AEM which was successful. the next step was to use "bulk workflow manager" in ACS-COMMONS to trigger DAM UPDATE ASSET workflow. for testing, i just started the process for only 5 assets and when i checked my workflow instances, it keeps repeating the same asset infinitely. i deleted more than 300 instances of this same asset. is there a way to completely stop this job. i tried stopping it from bulk workflow manager page. but nothing helped. please let me know if there's a way to stop the bulk workflow manager job.
Sathish Balan
@sathish-git
Hi @sindhugondela I’m guessing this loop is happening probably because of an existing workflow launcher. Can you check and tell whether your launcher for Asset modification is turned on or off?
sindhugondela
@sindhugondela
its turned on
i've read few posts in ACS issues that bulk workflow manager will not work with external process like scene 7 upload in DAM UPDATE ASSET Workflow.
is that true?
what is the workaround for bulk assets in that case?
Sathish Balan
@sathish-git
Well you don't really have a choice with respect to running the workflows on all the assets you have but I think you can try to atleast stop the repeats of workflow instances on the same payload.
If there is any launcher that is currently active for assets in the same path where you are trying to upload assets, turn it off and see if the looping stops?
Sathish Balan
@sathish-git
And yes, bulk workflow manager does not work with external processes
sindhugondela
@sindhugondela
@sathish-git thanks for your quick response. may i ask if there's any workaround to run workflows on batches of 10gb or something.
we have our assets ingested into AEM. but we turned off workflow launchers at that time to avoid issues with ingestion.
Sathish Balan
@sathish-git
So despite having no launchers active, the workflows are repeating on the same payload?
sindhugondela
@sindhugondela
i meant. launchers were turned off during ingestion of assets. and then they were turned on before the bulk workflow manager process started.
Sathish Balan
@sathish-git
Yes, so I'm thinking the looping was/is happening due to them being turned back on when you ran the bulk wf manager since the dam update workflow launchers get triggered on node modifications.
I can't think of a better way than using very specific wf launchers or bulk wf manager to trigger workflows on huge assets. If you have all the assets in specific folders, you can may be trigger workflows manually folder by folder if you want to do this in batches. Or may be come up with a python script to trigger wfs via curl commands..
sindhugondela
@sindhugondela
@sathish-git thank you.
Sathish Balan
@sathish-git
@sindhugondela welcome!
Ronald Diemicke
@RonaldDiemicke_twitter
Hey folks
Can anyone validate this issue? Adobe-Consulting-Services/acs-aem-commons#2046
That's at least part of the issue
sindhugondela
@sindhugondela
@sathish-git quick question? bulk workflow manager will not work with smart tags too?
Sathish Balan
@sathish-git
@sindhugondela I've not really tried it but I can't think of any reason why it shouldn't.
Sathish Balan
@sathish-git
@JowlsPC_twitter Hi, it looks like the your replication bundle version isn't what your ACS bundle is looking for. Can you check the version of the replication API bundle?
Search for "com.day.cq.cq-replication" in the bundles console
Christian Guerrero
@JowlsPC_twitter
I am seeing 6.2.46.CQ640-B0008
however I also see "Exported Packages com.day.cq.replication,version=6.5.0"
Sathish Balan
@sathish-git
Weird! I'm on AEM 6.5 which has replication 6.2.86 and ACS 4.3.2 works fine.
What's the version number of the ACS bundle you see in console?
Christian Guerrero
@JowlsPC_twitter
4.3.2
Sathish Balan
@sathish-git
How did you install it by the way?
Christian Guerrero
@JowlsPC_twitter
via package manager
Sathish Balan
@sathish-git
Well if you had installed it via package manager, I don't think we'd see this as the package name - gsmc-aem-commons-bundle, it usually will be com.adobe.acs.acs-aem-commons-bundle
Sathish Balan
@sathish-git
ACS 4.3.2 looks actually expects replication API version between 6.4 and 7. Your error says that the ACS bundle you have installed is looking for anything greater than or equal to 5.17.0 but not greater than 6.0.0