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
I don't think Vorto makes sense in the same way in v8 as it did in v7, but there are parts where the functionality is missing like in
Media
Members
Blocks / Elements
I think a v8 version should be made to work along with the built in localization. Meaning it should just automatically allow the use of all installed languages. The configuration of a Vorto editor, should simply consist of only a data type selection.
Some kind of limitation should be added.
Should not be allowed to be used in variant properties (can this be checked - can probably show a warning in doc type editor)
Should discourage use on non element document types. Preview in doc type editor could have a warning.
Could show a warning in doc type editor if only one language is installed.
Could probably cancel SaveContentType event if setup violates this.
The display of the property is open for ideas. For content nodes, where there already is a language selector in the header, I think the language selector for the different Vorto fields should be omitted, and they should then only show the active language for the node.
A language selector could then be added for non-content nodes (was going to try out this, but haven't come around to it).
The Value Converter for vorto values, should IMO simply return the underlying Data types value converter, with the value for the current language. Just like how Daves package works.
Open for suggestions :)
The text was updated successfully, but these errors were encountered:
Following the release of Daves multilingual textbox package, I started thinking of ways to get something like Vorto in v8.
I don't think Vorto makes sense in the same way in v8 as it did in v7, but there are parts where the functionality is missing like in
I think a v8 version should be made to work along with the built in localization. Meaning it should just automatically allow the use of all installed languages. The configuration of a Vorto editor, should simply consist of only a data type selection.
Some kind of limitation should be added.
The display of the property is open for ideas. For content nodes, where there already is a language selector in the header, I think the language selector for the different Vorto fields should be omitted, and they should then only show the active language for the node.
A language selector could then be added for non-content nodes (was going to try out this, but haven't come around to it).
The Value Converter for vorto values, should IMO simply return the underlying Data types value converter, with the value for the current language. Just like how Daves package works.
Open for suggestions :)
The text was updated successfully, but these errors were encountered: