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
If someone wants to use a module it should be properly translated at all time.
I suggest we move the reference to OrchardCore.Application.Cms.Core instead.
Unless what we expected was translations would not be supported when using OrchardCore.Application.Cms.Core.Targets on a web project instead of the latter.
The goal for us is to not load all the themes that comes with Orchard while still being able to use DataAnnotations translations.
The text was updated successfully, but these errors were encountered:
We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).
This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.
We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).
This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.
If someone wants to use a module it should be properly translated at all time.
I suggest we move the reference to OrchardCore.Application.Cms.Core instead.
Unless what we expected was translations would not be supported when using OrchardCore.Application.Cms.Core.Targets on a web project instead of the latter.
The goal for us is to not load all the themes that comes with Orchard while still being able to use DataAnnotations translations.
The text was updated successfully, but these errors were encountered: