Not able to apply custom metadata schema | Community
Skip to main content
V
Vani1012
Level 6
March 2, 2023
Solved

Not able to apply custom metadata schema

  • March 2, 2023
  • 4 replies
  • 1578 views

Hi,

I tried apply metadata schema(Tools > Assets > Metadata Schemas.) to a folder through apply folders. but when I click on apply folders its throwing error

Not Found

Cannot serve request to /mnt/overlay/dam/gui/content/processingprofilepage/selectfolderwizard.htmlundefined in org.apache.sling.servlets.get.DefaultGetServlet

Request Progress:

      0 TIMER_START{Request Processing}
      0 COMMENT timer_end format is {<elapsed microseconds>,<timer name>} <optional message>
      5 LOG Method=GET, PathInfo=null
      6 TIMER_START{handleSecurity}
  85614 TIMER_END{85608,handleSecurity} authenticator org.apache.sling.auth.core.impl.SlingAuthenticator@60aa1378 returns true
  85842 TIMER_START{ResourceResolution}
  86193 TIMER_END{350,ResourceResolution} URI=/mnt/overlay/dam/gui/content/processingprofilepage/selectfolderwizard.htmlundefined resolves to Resource=MergedResource [path=/mnt/overlay/dam/gui/content/processingprofilepage/selectfolderwizard, resources=[/libs/dam/gui/content/processingprofilepage/selectfolderwizard]]
  86197 LOG Resource Path Info: SlingRequestPathInfo: path='/mnt/overlay/dam/gui/content/processingprofilepage/selectfolderwizard', selectorString='null', extension='htmlundefined', suffix='null'
  86197 TIMER_START{ServletResolution}
  86199 TIMER_START{resolveServlet(/mnt/overlay/dam/gui/content/processingprofilepage/selectfolderwizard)}
  86893 TIMER_END{693,resolveServlet(/mnt/overlay/dam/gui/content/processingprofilepage/selectfolderwizard)} Using servlet org.apache.sling.servlets.get.DefaultGetServlet
  86896 TIMER_END{698,ServletResolution} URI=/mnt/overlay/dam/gui/content/processingprofilepage/selectfolderwizard.htmlundefined handled by Servlet=org.apache.sling.servlets.get.DefaultGetServlet
  86897 LOG Applying Requestfilters
  86903 LOG Calling filter: com.adobe.granite.resourceresolverhelper.impl.ResourceResolverHelperImpl
  86905 LOG Calling filter: org.apache.sling.security.impl.ContentDispositionFilter
  86907 LOG Calling filter: com.adobe.granite.csrf.impl.CSRFFilter
  86912 LOG Calling filter: org.apache.sling.i18n.impl.I18NFilter
  86916 LOG Calling filter: com.adobe.granite.httpcache.impl.InnerCacheFilter
  86920 LOG Calling filter: org.apache.sling.rewriter.impl.RewriterFilter
  86922 LOG Calling filter: com.day.cq.wcm.core.impl.WCMRequestFilter
  86929 LOG Calling filter: com.adobe.cq.history.impl.HistoryRequestFilter
  87118 LOG Calling filter: com.adobe.acs.commons.wcm.impl.AemEnvironmentIndicatorFilter$InnerEnvironmentIndicatorFilter
  87120 LOG Calling filter: com.adobe.cq.wcm.core.components.internal.servlets.CoreFormHandlingServlet
  87123 LOG Calling filter: com.day.cq.wcm.foundation.forms.impl.FormsHandlingServlet
  87125 LOG Calling filter: com.adobe.granite.optout.impl.OptOutFilter
  87128 LOG Calling filter: com.adobe.cq.social.commons.cors.CORSAuthenticationFilter

 Can anyone help me to fix this.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SivakumarKanoori

Hi @vani1012 

 

This below snippet from  /libs/dam/gui/coral/components/admin/folderschemaforms/clientlibs/folderschemaforms/js this path is triggering the javascript.

$(document).on("click",
".aem-assets-admin-profile-processing-addfolder, .aem-assets-admin-profile-processing-removefolder ",
function() {
var url = $(this).data("foundation-collection-action").data.href;
url = url.replace("{+item}", $(".foundation-selections-item").data("path"));
location.href = Granite.HTTP.externalize(url);
});

 

where as in your case {+item} resolved to undefined. Can check the value for this. $(".foundation-selections-item").data("path");

 

in success scenario the below values are resolving.
url = "/mnt/overlay/dam/gui/content/processingprofilepage/selectfolderwizard.html{+item}?profiletype=folderMetadataSchema"

$(".foundation-selections-item").data("path") = /conf/global/settings/dam/adminui-extension/foldermetadataschema/test


 

hope this helps

 

Thanks,

Siva

4 replies

SivakumarKanoori
Community Advisor
SivakumarKanooriCommunity Advisor
Community Advisor
March 2, 2023

@vani1012 : when you click on apply folders to particular folder . suppose foldername is contributors, there will be a one call happens in the network as below. Please check that, whther it throws any error.

 with below Payload :

 

Please check clearly in the network tab , if there is any other call gets failed which is belongs to metadataschema.

Thanks,Siva
    somen-sarkar
    Community Advisor
    somen-sarkarCommunity Advisor
    Community Advisor
    March 2, 2023

    Hi, Looks like the request is passing an undefined value after the URL.

    /mnt/overlay/dam/gui/content/processingprofilepage/selectfolderwizard.htmlundefined   

     

    It should passs the new metadata-schema details as suffix. Please check why it is passing undefined value ?

     

    Thanks,

    Somen

      V
      Vani1012Author
      Level 6
      March 2, 2023

      Yes I agree, its not sending the metadataaschema value. HOw to check and what to check

        Kiran_Vedantam
        Community Advisor
        Kiran_VedantamCommunity Advisor
        Community Advisor
        March 2, 2023

        Hi @vani1012 

         

        Can you check if you have the access to apply the metadata schema to that folder?

         

        Hope it helps!

        Thanks,
        Kiran Vedantam.

          SivakumarKanoori
          Community Advisor
          SivakumarKanooriCommunity AdvisorAccepted solution
          Community Advisor
          March 2, 2023

          Hi @vani1012 

           

          This below snippet from  /libs/dam/gui/coral/components/admin/folderschemaforms/clientlibs/folderschemaforms/js this path is triggering the javascript.

          $(document).on("click",
          ".aem-assets-admin-profile-processing-addfolder, .aem-assets-admin-profile-processing-removefolder ",
          function() {
          var url = $(this).data("foundation-collection-action").data.href;
          url = url.replace("{+item}", $(".foundation-selections-item").data("path"));
          location.href = Granite.HTTP.externalize(url);
          });

           

          where as in your case {+item} resolved to undefined. Can check the value for this. $(".foundation-selections-item").data("path");

           

          in success scenario the below values are resolving.
          url = "/mnt/overlay/dam/gui/content/processingprofilepage/selectfolderwizard.html{+item}?profiletype=folderMetadataSchema"

          $(".foundation-selections-item").data("path") = /conf/global/settings/dam/adminui-extension/foldermetadataschema/test


           

          hope this helps

           

          Thanks,

          Siva

          Thanks,Siva
            Terms & ConditionsAccessibility statement

            Loading footer...