StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11445959
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-07-12T06:14:38.540
FavoriteCount
0
LastActivityDate
2012-07-12T11:43:43.443
LastEditDate
2012-07-12T11:43:43.443
LastEditorUserId
419
OwnerUserId
1508171
ParentId
7724924
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
<p>Harp, your almost there. This is how I usually set it up in D7. </p> <ol> <li>Create a role called "Members"</li> <li>Create a new vocabulary called "Access"</li> <li>Add two terms to the "Access" vocabulary, "Public" and Members Only"</li> <li>Add a new field to each content type - Admin > Structure > Content Types of type term reference. I usually use the checkbox widget but it is up to you.</li> <li>Set the vocabulary to be the "Access" vocabulary you set up in step 2</li> <li>Set the default to be "Public" - this is optional but it means all pages are publicly accessible unless specifically set to "Members Only"</li> <li>Save</li> <li>Go to the Manage Display settings for that content type</li> <li>Set the Access field to hidden</li> <li>save</li> <li>Now go to Admin > Configuration > Taxonomy access control</li> <li>Go to edit access rules for anonymous users</li> <li>Under "New" select members in the dropdown</li> <li>Set each option in the row to "D"</li> <li>Click Add</li> <li>Do steps 12 to 15 for the authenticated user</li> <li>Do steps 12 to 15, expect select "A" instead of "D" for the members role</li> </ol> <p>Now when you select Members Only for the Access field on any node, that node will not be visible to the anonymous and authenticated users. Any user with the Members role will be able to view the node. This will also hide menu items that are directed to this node. See the taxonomy terms documentation for more help. <a href="http://drupal.org/node/31601" rel="nofollow">https://drupal.org/node/31601</a></p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODrupal TAC not working? Setup wrong?
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USKev
UserOwnerUserId
1. USkafmil
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTModeratorReview
2. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.