Talk:Roles-Based Security - Revision history

Agx at 16:58, 11 February 2011

2011-02-11T16:58:38Z

← Older revision		Revision as of 16:58, 11 February 2011
Line 3:		Line 3:
	* Added a note after the access table SQL code that the "node" and "action" columns in the "access" table must be exactly as shown (including case) along with a description of what happens if you change them, so people will recognize their mistake easily.		* Added a note after the access table SQL code that the "node" and "action" columns in the "access" table must be exactly as shown (including case) along with a description of what happens if you change them, so people will recognize their mistake easily.

	* by [[User:Agx]] - '''IMPORTANT''': if you didn't installed the samples data you many need the db_sequence table in order to make the RBAC system to work:		* by [[User:Agx]] - '''IMPORTANT''': if you didn't installed the samples data you many need the '''db_sequence''' table in order to make the ''RBAC'' system to work:
	CREATE TABLE db_sequence (		CREATE TABLE db_sequence (
	seq_name varchar(100) NOT NULL default '',		seq_name varchar(100) NOT NULL default '',

Agx at 16:58, 11 February 2011

2011-02-11T16:58:09Z

← Older revision		Revision as of 16:58, 11 February 2011
Line 2:		Line 2:

	* Added a note after the access table SQL code that the "node" and "action" columns in the "access" table must be exactly as shown (including case) along with a description of what happens if you change them, so people will recognize their mistake easily.		* Added a note after the access table SQL code that the "node" and "action" columns in the "access" table must be exactly as shown (including case) along with a description of what happens if you change them, so people will recognize their mistake easily.

			* by [[User:Agx]] - '''IMPORTANT''': if you didn't installed the samples data you many need the db_sequence table in order to make the RBAC system to work:
			CREATE TABLE db_sequence (
			seq_name varchar(100) NOT NULL default '',
			nextid int(10) unsigned NOT NULL default '0',
			PRIMARY KEY (seq_name)
			TYPE=MyISAM;

Preid at 12:36, 31 December 2008

2008-12-31T12:36:49Z

← Older revision		Revision as of 12:36, 31 December 2008
Line 1:		Line 1:
	*added the comment 'Be careful not to use the same text for the mainmenu item and the submenu item.', and changed code accordingly. Using both 'users' as main menu item and submenuitem resulted in a segmentation fault error.		*added the comment 'Be careful not to use the same text for the mainmenu item and the submenu item.', and changed code accordingly. Using both 'users' as main menu item and submenuitem resulted in a segmentation fault error.

	* Added note that the "node" and "action" columns in the "access" table must be exactly as shown (including case) along with a description of what happens if you change them, so people will recognize their mistake easily.		* Added a note after the access table SQL code that the "node" and "action" columns in the "access" table must be exactly as shown (including case) along with a description of what happens if you change them, so people will recognize their mistake easily.

Preid: /* "node" and "action" columns in "access" table must be exact */

2008-12-31T12:36:06Z

"node" and "action" columns in "access" table must be exact

← Older revision		Revision as of 12:36, 31 December 2008
Line 1:		Line 1:
	*added the comment 'Be careful not to use the same text for the mainmenu item and the submenu item.', and changed code accordingly. Using both 'users' as main menu item and submenuitem resulted in a segmentation fault error.		*added the comment 'Be careful not to use the same text for the mainmenu item and the submenu item.', and changed code accordingly. Using both 'users' as main menu item and submenuitem resulted in a segmentation fault error.

	~~== "node" and "action" columns in "access" table must be exact ==~~		* Added note that the "node" and "action" columns in the "access" table must be exactly as shown (including case) along with a description of what happens if you change them, so people will recognize their mistake easily.

	~~Note~~ that the "node" and "action" columns in the "access" table must be exactly as shown (including case).

	If you change them ~~in any way (such as capitalizing the column names)~~, ~~your profile permissions~~ will ~~be saved, but not loaded again later (resulting in users not having permissions to anything and all of the checkboxes for profile permissions being empty when you view the profile again later)~~.

Preid: New section: "node" and "action" columns in "access" table must be exact

2008-12-31T12:32:37Z

New section: "node" and "action" columns in "access" table must be exact

← Older revision		Revision as of 12:32, 31 December 2008
Line 1:		Line 1:
	*added the comment 'Be careful not to use the same text for the mainmenu item and the submenu item.', and changed code accordingly. Using both 'users' as main menu item and submenuitem resulted in a segmentation fault error.		*added the comment 'Be careful not to use the same text for the mainmenu item and the submenu item.', and changed code accordingly. Using both 'users' as main menu item and submenuitem resulted in a segmentation fault error.

			== "node" and "action" columns in "access" table must be exact ==

			Note that the "node" and "action" columns in the "access" table must be exactly as shown (including case).

			If you change them in any way (such as capitalizing the column names), your profile permissions will be saved, but not loaded again later (resulting in users not having permissions to anything and all of the checkboxes for profile permissions being empty when you view the profile again later).

Oli: New page: *added the comment 'Be careful not to use the same text for the mainmenu item and the submenu item.', and changed code accordingly. Using both 'users' as main menu item and submenuitem res...

2008-10-10T14:47:14Z

New page: *added the comment 'Be careful not to use the same text for the mainmenu item and the submenu item.', and changed code accordingly. Using both 'users' as main menu item and submenuitem res...

New page

*added the comment 'Be careful not to use the same text for the mainmenu item and the submenu item.', and changed code accordingly. Using both 'users' as main menu item and submenuitem resulted in a segmentation fault error.