LiveSite 7.4.1 aliases not working

Hi All,

For those of you that are testing LiveSite 7.4.1, do site map aliases work for you?

We just get the default site error page for any alias.

For example, directly accessing LiveSite using the following URL patterns:

http://{host}:{port}/{site} - returns the default page for the site.
http://{host}:{port}/{site}/{alias} - returns the site error page.
http://{host}:{port}/{site}/{alias}.page - returns the raw page XML (Note: This works in this case because often our URL aliases match the page paths).
http://{host}:{port}/sites/{site}/{alias}.page - returns the raw page XML.

The aliases within the site's default.sitemap are in the format: {site}/{alias}.

Because http://{host}:{port}/{site}/{alias}.page also returns the .page XML, it seems to indicate there's already some remapping happening - inserting the missing "/sites" in the path.

The same site structure and site map file worked on LiveSite 7.3.1.

The default site page renders correctly, so I suspect the problem is to do with the URL alias parsing.

I'll keep investigating, but if anyone has any suggestions, I'd love to hear it.

Cheers.

Find more posts tagged with

Comments

Rick Poulin

Edit: misread some of the information you posted.

My suggestion would be to turn on debug logging for classes such as the RenderingManager, RuntimeRenderingManager and URLParser and see what that output looks like.

Garth McMillan

Just a follow-up. I got our aliases working by overwriting the com.interwoven.livesite.runtime.URLParser class to set the mIsAlias property to true where appropriate (when a URL matches the alias pattern).

I need to do some more investigating because, from what I can tell, the behaviour between 7.3.1 and 7.4.1 appear similar. So I'm not sure why this is needed - 7.3.1 must be determining a URL is an alias somewhere not obvious.

Just a bit more information, if anyone is interested:

The reason I could fix the issue by changing the URLParser mIsAlias property is because in RuntimeRenderingManager.doSetupPageName() it checks if that property is true and then gets the page names etc. using aliases. However, it doesn't look as though the property ever gets set to true - it just remains as the default false. However, from my look at 7.3.1, it also doesn't seem to set that property to true, so I don't know... I need to research some more.

The regular expressions to match aliases have been changed between 7.3.1 and 7.4.1, in that the siteName property in 7.4.1 is set as "{site}" whereas it’s "/{site}" in 7.3.1. However, the full path to the .page regex (which works in 7.4.1) also sets it as "{site}", so that’s probably not related.

Bowker

Are you using segmentation? There are issues with aliases and segmentation that a simple-to-install-patch has been created.

Untitlednew.png

Garth McMillan

No. We're not using segmentation.

I'm hoping to spend a bit more time investigating the issue next week. I'll continue updating this thread if I find anything useful.