How to ...

Note about fragment-definitions and fragment-layouts in uPortal 4.2

Since uPortal 4.2 supports both Respondr AND universality/mUniversality, and there will be users coming up from uPortal 4.0 that have existing layout files that uPortal 4.1 will need to support, we needed to retain the existing file names but insure Respondr-specific layouts do not mess up sites that use Universality. Also as a convenience to the developers, we want to be able to have both layouts present and be able to flip from one theme to another without having to rebuild, redeploy, or alter data.

Our convention in naming for fragment-definition and fragment-layout files in the quick-start data: *respondr* means the file applies only to Respondr

Revise above and below for uPortal 4.2 to remove universality, and combine fragments since universality is no longer supported.

So for example in the quick-start data:

User	Applied fragment-layouts	Description
guest	all-lo	Applies to everyone (guest and authenticated users) for both Respondr, Universality, and mUniversality
	respondr-lo	Applies to everyone (except tenants that have their tenant-specific skin) if the Respondr theme is the one being used
	guest-lo	Applies to all guests for both Respondr, Universality, and mUniversality
	guest.respondr.lo	Applies to all guests if the Respondr theme is the one being used
authenticated user	all-lo	Applies to everyone (guest and authenticated users) for both Respondr, Universality, and mUniversality
	respondr-lo	Applies to everyone (except tenants that have their tenant-specific skin) if the Respondr theme is the one being used
	authenticated-lo	Applies to all authenticated users for both Respondr, Universality, and mUniversality
	authenticated.respondr.lo	Applies to all authenticated users if the Respondr theme is the one being used