Error saving content fragment instance | Community
Skip to main content
C
ChakaneSh
February 21, 2024

Error saving content fragment instance

  • February 21, 2024
  • 3 replies
  • 987 views

Were facing an issue with saving an instance of a content fragment.

From Navigation --> Assets --> Files -->  content fragment folder --> content fragment instance, I am unable to save new data in these content fragments. 

 

Below are screenshots of what we are seeing:

 

We are using AEM version 6.5.10 and intend to use GraphQL 0.0.6. 

 

Just curious to know if theres anything in the config manager or bundles that need to be taken care of to resolve these errors were seeing in the console. 

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

    3 replies

    Imran Khan
    Community Advisor
    Imran KhanCommunity Advisor
    Community Advisor
    February 21, 2024

    @chakanesh Looks like there is an issue with the person age field as it is validating it and throwing errors. Try below things:

    1. remove number field and try to save. If it works, looks like there is some issue with ootb number field.

    2. Create a vanilla instance having same service pack, don't install project related code/content/any other packages and try same steps.

      Kamal_Kishor
      Community Advisor
      Kamal_KishorCommunity Advisor
      Community Advisor
      February 21, 2024

      @chakanesh : In personAge field of your CF model, can you check if

      Type=Integer/Fraction

      ValidationType=Between

      Min and Max fields are set to numbers.
      I have tested this on AEM 6.5 and it is working fine for me.

      Ensure, you have not changed anything by accident in your code as this should work fine without any customization.

        kautuk_sahni
        Community Manager
        kautuk_sahniCommunity Manager
        Community Manager
        February 28, 2024

        @chakanesh  Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

        Kautuk Sahni
        C
        ChakaneShAuthor
        February 29, 2024

        @imran__khan Hi Imran,

        We have removed the number field and no longer getting the validation error. We are still left with error this at the moment

        jquery.js:4055 Uncaught TypeError: Cannot read properties of undefined (reading 'getElementsByClassName') at instanceGenerator.initializeUI (impl.js:1211:60) at instanceGenerator.createToolbar (richtext.js:4932:20) at instanceGenerator.initializeEditorKernel (richtext.js:48304:25) at instanceGenerator.startEditing (richtext.js:48666:12) at instanceGenerator.start (richtext.js:48696:12) at processConfig (richtext.js:39275:15) at Object.loadConfigAndStartEditing (richtext.js:39295:11) at ns.StyledTextEditor._start (editors.js:811:33) at ns.StyledTextEditor.start (editors.js:752:22) at ns.MultiEditor.start (editors.js:1379:23)

        Also, I can confirm with a vanilla instance everything works as expected. Although once im building the repo im using were running into problems. 

         

         

        Terms & ConditionsAccessibility statement

        Loading footer...