joe_s66

Re: Adding a replicant in the metadata schema - Adobe Experience Manager 13-12-2021

OK - here's the code that works:

201

Re: Creating a custom widget in metadata schema - Adobe Experience Manager 10-12-2021

Hi - I'm working on the same issue. Did you ever get your code to work? thanks.

122

Re: Adding a replicant in the metadata schema - Adobe Experience Manager 10-12-2021

Is it possible to wrap all the components into a "multifield" component that can be repeated? I see this info in the Granite UI documentation: /libs/granite/ui/components/coral/foundation/form/multifieldMultifield component allows to add/reorder/remove multiple instances of a field. In the simplest case this is a simple form input field (e.g. textfield, textarea) but it can also be a complex component acting as an aggregate of multiple subcomponents (e.g. address entry).

213

Re: Adding a replicant in the metadata schema - Adobe Experience Manager 08-12-2021

Thanks - I looked at the documentation but don't see any explanation on how to duplicate several fields into a new section using an "add section" button. Also I'm working directly in the XML code, not in the Metadata Schema Form template.

224

Adding a replicant in the metadata schema - Adobe Experience Manager 08-12-2021

I'm updating a metadata schema and need to add an "add language" button so content authors can add additional copies of the section. Can anyone please share an example to make this happen? Thanks.

236

How to sync deleted AEM Content - Adobe Experience Manager 23-11-2021

We use VLT-RCP to sync content in the DAM across various AEM author environments. This process will sync the various paths from the source system. Once synced, the latest content is then replicated to the publish instances. However we noticed that deleted content is not synced across the different AEM authors. Is there any way to sync deleted or expired content between AEM author environments?

151

Re: Issue with Adobe Experience Manager integration with PDF Embed API - Adobe Experience Manager 26-10-2021

It looks like we need to whitelist the following 4 URI patterns in Forcepoint to resolve the issue. (there are other javascript files besides main.js that the component is dependent on) https://documentcloud.adobe.com/dc-core/https://documentcloud.adobe.com/dc-rendition-provider/https://documentcloud.adobe.com/dcpreviewdropin/https://documentcloud.adobe.com/view-sdk/

281

Re: Issue with Adobe Experience Manager integration with PDF Embed API - Adobe Experience Manager 22-10-2021

We see the following URL getting blocked by Websense on our internal network: https://documentcloud.adobe.com/view-sdk/main.jsWe’re using it to connect to Adobe to pass the client API key for the AEM component “PDF Viewer”. Is there a workaround for this issue that anyone could recommend?

307

Issue with Adobe Experience Manager integration with PDF Embed API - Adobe Experience Manager 22-10-2021

We have extended the PDF viewer core component in our AEM environments. We have also created API keys for each of the domains in the Adobe Developer Console. When we set up the PDF viewer component in our STAGE author environment, we get the message "This application domain is not authorized to use the provided PDF Embed API Client ID. (please see attached screenshots) The API key is set up to the correct domain.

318