NitroHazeDev

Thanks Sumer and Kautak... appreciate the confirmation.I wonder if we could have it extracted perhaps somehow, maybe a workflow customization.Also curious,i uploaded a .mov and i do not find any metadata and yes, it is per the documentation . But why would we have metadata displayed without values and it cannot be editedi uploaded a .mp3 asset and it did not bring in the metadata either , but the documentation says it does .. please let me know

810

Re: Audio(.mp4) assets not extracting metadata - Adobe Experience Manager

Anyone please?

822

Audio(.mp4) assets not extracting metadata - Adobe Experience Manager

Hello,i found that when i imported an asset , .mp4, the audio bit rate, Audio codec etc, never got extracted and as a result is blank in the basic tab when you edit the properties, anyone knows if i could be missing a workflow perhaps?Please let me know

1.6K

Re: Oak indexing in aem 64 for dam:assetcontent - Adobe Experience Manager

So i did refer to it and created indices based on it but in vain . Then checked Oak Utilities : Index Definition Generator , validated and it looked right as well. I loved the generator url makes life easierBUT the main part that was incorrect was the "async" that was a misspell.. wonder if i was dozing but yeah , correcting the spelling helped.Thanks

1.0K

Re: Aem 6.4 Touch UI component droptarget does not retain thumbnail - Adobe Experience Manager

To anyone of interest , overlay the file upload js from libs and add a condition to check if the property contains a json , and pick thumbnail key value pair from the json property stored for the page node

1.1K

Oak indexing in aem 64 for dam:assetcontent - Adobe Experience Manager

I was trying to run a query with type - dam:AssetContent and on running it in query builder ui I get the result but I see an error in the error login traversing and that there is no index while I mocked up the dam:asset index under oak:index in aemproperty - metadata/cq:tags - throws no error while property - metadata/customprop - throws traversal error Custom prop is of type “long”query type- dam:AssetContentpath- /content/dam property - metadata/customprop property.value - 123could i be missin...

1.4K

Aem 6.4 Touch UI component droptarget does not retain thumbnail - Adobe Experience Manager

I was trying to use brightvove videos and i did customize the component to use it in touch uiI drag drop video from the content finder and put it in the drop target of the component which allows brightcove videos aloneon saving it the video renders on the page and plays, a json is stored at the content node for the video now the issue occurs when I click to edit the component again the thumbnail is missing and I see the message in the droptarget area that says something like it is trying to find...

1.3K

Re: AEM 6.4 unable to access content path via resourceresolver/session - Adobe Experience Manager

feike_visser: i would definitely want to keep that in mind.. nice to know.. thank you so very much

1.7K

Re: AEM 6.4 unable to access content path via resourceresolver/session - Adobe Experience Manager

I was surprised .. and i knew editing permissions for sling scripting giving permissions to code under apps is not the right way , thanks to people to pointed out against it....So apparently in 6.2 sling scripting user with certain privileges were used to access classes that extend wcmuspojo, i raised a ticket with daycare and they suggested this which helped me resolve the issue. This is the solution they provided and it worked for me

1.7K

Re: AEM 6.4 unable to access content path via resourceresolver/session - Adobe Experience Manager

Hi,I had to alter the code discussing with AdobeTry this:Class extending WCMUsepojo----------------GetResourceResolverService getService = getSlingScriptHelper().getService(GetResourceResolverService.class);if(getService ==null)return;resourceResolver= getService.getServiceResourceResolver("core-admin");// core-admin is the service name , //resourceResolverParams.put(ResourceResolverFactory.SUBSERVICE,"core-admin")Resource resource = resourceResolver.resolve(resourcePath);GetResourceResolverServ...

1.7K

Re: AEM 6.4 upgrade @reference does not work in a workflow - Adobe Experience Manager

So Scott, i finally have a response and after consultation and weeks of debugging assuming i was doing something wrong for something that is so simple, i am asked (by adobe) to avoid using @reference in abstract classes , and this worked on 6.2 and is something that breaks in 6.4, , with bunch of scr annotation errors and components appear to be in satisfied stateInfact abstract keyword for a service at times sets the component to state "16", solution - remove abstract keywordIf you have nested...

1.3K

Re: AEM 6.4 upgrade @reference does not work in a workflow - Adobe Experience Manager

Yes Scott, that helps, but with the keyword abstract there are issues , so looking into it

1.3K

Re: AEM 6.4 upgrade @reference does not work in a workflow - Adobe Experience Manager

Thanks Arun, i had that in my workflow, but missed adding it here ..so here are the updates:I got a custom workflow to work but the one i was trying didn't work and would not appear in the dropdown in the custom process stepreasons:1. Class that implements workflow process is marked abstractYet to investigate, ..This worked smooth on 6.2..

1.3K

Re: AEM Image Component with uploaded SVG - Adobe Experience Manager

Sure.. no problem at all

2.8K

Re: AEM 6.4 upgrade @reference does not work in a workflow - Adobe Experience Manager

Sure thanks i believe i used maven arch 13, but i am attaching the code herepackage com.test.core.workflows.general;public interface DemoWFService {public String showMessage(String msg);}------------------------------------package com.test.core.workflows.general;import org.slf4j.Logger;import org.slf4j.LoggerFactory;public class DemoWFServiceImpl implements DemoWFService {protected final Logger log = LoggerFactory.getLogger(this.getClass());String PrefixMessage = "Service Invoked by Workflow -- ...

1.3K

Re: AEM 6.4 upgrade @reference does not work in a workflow - Adobe Experience Manager

Will be logging a ticket with Adobe,Created classes as you've shared and weird issues were noted1. With @reference annotation, custom workflow process (java)step did not appear in the dropdown for the workflow2.Without @Reference annotation, the process step java class was visible.

1.3K

Re: AEM Image Component with uploaded SVG - Adobe Experience Manager

So i logged a day care ticket(#152132) and Adobe mentioned its a bug/known issue, SLING-7525 missing content-headers, they mentioned the response header is missing Content-Type,Binary Provider Overlay servlet as workaround was suggested but it didn't help.So suggestions provided by adobe:- Upload PNG and reference PNG- Modify code to work on similar to Image compoenntI preferred using using rendition of svg

2.8K

Re: AEM Image Component with uploaded SVG - Adobe Experience Manager

It looks like a bug in 6.4 , here are the suggestions i have received from adobe,since 6.4 rendered svg assets with OOTB image component(drag drop image to the component), mockup your component to do what image component does, or use png, i used the png/jpeg from the renditions folder

2.8K

Re: AEM 6.4 upgrade @reference does not work in a workflow - Adobe Experience Manager

I also tried @Reference ResourceResolverFactory rrf; and it appears to be null as well, so curious if @reference throws null for some unknown reason>

1.3K

Re: AEM 6.4 upgrade @reference does not work in a workflow - Adobe Experience Manager

I used the OSGI, yes i see the service as well. Sent the code over, its a custom service and not OOTB so i am not sure if that affects anything.I took off the @Reference annotation and just instantiated the class and it worked fine. i wonder why the annotation would not work within a workflow.I do see errors as well, could this be related?[com.adobe.granite.workflow.core.job.ExternalProcessPollingHandler(917)] : Could not get service from ref [com.adobe.granite.workflow.exec.WorkflowProcess]15.0...

1.3K

Re: AEM 6.4 upgrade @reference does not work in a workflow - Adobe Experience Manager

Anyone?

1.3K

AEM 6.4 upgrade @reference does not work in a workflow - Adobe Experience Manager

All i have a workflow process step and it references class A that exposes a service, but when i check for the value of A in the process step, it appears to be null,i am injecting this service A using the @Reference.

5.0K

Re: AEM 6.4 unable to see the custom workflow process in the dropdown - Adobe Experience Manager

Thanks really appreciate it

957

Re: AEM 6.4 unable to see the custom workflow process in the dropdown - Adobe Experience Manager

So even if my class extends another class should i just add WorkflowProcess.class or should i add the class name that it extends

911

Re: AEM 6.4 unable to see the custom workflow process in the dropdown - Adobe Experience Manager

Anyone please?

900

AEM 6.4 unable to see the custom workflow process in the dropdown - Adobe Experience Manager

Hey Guys,After refactoring code to 6.4 i am not able to see the custom process in the dropdown for the custom process step for the workflowAm i missing something?Refactored the annotations alone@Component(immediate = false, property={ Constants.SERVICE_DESCRIPTION + "=Description.", Constants.SERVICE_VENDOR + "=vendor", "process.label" + "=Label"})

2.1K

Re: Issue- AEM 6.4 Configurations not picking values from runmode config - Adobe Experience Manager

Thanks Arun, followed above steps and have it working now., Appreciate it

1.2K

Re: Issue- AEM 6.4 Configurations not picking values from runmode config - Adobe Experience Manager

so i figured out the issue, i see that the name being stored by the prev developers was com..test.core.abc.appid. How do i set this to a configuration in 6.4? I don't believe we could have a string with period as the name ?

1.3K

Re: Issue- AEM 6.4 Configurations not picking values from runmode config - Adobe Experience Manager

ok so now i change values in felix console and it reflects on the config.local config but i dont see the values from the config under config.local in felix console, is there an issue with the code?

1.2K