Query Field Blank After Upgrading Orchard from Version 1.8.3 to 2.1.5

[PP890]

Bug Description:
After upgrading Orchard CMS from version 1.8.3 to 2.1.5, the query field appears blank for all existing queries. This issue affects queries created using Elastic, Lucene, or SQL in the admin section, as they are no longer visible in the query field after the upgrade.

Newly created queries function correctly, but if a deployment plan is created from these new queries and imported into the same version, the query field still appears blank.

Orchard Core Version:
2.1.5

Steps to Reproduce:

Create a query (Elastic, Lucene, or SQL) in Orchard version 1.8.3 from the admin section.

Upgrade the source code to Orchard version 2.1.5.

Navigate to the admin section and open the same query created in version 1.8.3.

Notice that the query field is empty.

Expected Behavior:
All existing queries created in version 1.8.3 should remain visible and editable in the admin section after upgrading to version 2.1.5.

Logs and screenshots

Additional Information:
Even if the content JSON is updated via an SQL query in the CMS, the queries do not appear. However, when imported, only the query name and index are visible, while the query container remains empty.

I have also attempted to import this test package, but in OrchardCoreSource Project version 2.1.5, only the Name, Index, and SourceName are imported while the Query Container remains empty.

{
"name": "Sample Recipe",
"displayName": "Sample Recipe for Elasticsearch Query",
"description": "A recipe to import an Elasticsearch query into OrchardCore 2.1.5.",
"author": "Your Name",
"website": "https://yourwebsite.com",
"version": "1.0.0",
"issetuprecipe": false,
"categories": [],
"tags": [],
"steps": [
{
"name": "queries",
"Queries": [
{
"Name": "GetAllEntrants",
"Source": "Elasticsearch",
"ReturnContentItems": true,
"Properties": {
"ElasticsearchQueryMetadata": {
"Index": "content",
"Template": "{ "query": { "bool": { "must": [ { "term": { "Content.ContentItem.Published": "true" }}, { "term": { "Content.ContentItem.ContentType": "Entrant" } } ] } }, "sort": [ { "Entrant.ProjectName.keyword": { "order": "asc" } } ] }"
}
}
}
]
}
]
}

[Piedone]

There's a breaking change in 2.0 in Queries: https://docs.orchardcore.net/en/latest/releases/2.0.0/#queries However, it should migrate itself. Nevertheless, I'd recommend you upgrade to 2.0 first, and only then update to 2.1.6.

[PP890]

@Piedone But I Tried To Import Queries With Fresh CheckOut of Orchard Source Code 2.1.5 then also query container is empty.

[Piedone]

Could you please walk me through what do you mean by importing queries in this case? Because running the built-in query import recipes of 2.1.x works for me:

[PP890]

@Piedone

When I import queries through Package Import, only the Name and Index are imported, but the query container remains empty. I tried updating the queries directly in the database, but they still don't appear in the CMS. I also tried reloading the tenant, but they still don’t show up.

[Piedone]

Please provide the zip you try to import.

[PP890]

Queries (3).zip
@Piedone P.F.A

[Piedone]

You can reply to messages, BTW, like I do here, no need to open a new thread for each reply :).

So this is a minimal recipe that exhibits the issue, and I can confirm it:

{
  "name": "",
  "displayName": "",
  "description": "",
  "author": "",
  "website": "",
  "version": "",
  "issetuprecipe": false,
  "categories": [],
  "tags": [],
  "steps": [
    {
      "name": "Queries",
      "Queries": [
        {
          "Name": "GetEntrantsByCategory",
          "Source": "Elasticsearch",
          "ReturnContentItems": true,
          "Properties": {
            "ElasticsearchQueryMetadata": {
              "Index": "content",
              "Template": "{\r\n\t\u0022query\u0022: {\r\n\t\t\u0022bool\u0022: {\r\n\t\t\t\u0022must\u0022: [\r\n              {\u0022term\u0022: {\u0022Content.ContentItem.ContentType\u0022: \u0022Entrant\u0022}},\r\n              {%if Term != blank%}\r\n              \t{\u0022term\u0022: {\u0022Entrant.Category.Ids\u0022: \u0022{{ Term }}\u0022}},\r\n                  {%else%}\r\n                  {\u0022term\u0022: {\u0022Entrant.Category.Ids\u0022: \u0022return 0 result\u0022}},\r\n              {%endif%}\r\n              {%if PreviewMode == \u0022true\u0022 %}\r\n              { \u0022term\u0022 : { \u0022Content.ContentItem.Latest\u0022 : \u0022true\u0022 }}\r\n              {%else%}\r\n              \t\t{ \u0022term\u0022 : { \u0022Content.ContentItem.Published\u0022 : \u0022true\u0022 }}\r\n              {%endif%}\r\n            ]\r\n\t\t}\r\n\t},\r\n\t\u0022sort\u0022: [\r\n      {\u0022Content.ContentItem.DisplayText.Normalized\u0022: {\u0022order\u0022: \u0022asc\u0022}}\r\n    ]\r\n}"
            }
          }
        }
      ]
    }
  ]
}

This uses the following query template:

{
  "query": {
    "bool": {
      "must": [
        {
          "term": {
            "Content.ContentItem.ContentType": "Entrant"
          }
        },
        {
          "term": {
            "Entrant.Category.Ids": "{{ Term }}"
          }
        },
        {
          "term": {
            "Content.ContentItem.Latest": "true"
          }
        }
      ]
    }
  },
  "sort": [
    {
      "Content.ContentItem.DisplayText.Normalized": {
        "order": "asc"
      }
    }
  ]
}

I can also confirm that exporting and importing a Query right away exhibits the same issue, even with the built-in RecentBlogPosts Query, and also on the latest main. Opened a bug report: #17722

[PP890]

Thank you, @Piedone and @MikeAlhayek for your prompt and effective resolution of the issue.