Nested Content 0.5.0 and Umbraco.MultipleTextstring (+ other property editors) support
Hi. I love Umbraco and the community :-) -- However, now that Nested Content has become native to Umbraco, I think it's a little premature to call the previous Nested Content (0.4.0) "obsolete" if Umbraco.MultipleTextstring is unsupported. I'm unsure of what other property editors are unsupported, but we use Umbraco.MultipleTextstring extensively in the creation of customer support content. It's an unfortunate (but hopefully temporary) consequence of advancing the development of the Nested Content component that UI access to Nested Content already using Umbraco.MultipleTextstring has been disabled.
Understandably Umbraco.MultipleTextstring wasn't supported in an ideal fashion, and we've implemented work arounds for support and translations, but what was the reason for disabling accessibility? Also is there a risk to using Nested Content 0.4.0 and keeping up to date with Umbraco releases? If so, I will hold off until Umbraco.MultipleTextstring is properly supported. Many, many thanks :-)
Hi Lee. Many apologies for not responding sooner and I'm so appreciative of your time to correspond w/me and of your invaluable contribution of NestedContent to Umbraco. Second apologies for the dupe post, but the only love I got on that post was from bullfrogs and crickets. I'll comb through issues.umbraco.org for NestedContent and either kvetch for an ETA if a bug report has been made, otherwise I'll create one.
Anyway, I'd hardly call how I continue to use 0.4.0 a "workaround" but I'll gladly share my solution if it helps others.
I install NestedContent 0.4.0 from NuGet.
I select it in the backoffice by finding it here: Developer > Data Types > +Create
Here it is in action! I use Umbraco.MultipleTextstring to capture both bulleted and numeric lists.
What I consider the most valuable of the "workaround" are the instructions I provide to the translation service, to only "TRANSLATE THE TEXT HERE" and to make sure the string and the spaces before and after: \\r\\n are maintained.
\"list\":\" TRANSLATE THE TEXT HERE \\r\\n TRANSLATE THE TEXT HERE \"
I'm curious about your workaround, when you add \\r\\n (with surrounding spaces), is that in a single textbox?
I'll take another look at MultipleTextstring - see if there's anything obvious with why the support breaks. (I kinda took a step back when we handed NC over to core)
Hi Lee. Thanks for taking another look at MultipleTextstring :-)
More on: \\r\\n...
This is output by the Umbraco backoffice for docs/posts with NestedContent Umbraco.MultiTextstring objects when sent through Umbraco's translation workflow, to separate each Umbraco.MultiTextstring node.
Here's an example of what the object looks like in one of the output XML docs from Umbraco's translation process:
{\"name\":\"List\",\"ncContentTypeAlias\":\"myHelpList\",\"list\":\"This line represents one Umbraco.MultiTextstring.\\r\\nThis is another line\\r\\nAnd another line.\"}
Please excuse that I mentioned spaces surrounding the \\r\\n . In reviewing my documentation for the translation service, the excerpt I put in my earlier post was part of an exhaustive (exhausting - lol) use-case outline to communicate translation requirements to non-technical staff.
Hi guys, a little late to the party on this one but I'm having the same problem here after I recently upgraded a client's site from 7.5.3 to 7.13.2.
In the database, I've executed the following script:
UPDATE [dbo].[cmsDataType]
SET propertyEditorAlias = 'Umbraco.NestedContent'
WHERE propertyEditorAlias = 'Our.Umbraco.NestedContent'
Once I restart the application, this loads all the obsolete nested
content editors as the new core editor. My question is, is this valid? It seems to work and the site does not display any issues once content is published. Can you forsee anything I've not anticipiated?
Nested Content 0.5.0 and Umbraco.MultipleTextstring (+ other property editors) support
Hi. I love Umbraco and the community :-) -- However, now that Nested Content has become native to Umbraco, I think it's a little premature to call the previous Nested Content (0.4.0) "obsolete" if Umbraco.MultipleTextstring is unsupported. I'm unsure of what other property editors are unsupported, but we use Umbraco.MultipleTextstring extensively in the creation of customer support content. It's an unfortunate (but hopefully temporary) consequence of advancing the development of the Nested Content component that UI access to Nested Content already using Umbraco.MultipleTextstring has been disabled.
Understandably Umbraco.MultipleTextstring wasn't supported in an ideal fashion, and we've implemented work arounds for support and translations, but what was the reason for disabling accessibility? Also is there a risk to using Nested Content 0.4.0 and keeping up to date with Umbraco releases? If so, I will hold off until Umbraco.MultipleTextstring is properly supported. Many, many thanks :-)
Hi codeNdrum,
There's no risk in still using v0.4.0 - that version can run side-by-side with the core version.
The reason they were disabled in NC (for both Umbraco core and v0.5.0) is that they weren't (currently) supported, and also to set user expectations.
The best course of action here is to check the Umbraco issue tracker to see if a bug report has already been raised, then if not, create one for it. http://issues.umbraco.org/issues/U4?q=%22Nested+Content%22
I'm curious what workarounds you did to support Umbraco.MultipleTextstring - are these anything that you can share with the wider community?
Cheers,
- Lee
Hi Lee. Many apologies for not responding sooner and I'm so appreciative of your time to correspond w/me and of your invaluable contribution of NestedContent to Umbraco. Second apologies for the dupe post, but the only love I got on that post was from bullfrogs and crickets. I'll comb through issues.umbraco.org for NestedContent and either kvetch for an ETA if a bug report has been made, otherwise I'll create one.
Anyway, I'd hardly call how I continue to use 0.4.0 a "workaround" but I'll gladly share my solution if it helps others.
I install NestedContent 0.4.0 from NuGet.
I select it in the backoffice by finding it here: Developer > Data Types > +Create
Here it is in action! I use Umbraco.MultipleTextstring to capture both bulleted and numeric lists.
What I consider the most valuable of the "workaround" are the instructions I provide to the translation service, to only "
TRANSLATE THE TEXT HERE" and to make sure the string and the spaces before and after:\\r\\nare maintained.Hi codeNdrum,
No apology required, I know how it goes :-)
I'm curious about your workaround, when you add
\\r\\n(with surrounding spaces), is that in a single textbox?I'll take another look at MultipleTextstring - see if there's anything obvious with why the support breaks. (I kinda took a step back when we handed NC over to core)
Cheers,
- Lee
Hi Lee. Thanks for taking another look at MultipleTextstring :-)
More on:
\\r\\n...This is output by the Umbraco backoffice for docs/posts with NestedContent Umbraco.MultiTextstring objects when sent through Umbraco's translation workflow, to separate each Umbraco.MultiTextstring node.
Here's an example of what the object looks like in one of the output XML docs from Umbraco's translation process:
{\"name\":\"List\",\"ncContentTypeAlias\":\"myHelpList\",\"list\":\"This line represents one Umbraco.MultiTextstring.\\r\\nThis is another line\\r\\nAnd another line.\"}Please excuse that I mentioned spaces surrounding the
\\r\\n. In reviewing my documentation for the translation service, the excerpt I put in my earlier post was part of an exhaustive (exhausting - lol) use-case outline to communicate translation requirements to non-technical staff.Hi guys, a little late to the party on this one but I'm having the same problem here after I recently upgraded a client's site from 7.5.3 to 7.13.2.
In the database, I've executed the following script:
Once I restart the application, this loads all the obsolete nested content editors as the new core editor. My question is, is this valid? It seems to work and the site does not display any issues once content is published. Can you forsee anything I've not anticipiated?
is working on a reply...