StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15157640
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-03-01T12:19:33.980
FavoriteCount
0
LastActivityDate
2017-03-08T20:31:10.053
LastEditDate
2017-03-08T20:31:10.053
LastEditorUserId
201354
OwnerUserId
395258
ParentId
15156762
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
In the end, what you want to use is what will be <ol> <li>Easy to understand for someone else</li> <li>Convenient to you</li> </ol> You've grasped the DRY - don't repeat yourself - principle. This is very good. If you have to change something in the future, you don't want to have to change the same thing in multiple places (it's not convenient). So if you repeat the same thing in several different template files, you can use <code>get_template_part</code>. This function renders <code>include()</code> obsolete. You could stick your code into a function that takes the meta key as an argument. This would be a pretty neat solution. It would be very convenient. The problem is that if someone else reads this template they will not immediately know how that function looks, since it's something custom that you made up, and they will have to find that function in order to figure it out. So perhaps your best bet is to use a foreach loop: <pre><code>foreach( array( 'meta_key1', 'meta_key2' ) as $key ) { // Your code } </code></pre> If the code is not too long and is mostly about displaying information not so much processing it, this could be a good solution. But this only works if the output you want to generate is adjacent. Otherwise you're stuck with having to create a function, and in that case you should put it in functions.php. If the code does a lot of processing of information you should probably put it in functions.php. The template files are for displaying stuff, and should be readable by designers with only a little PHP experience. (btw it's not wrong for functions to contain both PHP and HTML. All template tags essentially are such functions. WordPress does not encourage truly strict separation.)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to reuse code in Wordpress Page Template?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USWillington Vega
UserOwnerUserId
1. USC. E.
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to reuse code in Wordpress Page Template?
 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.