StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18392762
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-08-23T00:16:57.577
FavoriteCount
0
LastActivityDate
2014-05-06T15:25:32.430
LastEditDate
2014-05-06T15:25:32.430
LastEditorUserId
1619796
OwnerUserId
1619796
ParentId
18390080
PostTypeId
2
Score
17
ViewCount
0
LastEditorDisplayName
text
Body
Which version of devise are you using? If you're on <code>3.1.0</code> or higher, this behavior is expected: <a href="https://github.com/plataformatec/devise/blob/master/CHANGELOG.md" rel="noreferrer">CHANGELOG.md</a> The tokens that are stored in the database are not supposed to match the tokens that you send in the confirmation e-mails. See <a href="https://github.com/plataformatec/devise/blob/master/lib/devise/models/confirmable.rb" rel="noreferrer">devise/lib/devise/models/confirmable.rb</a>, which now contains the following: <pre><code>def confirm_by_token(confirmation_token) original_token = confirmation_token confirmation_token = Devise.token_generator.digest(self, :confirmation_token, confirmation_token) confirmable = find_or_initialize_with_error_by(:confirmation_token, confirmation_token) </code></pre> As you can see, the token that you pass in via query string params is consumed by the <code>Devise.token_generator</code>, and the result of that operation is what's compared with the token in the database to discover the user record. It looks like it's temporarily possible (in 3.1 but not 3.2) to turn this off by setting <pre><code>config.allow_insecure_token_lookup = true </code></pre> in your devise initializer. But the default behavior has been changed to make devise more secure. See <a href="http://blog.plataformatec.com.br/2013/08/devise-3-1-now-with-more-secure-defaults/" rel="noreferrer">this blog post</a> for a complete rundown of the security improvements in devise 3.1, including this change.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODevise confirmation_token is invalid
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USgregates
UserOwnerUserId
1. USgregates
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PODevise confirmation_token is invalid
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. 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.