Units permissions, aka statuses

2 views

Skip to first unread message

asd

unread,

Dec 23, 2010, 1:53:29 PM12/23/10

to in-por...@googlegroups.com

Hello guys.
I think that the way how permissions system now works, especially how it
informs an end-user about insufficient permissions should be changed.
How it works now, for example: imagine the page on front-end which
contains some list of records (or separate record, doesnt really
matter). Each record belongs to some in-portal registered user (comment,
blog post, profile info etc.). And some details of this user are printed
on the template using u_Field. What i get right now if the user in that
list becomes Disabled/Pending - is blank "No Permission" page.
How this could happen? Admin goes to the admin interface, selects
disabled user and submits the record (seeing no warnings).
Front-end user submits record by himself, in later time admin for some
reason disables that user.
In both cases page on front-end becomes broken.

This problem was identified on In-Portal 5.0.2

Alexander Obuhovich

unread,

Dec 25, 2010, 9:07:01 PM12/25/10

to in-por...@googlegroups.com

I think, that user info from records, which he creates should not be displayed by <inp2:u_Field ... /> tag, but rather via that unit prefix, which is displayed.

For example user (prefix - u) has created blog (prefix - blog). Template displays all blogs from all users and displays Username of each user and blog name. Here is the proposed tags to be used on that template:

<inp2:m_DefineElement name="blog_element">

Blog Name: <inp2:Field name="Name"/><br/>

Blog Author: <inp2:Field name="Author"/><br/>

</inp2:m_DefineElement>

<inp2:blog_PrintList render_as="blog_element"/>

Here "Author" field of a blog is actually field Login from PortalUser table. This approach allows to safely display user's field, no matter what's his status is right now.

Idea here is to wrap all data display via main unit (blog in this case) and not use multiple units at the same time.