Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
- Home
- General
- Bug Report
- RE: when going to a user's personal page, an error appears: 404 page not found
RE: when going to a user's personal page, an error appears: 404 page not found
Hi all, I encountered a problem, when I try to open my user profile
or dashboard I get a proper redirect to the selected page, but instead
of content I see the message: page not found404.
Although in the
user's page manager these pages exist and there is no error in the
system logs.
Initially I thought that it was my portlets and
custom hooks breaking this transition, but running "clean"
liferay I still saw this error. I tried changing versions of liferay
from 7.4.3.65 to 7.4.3.89, but I got the same error everywhere.
P.s I tried enabling the Disable Private Pages option located in
control panel->system settings-> Release Feature Flags, but it
didn't fix the error.
BUT by running lifere together with tomcat this error disappeared.
This gave me an idea to take an older version of lifere, more precisely 7.3.x and see the result. As it turned out, in version 7.3 running on wildfly this error is also absent.
After that I concluded that most likely it is a system error when
working with wildfly. In order to better understand what the error is
I decided to include absolutely all logs of the portal and compare the
data received from the system running in tomcat and wildfly.
After
a careful study of the logs I found that when the system is deployed
on the wildfly server, when I go to the pages of the personal site I
get this error:
com.liferay.portal.kernel.exception.NoSuchLayoutException: User
layouts cannot be accessed via p_l_id.
This means that either the
user is unlogged, or the http method of the request does not match, or
the p_l_id from the database matches the system p_l_id.
In order
to better understand the error and ways to fix it, now I'm trying to
start the portal with my modified portal-impl module, but since I'm
new to this I'm not quite getting it(
Hi Ivan,
I was able to reproduce your issue in GA89 using WIldfly but was unable to in Master. Can you retest on a later version such as the newly released GA100 and see if it works for you now?
Powered by Liferay™