#File properties editor 7.1 install#
#File properties editor 7.1 upgrade#
#File properties editor 7.1 full#

If you’ve used Web Content Management extensively, you might have structures Step 3: Remove Duplicate Web Content Structure Field Names Manually publish changes) after the upgrade, since the system won’t know whatĬontent changed since the last publishing date.

#File properties editor 7.1 full#

If you skip this step, you must run a full publish (or Step 2: Publish All Changes from the Staged Site to the Live SiteĪnd have content or data saved on the staged site, you must Upgrade, troubleshoot any issues regarding these apps. Using to its latest version for your installation.

#File properties editor 7.1 upgrade#

Upgrade each Marketplace app (Kaleo, Calendar, Notifications, etc.) that you’re This tutorial describes these steps in detail. Step 8: Disable indexing during the upgrade process

#File properties editor 7.1 install#

Step 7: Install Liferay DXP 7.1 and the latest fix pack Step 6: Configure your Documents and Media file store Step 4: Synchronize a complete Liferay DXP backup Step 3: Remove duplicate web content structure field names Step 2: Publish all changes from the staged site to the live site

You’re ready to prepare your environment for upgrading to Liferay DXP 7.1. By deafult, this property is set to true, which sets a dark (inverse) header.Pre-upgrade process of cleaning and normalizing your data,

Halo theme supports the property, which controls the colour of the application header. They can be replaced in the manner described for Havana. If property is disabled, the icons for standard actions and screens are loaded similar to Havana theme - from image files in In this case, you can replace a standard icon only by creating a custom theme based on Halo (see below) and setting the required correlation between the icon and the font element name in -theme.properties file: In Halo theme, Font Awesome icons are used for standard actions and platform screens by default (if is enabled). For example, create.png file should be created to replace the icon for the standard create action (the file name can be easily identified by URL of the corresponding img HTML-element in the running application): You should just copy the required image file to the modules/web/themes/havana/icons directory of the project. Images used for standard actions and screens of the platform can be replaced in the project. You should just specify the name of the required constant of the in the icon property with a font-icon: prefix, for example: Button, can be also added to default themes.įor example, to add an icon to the Havana theme, you just have to add the image file to the modules/web/themes/havana directory described above (it is recommended to create a subfolder):Īfter that, you can use the icon in the application by specifying the path relatively to the theme directory in the icon property:įont elements of Font Awesome can be used instead of icons. Image files that will be used in the icon properties for actions and visual components, e.g. You should not specify the path to favicon.ico, since it must be located in the root directory of the theme. LoginWindow.logoImage = branding/myapp-login.png LoginWindow.welcomeLabel = Welcome to MyApp! Message packs allow you to use different image files for different user locales.Īpplication.logoImage = branding/myapp-menu.png These parameters are saved in the main message pack of the gui module (i.e the modules/gui//gui/messages.properties file and its variants for different locales). Other links can be used to set window captions and the login The path is specified relatively to the theme directory. Set the paths to icon files for application and login window using Set application logo image and Set login window logo image links. Open Project properties > Edit in CUBA Studio and click Branding at the bottom of the page. Here, havana is the directory of the theme, favicon.ico is the website icon, myapp-login.png - login window logo image, myapp-menu.png - main window logo image. Create the following files structure in the modules/web directory of the project: