liferay,liferay-6,liferay-theme
It would be helpful to see your portal_normal.vm, to give you the exact solution. But if you don't want the super secret theme development to leak out, then check if you have the following code in your portal_normal.vm file: <div class="container-fluid" id="wrapper"> <div class="row-fluid"> <div class="span12" id="content-wrapper"> <div id="content"> #if...
liferay,liferay-6,liferay-theme
You can apply theme to a page using following below steps. Control Panel Select your Site from left Panel(By default it would site from which you accessing Control Panel) Click on Site Pages Click on Page Name to which you want to apply theme (Public or Private) Select Look and...
liferay,liferay-6,liferay-theme,liferay-ide,liferay-velocity
I assume this code is in an action method or processAction method. Instead of re-directing from action-phase directly it would be better to use actionResponse.sendRenderParameter("jspPage", LibraryConstants.PAGE_SUCCESS) to set the jspPage to be rendered through the render or doView method. Also it would be helpful to check the sendRedirect documentation, where...
liferay,hook,liferay-6,portlet,liferay-theme
1.) You can migrate your data via the Control Panel. Navigate to Server Administration, there is a tab: Data Migration. You provide the credentials of the new Database and hit submit. That's all. 2.) I do not undstand your 2.nd Question to be honest.
liferay,liferay-6,liferay-theme
The below portal property fixed it. default.user.private.layout.regular.theme.id=mycustomtheme_WAR_mycustomtheme...
liferay,liferay-6,freemarker,liferay-theme
Pankaj Kathiriya was right :) The answer is : <#if (request.getParameter("param")?has_content && request.getParameter("param")?lower_case?matches("true"))> <#assign useServer = "http://bing.com"> <#else> <#assign useServer = "http://google.com">...
liferay,liferay-6,liferay-theme,liferay-velocity
I think you need to add hi_IN language as Available Languages in Portal Settings if it is already not there. To add this/or verify go to Control Panel --> Portal Settings --> Display Settings here you will find a input box Available Languages which shows all available locales (comma seperated),...
liferay,liferay-6,portlet,liferay-theme
The first thing that you lose control over in the portlet world is your URLs. If you request your jsp files through servlet requests (like you mention in the comments to your question), you'll have a servlet request that obviously bypasses the portal (portal requests would be generated through <portlet:actionURL...
java,jsp,liferay,liferay-theme
Yes, it's possible to override a taglib implementation with a jsp-hook (I've just tested it with the outstanding update to my custom navigation app, with exactly the jsp you mention). However, if you can solve your problem with css, I find that this is the more advisable solution. CSS is...
Menu collapses by default for phone and tablet viewports. You can create your own button to open/close collapsed menu in phone/tablet viewport. Check following simplified example: Theme velocity template: #if(!$is_signed_in) <div id="mainNavigationToggle" class="btn btn-secondary"> <i class="icon-reorder"></i> </div> #end Theme main.js: AUI().ready(function (A) { var navigationToggleBtn = A.one('#mainNavigationToggle'); // get our...
liferay,liferay-6,liferay-theme
groupId is typically the current site that is displayed and typically the same as scopeGroupId. However, content in Liferay can be "subscoped" to individual pages. You can find this in the configuration screen of several portlets. Thus, the data is not associated directly with the site (aka group), but with...
liferay,liferay-6,liferay-theme
I too analyzed ServicePreAction code, and found that all this code does is: checks if the user is logged in or not if yes, shows 'sign out' link, not otherwise You can simply create a hook to override html/portlet/dockbar/view_user_account.jspf to either remove that code snippet from this jsp to hide...
It's the name: You don't use content/Language*.properties, but just content/Language.properties. Otherwise I believe you're on the correct way to solve the problem, it's just this little detail
liferay,liferay-6,liferay-theme
I exactly don't know what solved it but here is what I did: Replaced the ROOT.war with a fresh installation. (I had done this previously). Removed jboss's tmp folder. (I had also done this before) Removed *.tmp files and liferay folder from /tmp/ folder of linux. Removed other different previous...
liferay,liferay-6,liferay-theme
Depending on the requirement, there are following two ways to check whether the logged in user is an admin user or not: Show dockbar to all the admin users: #if ($is_signed_in && $permissionChecker.isOmniadmin()) #dockbar() #end Show dockbar to specific admin user(s) based on role-name: #set($showDockBar = false) #foreach($role in $$themeDisplay.getUser().getRoles())...
liferay,liferay-6,liferay-theme
After few hours consumed on analyzing our portal environment finally I managed to solve it. Here is the reason of such strange problem: It turns out, the information about main parent theme (the one which can be inherited on child pages) is stored in different places for such options enabled...