nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

my LS/SP gripes

nipper

A couple of points from what I have seen with SP/LS. It is funny that there is some really cool functionality and yet some (seemingly) minor (and common) functionality has been left out.

Web servers have the concept of default datatype so that if I enter /some/path/ it will look for index.html (or whatever) and display. This is 1990's technology and yet LS cannot do something as simple as if I use /some/site/path/ default to index.page.

Since we have a mix of HTML pages and SP we cannot do a mass rewrite and our apache config looks quite ugly.

The other being that the finish button in SP cannot start a WF - which templates have supported since 2000 or so.

Andy

Find more posts tagged with

Comments

vpatel

Web servers have the concept of default datatype so that if I enter /some/path/ it will look for index.html (or whatever) and display. This is 1990's technology and yet LS cannot do something as simple as if I use /some/site/path/ default to index.page.

You should be able to just add "index.page" and / or "default.page" into the configuration file (web.xml) and it should work just fine. I have never tried it myself with LiveSite but have done it with app servers in general many times. I would bet that it will work. You need something like this:
<welcome-file>index.page</welcome-file>.

I do agree that this simple configuration could be done OOTB. Sounds like a FR.

Since we have a mix of HTML pages and SP we cannot do a mass rewrite and our apache config looks quite ugly.

Can you please provide a bit more detail on this one? I have done something similar with relative ease -- just trying to see your use case in more depth.

The other being that the finish button in SP cannot start a WF - which templates have supported since 2000 or so.

This works in CC Std but somehow left out in CC Pro. There maybe -- just maybe -- a way to "hack" it for CC Pro since its working in CC Std. Again sounds like a FR opportunity here :-)

nipper

You should be able to just add "index.page" and / or "default.page" into the configuration file (web.xml) and it should work just fine. I have never tried it myself with LiveSite but have done it with app servers in general many times. I would bet that it will work. You need something like this:
index.page.

I do agree that this simple configuration could be done OOTB. Sounds like a FR.

Follow the instructions Building a Toolkit in the LS manual ? I will try it

This works in CC Std but somehow left out in CC Pro. There maybe -- just maybe -- a way to "hack" it for CC Pro since its working in CC Std. Again sounds like a FR opportunity here :-)

Weird, but thanks. We were not planning to use CC-STD but may have to. I already filed a FR and the support doofus did not know that it works for STD and not for Pro

vpatel

You should be able to just add "index.page" and / or "default.page" into the configuration file (web.xml) and it should work just fine. I have never tried it myself with LiveSite but have done it with app servers in general many times. I would bet that it will work. You need something like this:
index.page.

I do agree that this simple configuration could be done OOTB. Sounds like a FR.
Follow the instructions Building a Toolkit in the LS manual ? I will try it

No, I do not believe LS TK will be the way to go here -- it may be but I do not believe so. You'll have to go over to LS Runtime server and make that edit manually in the "web.xml" file.

Alternatively (I just thought of this -- is it Friday yet?), you could do this without this web.xml config, rather use the OOTB URL Alias functionaliy :-)!

vpatel

Ah -- on the second thought I think the default/index.page in web.xml may not work because LS has its logic where if a page/URL is not found under the /sites path then it'll take you the "error" page or the "home/start" page defined for the site. This logic may precede/override the web.xml settings.

So your option may be to just go with URL Alias for now + file a FR.

nipper

Ah -- on the second thought I think the default/index.page in web.xml may not work because LS has its logic where if a page/URL is not found under the /sites path then it'll take you the "error" page or the "home/start" page defined for the site. This logic may precede/override the web.xml settings.

So your option may be to just go with URL Alias for now + file a FR.

The URL alias idea is for SP only correct ? We have people with bookmarks (or just typed in) /blah.com/some/folder/ , will that work with a URL alias ?

vpatel

The URL alias idea is for SP only correct ? We have people with bookmarks (or just typed in) /blah.com/some/folder/ , will that work with a URL alias ?

No - URL alias will work in LS Runtime as well. Yes you can have a user go to an URL like: http://www.mysite.com/some/path and through the URL Alias mapping have it map to /sites/some/my.page.

There are a few rules to adhere by when you create aliases though. It can only point to SP pages and NOT some external URL, each alias must be unique within the site, etc. You can see the full thing in the manuals.

HTH!

tanguyr

Ah -- on the second thought I think the default/index.page in web.xml may not work because LS has its logic where if a page/URL is not found under the /sites path then it'll take you the "error" page or the "home/start" page defined for the site. This logic may precede/override the web.xml settings.

So your option may be to just go with URL Alias for now + file a FR.

Edit: OOOOPS, my bad, we tried this and it didn't work. We use a custom 404 handler jsp for this.