Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Editable field isn't working within loops in page fragments

Written By

Ankit Gupta

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • Steps to reproduce:

    1. Under Site Builder > Page Fragments, Import fragment entries.zip(Attached)
    2. Drag the fragment on the content page, In the configuration defaultValue for iteration is 3. It works fine and fields are editable with default value 3.
    3. Click the fragments configuration icon and change the value for the Number of 'Number for Loop Variable' field to 15.
    4. Now if you randomly try to edit any field it's not editable, some fields get edited some don't.
    5. Check the browser's console and you will find the JS error mentioned below
Uncaught goog.asserts.AssertionError {
message: "Failure: expected param content of type function(), but got undefined.",
reportErrorToServer: true,
messagePattern: "Failure: expected param content of type function(), but got undefined.",
stack: "AssertionError: Failure: expected param content of...-dom@2.16.8/lib/IncrementalDomRenderer.js:4931:5)"
}

Environment

  • Liferay DXP 7.2

Resolution

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?