liferay theme

Today, my colleague asked me where the Liferay framework default resource file was obtained when Maven built theme, and I compared the process of using ant to compile the deployment theme and using MAVEN to compile the deployment theme, discovering that it was a completely different strategy when replicating the framew

Record today Liferay project from ant Switch to maven lesson. For tomorrow's demo, we've switched all the Liferay projects that were built with Ant to Maven, and the results are not always visible when deploying a theme application built by MAVEN to a Liferay server. I worked for half an hour, only to find out why, be

We can develop theme to let the system not use the default style. When we create a theme project with the wizard and compile it, the project structure is shown in the following illustration: where all the docroot below the _diffs directory are liferay from the default copy of the resource file. All we need to change is to build a parallel directory under the

It is very easy to get the portal site to use its own theme (subject) in Liferay, as follows: (1) In Dock-bar, select Manage->page Layout->look and Feel (2) then select "Define a specific look and feel for this page" (3) then select our custom theme (for example, we developed a theme named Demo-

After learning the ant build theme, Liferay theme, we easily ported the theme project to Maven. The following are the specific steps: Assume: Because we used the http://supercharles888.blog.51cto.com/609344/890525 development structure as shown in the article, let's assume we put the

Conclusion: Theme Upload logo will do the following things: (1) Using Uploadportletrequest object to handle the (2) for the uploaded logo picture is empty, then throw an exception. (3) for the upload of the logo picture is not empty, the first from the database to find the current layout, for logo definition logoid, and bar logoid add to the current layout and then back to the database, and then set according to the Boolean variable to determine

[Liferay] Liferay enables single-point logon and single-point liferay Last article: single-point logon using Liferay-OpenLDAP This article does not introduce concepts, but focuses on implementation. Liferay : 6.1.1 CE GA2 OpenLdap for Windows ：openldap-2.4.38-x86 Apache

Liferay version : Liferay-portal-6.1.1-ce-ga2 Server : Tomcat 7.0.25 Liferay is very large. The portal comes with dozens of Portlet, but you can choose to load the Portlet that comes with the portal as needed. Benefits: 1. Improved startup speed (performance) 2. The interface can be more concise. After all, no Portlet is needed. Look at Xuan Hu, it's

Document directory I. Custom Fields 2. Monitoring) Iii. Plug-in configuration 4. Page Template 5. website template Vi. Server Management VII. Portal instances 8. Plug-in Installation IX. Summary I. Custom Fields Custom fields are a method of adding attributes to many types of sets in a portal. For example, if you use liferay to create a book rating site, you can add custom fields to many collections in the portal. For example, you can add

Last article: single-point logon using liferay-OpenLDAP This article does not introduce concepts, but focuses on implementation. Liferay : 6.1.1 CE GA2 OpenLdap for Windows ：openldap-2.4.38-x86 Apache Directory Studio : Apache Directory Studio 2.0.0-M3 CAS : cas-server-3.5.2 Windows ： 7 x64 Chapter 2 CAS Configuration Download installation: https://www.apereo.org/cas/download The version used in th

Because our application is running on the Liferay application server, some optimizations for the server are of course our first thought. We have done a lot of testing before, because Liferay will have css-fast-load, and js-fast-load, these parameters will be a number of CSS files or several JS files merged into a single large file, which can significantly reduce the number of network IO overhead, We develo

1, download liferay-portal-src-5.2.3 and liferay-portal-ext-5.2.3 2, build ext: In the Portal project Build.xml in turn to execute clean, start, build-ext tasks; 3, Portal and ext items are added under the App.server.zcb.properties file, the file name "ZCB" for the computer's login, as follows: Lp.ext.dir=f://eclipse_project//liferay b-

Liferay has released version 4.1.0. The newest version provided des a message board and Web 2.0-style mail Portlet, Geronimo support, and improved LDAP integration. Now in its sixth year of development, liferay is JSR-168 compliant and runs on almost any major application server, database, and operating system, rendering over 700 deployment combinations. Additional features include: -Assigned communities t

Liferay has two types of services: 1) Internal ServicesLiferay core services, such as portal-impl.jar 2) External ServicesThat is, portal APIs, such as portal-kernel.jar and portal-service.jar The liferay internal service is updated frequently. Pay special attention to the liferay version upgrade. The liferay external

portal. that# happens by because the counter service would look up the properties# prefixed with "jdbc.default." To create its data Source. See the jdbc# properties prefixed with "Jdbc.default." For more information.## Setting a different value for the counter J DBC prefix allows better# fine tune the counter data source with its own set of configuration# settings for high AV Ailability installations. Note that these settings,# though separate, is a copy of the default settings with the newly#

After the Portlet is deployed, an exception is reported-cocould not initialize class com. liferay. util. Portlet. portletprops. Briefly describe the Portlet. properties. During the development of the Portlet, you can customize the configuration file-Portlet. properties similar to portal. properties. The procedure is as follows: 1. Create the Portlet. properties in classpath, such as the WEB-INF/src directory line.chart.types=line,spline,column,bar,t

Last time, in this blog http://supercharles888.blog.51cto.com/609344/897825, We're talking about how to fix the multiple dependencies on slf4j that arise when using Maven's Service-builder, and now we're going to show you how to customize the plugin. This allows you to avoid this error by using our own plug-ins instead of the default Liferay-maven-plugin in your project: Authoring of Plug-ins: Specific writing details will not say, anyway, is to use

The following is a typical startup process for Liferay server: 01.May 3:09:32 AM Org.apache.catalina.core.AprLifecycleListener Init02.info:the APR based Apache Tomcat Native Library which allows optimal performance in production environments is not fo und on the Java.library.path:d:\charles\softwares\java\jdk1.6.0_05\bin;03.May 3:09:34 AM org.apache.coyote.AbstractProtocol Init04.info:initializing Protocolhandler ["http-bio-8080"]05.May 3:09:34 AM or

Introduction: In the previous article, we explained from a macro perspective how Liferay deploys war packages to trigger listeners and complete the deployment process. However, we did not talk about the core deployDirectory, it is used to parse the contents of a temporary directory after the war package has been expanded to this directory, after re-processing and finally copying to the final deployment directory deployDir, we will study this content h

When we create Liferay applications (such as Portlet,theme) with Maven, we often have a version choice, as shown in the figure: The default show's last version of Archetype is selected, at which point we can only display the latest version of archetype, if we use the latest version of archetype development application, then eventually when the application deployed to the lower version of the container (