-
... (Object) stdClass
-
nid (String, 2 characters ) 97
-
type (String, 5 characters ) story
-
language (String, 0 characters )
-
uid (String, 1 characters ) 0
-
status (String, 1 characters ) 1
-
created (String, 10 characters ) 1280189877
-
changed (String, 10 characters ) 1280190054
-
comment (String, 1 characters ) 2
-
promote (String, 1 characters ) 1
-
moderate (String, 1 characters ) 0
-
sticky (String, 1 characters ) 0
-
tnid (String, 1 characters ) 0
-
translate (String, 1 characters ) 0
-
vid (String, 3 characters ) 112
-
revision_uid (String, 2 characters ) 60
-
title (String, 24 characters ) Energy makes a come back
-
body (String, 1131 characters ) <p>9.Go to User management>>Access contro...
-
<p>9.Go to User management>>Access control by taxonomy.<br /> There a couple of way to create access schemes. One is outlined in the comment to this page (thanks: johnmunro). Another one is to equate a "scheme" to a role and then proceed as follows. Select the “department” vocabulary, set the number of schemes to 4 and press “Save configuration”. Now click Scheme 1 (name it “sports author”) to assign view and update grants associated with the “sports” term to the Sports Author only. Then using Scheme 2 (“arts author) do the same for the “arts” term in relation to the Arts Author. Keeping things simple for now, use Scheme 3 to grant view, update and delete (if desired) access for all terms to the Moderator role. You may refine this later with more moderators. Finally, if the departmental content is to be viewed by the public, then use Scheme 4 (“public”) to grant view access only for all terms to anonymous users only. Do not include "authenticated users" in the "public" scheme as this will result in authors being able to create content for departments they don't belong to. Save.</p>
-
-
teaser (String, 53 characters ) 9.Go to User management>>Access control by taxo...
-
9.Go to User management>>Access control by taxonomy.
-
-
log (String, 0 characters )
-
revision_timestamp (String, 10 characters ) 1280190054
-
format (String, 1 characters ) 1
-
name (String, 0 characters )
-
picture (String, 0 characters )
-
data (NULL)
-
path (String, 30 characters ) content/energy-makes-come-back
-
current_revision_id (String, 3 characters ) 112
-
is_current (Boolean) TRUE
-
num_revisions (String, 1 characters ) 1
-
_workflow (String, 2 characters ) 10
-
revision_moderation (Boolean) TRUE
-
is_pending (Boolean) FALSE
-
last_comment_timestamp (String, 10 characters ) 1280189877
-
last_comment_name (NULL)
-
comment_count (String, 1 characters ) 0
-
taxonomy (Array, 1 element)
-
build_mode (Integer) 0
-
readmore (Boolean) TRUE
-
content (Array, 3 elements)
-
body (Array, 2 elements)
-
#value (String, 1131 characters ) <p>9.Go to User management>>Access contro...
-
<p>9.Go to User management>>Access control by taxonomy.<br /> There a couple of way to create access schemes. One is outlined in the comment to this page (thanks: johnmunro). Another one is to equate a "scheme" to a role and then proceed as follows. Select the “department” vocabulary, set the number of schemes to 4 and press “Save configuration”. Now click Scheme 1 (name it “sports author”) to assign view and update grants associated with the “sports” term to the Sports Author only. Then using Scheme 2 (“arts author) do the same for the “arts” term in relation to the Arts Author. Keeping things simple for now, use Scheme 3 to grant view, update and delete (if desired) access for all terms to the Moderator role. You may refine this later with more moderators. Finally, if the departmental content is to be viewed by the public, then use Scheme 4 (“public”) to grant view access only for all terms to anonymous users only. Do not include "authenticated users" in the "public" scheme as this will result in authors being able to create content for departments they don't belong to. Save.</p>
-
-
#weight (Integer) 0
-
-
#pre_render (Array, 1 element)
-
0 (String, 27 characters ) content_alter_extra_weights | (Callback) content_alter_extra_weights();
-
-
#content_extra_fields (Array, 11 elements)
-
title (Array, 3 elements)
-
label (String, 5 characters ) Title
-
description (String, 17 characters ) Node module form.
-
weight (String, 2 characters ) -5
-
-
body_field (Array, 4 elements)
-
label (String, 4 characters ) Body
-
description (String, 17 characters ) Node module form.
-
weight (String, 2 characters ) -1
-
view (String, 4 characters ) body
-
-
revision_information (Array, 3 elements)
-
label (String, 20 characters ) Revision information
-
description (String, 17 characters ) Node module form.
-
weight (String, 1 characters ) 2
-
-
author (Array, 3 elements)
-
label (String, 21 characters ) Authoring information
-
description (String, 17 characters ) Node module form.
-
weight (String, 1 characters ) 1
-
-
options (Array, 3 elements)
-
label (String, 18 characters ) Publishing options
-
description (String, 17 characters ) Node module form.
-
weight (String, 1 characters ) 3
-
-
comment_settings (Array, 3 elements)
-
label (String, 16 characters ) Comment settings
-
description (String, 20 characters ) Comment module form.
-
weight (String, 1 characters ) 5
-
-
menu (Array, 3 elements)
-
label (String, 13 characters ) Menu settings
-
description (String, 17 characters ) Menu module form.
-
weight (String, 2 characters ) -2
-
-
taxonomy (Array, 3 elements)
-
label (String, 8 characters ) Taxonomy
-
description (String, 21 characters ) Taxonomy module form.
-
weight (String, 2 characters ) -3
-
-
book (Array, 3 elements)
-
label (String, 4 characters ) Book
-
description (String, 17 characters ) Book module form.
-
weight (String, 1 characters ) 0
-
-
path (Array, 3 elements)
-
label (String, 13 characters ) Path settings
-
description (String, 17 characters ) Path module form.
-
weight (String, 1 characters ) 4
-
-
workflow (Array, 3 elements)
-
label (String, 8 characters ) Workflow
-
description (String, 20 characters ) Workflow module form
-
weight (String, 2 characters ) -4
-
-
-
-
-
Krumo version 0.2a
| http://krumo.sourceforge.net
node_access entries for nodes shown on this page
| node | prio | status | realm | gid | view | update | delete | explained |
|---|---|---|---|---|---|---|---|---|
| 97 | – | ok | tac_lite | 140 | 1 | 1 | Anonymous may view this node. | |
| 97 | – | ok | tac_lite_scheme_2 | 140 | 1 | 1 | Anonymous may view this node. | |
| 97 | – | ok | tac_lite_scheme_3 | 140 | 1 | 1 | Anonymous may view this node. | |
| 97 | – | ok | tac_lite_scheme_4 | 140 | 1 | 1 | Anonymous may view this node. | |
| 97 | – | ok | tac_lite_scheme_5 | 140 | 1′ | Anonymous may view this node. | ||
| 97 | – | empty | workflow_access | 1 | 0 | 0 | 0 | Anonymous may view this node. |
| 97 | – | empty | workflow_access | 2 | 0 | 0 | 0 | Anonymous may view this node. |
| 97 | – | ok | workflow_access | 3 | 1 | 1 | 0 | Anonymous may view this node. |
| 97 | – | ok | workflow_access | 4 | 1 | 1 | 1 | Anonymous may view this node. |
| 97 | – | ok | workflow_access | 5 | 1 | 1 | 0 | Anonymous may view this node. |
| 97 | – | empty | workflow_access | 6 | 0 | 0 | 0 | Anonymous may view this node. |
| 97 | – | ok | workflow_access | 7 | 1 | 0 | 0 | Anonymous may view this node. |
| 97 | – | ok | workflow_access | 8 | 1 | 1 | 0 | Anonymous may view this node. |
| 97 | – | empty | workflow_access_owner | 0 | 0 | 0 | 0 | Anonymous may view this node. |
(Some of the table elements provide additional information if you hover your mouse over them.)
Anonymous (user 0) can use these grants for view access (if they are present above):
- all: 0
- workflow_access: 1
- workflow_access_owner: 0
- tac_lite: 0
- tac_lite_scheme_2: 0
- tac_lite_scheme_3: 0
- tac_lite_scheme_4: 0
- tac_lite_scheme_5: 0, 141, 140, 142