#309 ✓resolved

Module level permissions do not migrate from 0.97.0-GA20090213

Reported by theohiobloke | August 17th, 2011 @ 06:08 PM | in Stable (closed)

The permissions for modules on pages do not migrate in the last step of the migration wizard.
Tried removing existing permissions and they do not come in from the old site.

Page level permissions are working it is only the pages where the modules have individual permissions attached to them.

Comments and changes to this ticket

  • theohiobloke

    theohiobloke August 17th, 2011 @ 06:36 PM

    On further review it was found that users that do not have all the permissions checked at the module level will see this problem. Problem occurred with user who had Add permissions for a Container module but not manage.

    Same user had all permissions at the textmodule level but these did NOT translate over to the new server.

  • dleffler

    dleffler August 20th, 2011 @ 01:20 AM

    • Assigned user cleared.
    • Milestone set to Stable
    • Milestone order changed from “83” to “0”

    So the question...what was the permission NAME (& module) on 0.97, and what should it translate to in 2.0?

  • dleffler

    dleffler August 20th, 2011 @ 01:39 AM

    • Assigned user set to “dleffler”

    Need to confirm the following:

    • user (group) was COPIED over (must have same user id# in both new & old databases AND user MUST exist in 2.0 database)
    • 'Migrate content permissions?' was checked (assuming it was since some container/module permissions came over)
    • ALL content was copied over (only copy over permissions where 'source' is equal)
    • in the reference above if there was a user with 'add' permission on 'textmodule' with src of "@random123), it would be saved on the 2.0 system as 'create' premission on 'textController' with src of '@random123'

    Algorythm used is:

    • delete user & group permission tables
    • create list of 2.0 users
    • cycle through each user (in turn)
    • cycle through all this users's 1.0 permissions (in turn)
    • check if module is migrated to 2.0, if so 'translate' permission name
    • if there is a container with corresponding module & source (translated to 2.0 if needed) then insert the translated user permission.
    • after going through all the user's permissions, and the 2.0 users, then go through all the 2.0 groups in the same manner
  • dleffler

    dleffler August 20th, 2011 @ 01:46 AM

    On further review, there are only two valid permissions with 0.97 text modules...'administrate' (which is tranlated to perms), and 'edit' (which translated as-is). The 'approve' and 'manage workflow' permissions are deprecated.

    There was NO create or add permission for 1.0 text modules since they only had one content. NOT sure if this is moot, or I need to add additional algorythm check for textmodules...just did a straight 1:1 copy/translate.

  • dleffler

    dleffler August 23rd, 2011 @ 03:15 AM

    • State changed from “new” to “resolved”
    • Tag set to migration, permissions
    • Milestone order changed from “5” to “0”

    resolved on last commit by adding both an edit & create permission

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Bug Tracker for Exponent CMS

Shared Ticket Bins

People watching this ticket