AEM 6.5.21 - SP21 Facing issues with Content Fragment Models | Community
Skip to main content
chirran414
chirran414
Level 4
December 30, 2024
Solved

AEM 6.5.21 - SP21 Facing issues with Content Fragment Models

  • December 30, 2024
  • 2 replies
  • 2200 views

 

Hi everyone,

 

We recently upgraded from AEM 6.5 SP14 to SP21, and since the upgrade, we’ve been facing an issue where content fragment models (CFMs) aren’t retaining field values. After editing and saving the content fragment models, the values don’t seem to stick. This happens with both existing CFMs and newly created CFMs.

Here’s what we’ve noticed so far:

  • No new nodes are created under CRX/DE after saving the CFMs.
  • The issue happens consistently across different models and environments.

I’ve checked the logs and here are some of the errors I’m seeing:

 


23.12.2024 11:46:28.227 *ERROR* No renderer for extension html, cannot render resource
23.12.2024 11:46:28.258 *WARN* Could not add property to granite:data resource as it does not exist.

 

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}}]]

 

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 experienced something similar after upgrading to AEM 6.5 SP21? Any ideas or suggestions would be really appreciated.

Thanks so much!

Best answer by chirran414

Hey @chirran414 I installed SP21 locally and did not encounter any issues when creating or updating CFMs, or when working with CFMs based on those.

 

The issue appears to be related to the fact that the "translatablefield" option is only available in AEMaaCS. I installed SP21 as you mentioned, and this option is unavailable in that version. Since the CFMs you've defined are configured to use this property, it is causing a rendering issue. My guess is that removing the CFMs that rely on this property will resolve the issue. 

 

[1]. AEMaaCS: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/sites/administering/content-fragments/content-fragment-models#properties VS AEMonPremise: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/assets/content-fragments/content-fragments-models#properties (You will notice Translatable is not mentioned in the onPremise documentation)

[2] 

 

Hope this helps

 


Found the solution

On Vanilla instance Apache Sling Request Parameter Handling config has default Maximum File Count value as 10000.

But after our code deployment this value is resetting to 50 due to our custom config. Once we update this to 10000 its working as expected. 

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.

 

2 replies

EstebanBustamante
Community Advisor and Adobe Champion
EstebanBustamanteCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
December 30, 2024

Hi, 


The log entry below indicates that something was not properly activated or refreshed after the SP upgrade. Can you try restarting the instance to see if that helps and validate that all the bundles are active?

No renderer for extension html, cannot render resource TypeOverwritingResourceWrapper, type=dam/cfm/models/editor/components/datatypeproperties/translatablefield,

 

Hope this helps

Esteban Bustamante
chirran414
chirran414Author
Level 4
December 30, 2024

Hello @estebanbustamante ... yes I already tired that. 

mahi1729
mahi1729
Level 4
December 31, 2024

Can you check if you see this issue with DAM metadata schema updates as well? We found that there is an issue with form builder functionality impacting multiple areas, and AMS confirmed that this is a known issue where there is a specific sling config which has a config that needs to be automatically increased to 10000 after upgrade, but for some reason it fails. See if you are facing issue in metadata schema builder as well, so I can confirm the fix. Thanks !

    Terms & ConditionsAccessibility statement

    Loading footer...