WPizard

A powerful WordPress plugin that lets you retrieve and display virtually any data in WordPress using simple shortcodes. Effortlessly pull information from posts, users, options, and more — with support for dynamic attribute parsing, flexible formatting, and customizable output wrapping.
It supports: 
– Post Field 
– Post Meta 
– Term Field 
– Term Meta (coming soon) 
– User Field 
– User Meta 
– Link 
– Option 
– Function (whitelisted)
You can also: 
– Apply custom formatting (date, datetime, number, capitalize, uppercase, lowercase, strip_tags, etc.) 
– Add before/after text 
– Use fallback values 
– Use nested shortcodes inside attributes 
– Use URL parameters as values 
– Cache output 
– Secure and sanitize output
<h3>Shortcode Usage</h3>
General syntax: 
 <code>[anys type="TYPE" name="KEY" id="ID" before="TEXT" after="TEXT" fallback="TEXT" format="FORMAT" delimiter="DELIMITER"]</code>
Attributes: 
– <code>type</code> — <code>post-field</code>, <code>post-meta</code>, <code>user-field</code>, <code>user-meta</code>, <code>option</code>, <code>function</code> (required) 
– <code>name</code> — The field name, meta key, option name, or function call (required) 
– <code>id</code> — Post ID or User ID (optional; defaults to current context) 
– <code>before</code> — Text to prepend before output (optional) 
– <code>after</code> — Text to append after output (optional) 
– <code>fallback</code> — Value if empty (optional) 
– <code>format</code> — Output formatting type (optional: <code>date</code>, <code>datetime</code>, <code>number</code>, <code>capitalize</code>, <code>uppercase</code>, <code>lowercase</code>, <code>strip_tags</code>, <code>values</code>, <code>keys_values</code>, etc.) 
– <code>delimiter</code> — Separator used to join multiple values (optional)
<h3>Supported Types and Examples</h3>
Post Field 
Retrieve standard post fields by name.
Examples:
<ul>
<li><code>[anys type="post-field" name="post_title"]</code> — Shows the post title.</li>
<li><code>[anys type="post-field" name="post_date" format="date"]</code> — Shows the post publish date (formatted).</li>
<li><code>[anys type="post-field" name="post_author" id="123"]</code> — Shows the author ID of post <code>123</code>.</li>
<li><code>[anys type="post-field" name="post_content" fallback="No content"]</code> — Shows the post content or fallback text.</li>
</ul>
Other fields supported: <code>ID</code>, <code>post_name</code>, <code>post_excerpt</code>, <code>post_status</code>, <code>comment_status</code>, <code>ping_status</code>, <code>post_password</code>, <code>post_parent</code>, <code>menu_order</code>, <code>guid</code>, <code>post_type</code>, <code>post_mime_type</code>, <code>post_modified</code>, <code>post_modified_gmt</code>
Post Meta 
Retrieve post meta by key.
Examples:
<ul>
<li><code>[anys type="post-meta" name="my_meta_key"]</code> — Shows value of <code>my_meta_key</code>.</li>
<li><code>[anys type="post-meta" name="price" id="456" format="number"]</code> — Shows the <code>price</code> of post <code>456</code>, formatted as number.</li>
<li><code>[anys type="post-meta" name="release_date" format="date"]</code> — Shows release date formatted as date.</li>
</ul>
Term Field 
Retrieve standard term fields by name.
Examples:
<ul>
<li><code>[anys type="term-field" name="name"]</code> — Shows the term name.</li>
<li><code>[anys type="term-field" name="slug"]</code> — Shows the term slug.</li>
<li><code>[anys type="term-field" name="term_id" id="15"]</code> — Shows the ID of term <code>15</code>.</li>
<li><code>[anys type="term-field" name="taxonomy" id="15"]</code> — Shows the taxonomy of term <code>15</code>.</li>
<li><code>[anys type="term-field" name="description" fallback="No description"]</code> — Shows term description or fallback text.</li>
<li><code>[anys type="term-field" name="count" id="15" format="number"]</code> — Shows the number of posts in term <code>15</code>.</li>
</ul>
Other fields supported: <code>term_group</code>, <code>parent</code>
Notes: 
– If no “id” is provided, it defaults to the current queried term (e.g., category/tag archive page). 
– Supports “before”, “after”, “fallback”, and “format” (for number, date, etc.).
User Field 
Retrieve user standard fields.
Examples:
<ul>
<li><code>[anys type="user-field" name="user_email" id="12"]</code> — Shows email of user <code>12</code>.</li>
<li><code>[anys type="user-field" name="display_name"]</code> — Shows current user display name.</li>
<li><code>[anys type="user-field" name="user_registered" format="date"]</code> — Shows user registration date.</li>
</ul>
Common user fields: <code>ID</code>, <code>user_login</code>, <code>user_nicename</code>, <code>user_url</code>, <code>user_activation_key</code>, <code>user_status</code>, <code>description</code>
User Meta 
Retrieve user meta by key.
Examples:
<ul>
<li><code>[anys type="user-meta" name="favorite_color" id="12"]</code> — Shows favorite_color of user <code>12</code>.</li>
<li><code>[anys type="user-meta" name="profile_phone"]</code> — Shows current user’s phone.</li>
</ul>
Link 
Retrieve URLs or generate link anchors for common WordPress locations.
Examples:
<ul>
<li><code>[anys type="link" name="logout"]</code> — Returns the logout URL.</li>
<li><code>[anys type="link" name="logout" redirect="/"]</code> — Returns the logout URL and redirects to home after logout.</li>
<li><code>[anys type="link" name="login" redirect="/dashboard"]</code> — Returns the login URL with redirect to <code>/dashboard</code>.</li>
<li><code>[anys type="link" name="register"]</code> — Returns the registration URL.</li>
<li><code>[anys type="link" name="home"]</code> — Returns the home page URL.</li>
<li><code>[anys type="link" name="siteurl"]</code> — Returns the main site URL.</li>
<li><code>[anys type="link" name="admin"]</code> — Returns the WordPress admin URL.</li>
<li><code>[anys type="link" name="profile"]</code> — Returns the user profile page URL.</li>
<li><code>[anys type="link" name="post" id="123"]</code> — Returns the permalink for post with ID <code>123</code>.</li>
<li><code>[anys type="link" name="term" id="45"]</code> — Returns the archive link for term with ID <code>45</code>.</li>
<li><code>[anys type="link" name="current"]</code> — Returns the current page URL.</li>
<li><code>[anys type="link" name="auth"]</code> — Dynamically returns the login or logout URL based on user status.</li>
</ul>
Formatting options:
<ul>
<li><code>[anys type="link" name="logout" format="anchor"]</code> — Outputs a clickable link: <code><a href="...">Logout</a></code>.</li>
<li><code>[anys type="link" name="auth" format="anchor"]</code> — Dynamically shows Login or Logout link depending on user state.</li>
<li><code>[anys type="link" name="auth" format="anchor" label_logged_in="Sign Out" label_logged_out="Sign In"]</code> — Customizes labels for both states.</li>
</ul>
Attributes supported: 
– <code>name</code>: The link type (e.g., <code>logout</code>, <code>login</code>, <code>home</code>, <code>admin</code>, etc.). 
– <code>redirect</code>: Optional redirect URL (used for login/logout links). 
– <code>format</code>: Either <code>url</code> (default) or <code>anchor</code> for clickable links. 
– <code>target</code>: Optional anchor target (e.g., <code>_blank</code>). 
– <code>label</code>: Optional link text (default varies by type). 
– <code>label_logged_in</code>: Custom label when the user is logged in (used with <code>auth</code>). 
– <code>label_logged_out</code>: Custom label when the user is logged out (used with <code>auth</code>). 
– <code>id</code>: Used for post and term links.
Option 
Retrieve WordPress option values.
Examples:
<ul>
<li><code>[anys type="option" name="blogname"]</code> — Shows site title.</li>
<li><code>[anys type="option" name="admin_email"]</code> — Shows site admin email.</li>
</ul>
Function 
Execute a whitelisted PHP function and optionally pass arguments.
Examples:
<ul>
<li><code>[anys type="function" name="date_i18n, F j, Y"]</code> — Shows today’s date.</li>
<li><code>[anys type="function" name="sanitize_text_field, (anys type='option' name='blogdescription')"]</code> — Sanitizes and shows site description.</li>
<li><code>[anys type="function" name="date_i18n, F j, Y" before="Today is "]</code> — Shows today’s date with custom prefix.</li>
<li><code>[anys type="function" name="date_i18n, F j, Y" after="."]</code> — Shows today’s date with custom suffix.</li>
<li><code>[anys type="function" name="my_custom_function" fallback="N/A"]</code> — Shows output of custom function or fallback.</li>
<li><code>[anys type="function" name="my_custom_function" format="capitalize"]</code> — Shows output of custom function and automatically capitalizes the output (e.g., “hello world” → “Hello World”).</li>
<li><code>[anys type="function" name="my_custom_function" delimiter=", "]</code> — Shows output of custom function. If the function returns an array, the values are joined using the given delimiter (e.g., <code>["apple", "banana"]</code> → “apple, banana”).</li>
</ul>
Notes: 
– Only functions whitelisted in plugin settings can be executed. 
– Arguments can include other <code>[anys]</code> shortcodes using <code>()</code> instead of <code>[]</code>. 
– Output can be formatted or wrapped with <code>before</code>/<code>after</code> content and fallback.
<h3>Dynamic Attribute Parsing</h3>
Supports dynamic placeholders inside attribute values: 
– <code>{get:param}</code> — gets value from $_GET[‘param’] 
– <code>{post:param}</code> — gets value from $_POST[‘param’] 
– <code>{func:function_name,arg1,arg2}</code> — calls a whitelisted PHP function 
– <code>{shortcode:(tag)}</code> — parses nested shortcode (use <code>()</code> instead of <code>[]</code>) 
– <code>{const:CONSTANT_NAME}</code> — replaces with PHP constant value
Example: 
 <code>[anys type="post_field" name="post_title" id="{get:post_id}" before="Title: "]</code>
<h3>Formatting Options</h3>
<ul>
<li><code>date</code> — Format timestamps using WordPress date format.</li>
<li><code>datetime</code> — Format timestamps using WordPress date and time format.</li>
<li><code>number</code> — Localized number format.</li>
<li><code>json</code> — Encode value as JSON string.</li>
<li><code>serialize</code> — Serialize PHP value.</li>
<li><code>unserialize</code> — Unserialize string if serialized.</li>
<li><code>print_r</code> — Human-readable output of variable.</li>
<li><code>var_export</code> — Parsable string representation.</li>
<li><code>implode</code> — Join array values.</li>
<li><code>values</code> — Join array values only.</li>
<li><code>keys</code> — Join array keys only.</li>
<li><code>keys_values</code> — Join array key-value pairs.</li>
<li><code>capitalize</code> — Capitalize words.</li>
<li><code>uppercase</code> — Uppercase all characters.</li>
<li><code>lowercase</code> — Lowercase all characters.</li>
<li><code>strip_tags</code> — Remove HTML/PHP tags.</li>
</ul>
Custom formats are supported via filters.
<h3>Hooks</h3>
Filters 
– <code>anys/attributes</code> — Filter attributes before processing. 
– <code>anys/{type}/attributes</code> — Filter attributes dynamically by type. 
– <code>anys/output</code> — Filter final output. 
– <code>anys/{type}/output</code> — Filter output dynamically by type. 
– <code>anys/link/handlers</code> – Filter link handlers.
Actions 
– <code>anys/output/before</code> — Fires before output. 
– <code>anys/{type}/output/before</code> — Fires before output for specific type. 
– <code>anys/{type}/missing</code> — Fires when handler file missing. 
– <code>anys/output/after</code> — Fires after output. 
– <code>anys/{type}/output/after</code> — Fires after output for specific type.
<h3>Security</h3>
<ul>
<li>All inputs sanitized using WordPress functions.</li>
<li>Function calls restricted to whitelisted list.</li>
<li>Outputs sanitized with <code>wp_kses_post()</code>.</li>
<li>Dynamic parsing uses caching for performance.</li>
</ul>
<h3>Support & Contribution</h3>
For bugs, feature requests, or contributions, open an issue or PR on the <a href="https://github.com/wpizard/anything-shortcodes" rel="nofollow ugc">plugin repository</a>.
Thank you for using Anything Shortcodes!

Anything Shortcodes

Retrieve and display any WordPress data with shortcodes — posts, users, options, and more, with flexible formatting and customization.

Mohammad Jangda

Joey Kudish

cvernon

stresslimit

An easy way to add custom fields to your object types (post, pages, custom post types, users) & to generate option pages.
The goal of this plugin is to help you rapidly build familiar, intuitive interfaces for your users in a very WordPress-native way.
The custom field panel is nice, but not quite the easiest thing for users to work with. Adding your own metaboxes and fields involves a lot of time and repetitive code that could be better used elsewhere.
This plugin handles all that heavy-lifting for you behind-the-scenes, so that you can focus on more on building out and connecting your data rather than all the minor details. This single piece of code <code>x_add_metadata_field( 'my-field-name', 'post' );</code> generates a metabox with a text field inside it, with the necessary hooks to save the entered values.
The API is similar to that used for registering custom post types and taxonomies so it should be familiar territory.
NOTE: The plugin now requires WordPress 3.3+ (chiefly for the wysiwyg & datepicker fields)
Like what you see? Want more field types and features added? <a href="mailto:tech@stresslimitdesign.com" rel="nofollow ugc">Get in touch</a> or <a href="https://github.com/jkudish/custom-metadata" rel="nofollow ugc">contribute on github</a>
<blockquote>
See “Other Notes” section for usage information
</blockquote>
<h3>Usage</h3>
<h4>Object Types</h4>
The main idea behind this plugin is to have a single API to work with regardless of the object type. Currently, Custom Metadata Manager works with <code>user</code>, <code>comment</code> and any built-in or custom post types, e.g. <code>post</code>, <code>page</code>, etc.
<h4>Registering your fields</h4>
For the sake of performance (and to avoid potential race conditions), always register your custom fields in the <code>admin_menu</code> hook. This way your front-end doesn’t get bogged down with unnecessary processing and you can be sure that your fields will be registered safely. Here’s a code sample:
<pre><code>add_action( 'admin_menu', 'my_theme_init_custom_fields' );

function my_theme_init_custom_fields() {
 if( function_exists( 'x_add_metadata_field' ) && function_exists( 'x_add_metadata_group' ) ) {
 x_add_metadata_field( 'my_field', array( 'user', 'post' ) );
 }
}
</code></pre>
<h4>Getting the data</h4>
You can get the data as you normally would using the <code>get_metadata</code> function. Custom Metadata manager stores all data using the WordPress metadata APIs using the slug name you provide. That way, even if you decide to deactivate this wonderful plugin, your data is safe and accessible. For options, you can use <code>get_option</code>.
Example:
<pre><code>$value = get_metadata( 'post', get_the_ID(), 'featured', true ); // Returns post metadata value for the field 'featured'
</code></pre>
<h4>Adding Metadata Groups</h4>
A group is essentially a metabox that groups together multiple fields. Register the group before any fields
<pre><code>x_add_metadata_group( $slug, $object_types, $args );
</code></pre>
Parameters
<ul>
<li><code>$slug</code> (string) The key under which the metadata will be stored.</li>
<li><code>$object_types</code> (string|array) The object types to which this field should be added. Supported: post, page, any custom post type, user, comment.</li>
</ul>
Options and Overrides
<pre><code>$args = array(
 'label' => $group_slug, // Label for the group
 'context' => 'normal', // (post only)
 'priority' => 'default', // (post only)
 'autosave' => false, // (post only) Should the group be saved in autosave? NOT IMPLEMENTED YET!
 'exclude' => '', // see below for details
 'include' => '', // see below for details
);
</code></pre>
<h4>Adding Metadata Fields</h4>
<pre><code>x_add_metadata_field( $slug, $object_types, $args );
</code></pre>
Parameters
<ul>
<li><code>$slug</code> (string) The key under which the metadata will be stored. For post_types, prefix the slug with an underscore (e.g. <code>_hidden</code>) to hide it from the the Custom Fields box.</li>
<li><code>$object_types</code> (string|array) The object types to which this field should be added. Supported: post, page, any custom post type, user, comment.</li>
</ul>
Options and Overrides
<pre><code>$args = array(
 'group' => '', // The slug of group the field should be added to. This needs to be registered with x_add_metadata_group first.
 'field_type' => 'text', // The type of field; 'text', 'textarea', 'password', 'checkbox', 'radio', 'select', 'upload', 'wysiwyg', 'datepicker', 'taxonomy_select', 'taxonomy_radio'
 'label' => '', // Label for the field
 'description' => '', // Description of the field, displayed below the input
 'values' => array(), // Values for select and radio buttons. Associative array
 'display_callback' => '', // Callback to custom render the field
 'sanitize_callback' => '', // Callback to sanitize data before it's saved
 'display_column' => false, // Add the field to the columns when viewing all posts
 'display_column_callback' => '', // Callback to render output for the custom column
 'required_cap' => '', // The cap required to view and edit the field
 'exclude' => '', // see below for details
 'include' => '', // see below for details
 'multiple' => false, // true or false, can the field be duplicated with a click of a button?
 'readonly' => false, // makes the field be readonly (works with text, textarea, password, upload and datepicker fields)
);
</code></pre>
<h4>Include / Exclude</h4>
You can exclude fields and groups from specific object. For example, with the following, field-1 will show up for all posts except post #123:
<pre><code>$args = array(
 'exclude' => 123
);
x_add_metadata_field( 'field-1', 'post', $args );
</code></pre>
Alternatively, you can limit (“include”) fields and groups to specific objects. The following will ”only” show group-1 to post #456:
<pre><code>$args = array(
 'include' => 123
);
x_add_metadata_group( 'group-1', 'post', $args );
</code></pre>
You can pass in an array of IDs:
<pre><code>$args = array(
 'include' => array( 123, 456, 789 );
);

With multiple object types, you can pass in an associative array:
</code></pre>
$args = array( 
 ‘exclude’ => array( 
 ‘post’ => 123, 
 ‘user’ => array( 123, 456, 789 ) 
 ) 
);
<h4>Examples</h4>
For examples, please see the <a href="https://github.com/jkudish/custom-metadata/blob/master/custom_metadata_examples.php" rel="nofollow ugc">custom_metadata_examples.php</a> file included with the plugin. Add a constant to your wp-config.php called <code>CUSTOM_METADATA_MANAGER_DEBUG</code> with a value of <code>true</code> to see it in action:
<pre><code>define( 'CUSTOM_METADATA_MANAGER_DEBUG', true );
</code></pre>
<h4>TODOs</h4>
Stuff we have planned for the future:
<ul>
<li>Ability to clone (multiple) groups of fields</li>
<li>Ability Pass in attributes for built-in fields (e.g. class, data-*, etc.)</li>
<li>Additional field types (multi-select, multi-checkbox)</li>
<li>Limit or exclude groups and fields using a custom callback</li>
<li>Autosave support for fields on post types</li>
<li>Client- and server-side validation support</li>
<li>Add groups and fields to Quick Edit</li>
</ul>

Custom Metadata Manager

An easy way to add custom fields to your object types (post, pages, custom post types, users)

Anything Shortcodes vs Custom Metadata Manager