We have installed EP6 SP1 and PDK Package for SP1. We have deployed our par (Custom applications) files in SP1. We tried to test the custom iViews using Component Inspector .it gives "iView not found error". But when we created iView (Content Management ->New iView from par file) based on the same application, it working properly. I think there is some problem with PDK BP for SP1.
We learnt from help files that from SP1 onwards, one cant access iViews using URL becase of security zone defined here. is there any problem in security zone defined for PDK iViews??.
1 Answer
-
Posted on Sep 30, 2003 at 01:43 PM
EP Content Developer News, Hints
could you please check following:                                                    ÂÂ
The deprecated EP5 IUser Interface isAdmin() per default returns true                ÂÂ
if the IUser object is assigned to one of following roles:                           ÂÂ
pcd:portal_content/administrator/super_admin/super_admin_role                        ÂÂ
pcd:portal_content/administrator/content_admin/content_admin_role                    ÂÂ
pcd:portal_content/administrator/system_admin/system_admin_role                      ÂÂ
pcd:portal_content/administrator/user_admin/user_admin_role                          ÂÂ
In order to check:                                                                   ÂÂ
- logon to the portal with an adminitrator's account                                 ÂÂ
- goto UserAdministration -> RoleAssignment                                          ÂÂ
- Search fur the user who encounters the defect of isAdmin=false                     ÂÂ
and check if this user is assigned to one of the above mentioned                    ÂÂ
roles. If the user is not assigned to these roles isAdmin() returns                 ÂÂ
false.
Normally this should be your result:
You check the role assignment and find out that                                  ÂÂ
that logon user is assigned to "com.sap.portal.super_admin_role".              ÂÂ
You changed the assigned role from "com.sap.portal.super_admin_role"             ÂÂ
to "super_admin_role" and Compoent manager is rendered normally.               ÂÂ
So this issue should be resolved.
Best regards,
Oliver
Add comment
Add comment