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
RE: Direct web content is not displayed after the upgrade from 7.1.2 to 7.1
Hi guys,
We are testing the Liferay update from the current version we have, the 7.1.2 GA3, to the 7.1.3 GA4. After launching the usual process described in the documentation (in local) everything seems to go correctly unless the direct web contents we already had(eg: http: // localhost: 8080 / - / post/1) are not displayed, instead we get a 404 and nothing in the logs.
We have reviewed issues, forum etc but we did not find anything. Any ideas?.
Thanks in advance.
We are testing the Liferay update from the current version we have, the 7.1.2 GA3, to the 7.1.3 GA4. After launching the usual process described in the documentation (in local) everything seems to go correctly unless the direct web contents we already had(eg: http: // localhost: 8080 / - / post/1) are not displayed, instead we get a 404 and nothing in the logs.
We have reviewed issues, forum etc but we did not find anything. Any ideas?.
Thanks in advance.
Hi,I update myself ...
There seems to be a problem when the "/" character is added to the friendly url of a content. The closest thing I see in the Jira is https://issues.liferay.com/browse/LPS-88501 but it does not fit me because I'm with a version 7.1.3 GA4 : /
Regards
There seems to be a problem when the "/" character is added to the friendly url of a content. The closest thing I see in the Jira is https://issues.liferay.com/browse/LPS-88501 but it does not fit me because I'm with a version 7.1.3 GA4 : /
Regards
Hi,
I update myself ...
The problem seems to have been introduced in this commit https://github.com/liferay/liferay-portal/commit/9aeb8232215ff5331bdf6ff303a76b54d9524ed8#diff-88404608066b298ac8f681687363f86b. The intention seems to have been to add one more parameter, the ddmTemplateKey, however the result has been that you can not have friendly urls like this: http: // localhost: 8080 / - / post / 1. Am I right or does something escape me? Is it a bug? By the way, it seems that it also affects 7.2.
Regards
I update myself ...
The problem seems to have been introduced in this commit https://github.com/liferay/liferay-portal/commit/9aeb8232215ff5331bdf6ff303a76b54d9524ed8#diff-88404608066b298ac8f681687363f86b. The intention seems to have been to add one more parameter, the ddmTemplateKey, however the result has been that you can not have friendly urls like this: http: // localhost: 8080 / - / post / 1. Am I right or does something escape me? Is it a bug? By the way, it seems that it also affects 7.2.
Regards
Hi Javier,The commit you have pointed out generates the following regression:https://issues.liferay.com/browse/LPS-96209
Do you think is the same case than yours?Thanks.
Do you think is the same case than yours?Thanks.
Hi Alberto,
Yes, it is the same case. I need a master class to search for issues in the Jira of Liferay
Thanks for the reply!.
Yes, it is the same case. I need a master class to search for issues in the Jira of Liferay
Thanks for the reply!.
Hi Javier,
No worries, I found it because I remember a case like yours. That fix hasn't been included in an official release yet but these are the changes needed for solving it:
https://github.com/brianchandotcom/liferay-portal/pull/74114/files#diff-c390ac9e0875dc7752601ec6dd4939e8
If you need to modify the current friendlyUrls in the database (I guess no because you are still pending to upgrade) maybe you can execute the previous logic via a groovy script.
https://github.com/brianchandotcom/liferay-portal/pull/74114/files#diff-a5276e9721732e5419b5f8f32e161cb5
You should extend the service to Normalize the friendlyUrl as we do in the previous commit (you could also use a listener or something like that)
Please, let me know if this solves the issue or you have any problem with it.
Cheers!
No worries, I found it because I remember a case like yours. That fix hasn't been included in an official release yet but these are the changes needed for solving it:
https://github.com/brianchandotcom/liferay-portal/pull/74114/files#diff-c390ac9e0875dc7752601ec6dd4939e8
If you need to modify the current friendlyUrls in the database (I guess no because you are still pending to upgrade) maybe you can execute the previous logic via a groovy script.
https://github.com/brianchandotcom/liferay-portal/pull/74114/files#diff-a5276e9721732e5419b5f8f32e161cb5
You should extend the service to Normalize the friendlyUrl as we do in the previous commit (you could also use a listener or something like that)
Please, let me know if this solves the issue or you have any problem with it.
Cheers!
Hi Alberto,
On modifying the urls in database, I think it is easier to upgrade and then change the urls with the groovy script that you propose.
About the service, we will study it, perhaps the listener is the best option.Thank you very much for the reply!.
Regards..
On modifying the urls in database, I think it is easier to upgrade and then change the urls with the groovy script that you propose.
About the service, we will study it, perhaps the listener is the best option.Thank you very much for the reply!.
Regards..
Copyright © 2025 Liferay, Inc
• Privacy Policy
Powered by Liferay™