I just migrated a DXP server from 2026.q1.2-lts to Liferay Digital Experience Platform 2026.Q3.1 (August 22, 2026) without errors.
Logging in as Administrator, the contents of Control Panel —> OBJECT —> Objects is empty, completely blank. Please see the screenshot below.
Using F12 key there are the below errors:
TypeError: can't access property "length", F.items is undefined
Lu ViewObjectDefinitions.tsx:321
React 10
react-dom.production.min.js:189:30
Uncaught TypeError: can't access property "length", F.items is undefined
Lu ViewObjectDefinitions.tsx:321
React 10
ViewObjectDefinitions.tsx:321:6
—
It seems that the backend does not provide the list of Object definitions to the React frontend.
Note that I reindexed already the remote ElasticSearch instance.
Thank you in advance for any help.
3 Answers
3
Hi @icarrara ,
You mentioned you tried reindexing already, have you cleared the OSGI cache? Sometimes stale osgi cache from pre-upgrade can cause weird errors.
I would:
If that doesn’t work, I’d also check to see if there are any elastic search (exceptions, missing plugins, etc…) in the Liferay error logs when you access the object page.
Hi, and thanks for your comments.
Every DXP 2026.q1.2-lts server I update to 2026.q3.1 has the same issue.
When I go to “Control Panel —> Objects,” I get a blank page that produces the errors shown in this screenshot - Of course I reindexed and cleaned the various temp folders:
SOLVED
I did the upgrades from Liferay Portal from 7.4.3.132-ga132 to DXP 2026.q1.2-lts to 2026.Q3.1 without any database upgrade errors.
I discovered that in some rows of the “ObjectField” table, the “readOnly” field contained the value “1” instead of “true,” which is what the code expects.
The code expects to read an ENUM; this caused an error that resulted in the contents of Control Panel —> OBJECT —> Objects appearing empty—completely blank.
I used the following SQL code and the problem is resolved:
– Converte ‘1’ in ‘true’
UPDATE ObjectField
SET readOnly = ‘true’
WHERE readOnly = ‘1’;
-- Converte ‘0’ in ‘false’
UPDATE ObjectField
SET readOnly = ‘false’
WHERE readOnly = ‘0’;
Thanks to everyone who contributed to this issue.
Have you done a reindex of ElasticSearch ?
– Eric_DARIEL