There were a mass amount of UI changes between 6.0 to 6.2 - how do we manag

[Meghan Erickson, modificado 9 Anos atrás.]

Hello,

There was a massive amount of invasive UI changes between 6.0 to 6.2. These changes override much of our custom CSS - disrupting the overall look and feel of our website. We can't be the first ones who've gone through this. Is there an easier way to do this without refactoring all of our client-side code?

Basic Details:
During our upgrade, we first built our theme off of classic parent, which severely disrupted our site's CSS. So then we tried building our theme based off of _unstyled parent, which caused the dockbar and the left-side admin-panel to not function and not appear properly. Without this we cannot carry out all of the administrative functions we need to (such as adding a portlet to a page.)

[David H Nebinger, modificado 9 Anos atrás.]

You want to start your theme from _unstyled if you plan on supplying style to every class. You can use _styled if you'd like to use some basic styling.

You never, ever want to start from classic. Classic is there pretty much just for a classic theme, but it is not meant to be a platform to build themes from.

[Byrån Zaugg, modificado 9 Anos atrás.]

Meghan Erickson:

Is there an easier way to do this without refactoring all of our client-side code?

Try using the AlloyUI 2.0 / Bootstrap Migration and AUI Upgrade Tool

[M J, modificado 9 Anos atrás.]

Start creating your theme from scratch in Liferay 6.2 based on classic style. This way, you can have a decent theme with and without the dockbar. I have built one like that and it works with and without the dockbar. Upgrading would be a pain in the rear end, it simply DOESN'T work!

[Jack Bakker, modificado 9 Anos atrás.]

I'm with MJ on this one, on v6.2 I also have been starting 'from scratch' starting with classic, velocity ; where after creating the theme, I copy the following in : ROOT/html/themes/classic/_diffs ; then carrying on to restyle it as needed