[#UP-1897] Re-evaluate the balance of duties between user- and layout-oriented scripts

uPortal

Re-evaluate the balance of duties between user- and layout-oriented scripts

Created: 10/Jan/08 04:04 PM Updated: 18/Apr/08 10:52 AM

Component/s:

Import / Export

Affects Version/s:

None

Fix Version/s:

3.0.0

Original Estimate:	Unknown	Remaining Estimate:	Unknown	Time Spent:	Unknown
File Attachments:	1. userProfileExport.patch (27 kb)

Description

« Hide

uPortal (as I understand it) is capable of generating a layout (from uPortalTemplateUsername) for a user who doesn't have one. It should be the case, therefore, that when a user in imported but no layout is imported for him/her, the uPortal infrastructure will generate a layout based on template user per-normal.

It isn't working this way at the moment. If you want to import a user, you *must* also import a layout, else the user won't be able to log in and use the portal.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Eric Dalquist [11/Apr/08 01:06 PM]

I created a user via md5password and then logged in as that user. The login results in the following entries being created for the user:

In UP_USER

USER_ID	USER_NAME	USER_DFLT_USR_ID	USER_DFLT_LAY_ID	NEXT_STRUCT_ID	LST_CHAN_UPDT_DT
14	edalquist	1	1	8	<null>

In UP_USER_PROFILE

USER_ID	PROFILE_ID	PROFILE_NAME	DESCRIPTION	LAYOUT_ID	STRUCTURE_SS_ID	THEME_SS_ID
14	1	HTML browser profile	A sample profile for common web browsers	<null>	<null>	<null>

[ Permlink | « Hide ]

Eric Dalquist [11/Apr/08 01:09 PM]

(continuing previous comment)

The USER_DFLT_LAY_ID NEXT_STRUCT_ID values from from the portal template user.

With this information I think the <profile> block in the .user entity files should be moved into the .layout files and the .layout files. The import-user script will just create a stub in UP_USER_PROFILE and the import-layout script will take care of the structure and theme params associated with the profile.

[ Permlink | « Hide ]

Eric Dalquist [11/Apr/08 01:14 PM]

Drew,

I'd like to get your insight in the best way to accomplish this, we'd be moving the <profile> block from .user entity files to .layout entity files and I'm not sure how to appropriately author the import files to deal with the 2.6 formated exports?

[ Permlink | « Hide ]

Eric Dalquist [12/Apr/08 02:33 PM]

This patch moves the profile from the .user to the .layout files for importing and exporting. Entities exported from 2.6 will still work as the 2.6 user and layout import scripts are not touched.

[ Permlink | « Hide ]

Eric Dalquist [15/Apr/08 11:32 AM]

The <profile> element has been moved from the .user entity into the .layout entity.