Need suggestion, we are using Liferay Portal 6.2 we would like to have spring security features integrated, was able find documents on Acegi security integration with Liferay portal 4.2 and 4.3 versions.
http://acegi-ext.sourceforge.net/acegi-portlet-liferay.html
When i started following same steps in Liferay 6.2, i am stuck in very first step of introducing Application context XML in web.xml inside (ROOT).Even if i set contextConfigLocation to applicationContext.xml , it is never recognised and picked.
I can see in web.xml instead of "org.springframework.web.context.ContextLoaderListener" in Liferay 6.2 web.xml find "com.liferay.portal.spring.context.PortalContextLoaderListener".
It will be great if can get some help on this
Awaiting your response
Related
I have a portlet bundle as a war in Liferay 6.2. We are planning to convert it into module as per the Liferay 7. So we have the change of Portlet name and hence Id.
Now we would like to run the upgrade process which will take care below scenarios
Updating Portlet Preferences with new Portlet Id
Updating Layouts to consider new Portlet Id
Updating ResourceAction table to consider new Portlet Id
I have undergone few dev.liferay.com but couldn't fine proper guide to do the same. I followed 6.2 approach by creating the Upgrade class by extending UpgradeProcess class and then overriding the threshold values. However, it doesn't work for me.
Could you please help me with this Upgrade scenario?
Regards,
Suyash Bhalekar
I have been reading the liferay documentation about migrating from liferay 6 to liferay 7 (https://dev.liferay.com/develop/tutorials/-/knowledge_base/7-0/from-liferay-6-to-liferay-7).
I have a basic liferay 6.1.2 application bundle with tomcat that contains a few portlets and all I need is to make it work the same way, without using any new feature (OSGI and all) with liferay 7.
Do you know where I could find a list of new configuration files and a list of the ones that have been deleted?
Is there a place where I can find the new dependencies required by liferay 7 for each of my portlets?
I used the liferay tool to generate the new theme so that's a start...
Any links or advices would be appreciated,
Thanks
EDIT :
I can start liferay 7 with the portlet inside the /deploy. I get no errors, only info like "portlet1.war does not have a WEB-INF/liferay-plugin-package.xml or liferay-plugin-package.properties."
The localhost_host_access.log show a few 404 but not as an error...
I really dont know how to proceed to have information (errors, logs,....) to make this work : my portal is still empty.
You can follow the upgrade procedure (read through the link you've provided) and it should be able to
upgrade your database
upgrade parts of your code
If you are using Liferay IDE or Developer Studio there is code migration wizard. It will not solve all issues but will examine your code and advise you how to change things it can not change itself. This recording in an year old but it will give you an idea of what IDE does (probably more by now). It uses a database of breaking changes, most of which is published here so you can check what is relevant to you.
I do not recommend you do that. First migrates from 6.1 to 6.2 and after 6.2 to 7 or you can redo the entire portal, from Liferay we do not recommend making such low migrations. I recommend you look at the community and OSGI ...
Setting in liferay-portal-6.2-ce-ga2/tomcat-7.0.42/webapps/ROOT/WEB-INF/classes/portal-ext.properties:
journal.structure.force.autogenerate.id=false
journal.template.force.autogenerate.id=false
used to enable YOU editing structure and template id.
This DOES NOT work anymore in liferay 6.2
Using liferay 5.x (and I've read on the web about liferay 6.1) was fine.
Does anybody know how to do this again?
It seems that there is a fix implemented for this in Liferay 6.2 EE. I am experiencing the same problem on Liferay 6.2 CE though. Hopefully I will be able to solve it.
The fix is discussed in the following Liferay Issue: https://issues.liferay.com/browse/LPS-48441. You can follow it as a possible direction to get the solution.
Regards.
EDIT: If you want to "avoid the patching" of this issue, you could use the Scripting Console from the Control Panel and change the structures or templates ids running a script. You can get it from my response in the Liferay thread in here:
Structures and Templates Ids autogeneration not working - Liferay 6.2 CE GA2
Structure-Template of Journal Article got changes in Liferay 6.2 version.
dynamic.data.mapping.structure.force.autogenerate.id=false
dynamic.data.mapping.template.force.autogenerate.key=true
are the new properties for having structure-id and template-id as editable.
As the title states, i'm trying to convert these Vignette portlets into Liferay portlets.
Is there any documentation on this anywhere? I've searched the entire Internet
-When trying to deploy my WARs right off the bat, I'm getting a "missing liferay.plugin.packet.xml" which tells me the entire portlet must be reconfigured to work with Liferay.
-Running Liferay 6.1.1 ga2 on Web Logic 12c server
Cheers!
You mean "liferay-plugin-package.xml", don't you?
You will find such a file in the source of Liferay at /portal-web/docroot/WEB-INF/liferay-plugin-package.xml. For other examples just download sources from other Portlets (Github or Liferay-Marketplace).
Besides some other values, this file defines how Liferay should handle your war (layout-template, portlet, theme).
EDIT: As the marketplace does not allow (plz see the comment in: liferay-plugin-package_6_1_0.dtd) portlets having an liferay-plugin-package.xml, I would recommend to use the corresponding properties file.
Reference file (in the portal sources): /definitions/liferay-plugin-package_6_1_0.properties
I would to follow this Tutorial:
Tutorial SAML
So, I used Liferay EE (30d trial version).
In the tutorial I must to use SAML Plugin Portlet WAR
In Marketplace" from the menu on the top of this page.
Under the left side menu, there's a search box. I insert "SAML" and I press the "Enter" key
I can't download this portlet probably because my account is not linked to an Liferay EE (my version is only trial version)
Is correct this way to download the SAML Plugin Portlet WAR?
EE plugins are only available on the marketplace if you're a registered EE customer. To get hold of EE-only-plugins you'll have to contact Liferay sales.