We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wordpress 6.6.2
Using pods to create custom content type.
I have a custom template like this
<div class="latestposts"> <div>{@post_thumbnail}</div> <div class="postexcerpt"> <div>{@post_title}</div> <div>{@post_excerpt}</div> <div class="tags"> [each post_tag] <span class=newstag>{@title}</span> [/each] </div> <div> {@post_date} </div> <div> {@post_author, cc_get_the_author_display_name} </div> </div> </div>
I have added a function to my functions.php using the theme file editor
function cc_get_the_author_display_name($userID) { return get_the_author_meta( 'display_name', $userID ); }
The output on the page is just the ID value of the author. It looks to me like the filter function is not even being called.
3.2.7.1
Author displayed a 1, not author name.
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
Wordpress 6.6.2
Using pods to create custom content type.
I have a custom template like this
I have added a function to my functions.php using the theme file editor
The output on the page is just the ID value of the author. It looks to me like the filter function is not even being called.
Version
3.2.7.1
Testing Instructions
Supports:
[x] Title
[x] Editor
[x] Author
[x] Featured Image
[x] Excerpt
[ ] Trackbacks
[ ] Manually Edit Custom Fields (can cause slow performance)
[x] Comments
[x] Revisions
[ ] Page Attributes
[ ] Post Formats
[x] Quick Edit
Screenshots / Screencast
Author displayed a 1, not author name.
Possible Workaround
Site Health Information
No response
Pods Package
No response
The text was updated successfully, but these errors were encountered: