sitemap segmentation based on locale

How do you create a segmentation rule based on locale of the current user

Find more posts tagged with

Comments

Sorry, but RTFM, SitePub Dev guide. It's somewhat documented as the "verbalization" chapter. (assuming that's not a OOTB condition.. I don't have a build to check atm)

Read up on that and if you're still confused, post a more specific question. Don't forget to state your TS version.

leec

RTFM

RTM maybe, we've not even been introduced!

I've read the crazy stuff around verbalisation with increasing dismay, what a dogs diner. Anyway

[Bean Object="context"]
[Path]pageName[/Path]
[/Bean]

So setting up say country of a users locale implies
context.getLocale().getCountry()
which in turn is represented by

[Bean Object="context"]
[Path]Locale.Country[/Path]
[/Bean]

or should i be using method calls (i don't think so, assuming its like the page token stuff)

Anyway its not quite working

Rick Poulin

RTM maybe, we've not even been introduced!

Sorry, no offense intended. The trouble with acronyms is it's easy to forget what the individual letters stand for Smiley Happy

So setting up say country of a users locale implies
context.getLocale().getCountry()
which in turn is represented by

[Bean Object="context"]
[Path]Locale.Country[/Path]
[/Bean]

I think you're on the right path, though your syntax confuses me. You'll find examples here, which is where you want to create your "user locale" condition.
/iwadmin/main/livesite/config/WORKAREA/shared/rules/verbalizations/conditions/

Your bean.path is almost correct, but you want lower case "locale.country". That's just a java bean notation thing. Note that this returns the two-letter country code (e.g. "US"), so if you wanted to match on the full name of the country, you'd want "locale.displayCountry" (e.g. "United States").

One more side note is that context.getLocale() can be configured to compute a locale based on different things, and this thing is NOT the user's browser's preferred locale by default. If you *always* want to segment based on the browser's perferred locale, then you want context.getBrowserClientRequestLocale(), which means you want bean.path=browserClientRequestLocale.country.

leec

As it turns out verbalisation files must have .xml suffix

Works now.

As an aside how many active segments can a site have. The Doc's seem to suggest 8(?) If I give access to creating segments to our business unit they will go mental and will try and create hundreds for sure. What seems to be the practical limit ? sites will be under load (but are on chunky machines)

tr3_test.rptdesign

Rick Poulin

As far as I know, there is no 'hard' limit. I have read the "8 segments per site" recommendation somewhere (SitePub dev guide maybe), but that's like the "max 12 components per page". It's a soft ballpark figure for optimal performance. You page can easily have 30 components on it, if caching is on and they don't all run off to externals to compute the value of pi. Similarly, if your segments do very quick and basic checks, then going to 25 might not be so bad. Hundreds is almost certainly a bad idea (every segment in the site is evaluated for every page request, so performance can quickly become a big issue).

Just remember your use cases and evaluate whether segments is really the right solution. Segments are meant for creating large groups of users. You shouldn't have segments that only apply to 2-3 end users. If your use cases go more granular than 10ish groupings of users, then consider building your sitemap dynamically rather than by hand -- perhaps using a combination of rules and LSCS queries. If that still doesn't suffice, then what you're looking for is a portal, which LiveSite definitely is not.