Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
RE: How to create classic theme in liferay 7.1?
Hello
I create a theme in Liferay using yo and gulp and try to extend with Liferay classic theme but I couldn't found an option for extent with Liferay classic theme.
I try to extend classic theme with "gulp kickstart" but there is no option for a classic theme, Please find an attached screenshot.
I m using liferay-ce-portal-7.1.0-ga1 , node version v8.11.3, CLI version 3.9.1, Local version 3.9.1
Anyone have an idea how to create the classic theme(I mean extend out the custom theme with the classic theme) in Liferay 7.1??
Attachments:
is there any solution or steps for it??
Hi kartikshiroya,
I got the same message. Worked fine with 7.0, but not on 7.1!
I did the following:
(1) dwnload the liferay-ce-portal source, and unzipped.
(2) Got the necessary files of common themes atsourceRoot/modules/apps/foundation/frontend-theme/frontendtheme-classic/src.
(3) copy the content of above src folder into my new theme src folder, and deploy.
Hope, it may help.
Thanks,DT
D T:Hi kartikshiroya,
I got the same message. Worked fine with 7.0, but not on 7.1!
I did the following:
(1) dwnload the liferay-ce-portal source, and unzipped.
(2) Got the necessary files of common themes atsourceRoot/modules/apps/foundation/frontend-theme/frontendtheme-classic/src.
(3) copy the content of above src folder into my new theme src folder, and deploy.
Hope, it may help.
Thanks,DT
Hello D T,
Thanks for reply, But i tried above things
Copy necessary files from liferay-ce-portal-src-7.1.0-ga1\modules\apps\frontend-theme\frontend-theme-classic\src
And deployed same , But i m getting following error.
^
Error: build\_css\portlet\_topper.scss
Error: no mixin named text-overflow
on line 90 of build/_css/portlet/_topper.scss
from line 8 of build/_css/_portlet.scss
from line 15 of build/_css/main.scss
>> @include text-overflow
Regards,
Kartik
Hi Kartik,
This issue seems to be related with a mixin for text-overflow, I solved it (temporary) by creating my own text-overflow mixin, you can see the answer in this thread: https://community.liferay.com/forums/-/message_boards/message/110944870/maximized?_com_liferay_message_boards_web_portlet_MBPortlet_showBreadcrumb=false
Best regards.
Alex Arriaga:Hi Kartik,
This issue seems to be related with a mixin for text-overflow, I solved it (temporary) by creating my own text-overflow mixin, you can see the answer in this thread: https://community.liferay.com/forums/-/message_boards/message/110944870/maximized?_com_liferay_message_boards_web_portlet_MBPortlet_showBreadcrumb=false
Best regards.
Hello Alex,
Yes, It works fine.
Thanks for Solution.
Best Regards,
Kartik
Now all this theory aside, I get it -- classic is just that many more steps ahead than _styled, so it can be a great time saver. One thing I have done in the past that seems to have worked pretty well, was I "cloned" the Classic theme into my own parent theme. By doing this I was able to get the "acceleration" of a theme that was a few more steps ahead, but also mitigate the risk of changes to the classic theme affecting me down the road. Just a suggestion and some food for thought.
The Liferay Theme Generator generates broken themes, end of story there and it's not possible to find the code through NPM very easily so I'm putting a link here to it. Gulp Kickstart often doesn't work.
See the two screenshots, one is classic admin and one is my "custom theme" ... I don't have time. I want to generate an admin theme that is a copy of classic and a site theme that is a copy of classic. So does everyone else. Here I don't want to style the control panel very heavily and I don't have the skillsets for theme contributors. The person who can write a theme contributor may not have capacity to build me a theme contributor that I can't maintain myself if he leaves the team. The theme contrivutor would be used once it wouldn't be reused so that's a waste of time too. A front end developer coming after me would have challenges too with theme contributors.
There are business continuity issues with mixing Java and UI skillsets, unicorns exist but theme contributors have to go.
Time is short, I don't have time to write a theme for Liferay it's too hard and it's not actually my time or money that I'm wasting it's my clients.
https://github.com/liferay/liferay-portal/tree/7.2.x/modules/apps/frontend-theme/frontend-theme-classic
It's our potential that is being wasted, if we have to faff around trying to figure out how to make the theme "look fixed" we can't do other tasks.
Powered by Liferay™