I am upgrading Liferay from 5.2 to 6.1. I want to know similar to core liferay, for theme also we have to follow two steps up-gradation (i.e from 5.2 to 6.0 then 6.0 to 6.1) or we can directly go for 5.2 to 6.1 theme upgrade.
The theme doesn't require any sort of upgrade process so you'll only need to rewrite it once.
Basically you'll just need to make sure that the theme is using 6.1 API and AUI.
The most complicated of the two being migrating from jQuery to AUI (YUI).
Here is a "rosetta stone" to get you started: http://www.jsrosettastone.com/
The upgrade is not like the core liferay.
Steps (more of a check-list) to look for when upgrading themes:
1) You have to change the liferay-look-and-feel.xml's <version>6.1+</version>.
2) You would need to manually include jQuery, as now it is not part of Liferay (Alloy UI is now a part). You can include them through the template files (*.vm).
3) There are a lot of customizations in the template files (portal_normal.vm, portlet.vm, navigation.vm etc) from 5.2 to 6.1, so if you have done customizations to these then you would have to again customize them.
4) Also a lot of CSS changes have happened since 5.2, infact 6.1 UI is almost completely different from 5.2. So you will have to again style liferay html elements as it now uses alloy UI JSP tags to render them.
Hope this helps.
Related
The scenario is a mobile page developed with JSF and Primeface Mobile. I want to navigate in the same xhtml page between multiple pages (have a look at: JSF Primefaces Mobile navigation). After upgrading PrimeFaces from version 6.1 to 7.0 org.primefaces.mobile.application.MobileNavigationHandler does NOT exist anymore. What do i need to use instead? The migration guide "6.2 to 7.0" (https://github.com/primefaces/primefaces/wiki/Migration-Guide) doesnt help me: "[...] Mobile has been removed in favor of responsive features. [...]"
There is NO migration path for you other than rewriting your code.
PrimeFaces Mobile was completely removed in 7.0
See this blog post from Primefaces: https://www.primefaces.org/primefaces-6-2-roadmap/
PF Mobile is a renderkit for the existing components however we’ve
just realized that we have to maintain two different sets at the same
time so decided to deprecate PF Mobile and focus on the responsiveness
of the standard renderkit. So in 6.2, mobile will be deprecated and
removed in 7.0.
Have a look at my migrated fork: https://github.com/djmj/primefaces-mobile.
I extracted the mobile components from PrimeFaces 6.1 and adapted them to PrimeFaces 7.0 as a separate library. I did testing with mobile showcase and will test it in our own application and production the next days.
I started to read about wicket integration with liferay. I found very old information that wicket portlet is no longer supported, but wicket version 1.5.6 works fine with liferay 6.0. What about Liferay 6.2?
Just yesterday a user from the community created a Pull Request to fix the support for Liferay: https://github.com/wicketstuff/core/pull/476.
The Pull Request is for WicketStuff 7.x though. You are very welcome to port the fixes to wicket-6.x branch and we will add them for WicketStuff 6.23.0.
WicketStuff 1.5.x is not maintained anymore.
Apache Wicket version 6.x, 7.x and 8.x supports JSR286 portlets.
Please see the following wiki of how to use the apache wicket portlet bridge.
https://github.com/wicketstuff/core/wiki/Portlet
I have a problem with WebSphere 6.1 and Primefaces. I have created an application, but used a local Tomcat appserver for testing. Everything was working fine, until I tried to deploy it on WAS 6.1.
After investigating the internal server problem, I saw, that WAS 6.1 only supports JSF 1.1, so I can throw out the whole interface :S
My question is, what is the best and most importantly, the fastest solution for this:
my interface is very simple, only panels, commandbuttons, a menu and a printer component. Is it possible to go back to a previous version of primefaces that supports jsf 1.1 keeping most of the code? (as I read, primefaces 1.1 is the last, which is far away from 3.5 )
use another faces implementation, if yes which one is the easiest to switch to from primefaces
can WAS 6.1 be made somehow compatible with JSF 2?
any other way
It's possible if you drop the necessary JSF 2.0/2.1 + PrimeFaces 3.5 JARs in webapp's /WEB-INF/lib and set in WebSphere admin the classloader policy to PARENT_LAST on both the EAR and WAR. This will force WebSphere to load webapp-bundled JSF instead of its own bundled JSF.
I am using Liferay 6.1.1GA2, which includes YUI 3.4.0. As of this posting, the YUI library is currently up to version 3.8.0.
Is there a way to upgrade this library within Liferay so that I won't have to include the newer version inside each portlet I deploy? I can see including the current version on top of the Liferay version leading to problems very quickly.
I have a portlet that worked fine on Liferay 6.1 portal but when I deploy it on Liferay 5.2.3
my configuration page did not even open.
How should I make it work ?
Here is a nice authoritative answer to a very similar question.
The portlets of newer versions are not designed to work on older installation of Liferay. Since they are compiled using the latest plugins-sdk and the also the different jars which have changed since the last version.
So if you want the newer version portlet to work with any older version then you have to compile the portlet with an older version of Liferay with that plugins-SDK. And I am sure there would be a lot of classes and jsp-tags in the Liferay 6.1 portlet which would not work in Liferay 5.2.3.