Problem with a purchased plugin and 6.2 GA5

[Jonatan Oyola, modificado hace 8 años.]

Hi, I've update from Liferay 6.2 ga4 to ga5 and now I have some problems to use a purchased plugin.

INFO: Deploying web application directory /opt/liferay-portal-6.2-ce-ga5/tomcat-7.0.62/webapps/lims-muc-portlet
Dec 08, 2015 10:33:58 PM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Error registering applications for lims-muc-portlet. This Liferay version does not support this application.
Dec 08, 2015 10:33:59 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /opt/liferay-portal-6.2-ce-ga5/tomcat-7.0.62/webapps/lims-muc-portlet has finished in 1,875 ms

The first time I started Liferay 6.2 GA5, the plugins works.

Also, I want to resintall, and I can't do it. See the attachment image.

Please, I need help.

[Juan Gonzalez, modificado hace 8 años.]

I think this message from your logs is clear enough:

Error registering applications for lims-muc-portlet. This Liferay version does not support this application.

So the app isn't compatible with that version. That's one of the things you have to check before upgrading. You may contact the app author to know when that new version will be available.

There is a trick to change that version in liferay-plugin-package.properties, but then responsibility about the app will be totally yours and you may face unexpected errors.

[Jonatan Oyola, modificado hace 8 años.]

Hi Juan,

The first time I started Liferay 6.2 GA5, the plugins works successfully.

Anyway, 6.2 GA4 and 6.2 GA5 is a minor version. It should works with problems. My custom plugins works without any changes.

liferay-plugin-package.xml (lims-muc-portlet)

<liferay-versions>^M
        <liferay-version>6.2.0+</liferay-version>^M
       <liferay-version>6.2.10+</liferay-version>^M
</liferay-versions>

Also, I've contacted to the developer and He said that it works in GA5.

Juan Gonzalez:

I think this message from your logs is clear enough:

Error registering applications for lims-muc-portlet. This Liferay version does not support this application.

So the app isn't compatible with that version. That's one of the things you have to check before upgrading. You may contact the app author to know when that new version will be available.

There is a trick to change that version in liferay-plugin-package.properties, but then responsibility about the app will be totally yours and you may face unexpected errors.

[Juan Gonzalez, modificado hace 8 años.]

I see there are two versions (Premium and non premium) of the same app. Did you installed both of them in same Liferay installation at some time, even not being installed both at the same time?

[Jonatan Oyola, modificado hace 8 años.]

I've installed only the premium version of application.

I didn't found the message log: Error registering applications for {0}. This Liferay version does not support this application on the source of core and pluggins. So I suppose that It's validate remotely, is It true???

Steps to upgrade Liferay... Is It ok?

mv /opt/liferay-portal-6.2-ce-ga4/*.properties /opt/liferay-portal-6.2-ce-ga5/
mv /opt/liferay-portal-6.2-ce-ga4/data /opt/liferay-portal-6.2-ce-ga5/
mv /opt/liferay-portal-6.2-ce-ga4/deploy /opt/liferay-portal-6.2-ce-ga5/
mv /opt/liferay-portal-6.2-ce-ga4/tomcat-7.0.42/webapps/lims-muc-portlet /opt/liferay-portal-6.2-ce-ga5/tomcat-7.0.62/webapps
mv /opt/liferay-portal-6.2-ce-ga4/tomcat-7.0.42/webapps/magnacademy-portlet /opt/liferay-portal-6.2-ce-ga5/tomcat-7.0.62/webapps
mv /opt/liferay-portal-6.2-ce-ga4/tomcat-7.0.42/webapps/magnacademy-theme /opt/liferay-portal-6.2-ce-ga5/tomcat-7.0.62/webapps
mv /opt/liferay-portal-6.2-ce-ga4/tomcat-7.0.42/webapps/magnapedia-portlet /opt/liferay-portal-6.2-ce-ga5/tomcat-7.0.62/webapps
mv /opt/liferay-portal-6.2-ce-ga4/tomcat-7.0.42/webapps/solr4-web /opt/liferay-portal-6.2-ce-ga5/tomcat-7.0.62/webapps
./startup.sh

[Juan Gonzalez, modificado hace 8 años.]

Hmmm if it's a paid app maybe there are some constraints about this license, as you bought the app to use in 6.2 GA4 and now you're using GA5...I honestly don't know if that could be a problem.

[Jonatan Oyola, modificado hace 8 años.]

So You are saying that I must buy another license for a minor version of Liferay?

Juan Gonzalez:

Hmmm if it's a paid app maybe there are some constraints about this license, as you bought the app to use in 6.2 GA4 and now you're
using GA5...I honestly don't know if that could be a problem.

When I bought the pluggin in the marketplace, I understood that the license is for only one instance of server, not for version of liferay.

Should I create an issue in Jira?

[Juan Gonzalez, modificado hace 8 años.]

Jonatan Oyola:

So You are saying that I must buy another license for a minor version of Liferay?

Juan Gonzalez:

Hmmm if it's a paid app maybe there are some constraints about this license, as you bought the app to use in 6.2 GA4 and now you're
using GA5...I honestly don't know if that could be a problem.

When I bought the pluggin in the marketplace, I understood that the license is for only one instance of server, not for version of liferay.

Should I create an issue in Jira?

Hi Jonatan,

I really don't know if that can cause a problem. I pointed this forum post to the Marketplace developers, hopefully they will answer here soon.

[Marcel Mika, modificado hace 8 años.]

Hi guys,

I'm the app author. I just installed LIMS MUC portlet on Liferay 6.2 GA5 and all seems fine:

12:04:18,667 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][AutoDeployDir:204] Processing lims-muc-portlet-6.2.0.1.war
12:04:18,677 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][PortletAutoDeployListener:79] Copying portlets for /Users/marcelmika/Library/Liferay/liferay-portal-6.2-ce-ga5/deploy/lims-muc-portlet-6.2.0.1.war
12:04:18,729 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][BaseDeployer:863] Deploying lims-muc-portlet-6.2.0.1.war
12:04:18,733 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][BaseDeployer:966] Updating Messenger for Liferay (MUC) from version 6.2.0.1 to version 6.2.0.1
12:04:19,835 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][BaseDeployer:2391] Modifying Servlet 2.4 /Users/marcelmika/Library/Liferay/liferay-portal-6.2-ce-ga5/tomcat-7.0.62/temp/20151209120418733/WEB-INF/web.xml
12:04:20,198 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][PortletAutoDeployListener:91] Portlets for /Users/marcelmika/Library/Liferay/liferay-portal-6.2-ce-ga5/deploy/lims-muc-portlet-6.2.0.1.war copied successfully. Deployment will start in a few seconds.
12:04:28,613 INFO  [ContainerBackgroundProcessor[StandardEngine[Catalina]]][HotDeployEvent:145] Plugin lims-muc-portlet requires marketplace-portlet
12:04:28,616 INFO  [ContainerBackgroundProcessor[StandardEngine[Catalina]]][PortletHotDeployListener:525] Unregistering portlets for lims-muc-portlet
12:04:28,663 INFO  [ContainerBackgroundProcessor[StandardEngine[Catalina]]][PortletHotDeployListener:560] 1 portlet for lims-muc-portlet was unregistered
12:04:28,674 INFO  [ContainerBackgroundProcessor[StandardEngine[Catalina]]][HookHotDeployListener:982] Hook for lims-muc-portlet was unregistered
12:04:28,713 INFO  [ContainerBackgroundProcessor[StandardEngine[Catalina]]][PluginPackageUtil:1016] Reading plugin package for lims-muc-portlet
12:04:30,674 INFO  [localhost-startStop-3][HotDeployEvent:145] Plugin lims-muc-portlet requires marketplace-portlet
12:04:30,674 INFO  [localhost-startStop-3][HotDeployImpl:217] Deploying lims-muc-portlet from queue
12:04:30,675 INFO  [localhost-startStop-3][PluginPackageUtil:1016] Reading plugin package for lims-muc-portlet
12:04:32,007 INFO  [localhost-startStop-3][HookHotDeployListener:709] Registering hook for lims-muc-portlet
12:04:32,069 INFO  [localhost-startStop-3][ApplicationStartupAction:81] LIMS is already synced
12:04:32,071 INFO  [localhost-startStop-3][HookHotDeployListener:851] Hook for lims-muc-portlet is available for use
12:04:32,073 INFO  [localhost-startStop-3][PortletHotDeployListener:344] Registering portlets for lims-muc-portlet

This is the liferay version property in liferay-plugin-package.properties:
liferay-versions=6.2.0+,6.2.10+

This should be fine right?

[Juan Gonzalez, modificado hace 8 años.]

Marcel Mika:

Hi guys,

I'm the app author. I just installed LIMS MUC portlet on Liferay 6.2 GA5 and all seems fine:

12:04:18,667 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][AutoDeployDir:204] Processing lims-muc-portlet-6.2.0.1.war
12:04:18,677 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][PortletAutoDeployListener:79] Copying portlets for /Users/marcelmika/Library/Liferay/liferay-portal-6.2-ce-ga5/deploy/lims-muc-portlet-6.2.0.1.war
12:04:18,729 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][BaseDeployer:863] Deploying lims-muc-portlet-6.2.0.1.war
12:04:18,733 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][BaseDeployer:966] Updating Messenger for Liferay (MUC) from version 6.2.0.1 to version 6.2.0.1
12:04:19,835 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][BaseDeployer:2391] Modifying Servlet 2.4 /Users/marcelmika/Library/Liferay/liferay-portal-6.2-ce-ga5/tomcat-7.0.62/temp/20151209120418733/WEB-INF/web.xml
12:04:20,198 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][PortletAutoDeployListener:91] Portlets for /Users/marcelmika/Library/Liferay/liferay-portal-6.2-ce-ga5/deploy/lims-muc-portlet-6.2.0.1.war copied successfully. Deployment will start in a few seconds.
12:04:28,613 INFO  [ContainerBackgroundProcessor[StandardEngine[Catalina]]][HotDeployEvent:145] Plugin lims-muc-portlet requires marketplace-portlet
12:04:28,616 INFO  [ContainerBackgroundProcessor[StandardEngine[Catalina]]][PortletHotDeployListener:525] Unregistering portlets for lims-muc-portlet
12:04:28,663 INFO  [ContainerBackgroundProcessor[StandardEngine[Catalina]]][PortletHotDeployListener:560] 1 portlet for lims-muc-portlet was unregistered
12:04:28,674 INFO  [ContainerBackgroundProcessor[StandardEngine[Catalina]]][HookHotDeployListener:982] Hook for lims-muc-portlet was unregistered
12:04:28,713 INFO  [ContainerBackgroundProcessor[StandardEngine[Catalina]]][PluginPackageUtil:1016] Reading plugin package for lims-muc-portlet
12:04:30,674 INFO  [localhost-startStop-3][HotDeployEvent:145] Plugin lims-muc-portlet requires marketplace-portlet
12:04:30,674 INFO  [localhost-startStop-3][HotDeployImpl:217] Deploying lims-muc-portlet from queue
12:04:30,675 INFO  [localhost-startStop-3][PluginPackageUtil:1016] Reading plugin package for lims-muc-portlet
12:04:32,007 INFO  [localhost-startStop-3][HookHotDeployListener:709] Registering hook for lims-muc-portlet
12:04:32,069 INFO  [localhost-startStop-3][ApplicationStartupAction:81] LIMS is already synced
12:04:32,071 INFO  [localhost-startStop-3][HookHotDeployListener:851] Hook for lims-muc-portlet is available for use
12:04:32,073 INFO  [localhost-startStop-3][PortletHotDeployListener:344] Registering portlets for lims-muc-portlet

This is the liferay version property in liferay-plugin-package.properties:
liferay-versions=6.2.0+,6.2.10+

This should be fine right?

Hi Mika, yes, that should work as stated in Marketplace documentation.

[Ryan Park, modificado hace 8 años.]

Hi Jonatan,

First, I see that the latest version of Messenger for Liferay (MAC) should be compatible with the version of Liferay you're running. Try updating Messenger for Liferay (MAC) without the license. If you're upgrading an existing instance, your old license should still be present.



If this does not work, click "Manage Licenses" and "Deauthorize" on the following page.

If deauthorize is not present, it is because you manually generated the license. To deauthorize it, you'll have to contact [e-mail] and they'll release the license for you.

If you're still unable to resolve it you can always contact [e-mail] for assistance with licensing issues. If you email, make sure you provide the email account that has the license you're trying to register.

Hope this helps!