portal-ext.properties problem in 5.1.1

[Mark Mey Fedalizo Atil, modificado 15 Anos atrás.]

why cant my default theme in portal-ext.properties wont load??

the code is this

##

#
# Set this to false if the system does not use allow users to modify the
# look and feel.
#
look.and.feel.modifiable=false

#
# Set the default layout template id.
#
default.layout.template.id=2_columns_ii

#
# Set the default theme id for regular themes.
#
default.regular.theme.id=crystalx

#
# Set the default color scheme id for regular themes.
#
default.regular.color.scheme.id=01

#
# Set the default theme id for wap themes.
#
default.wap.theme.id=mobile

#
# Set the default color scheme id for wap themes.
#
default.wap.color.scheme.id=01

#
# Set this to true if you want a change in the theme selection of the public
# or private group to automatically be applied to the other (i.e. if public
# and private group themes should always be the same).
#
theme.sync.on.group=false

##

is there any bugs in 5.1.1?

[Ray Augé, modificado 15 Anos atrás.]

You must use the fully qualified theme name, this includes the war
application name in which the theme is deployed.

The easiest way to obtain this is from the theme selection screen and
view source... (I know this is pretty lame...).

It looks something like "flange_WAR_flangetheme" where "flange" is the
themeid, and flangetheme is the theme WAR (minus underscores, spaces and
dashes).

So, there are two different issues here:

1 - the properties file should hint at this particular point.
2 - there should be an easier way to get the FQTI (Fully Qualified Theme
Id)

HTH!

[Ray Augé, modificado 15 Anos atrás.]

Here are some new hints I've added to the portal.properties file:

    #
    # Set the default theme id for regular themes.
    #
    # Note: When using a plugin themes, the theme id must be the fully qualified 
    # theme name. This takes the form of 
    #    
    #     themeId_WAR_webapplicationcontext
    #
    # The webapplicationcontext will have spaces, underscores and dashes 
    # stripped away.
    #
    default.regular.theme.id=classic
...

    #
    # Note: When using a plugin portlets, the portlet id must be the fully 
    # qualified portlet name. This takes the form of 
    #    
    #     portletId_WAR_webapplicationcontext
    #
    # The webapplicationcontext will have spaces, underscores and dashes 
    # stripped away. The portlet id may also require an instance id. The 
    # instance id can be made up, and is a 4 char alphanumeric string.
    #
    default.guest.public.layout.column-1=58
...

(I actually forgot to add that periods will also be stripped.)


So, if you have a portlet/theme deployed in a WAR context [tt]/my-war-1.3.7[/tt]

the FQTI (Fully Qualified Theme Id) for a theme called [tt]theme1[/tt] will be:

[tt]theme1_WAR_mywar137[/tt]

the FQPI (Fully Qualified Portlet Id) for portlet called [tt]portlet1[/tt] will be:

[tt]portlet1_WAR_mywar137[/tt]


Let's hope these hints survive review.

[Mark Mey Fedalizo Atil, modificado 15 Anos atrás.]

ok i'll try to use your code

if something happens, good or bad i'll contact you

tnx ray

[Mark Mey Fedalizo Atil, modificado 15 Anos atrás.]

w8

is this code will work on liferay 5.1.1??

[Ray Augé, modificado 15 Anos atrás.]

yup!

[Mark Doerr, modificado 15 Anos atrás.]

I'm having the same issue with default.layout.template.id. i've tried using my custom layout's id in about every I can figure out and it doesn't work.

Assuming my layout template is called "foo", I've tried

• default.layout.template.id=foo-layouttpl (as it appears on the Enterprise Admin Portlet)
• default.layout.template.id=foo_WAR-foolayouttpl (applying what Ray Augé suggests for themes in this thread)
• default.layout.template.id=foo (because it seemed a reasonable guess at this time)

None of these seemed to work

Liferay 5.1.2 on Tomcat 5.5.26.

[Lari Tuominen, modificado 15 Anos atrás.]

Hi Mark. Here's some information:

http://www.liferay.com/web/guest/community/forums/-/message_boards/message/1496740

In addition

foo_WAR-foolayouttpl (applying what Ray Augé suggests for themes in this thread)

compared to

foo_WAR_foolayouttpl

Hope this helps.

- Lari

[Mark Doerr, modificado 15 Anos atrás.]

Ah yes. That was a typo in the post, but not a typo in the properties file. And just to make sure, I tried it again using the correct foo_WAR_foolayouttpl just to be sure and still no go.

[Kyrre Myrbostad, modificado 14 Anos atrás.]

Struggling with the same issue here. My theme is recognized using the suggested syntax, but my layout is not.

- Template id is "ntnu_3_column" taken from liferay-layout-templates.xml in the war file
- Display-name is "NTNU-3-column-layouttpl" taken from web.xml

The layout is visible and selectable in the admin GUI, and works fine.

... so i try this:

default.layout.template.id=ntnu_3_column_WAR_NTNU3columnlayouttpl

My portal-ext.properties file is read properly, but nothing seems to happen. Can't find anything in the logs either, allthough im not sure what logging parameter to tweak to get more info.

Mark, could I ask if you have solved your issue?

I have even tried using the EXT-environment to avoid the naming scheme, but still the default.layout.template.id seems hard-wired to 2_columns_ii

My solution so far has been to simply redefine the content of 2_columns_ii in liferay-layout-templates.xml. Very ugly, but it works...

[Aarti Jain, modificado 14 Anos atrás.]

Hi Kyrre,

You need not apply the syntax that you applied to theme in the case of layouts.

Just take out the template id from \webapps\3-2-3-columns-layouttpl\WEB-INF\liferay-layout-templates.xml and set in portal-ext.properties. In your case it will be:

default.layout.template.id=ntnu_3_column

Regards,
Aarti Jain
Impetus Infotech Pvt. Ltd.
Noida

[Kyrre Myrbostad, modificado 14 Anos atrás.]

Hi Aarti,
thanks for your reply. I tried that first however, before I used the abovementioned syntax.

Still every time I made a new page it was with 2_columns_ii.

Strange indeed...

[Aarti Jain, modificado 14 Anos atrás.]

Hi Kyrre,

I agree to you.

This is the way devised by liferay to change the default layout template but its not working.I think its a bug.

Instead of making changes to the content of 2_columns_ii template you can try by changing this property directly in portal.properties file in portal-impl.jar. I have not tried it but may be your problem gets solved.

Regards,
Aarti Jain
Impetus Infotech Pvt. Ltd.
Noida

[Mark Doerr, modificado 14 Anos atrás.]

Kyrre Myrbostad:

Mark, could I ask if you have solved your issue?

I have even tried using the EXT-environment to avoid the naming scheme, but still the default.layout.template.id seems hard-wired to 2_columns_ii

My solution so far has been to simply redefine the content of 2_columns_ii in liferay-layout-templates.xml. Very ugly, but it works...

I have not had any success. but I will give your suggestion a try. I wonder if a JIRA issue would get more response on the subject.

[Mikko Väänänen, modificado 14 Anos atrás.]

My workaround for setting default layout id is here:

public class LayoutListener extends BaseModelListener<layout> {
	@Override
	public void onBeforeCreate(Layout model) throws ModelListenerException {

		// workaround for default.layout.template.id which doesn't work in 5.2.3
		model.getTypeSettingsProperties().setProperty("layout-template-id",
				"1-3-columns");
	}
}</layout>

Then that listener is registered in portal-ext.properties in property value.object.listener.com.liferay.portal.model.Layout. Works using ext. That could be of course improved by reading the layout id from property file instead of hard coding it.

//Mikko

[Rocco Germinario, modificado 14 Anos atrás.]

Hi all,
I found a simpler workaround: just set both default.layout.template.id and layout.default.template.id

I think that this is a bug so I reopened LEP-5361 on JIRA.

[Mark Doerr, modificado 14 Anos atrás.]

Rocco Germinario:

Hi all,
I found a simpler workaround: just set both default.layout.template.id and layout.default.template.id

I think that this is a bug so I reopened LEP-5361 on JIRA.

<Snarky_Comment>And why are there two properties with virtually identical names? </Snarky_Comment>

[Thomas Kellerer, modificado 13 Anos atrás.]

Rocco Germinario:

Hi all,
I found a simpler workaround: just set both default.layout.template.id and layout.default.template.id

I think that this is a bug so I reopened LEP-5361 on JIRA.

Still doesn't work for me.

The Layout is not selected when I create a new page, even when I add both properties to portal-ext

Any ideas how I could deifne a default layout for new pages?

[Thomas Kellerer, modificado 13 Anos atrás.]

Thomas Kellerer:

Rocco Germinario:

Hi all,
I found a simpler workaround: just set both default.layout.template.id and layout.default.template.id

I think that this is a bug so I reopened LEP-5361 on JIRA.

Still doesn't work for me.

Sorry, was my fault. I edited the wrong portal-ext.properties.

[Chris Rail, modificado 13 Anos atrás.]

Setting the default Theme and default Template Layout does not work for me either. Neither of these functionalities work for me, and it kills productivity. I followed every tutorial / workaround I could find. No success.

I own both the Liferay Portal 6 Enterprise Intranets and Liferay User Interface Development books, and neither helps with this topic.

On this note, I've yet to discover a reference for files like portal-ext.properties and look-and-feel.xml. Does anyone know if such a reference exists?

Any further insight is greatly appreciate.

Thanks yous!

[Leo Gong, modificado 12 Anos atrás.]

Rocco Germinario:

Hi all,
I found a simpler workaround: just set both default.layout.template.id and layout.default.template.id

I think that this is a bug so I reopened LEP-5361 on JIRA.

I'm using liferay6.06, and still found this bug. I just set layout.default.template.id=type82 and it works ."type83" is my template id in liferay-layout-templates.xml.