Liferay 7.0.6 CE Staging page URL

Ervinas Marocka, modified 6 Years ago. Junior Member Posts: 31 Join Date: 10/8/18 Recent Posts
Hello,I'm currently staging everything to the site. Staging completes and somehow in some places, where asset publisher has an article in which there are several URLS to other pages (in articles there are targets to other pages urls, redirects), somehow liferay changes the redirecting page target url. For example: the article has a text with a redirect to : "https://example.com/web/example" and after staging in live site this redirection becomes : "https://example.com/web/guest_data_handler_path_context@/web/guest_data_handler_path_context@....../example" Why is it doing like so?Was looking the logs, everything i can see is during export : [BaseTextExportImportContentProcessor:837] Unable to process layout URL /guest/exampleHow can I identify the problem? Or maybe someone knows the thing here? Thanks.
thumbnail
Olaf Kock, modified 6 Years ago. Liferay Legend Posts: 6441 Join Date: 9/23/08 Recent Posts
Ervinas Marocka:

Hello,I'm currently staging everything to the site. Staging completes and somehow in some places, where asset publisher has an article in which there are several URLS to other pages (in articles there are targets to other pages urls, redirects), somehow liferay changes the redirecting page target url. For example: the article has a text with a redirect to : "https://example.com/web/example" and after staging in live site this redirection becomes : "https://example.com/web/guest_data_handler_path_context@/web/guest_data_handler_path_context@....../example" Why is it doing like so?Was looking the logs, everything i can see is during export : [BaseTextExportImportContentProcessor:837] Unable to process layout URL /guest/exampleHow can I identify the problem? Or maybe someone knows the thing here? Thanks.
smells like an issue with template processing to me. E.g. @data_handler_path_context@ would make more sense to me than _data_handler_path_context@
However, this is nothing more than a very wild guess. I haven't seen this problem.
What happens with local staging, is that you get a staging site, with a different name (from memory: example.com/web/example-staging) and naturally absolute links should be rewritten to point to content relative to the staging site, to stay in the same context.
Maybe this rings a bell to someone who has seen it before?
Ervinas Marocka, modified 6 Years ago. Junior Member Posts: 31 Join Date: 10/8/18 Recent Posts
I've found the solution. Not sure how it becomes like that, but maybe if staging process can't find a page which is referenced inside an article, it calls like guestdata_handler_path_context@. Not sure. I replaced url in the articles without no /guest urls and it staged okay. There is an additional problem with "no portletpreferences exists with the key". I have staged everthing. AssetCategories, webarticles, tags. Everything related with this. But it saying in logs that during export there is no portletpreferences exists with the key. Not sure. Maybe there is something to enable way more detailed logging? I've switched to DEBUG on all exportimport, lar, com.liferay classes.