OrchardCMS / OrchardCMS/OrchardCore.Commerce

The File Content Definition not generate ContentDefinition.json (OCC-213)

Open
#396 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
231
Forks
94
Avg merge
7d 7h
Merged PRs (30d)
1

Description

Describe the bug

enable the File Content Definition feature, but file ContentDefinition.json is not generated or be generated with un-usable data likes
{ "ContentTypeDefinitionRecords": [], "ContentPartDefinitionRecords": [ { "Name": "PublishLaterPart", "Settings": { "ContentPartSettings": { "Attachable": true, "Description": "Adds the ability to schedule content items to be published at a given future date and time." } }, "ContentPartFieldDefinitionRecords": [] } ], "Identifier": "4pkwq8kekdarfx3zxx0nrx39xe" }

The OrchardCore.Commerce.Web reference OrchardCore 1.7.0
image

To Reproduce

Steps to reproduce the behavior:

  1. Run a new OrchardCore.Commerce.Web for setting up a site with the "Orchard Core Commerce - Development" recipe
  2. The setting-up site step success, you can see the start page with some test content
  3. Go to the Admin and enable the "File Content Definition" feature
  4. Go out to view the start page => see exception
  5. Check the App_Data/Sites/Default/ContentDefinition.json
  6. Go to the Admin and disable the "File Content Definition" feature => site will work again
Expected behavior

A clear and concise description of what you expected to happen.

Screenshots

If applicable, add screenshots to help explain your problem.

Jira issue

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in OrchardCore.Commerce.Web using the "Orchard Core Commerce - Development" recipe, then enable the File Content Definition feature and inspect App_Data/Sites/Default/ContentDefinition.json. Compare the generated content with the reported unusable data and confirm the start page exception. Done means the file contains usable definitions and the site remains functional with the feature enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.