Site Logo
Looking for girlfriend > Looking for boyfriend > Liferay velocity get friendly url

Liferay velocity get friendly url

Site Logo

There are 3 different places to use Velocity templating in Liferay Portal. Each place introduces its own slight difference in behavior. These differences are noted below. In the theme, we assume 1 that more power is greater flexibility to develop cool stuff… and 2 the portal admin is taking FULL responsibility for installing a theme that might potentially have code which could kill the entire system this is why we have official and non-official plugins as the same could be said for webs, portlets and hooks.

SEE VIDEO BY TOPIC: Liferay SEO Contribution


Site Logo

WebSynergy's properties files differ from the configuration files of most other products in that changing the default configuration file is discouraged. In fact, the file that contains all of the defaults is stored inside of a. Why is it set up this way? Because WebSynergy uses the concept of overriding the defaults in a separate file, rather than going in and customizing the default configuration file. You put just the settings you want to customize in your own configuration file, and then the configuration file for your portal is uncluttered and contains only the settings you need.

This makes it far easier to determine whether a particular setting has been customized, and it makes the settings more portable across different instances of WebSynergy.

The default configuration file is called portal. What follows is a brief description of the options that can be placed in the portal-ext. These are presented in a logical order, not an alphabetical one, as many properties relate to other properties in the system. You need to create the portal-ext. This property specifies where to get the overridden properties. By default, it is portal-ext. Updates should not be made on the original file portal.

Furthermore, each portal instance can have its own overridden property file following the convention portal-companyid. For example, one read order may be: portal. You can add additional property files that overwrite the default values by using the external-properties system property. A common use case is to keep legacy property values when upgrading to newer versions of WebSynergy. For example:. This specifies the path of the portal servlet context.

This is needed because javax. ServletContext does not have access to the context path until Java EE 5. Specifies the default root path for various repository and resource paths. Under this path several directories will be created for the hot deploy feature, JCR, etc. This should never be set to true unless you are running the TCK tests.

Set this to true to automatically create tables and populate with default data if the database is empty. Set this to to true to populate with the minimal amount of data. Set this to false to populate with a larger amount of sample data.

Input a list of comma delimited class names that implement com. These classes will run on startup to upgrade older data to match with the latest version. These classes will run on startup to verify and fix any integrity problems found in the database. These classes are used to process the auto deployment of WARs. Set the directory where auto deployed WARs are copied to. The application server or servlet container must know to listen on that directory.

Different containers have different hot deploy paths. Set a blank directory to automatically use the application server specific directory. Set the following to true if deployed WARs are unpacked. Set this to false if your application server has concurrency issues with deploying large WARs. Set the following to true if you want the deployer to rename portlet. This is only needed when deploying the portal on WebSphere 6. Note that according to IBM, on versions after 6.

PortletDeploymentEnabled and set it to false. This parameter causes WebSphere's built-in portlet container to ignore your portlet application when it is deployed, enabling WebSynergy to pick it up.

This will append a 1 in front of your WAR name. For example, if you are deploying a portlet called testportlet. JBoss now knows to load this portlet after the other WARs have loaded; however, it will remove the 1 from the context path. Set the path to Tomcat's configuration directory. This property is used to auto deploy exploded WARs.

Tomcat context XML files found in the auto deploy directory will be copied to Tomcat's configuration directory. Set the path to Tomcat's global class loader. This property is only used by Tomcat in a standalone environment.

These classes are used to process the deployment and undeployment of WARs at runtime. Set the undeploy interval in milliseconds on how long to wait for the undeploy process to finish. Set the following to true to undeploy a plugin before deploying a new version. This property will only be used if the property hot. Set this property to false to avoid receiving on screen notifications when there is a new version of an installed plugin. Administrators won't be notified when a new version of these plugins are available.

You can also end the id with an asterisk to match any id that start with the previous character. Set this property for the portlet container implementation to use. The default implementation is the internal implementation and provides for the best backwards compatibility.

The Sun implementation provides more features and will be the recommended implementation in the future. Set this property to define the default virtual path for all hot deployed portlets. Set this property to true to load the theme's merged CSS files for faster loading for production. Set this property to false for easier debugging for development.

Set this property to set the default virtual path for all hot deployed themes. Set this with an absolute path to specify where imported theme files from a LAR will be stored.

This path will override the file-storage path specified in liferay-themeloader. Themes can be imported via LAR files. Set this to true if imported themes should use a new theme id on every import. This will ensure that a copy of the old theme is preserved in the theme loader storage path. However, this also means that a lot of themes that are no longer used remain in the file system.

It is recommended that you set this to false. Input a list of comma delimited resource action configurations that will be read from the class path. Input a list of comma delimited Spring configurations. These will be loaded after the bean definitions specified in the contextConfigLocation parameter in web. Many of the following properties should only be customized if you have advanced knowledge of Hibernate.

They map to various Hibernate configuration options which themselves have detailed documentation. Set the Hibernate connection release mode. You should not modify this unless you know what you're doing. The default setting works best for Spring managed transactions. See the method buildSessionFactory in class org. Set the Hibernate cache provider. Ehcache is recommended in a clustered environment.

See the property net. Use these properties to disable Hibernate caching. This may be a performance hit; you may only want to use these properties for diagnostic purposes. Set the JDBC batch size to improve performance. If you're using Oracle 9i, however, you must set the batch size to 0 as a workaround for a hanging bug in the Oracle driver.

Use the classic query factory until WebLogic and Hibernate 3 can get along. Set the classpath to the location of the Ehcache config file for internal caches. Edit the file specified in the property ehcache. Commons Pool is used to pool and recycle objects that are used very often. This can help lower memory usage. There is some debate over the synchronization issues related to Commons Pool. Set this to false to disable object pooling.

There are two lists of files specified in the properties javascript. As the name suggests, the barebone list is a trimmed down version of the everything list whereas the everything list is a list of all loaded JavaScript files. The two lists of files exist for performance reasons because unauthenticated users usually do not utilize all the JavaScript that is available.

See the property javascript. The list of files are also merged and packed for further performance improvements.

Access Objects from Velocity

WebSynergy's properties files differ from the configuration files of most other products in that changing the default configuration file is discouraged. In fact, the file that contains all of the defaults is stored inside of a. Why is it set up this way?

Good book. Helped me get started with Liferay and design my custom theme.

Categories Categories Recent Posts Statistics. Home Liferay Portal English 2. Josh Asbury, modified 11 Years ago. I have created a template which uses the link to page feature in the structure -- linking an image to a page.

Oh no! Some styles failed to load. 😵

By using our site, you acknowledge that you have read and understand our Cookie Policy , Privacy Policy , and our Terms of Service. Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information. I want to get a friendly URL for a layout based on layout id. Currently this is how I do it:. Learn more. Asked 6 years, 6 months ago. Active 4 years, 2 months ago.

Action URL in Liferay

Obtain the plugin binary package from the Liferay Marketplace and deploy using the Liferay control panel Apps page in the usual way. If you have pre-existing content in your portal, tiny URLs for them will be automatically generated during portal startup. This operation may take some time to complete, depending on how much content you have on your portal. The portal will not come up until it has finished.

Without action URL we can't imagine portlet development.

Account Options Sign in. My library Help Advanced Book Search. Packt Publishing Amazon. Liferay Portal 5.

Subscribe to RSS

Post a Comment. Search for:. Friday, June 13,

SEE VIDEO BY TOPIC: Liferay 6.2 Creating user friendly URL

Here you can find more detailed information about the Gentics Portlets and their general features. Many of them are switched on by default. Others can be switched on manually. For specific description of certain portlets please see the subpages on the left. All portlets need to be able to recognize a print view parameter.


Jul 24, - Logic: Get url variable ("page") value. -set $total to the size of the #set ($friendlyURL Pagination JS that can be included in the velocity file.








Comments: 1
  1. Shaktizil

    You are mistaken. I can defend the position. Write to me in PM, we will talk.

Thanks! Your comment will appear after verification.
Add a comment

© 2020 Online - Advisor on specific issues.