The client dependency generates a new code on upgrade and invalidates the cache....I noticed this recently when I had the file open (very handy!)
But yes I cleared the cache as well.
I've checked (and attached) the CSS source and looks like someone's made the floating buttons absolute (they weren't in 7.11.1). Which has now broken the control.
hmm that's odd, the absolute positioning cannot be disputed in the source code which wasn't there in 7.11. So i'm not sure in what scenario that would work on a fresh build vs an existing one.
Aha, that's a good find. If I recall correctly you can switch from the package version of NC to the core version of NC without problems. I don't think we changed the stored data format at all.
Of course make sure to create a database backup first as I am not 100% sure the data format is the same, but I remember that being the goal for building NC into core, to be able to switch easily.
I recently removed the legacy Nested Content from a project. The only thing needed was changing the datatype. If i recall correctly you don't even need to reset the datatype configuration.
Yes, we're aware that we caused problems on the non-core ones, working on it.
But.. the core NC instance looks fine, right? And you tried switching all your non-core ones to the the core one? That was what I gathered from your updates that you were going to try that.
Anyway, we're working on a solution soon to make both happy again side-by-side , I'll keep you posted!
No, both core and non-core versions of NC look like my screen grabs posted after 7.12 upgrade. So both are broken without me manually tweaking the CSS.
As Lee has described how to move to core without losing data (SQL) i'll convert the old ones over now.
Alright, try to make 100% sure that the css is the one you got with 7.12.0 - no cheating and making manual tweaks. 😉😉
Then make sure to bump ClientDependency.config.
You may need to do a hard cache refresh in your browser.
After that the Core version of NC should look just fine, I can reproduce that on a clean install. However, I am very unfamiliar with NC, so I don't know where the orange things are coming from, happy to test if I know how to make them appear! 🙂
So I think it's fairly safe to say the CSS changes were clashing with the non-core version in my build. Subsequently removing (thanks to Lee's tidbit) the plug-in has now solved the problem!
So maybe a few tweaks to try and allow the two to co-exist in the same project would be sensible.
Alright, for anyone else running into this problem, this will be fixed in 7.12.1 which is due out early next week. We've updated the styles that the core NC uses so that they don't conflict with the "legacy" NC version if it is also installed.
After updating the files, make sure you update the version in your ~/Config/ClientDependency.config file (just make it 1 higher or lower) and refresh the site.
Before:
After:
@martin: I've confirmed that the sorting issue has been there for longer, also in the legacy version. We're looking into fixing that as well, but no promises for 7.12.1 :)
Nested content broken in Backoffice CSS in 7.12
Ohhhh and I was so looking forward to this mammoth update!
The CSS seems to be broken for nested content. See screenshot
https://github.com/umbraco/Umbraco-CMS/blob/c85185bdb0e8a50609fa82bd0f83c4f7af8ae1df/src/Umbraco.Web.UI.Client/src/less/components/umb-nested-content.less
Hi Martin,
I assume you did an upgrade.
Have you tried clearing your ClientDependency cache ?
Last time I ran 7.12 from source Nested Content looked fine.
Dave
How to clear CD cache?
The client dependency generates a new code on upgrade and invalidates the cache....I noticed this recently when I had the file open (very handy!)
But yes I cleared the cache as well.
I've checked (and attached) the CSS source and looks like someone's made the floating buttons absolute (they weren't in 7.11.1). Which has now broken the control.
M.
Which browser are you using ?
Dave
Chrome 68
Just to confirm, I see that it looks a bit weird now, still works but it's not ideal :)
Working on it!
i've gone into the compiled CSS in my build and I ripped out position: absolute; left, top and the padding for .nested-content__icons
Seems to mostly go back to normal after that.
M.
Weirdly, on a fresh install it all works well, I'll look into the install where it looks weird and compare them.
hmm that's odd, the absolute positioning cannot be disputed in the source code which wasn't there in 7.11. So i'm not sure in what scenario that would work on a fresh build vs an existing one.
Good luck finding the problem.
Many thanks M.
Same problem. But I updated with nuget from version where nested content was not a part of core. May be it is important.
Not disputing, just saying it looks normal on a fresh install! Note the dev tools..
Ahh Sebastiaan, I think Dmitriy may have uncovered the answer.
In my build i'm using the latest non-core AND core versions of nested content, due to the length of this project.
So the CSS must've busted the non-core version!
M.
I have tried to update the same old site to 7.11.1 and problem don't appears. Looks like issue exactly in 7.11
Aha, that's a good find. If I recall correctly you can switch from the package version of NC to the core version of NC without problems. I don't think we changed the stored data format at all.
Of course make sure to create a database backup first as I am not 100% sure the data format is the same, but I remember that being the goal for building NC into core, to be able to switch easily.
Hi Sebastiaan, Martin,
I recently removed the legacy Nested Content from a project. The only thing needed was changing the datatype. If i recall correctly you don't even need to reset the datatype configuration.
Dave
Hi Sebastiaan.
I'm pretty sure I tried and lost the data trying to switch but I will validate that for sure shortly.
I'll also check to see what it looks like visually, by swapping.
Back soon!
M
For swapping NC from (old) package version to the Umbraco core version, please see my answer on this thread... https://our.umbraco.com/forum/using-umbraco-and-getting-started/90229-migrating-nested-content-to-77#comment-284837
Hi Lee
Many thanks for the clarification, I was pretty sure data gets blatted...I'll use that SQL to replace my existing datatypes. :-)
Cheers Martin
I've just checked my doc/datatypes and this CSS problem is definitely breaking the core version of nested content!
Bah!
M.
Did you revert the changes you made earlier though? It should only affect the package version of NC, right?
Hi Sebastiaan
Yes I reverted.
Sadly the result on a non-core nested content is even worse!
problems here appear to be in (i've commented culprits out)...
in umbraco.css
in nestedcontent.css
extra: the second entry was merely just to get the thing working again.
Yes, we're aware that we caused problems on the non-core ones, working on it.
But.. the core NC instance looks fine, right? And you tried switching all your non-core ones to the the core one? That was what I gathered from your updates that you were going to try that.
Anyway, we're working on a solution soon to make both happy again side-by-side , I'll keep you posted!
Hi Sebastiaan
No, both core and non-core versions of NC look like my screen grabs posted after 7.12 upgrade. So both are broken without me manually tweaking the CSS.
As Lee has described how to move to core without losing data (SQL) i'll convert the old ones over now.
M.
Alright, try to make 100% sure that the css is the one you got with 7.12.0 - no cheating and making manual tweaks. 😉😉
Then make sure to bump ClientDependency.config.
You may need to do a hard cache refresh in your browser.
After that the Core version of NC should look just fine, I can reproduce that on a clean install. However, I am very unfamiliar with NC, so I don't know where the orange things are coming from, happy to test if I know how to make them appear! 🙂
Also make sure the css from the legacy NC package is not loaded. It uses the same class names.
Dave
Ok so I did the following to my 7.12 build...
ALL IS GOOD!
So I think it's fairly safe to say the CSS changes were clashing with the non-core version in my build. Subsequently removing (thanks to Lee's tidbit) the plug-in has now solved the problem!
So maybe a few tweaks to try and allow the two to co-exist in the same project would be sensible.
Cheers M.
Ah that makes sense when both are loaded they would start clashing, good find!
Yup, we're probably going to rename the css classes for the core version so they won't clash any more.
Oh crud!
I've found another bug! albeit minor!
Drag change the order of a collapsed NC and it stays confined vertically to the containing block.
Do the same for an expanded one and it suddenly jumps out of the container to the left as your drag up and down!
The behaviour is a bit weird as it seems to happen sometimes to collapsed ones too after bug exhibits itself.
M.
I saw that earlier too, we'll have a look!
One extra thing...
After you've dropped an item during a sort, I think it should remain collapsed or if you've dragged an expanded that should remain expanded.
If you drag a collapsed item sometimes it expands....quite annoying if you're doing multiple sorts.
M.
Alright, for anyone else running into this problem, this will be fixed in 7.12.1 which is due out early next week. We've updated the styles that the core NC uses so that they don't conflict with the "legacy" NC version if it is also installed.
For now you can drop these updated files in your ~/Umbraco folder:
After updating the files, make sure you update the version in your ~/Config/ClientDependency.config file (just make it 1 higher or lower) and refresh the site.
Before:
After:
@martin: I've confirmed that the sorting issue has been there for longer, also in the legacy version. We're looking into fixing that as well, but no promises for 7.12.1 :)
is working on a reply...