Content Fragment Models are not saving after AEM 6.5 SP21 upgrade | Community
Skip to main content
N
NarayanaCh
Level 3
December 29, 2024
Solved

Content Fragment Models are not saving after AEM 6.5 SP21 upgrade

  • December 29, 2024
  • 1 reply
  • 497 views

Hello Everyone,

 

After upgrading from AEM 6.5 SP14 to SP21, we're encountering issues with Content Fragment Models (CFMs). The main problems are

Fields Not Retaining Values: After editing and saving CFMs, fields do not retain their values, and we see the following warning:

 

23.12.2024 11:46:28.227 *ERROR* [[0:0:0:0:0:0:0:1] [1734979588163] GET /mnt/overlay/dam/cfm/models/editor/content/editor.html/conf/demo/settings/dam/cfm/models/testing-sp HTTP/1.1] org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource TypeOverwritingResourceWrapper, type=dam/cfm/models/editor/components/datatypeproperties/translatablefield, path=/mnt/overlay/dam/cfm/models/editor/content/editor/jcr:content/body/items/wizard/items/editorStep/items/content/items/{{field_id}}, resource=[TypeOverwritingResourceWrapper, type=dam/cfm/models/editor/components/datatypes/field, path=/mnt/overlay/dam/cfm/models/editor/content/editor/jcr:content/body/items/wizard/items/editorStep/items/content/items/{{field_id}}, resource=[FormResourceImpl, type=, path=/mnt/overlay/dam/cfm/models/editor/content/editor/jcr:content/body/items/wizard/items/editorStep/items/content/items/{{field_id}}]]

 

23.12.2024 11:46:28.258 *WARN* [[0:0:0:0:0:0:0:1] [1734979588163] GET /mnt/overlay/dam/cfm/models/editor/content/editor.html/conf/demo/settings/dam/cfm/models/testing-sp HTTP/1.1] com.adobe.cq.dam.cfm.ui.impl.models.FragmentReferenceViewImpl Could not add property to granite:data resource as it does not exist.

 

23.12.2024 11:46:28.263 *WARN* [[0:0:0:0:0:0:0:1] [1734979588163] GET /mnt/overlay/dam/cfm/models/editor/content/editor.html/conf/demo/settings/dam/cfm/models/testing-sp HTTP/1.1] com.adobe.cq.dam.cfm.ui.impl.models.FragmentReferenceViewImpl Could not add property to granite:data resource as it does not exist.

 

Has anyone faced similar issues after upgrading to SP21?

Any tips on fixing the granite:data issue and ensuring fields save properly?

How can we resolve the FileCountLimitExceededException error with file uploads?

 

NOTE: I do not see any nodes added in the crx/de, after editing CFM.

    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 NarayanaCh

    Found the solution

    The issue was related to the Apache Sling Request Parameter Handling configuration in the Vanilla instance. By default, the "Maximum File Count" is set to 10,000. However, after we deployed our code, a custom configuration was overriding this setting and resetting it to 50. Once we updated the value back to 10,000, everything started working as expected.

     

    Seems Adobe updated this Maximum File Count to 10000 from 50 after SP14.

    1 reply

    N
    NarayanaChAuthorAccepted solution
    Level 3
    January 3, 2025

    Found the solution

    The issue was related to the Apache Sling Request Parameter Handling configuration in the Vanilla instance. By default, the "Maximum File Count" is set to 10,000. However, after we deployed our code, a custom configuration was overriding this setting and resetting it to 50. Once we updated the value back to 10,000, everything started working as expected.

     

    Seems Adobe updated this Maximum File Count to 10000 from 50 after SP14.

      Terms & ConditionsAccessibility statement

      Loading footer...