I'm new to Orbeon Forms, I would like to use the Liferay portlet plugin but I cannot find the download file: there is only in the nightly build. Is it possible to have a more stable version to try it?
The most stable version of the Orbeon Forms portlet support is the one in the nightly builds, as there has just been a series of bug-fixes for the upcoming Orbeon Forms 3.9 release.
It's technically not a plugin: you just deploy a nightly build of the Orbeon Forms PE orbeon.war into Liferay and the Orbeon Forms portlet will be available.
Related
How can i change powered by liferay to custom label and hyperlink when clicking liferay . I am new to liferay development . Can some suggest to create hook for changing basic functionalities in liferay 7.
You need to write a fragment in Liferay 7
Here is the tutorial
https://dev.liferay.com/develop/tutorials/-/knowledge_base/7-0/overriding-a-modules-jsps
The latest IDE Of Liferay (Released in Dec 2016) provides option to create Liferay fragment hook through IDE.
Previous IDE didnt had the support, other option is you can create through Blade.
To change powered by liferay you must create your custom theme for the liferay.
In liferay you can customize the liferay default theme and there you can modify powered by and liferay with any message as per your requirement.
For more info use these links: Creating theme and Creating basic theme.
There are many sites which provides articles for upgrading liferay 6.2 to dxp but only for ant project. How can we upgrade liferay 6.2 maven project to liferay dxp gradle project ?
The strategy to upgrade your code is exactly the same. Liferay's Plugins SDK defaulted to Ant until 6.2, now you have the choice between liferay-workspace (gradle based), gradle and maven - just choose the build environment you'd like (sounds like you'd like to continue with maven) and add your code to an empty blueprint for the project of your choice.
There's an upgrade tool in Liferay IDE that might help you - even if it doesn't use the build tool of your choice or if eclipse isn't the IDE of your choice: The upgrade tool is a one-off tool to use during upgrade. No matter what the result is on: You can always check (for example) Liferay's blade-sample project to find the proper build descriptors for Maven - and adapt them to your project.
Edit: After the clarification: Your main task is still the upgrade of the code. As of moving from Maven to gradle: Identify the dependencies and translate from pom.xml syntax to gradle's declaration - the contents are similar (e.g. group, name, version), only how you're writing them down is different. If you have made elaborate custom modifications to your pom.xml try to go without them first. You can start with a stock build.gradle (e.g. from blade-samples that most closely match your project) and then fix compile-time dependencies as you go.
I'm not aware of an automated process that does this translation for you (and most likely you'd bump up a few version numbers in the process anyway)
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 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.