Forums

Home » Liferay Portal » English » 2. Using Liferay » General

Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Thorben V
Default landing page not working
September 15, 2008 2:32 AM
Answer

Thorben V

Rank: New Member

Posts: 8

Join Date: March 5, 2008

Recent Posts

Hello!

It seems that I cannot forward the users to a default community. In my installation every user is member of the xyz community. I'd like the user to be redirected to the first page in the private community of xyz. Therefore I added the following lines to the portal-ext.properties:

default.landing.page.path=/group/xyz/page1
auth.forward.by.last.path=true

I does not have any effect at all. After login in the user is still on the login page. Am I using these statements in the wrong way? I'm using Liferay 5.1.1 on Tomcat 6.0.18.

Thanks for any help.

Thorben
Isabel M
RE: Default landing page not working
October 10, 2008 12:59 PM
Answer

Isabel M

Rank: Junior Member

Posts: 37

Join Date: April 23, 2008

Recent Posts

If you installed Liferay in context other than root you need to include the context in your default landing page path. For example if Liferay is in /portal instead of the default "/" your settings will be:

default.landing.page.path=/portal/group/xyz/page1
auth.forward.by.last.path=true


This worked for me. Hope it helps someone.

Isabel
Scott Palmer
RE: Default landing page not working
March 22, 2011 6:48 PM
Answer

Scott Palmer

Rank: Junior Member

Posts: 36

Join Date: January 8, 2010

Recent Posts

After upgrading to Liferay 6EE SP1 this appears to have stopped working. Is anyone else having the same issue?
Scott Palmer
RE: Default landing page not working
June 14, 2011 8:22 PM
Answer

Scott Palmer

Rank: Junior Member

Posts: 36

Join Date: January 8, 2010

Recent Posts

Scott P:
After upgrading to Liferay 6EE SP1 this appears to have stopped working. Is anyone else having the same issue?


FYI If you are using EE 6 SP1 with basic auth enabled then the default landing page property does not work. It's a bug. Best bet is to request a patch.