topic Re: adf-content-metadata-card component in Alfresco Forum

adf-content-metadata-card component

anshu_kumar — Mon, 04 Jun 2018 09:18:42 GMT

Hi,I am using ADF 2.3.0 and ACS 5.2.1 and using <adf-content-metadata-card> component to list all properties of a node.<adf-content-metadata-card [node]="node" [multi]="true" [readOnly]="false"> </adf-content-metadata-card>Also, configured contextRootEcm to use a different context

Re: adf-content-metadata-card component

dvuika — Mon, 04 Jun 2018 09:41:51 GMT

Instead of changing the context root in the JS-API you can change the ACS url in the `app.config.json` file (ecmHost)

Re: adf-content-metadata-card component

anshu_kumar — Mon, 04 Jun 2018 09:56:31 GMT

Hi Denys,

Yes, I changed both host (ecmHost) and context (contextRootEcm) in ''app.config.json'' only.

The application works absolutely fine. I am able to authenticate, navigate, perform actions on node, etc. all good.

The only thing that does not work is when I click on 'More Information' available in adf-content-metadata-card component. In the browser console, I get --404 Not Found-- and when I check the REST URL, it does not have the context as set in app.config.json. Hence, it fails.

Re: adf-content-metadata-card component

dvuika — Mon, 04 Jun 2018 13:03:24 GMT

Can you try only changing the ecmHost value? typically you should not be changing contextRootEcm if you have correctly configured repository URL

Re: adf-content-metadata-card component

andraspopovics — Mon, 04 Jun 2018 13:12:36 GMT

Hi,

Can you please give us a little bit more of the context? Which is the request exactly which gives you 404?

Re: adf-content-metadata-card component

anshu_kumar — Mon, 04 Jun 2018 14:38:00 GMT

Hi Denys,

Denys Vuika‌ Andras Popovics‌

I know the default context of the repository URL is 'alfresco'.

However, the context of our repository is 'alfresco/content'. This is configured based on organization standards.

Therefore, we have set the context to

"contextRootEcm": "alfresco/content",

Now, our adf-application works perfectly fine. Authentication, navigation, document list rendering, node actions(copy, move, delete, lock/unlock, etc) all works fine. The REST URL for these has the context as 'alfresco/content', so it renders the service fine.

But this is not the case when the application tries to get More Information in adf-metadata-card-content component.

The REST URLs built here does not take the configured context into consideration. Instead, it keeps the default.

Re: adf-content-metadata-card component

anshu_kumar — Mon, 04 Jun 2018 14:54:37 GMT

Hi Andras,

Requests which gives 404 when ''contextRootEcm'' is set to have a value other than default(''alfresco'') context are:

{hostname}/alfresco/s/api/classes/cm_versionable
{hostname}/alfresco/s/api/classes/cm_titled
{hostname}/alfresco/s/api/classes/cm_auditable
{hostname}/alfresco/s/api/classes/cm_author
{hostname}/alfresco/s/api/classes/cm_content

There is one other request for custom aspect, that also fails. I have not included that.

I guess these requests are based on older REST APIs as I could not find any on Alfresco Content Services REST API Explorer

Re: adf-content-metadata-card component

andraspopovics — Mon, 04 Jun 2018 15:10:55 GMT

May I ask you, whether you have Share or not?
Those API endpoints I'm afraid only accessible if you have Share.

Re: adf-content-metadata-card component

anshu_kumar — Tue, 05 Jun 2018 06:24:00 GMT

Hi Andras,

We are using Angular based ADF UI.

One of the OOTB ADF components that I have used is Content Metadata Card Component

Those API endpoints are requested through this very component. We have not done any changes to it.

Re: adf-content-metadata-card component

dvuika — Tue, 05 Jun 2018 06:34:39 GMT

Andras Popovics I think the 'getClass' has different context root hardcoded and it needs to be fixed: alfresco-js-api/ClassesApi.js at development · Alfresco/alfresco-js-api · GitHub

Re: adf-content-metadata-card component

andraspopovics — Tue, 05 Jun 2018 09:11:11 GMT

Yes, those endpoints are meant to be "private/internal" that is why those can be only used with the Share. Until further endpoints improved for the metadata, this is a known limitation of the content metadata card unfortunately.

Re: adf-content-metadata-card component

anshu_kumar — Tue, 05 Jun 2018 11:11:01 GMT

Hi Denys/Andras,

In which release do we expect this fix?

Re: adf-content-metadata-card component

eugenio_romano — Fri, 08 Jun 2018 10:48:25 GMT

Hi Is going to be fixed in 2.4.0 next version

Re: adf-content-metadata-card component

anshu_kumar — Fri, 08 Jun 2018 11:20:50 GMT

thanks Eugenio.