You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if you have multiple ContentPickerFields using the same DisplayedContentTypes set to them, you get very annoying problems:
If you have an item already set to the ContentPickerField then the field might not render the DisplayText, because the item wasn't loaded
The ContentPickerFields don't show any items to select if you click in them. Sometimes some show some items and the other one doesn't. If you input a search string into the ContentPickerField it will successfully show the list of chooseable items.
In Sentry I see the exception thrown in the screenshot below
Orchard Core version
2.0
To Reproduce
My setup is:
Hosted in an Azure App Service with the basic dev plans, so it's rather slow
Using MySql as DB
Using multiple tenants
Using distributed tenants (multiple servers, one DB)
The types were generated in code
We do have a lot of content items (>10000)
Locally with Sqlite and in a tenant this problem occurs too
Expected behavior
ContentPickerFields work as in 1.8.x and show the expected content
Logs and screenshots
Sentry error
Example in the CMS
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently if you have multiple
ContentPickerField
s using the sameDisplayedContentTypes
set to them, you get very annoying problems:ContentPickerField
then the field might not render theDisplayText
, because the item wasn't loadedContentPickerField
s don't show any items to select if you click in them. Sometimes some show some items and the other one doesn't. If you input a search string into theContentPickerField
it will successfully show the list of chooseable items.Orchard Core version
2.0
To Reproduce
My setup is:
Expected behavior
ContentPickerField
s work as in 1.8.x and show the expected contentLogs and screenshots
Sentry error
Example in the CMS
The text was updated successfully, but these errors were encountered: