Updates to permission names are not managed [#80253]

As pwolanin reported in http://drupal.org/node/77990, it is possible to change the machine-readable name of a node type, but when that change is made, the permissions for that node type still use the old machine-readable name. When a node type's machine-readable name is updated, the permissions for that node type need to be updated as well.

Comment	File	Size	Author
#3	content_types_update_permissions_02.patch.txt	1.31 KB	Jose Reyero
#1	content_types_update_permissions_01.patch	1.3 KB	Jose Reyero
#1

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

Jose Reyero CreditAttribution: Jose Reyero commented 30 November 2006 at 19:28

Version:	x.y.z	» 5.0-beta2
Status:	Active	» Needs review

File	Size
content_types_update_permissions_01.patch	1.3 KB

Here's the patch

Comment #2

drumm

he/him

NY, US

CreditAttribution: drumm commented 19 December 2006 at 09:35

Status:

Needs review

» Needs work

There are hooks for this; the added code should be in the user module. And the indentation needs to be fixed for that UPDATE query.

Comment #3

Jose Reyero CreditAttribution: Jose Reyero commented 21 December 2006 at 17:42

File	Size
content_types_update_permissions_02.patch.txt	1.31 KB

Fixed indentation.

About your comment
>There are hooks for this; the added code should be in the user module

I disagree. This is content types specific and the user module doesn't know -nor needs to know- about content type names or permissions.

Comment #4

tstoeckler

he/him

German

Essen, Germany

CreditAttribution: tstoeckler commented 21 May 2011 at 21:10

Title:	permission name should change when node type name is updated	» Updates to permission names are not managed
Version:	5.0-beta2	» 8.x-dev
Component:	node system	» user.module

I just tried this out, and it is still a valid issue.

Comment #5

sureshbabudrupal CreditAttribution: sureshbabudrupal commented 22 June 2011 at 05:23

Title:	Updates to permission names are not managed	» There is no ckeditor.js in ckeditor.
Component:	user.module	» upload.module
Assigned:	Unassigned	» sureshbabudrupal

When i was installed the ckeditor then bellow text came

The CKEditor component is not installed correctly. Please go to the CKEditor homepage to download the latest version. After that you must extract the files to sites/all/modules/ckeditor/ckeditor or sites/all/libraries/ckeditor and make sure that the file sites/all/modules/ckeditor/ckeditor/ckeditor.js or sites/all/libraries/ckeditor/ckeditor.js exist. Refer to the README.txt for more information.

There is no ckeditor.js in ckeditor.

Comment #6

tstoeckler

he/him

German

Essen, Germany

CreditAttribution: tstoeckler commented 22 June 2011 at 11:20

Title:	There is no ckeditor.js in ckeditor.	» Updates to permission names are not managed
Component:	upload.module	» user.module
Assigned:	sureshbabudrupal	» Unassigned

Restoring values.
Please open a new issue if you have any problem that is not related to this one.

Comment #7

drupal_was_my_past CreditAttribution: drupal_was_my_past commented 23 November 2011 at 06:21

Issue tags:

+Needs tests

This patch should include tests.

Comment #8

23 November 2011 at 06:21

Version:

8.0.x-dev

» 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Comment #9

23 November 2011 at 06:21

Version:

8.1.x-dev

» 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.