liferay crm

1. Cancel the display of the above dockbar This is the default code in the liferay topic, that is, all login users will display this control bar. Dockbar is the top column. #if ($is_signed_in) #dockbar()#end Change to the following: #if (($is_signed_in) $permissionChecker.isCompanyAdmin($company_id)) #dockbar()#end Non-admin users will not be displayed Ii. Access prohibited You can still access the Control Panel through this connection: Http: // lo

Now let's make a summary: In fact, in order to have a better user experience, we have optimized from all aspects: The resource itself is cropped in size: For CSS,JS resources, we compress them with yui-compressor. For image resources, we use the Sprite tool bar multiple small pictures merged into large single pictures The cost of resources being downloaded from the server to the client is reduced: We have enabled the filtering of gzip filter on the server so that all the resources are comp

In Liferay, if we want to use our own JS library (such as the EXT-JS Library) instead of the default AUI library, you can follow these steps: (1) Place the library file We go to the $liferay_home/tomcat-7.0.23/webapps/root/html/js directory to build a directory called ExtJS, and then copy ext-all.js into. (2) Create the portal-ext.properties in the $liferay_home directory and then from the portal.properties in the Portal-impl.jar package Javascri

The Liferay SDK has the following directory structure: clients/is the directory for the client plug-in and provides an ant script to create the client plug-in dist/This directory holds the archive applications for deployment and release. For example, the last time we wrote 2 portlets, here are 2 corresponding applications: ext/is the directory of the Ext plugin and provides an ant script to create the EXT plug-in hooks/is the directory of the

DockBar is the most active element in Liferay, because almost all of the user's operations start from the DockBar, so we're here to analyze the DockBar in depth. Structure of the DockBar: DockBar is divided into 2 parts from the whole, part is the left The other part is the right So the final DockBar structure is (I omitted a lot of code):

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 whether it is the logo associated to the hook

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 theme we're developing in D:\WalmartProject. First: Let's use the Maven Theme Wizard to create a theme: Once created, because we want our pom.xml to inherit Father

. Servicecomponentlocalserviceimpl.java is the core of the class, if you carefully study the code of this class will have other gains, here is only one example: you can see that this class actually supports the operation of upgrading the database, As long as the previous tablesql and the new TAblesql inconsistent, will perform the upgrade database operations, according to our thinking, we deployed two times the tables.sql is inconsistent, why not execute this code? Debugging finds that the Table

Brief introduction: It is well known that cross-domain problems are a very common requirement, such as having a client's EXT-JS control render a JSON object from the server side. We can solve them in many ways, such as JSONP. However, in Liferay, we can use the Serveresource method to gracefully resolve Cross-domain access issues. Whiteboard Analysis: Here is the whiteboard on the technical symposium: Workaround: First write a Serveresource met

In Liferay, if you can use good portletpreferences then it will be very powerful: Brief introduction: Portletpreferences is a combination of a set of information related to the current user, and we can allow a logged on user to share data through this portletpreferences on different pages of a portlet, at different stages, Without having to worry about other users stealing the data. The benefit of using this shared data is that it does not require s

Recently our team asked Liferay to do the front page tuning, of course, the evaluation tool is the most important, in order to see the specific page loading time and so on, our first choice of course is the Chrome Browser diagnostics tool, but the total feeling is not professional, based on my experience, I still recommend YSlow, it The index of the page will be graded, and then finally get the total score then rating, General level has A,B,C,D,E,F6 l

In the Liferay Control Panel, when you click the search user in the user panel: The requests sent to the server are as follows: Based on the configuration in Struts-config.xml, we find forward that match struts-action to/user_admin/view_users: Then go to tiles-def.xml and find the page that matches forward for Portlet.users_admin.view: So, we found the page is/portlet/users_admin/view.jsp:

", "Com.liferay.portlet.maximize-help", "Com.liferay." Portlet.parent-struts-path "," Com.liferay.portlet.pop-up-print "," Com.liferay.portlet.preferences-co Mpany-wide "," Com.liferay.portlet.preferences-owned-by-group "," Com.liferay.portlet.preferences-uniq Ue-per-layout "," Com.liferay.portlet.private-request-attributes "," Com.liferay.portlet.private-sessi On-attributes "," com.liferay.portlet.remoteable "," Com.liferay.portlet.render-timeout "," Com.liferay.portlet.render-weight "," Com.li

It is widely reported that I log on to the 64-bit server and the server is stuck (I don't know why) So I decided to say goodbye to 64 for everyone's happiness. Haha. I set up an environment on other servers, and everything went smoothly, because it has been set up many times, However, when Tomcat is started at the end, when auto deploy restart started for/LTC/home/liferay/deploy is started, nothing will go down, and it won't be done after a long time,

Introduction: We all know that we can use sessions to store attributes, but Liferay PortletSession is somewhat special. It can use different scopes to store different attributes. Our sample code is as follows: 650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/15061KS6-0.png "title =" 1.png" alt = "153666521.png"/> Here we will study the details of PortletSession, for example, how to store the attributes on different scopes. D

In the/portal-master/portal-impl/src/portal.properties file, the following configuration is available:# # Input A list of sections that would be included as part of the organization# form when adding an organization. #organ Izations.form.add.main=details,organization-siteorganizations.form.add.identification= Organizations.form.add.miscellaneous=# Input A list of sections that'll be included as part of the Organizatio n# form when updating a organization. #organizations. Form.update.main=detail

22:00:39,557 ERROR [schedulermessagelistener:53] Unable to process message {destinationname=liferay/scheduler_engine, Responsedestinationname=null, Responseid=null, payload= COM.LIFERAY.PORTAL.KERNEL.SCHEDULER.MESSAGING.SCHEDULERREQUEST@D870CB, Values=null} Com.liferay.portal.kernel.scheduler.SchedulerException:Unable to start Scheduler At Com.liferay.portal.scheduler.quartz.QuartzSchedulerEngineImpl.start (quartzschedulerengineimpl.java:276) At Com.l

This problem actually stuck me for 1 hours, mainly beginning to think complex. Because the default if the site to do in-station navigation, we are implemented with JS, and Liferay page is so complex, because the portal page is composed of a portlet, each page ID composition is also very complex, so I have been doing it for a long time did not get out, Until I returned to the basic definition of portal. In the portal definition, a very important feat

Liferay has a service builder mechanism that generates a set of interfaces and classes and configuration files for the persistence Layer and service layer, and when we write a service.xml and invoke ant target as Build-service, The framework uses the Servicebuilder class to parse the Service.xml file: For example, the service.xml we create is: When we run Build-service Target, the location of this service.xml file is used with the first paramete

Liferay 6.1 Creates a new user page as shown in figure: The code for this page is in/html/portlet/login/create_account.jsp: ...