[SOLVED] Content list column is empty after squidex upgrade to version 7.14

Bugs Solved Bugs
1

I have…

  • Checked the logs and have uploaded a log file and provided a link because I found something suspicious there. Please do not post the log file in the topic because very often something important is missing.

I’m submitting a…

  • Regression (a behavior that stopped working in a new release)
  • Bug report
  • Performance issue
  • Documentation issue or request

Current behavior

When loading content list of particular schema the column Status (after squidex upgrade is delayed in gridview settings as data.Status) is empty.
This only started after squidex upgrade version 7.14.
When loading any record details the Status field is correctly populated.

For reference please check screenshot of list /record details and schema definition.

Hotline
Hotline3850×2150 655 KB

Expected behavior

When loading content list of particular schema the column Question Status value should be populated.

Minimal reproduction of the problem

Environment

  • Self hosted with docker
  • Self hosted with IIS
  • Self hosted with other version
  • Cloud version

Version: [VERSION]

Browser:

  • Chrome (desktop)
  • Chrome (Android)
  • Chrome (iOS)
  • Firefox
  • Safari (desktop)
  • Safari (iOS)
  • IE
  • Edge

Others:

2

Hi.

the field names have been normalized in one of the recent versions. Before it was like

Status.
meta.id`

Now it is just

data.Status
id

I think your problem could be that it is named “status”, perhaps the migration assumes that it is the normal status field. I will investigate that.

3

I cannot reproduce it. I think I might need a database backup or something like that.

4

I have a idea. I think these custom user settings are not migrated probably. It might help by just clicking the “Reset” button in the column selection.

5

Hi,

I have tried to reset settings but it is not working .

image
image1385×535 37.8 KB

6

Then I need your backup.

7

Hi,

If you need backup to reproduce issue . you can create test schema with Status field. For your reference sample schema script .

{
    "previewUrls": {},
    "properties": {
        "validateOnPublish": false
    },
    "category": "Hotline",
    "scripts": {},
    "isPublished": true,
    "fieldRules": [],
    "fieldsInLists": [],
    "fieldsInReferences": [],
    "fields": [
        {
            "name": "Status",
            "properties": {
                "isRequired": false,
                "isRequiredOnPublish": false,
                "isHalfWidth": false,
                "fieldType": "String",
                "createEnum": false,
                "editor": "Dropdown",
                "inlineEditable": false,
                "isEmbeddable": false,
                "isUnique": false,
                "allowedValues": [
                    "open",
                    "closed"
                ],
                "contentType": "Unspecified",
                "label": "QStatus"
            },
            "isLocked": false,
            "isHidden": false,
            "isDisabled": false,
            "partitioning": "invariant"
        }
    ],
    "type": "Default"
}

If we do not select status in list then we are able to see Question Status value in list .

image
image1469×818 66.5 KB

8

I have pushed a fix to master branch.

9

We have tried with new master build and it is working fine. we are able to see field value in list .
Thank you for your help

1 Like