Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The ListPart in custom widget reported errors "The page could not be found". #15219

Closed
effapp opened this issue Feb 1, 2024 · 1 comment
Closed

Comments

@effapp
Copy link

effapp commented Feb 1, 2024

Describe the bug

The ListPart in custom widget reported errors "The page could not be found".

To Reproduce

Steps to reproduce the behavior:

  1. Create a new content type with Widget stereotype and name ListWidget.

  2. Add ListPart to ListWidget.

  3. Set "Contained Content Types" of ListPart Settings to "Product".

  4. Create a new content item of Page and add a ListWidget to Flow of the content item of Page.
    image

  5. Click on 'List Items' then display ""The page could not be found".
    image

  6. Click on 'Edit List Widget' then display ""The page could not be found".

  7. Click on 'Create Product' to add a couple of product content items, but the widget don't display these content items.
    image

@effapp effapp added the bug 🐛 label Feb 1, 2024
@MikeAlhayek
Copy link
Member

I have no idea why you would add ListPart using Flow Part.

I am guessing you are doing something fundamentally wrong.

List part will allow you to create multiple contents under a single content. For example, if your content item is called Company and it has a list part with Location as a contained content type, then under each Company content item you'll have the ability to add/removed/edit multiple locations using the list part.

Maybe you can elaborate about your use case so we can provide you more guidance. This isn't a issue so I am converting this issue to a discussion.

@OrchardCMS OrchardCMS locked and limited conversation to collaborators Feb 2, 2024
@MikeAlhayek MikeAlhayek converted this issue into discussion #15232 Feb 2, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants