Allows you to perform certain actions on posts and comments with shortcode directives.

Ross Wintle

Turbo Admin

Work faster with WordPress using a quick-access command palette and a collection of Dashboard improvements. Simply install, activate and go!

Shaan

CPT Commands

Adds a set of new search results to the WordPress command palette (CMD+K/CTRL+K) for all entries from registered Custom Post Types.

therealwebdisrupt

Task Runner

I have created a task runner for WordPress that can be used to automate tasks to one click. This is a

Kakon Barman

Disable Commands – Custom Key Binding in Command Palette

Adds comprehensive control over the WordPress admin command palette, including the ability to disable it or assign a custom keyboard shortcut.

miunosoft

Michael Uno

<h4>Quickly manage posts/comments in front-end with command-like-shortcodes</h4>
Say, you find a comment that should be hidden or deleted on your site. Usually, you click on the Edit link of the comment and manage it back-end.
What if you could delete/hide it by commenting on it?
This plugin lets you manage posts and comments with command-like-shortcodes.
In this case, you reply to the comment you want to hide by typing <code>[$comment hold]</code>.
<h4>Bulk actions on certain posts/comments</h4>
If you want to bulk-delte comments that belong to a certain post, comment on the post by typing <code>[$comment delete]</code>.
If you have a hierarchical post type and want to add the same tag to all direct children of a certain post plus the post itself, then comment on the post by typing <code>[$tag mytag --to="siblings,self"]</code>.
Like this, a bit complex operations can be achived with the shortcode directives.
<h4>Getting Started</h4>
To experience what this plugin does, follow these steps. 
1. After activating the plugin, pick a test post which has been published already. 
2. Go to the page of the post in front-end. 
3. Submit a comment to the post with the shortcode <code>[$post_status private]</code>.
Now it should be hidden for normal site visitors.
<ol>
<li>To revert the change, submit a comment to the post with the shortcode <code>[$post_status publish]</code>.</li>
</ol>
It should be visible to normal site visitors.
By default, the plugin enables the features for the buil-in <code>post</code> and <code>page</code> post types. If you like to support different post types, go to Dashboard -> Tools -> Shortcode Directives. There, you can pick which post types to have the ability of shortcode directives.
For usage details, please see the Other Notes seciton.
You should have grapsed the idea of how this plugin works by now. Hope you find it useful!
<h4>Supported Languages</h4>
<ul>
<li>English</li>
</ul>
<h3>Usage</h3>
<h4>$post_status</h4>
Sets a specified post status. 
Format
<pre><code>[$post_status {status}]
</code></pre>
Examples 
Changes the post status to <code>pending</code>.
<pre><code>[$post_status pending]
</code></pre>
Changes the post status to <code>draft</code>.
<pre><code>[$post_status draft]
</code></pre>
Option: –to 
Specifies which post to apply the directive operation. This <code>--to</code> option is avialble for all the directives except <code>$comment</code>. Use <code>children</code>, <code>siblings</code>, and <code>descendants</code> for builk actions. 
– self (default): the comment/post iteself. When a comment with a directive is submitted to a post, that post will be the subject post and it is considered the one denoted by the option value, <code>self</code>. 
– parent: the parent post of the subject post. 
– {post ID}: the post ID. 
– children: the direct child posts of the subjec post if the post type supports the <code>hierarchical</code> option. 
– siblings: the sibling posts of the subject post in hierarchical relationships if the post type supports the <code>hierarchical</code> option. 
– decendants: all the decendants which belong to the subject post if the post type supports the <code>hierarchical</code> option.
This moves all the descendant posts to trash.
<pre><code>[$post_status trash --to=descendants]
</code></pre>
<h4>$post_parent</h4>
Sets a post parent ID. 
Format
<pre><code>[$post_parent {post ID}]
</code></pre>
Sets a post parent of a post ID of 1451.
<pre><code>[$post_parent 1451]
</code></pre>
This removes a post parent.
<pre><code>[$post_parent 0]
</code></pre>
Option: –to 
The same option values are supported described in the <code>$post_status</code> section above.
<h4>$post_column</h4>
Sets a value with a specified post column name to an existent post column. 
Format
<pre><code>[$post_column --column={colum name} {value}]
[$post_column --column={colum name} --value="some value"]
</code></pre>
Setting the value <code>3</code> to the <code>menu_order</code> column.
<pre><code>[$post_column column=menu_order 3]
</code></pre>
When a value must have a white space, use the <code>--value</code> option.
<pre><code>[$post_column --column=post_title --value="This is a title"]
</code></pre>
Option: –to 
The same option values are supported described in the <code>$post_status</code> section above.
<h4>$post_meta</h4>
Sets a post meta value. 
Format
<pre><code>[$post_meta {key} {value}]
[$post_meta {key1}="{some value1}" {key2}="{some value2}" {key3}="{some value3}"...]
</code></pre>
This sets the post meta value <code>bar</code> to the <code>_foo</code> meta key.
<pre><code>[$post_meta _foo bar]
</code></pre>
For values containing white-spaces and multiple key-value pairs, use the attribute style format.
<pre><code>[$post_meta _question="Why did the chicken cross the road?" _answer="To get to the other side"]
</code></pre>
To delete meta keys, use the <code>--action</code> option by passing <code>delete</code>. This deletes the <code>_question</code> and <code>_answer</code> meta keys and their values from the database.
<pre><code>[$post_meta _question _answer --action="delete"]
</code></pre>
Note: the <code>--to</code> and <code>--action</code> option names are reserved by the plugin so you cannot specify them with the option name like <code>[$post_meta --action="my value" --to="another value"]</code>.
If you have to set them, use the command-line style format introduced above.
<pre><code>[$post_meta --action "Some value here."]
[$post_meta --to "Another value here."]
</code></pre>
Option: –to 
The same option values are supported described in the <code>$post_status</code> section above.
<h4>$taxonomy</h4>
Sets taxonomy terms with a specified taxonomy slug. 
Format
<pre><code>[$taxonomy --slug={taxonomy slug} {term1} {term2} {term3}...]
</code></pre>
This adds the <code>Apple</code>, <code>Banana</code>, <code>Apple Pie</code> terms of the <code>post_tag</code> taxonomy to the post.
<pre><code>[$taxonomy --slug=post_tag Apple Banana "Apple Pie"]
</code></pre>
Option: –action 
– add (default) : adds the specified terms 
– remove : removes the specified terms 
– remove_all/remove_all : removes all the associated terms 
– delete : deletes the specified terms from the database if they are assigned to the post 
– delete_all/delete-all : deletes all the associated terms from the database
This removes the <code>Apple</code>, <code>Banana</code>, <code>Apple Pie</code> terms of the <code>post_tag</code> taxonomy from the post.
<pre><code>[$taxonomy --slug=post_tag Apple Banana "Apple Pie" --action=remove]
</code></pre>
This deletes the <code>Apple</code>, <code>Banana</code>, <code>Apple Pie</code> terms of the <code>post_tag</code> taxonomy from the database if they are assigned to the post.
<pre><code>[$taxonomy --slug=post_tag Apple Banana "Apple Pie" --action=delete]
</code></pre>
This removes all the assigned terms of the <code>post_tag</code> taxonomy from the post.
<pre><code>[$taxonomy --slug=post_tag --action=remove_all]
</code></pre>
This deletes all the assigned terms of the <code>post_tag</code> taxonomy from the database.
<pre><code>[$taxonomy --slug=post_tag --action=delete_all]
</code></pre>
Option: –to 
The same option values are supported described in the <code>$post_status</code> section above.
<h4>$tag</h4>
Sets non-hierarchical taxonomy terms. 
Format
<pre><code>[$tag {tag1} {tag2} {tag3}...]
</code></pre>
When the <code>$tag</code> directive is given, the plugin searches for a non-hierarchical taxonomy associated with the post type of the post and sets the given terms to the post. If a non-hierarchical taxonomy is not found, no action will be taken. If you have multiple non-hierarchical taxonomies for a particular post type which supports shortcode directives, use the <code>$taxonomy</code> directive. See the <code>$taxonomy</code> section above.
This adds the <code>Apple</code>, <code>Banana</code>, <code>Apple Pie</code> tags to the post.
<pre><code>[$tag Apple Banana "Apple Pie"]
</code></pre>
Option: –action 
The same action values with the <code>$taxonomy</code> directive are supported.
This removes the <code>Apple</code>, <code>Banana</code>, <code>Apple Pie</code> tags from the post.
<pre><code>[$tag --action=remove Apple Banana "Apple Pie"]
</code></pre>
This deletes the <code>Apple</code>, <code>Banana</code>, <code>Apple Pie</code> terms from the database if they are assigned to the post.
<pre><code>[$tag --action=delete Apple Banana "Apple Pie"]
</code></pre>
This removes all the tags associated with the post.
<pre><code>[$tag --action=remove_all]
</code></pre>
This deletes all the tags associated with the post from the database.
<pre><code>[$tag --action=delete_all]
</code></pre>
Option: –to 
The same option values are supported described in the <code>$post_status</code> section above.
<h4>$category</h4>
Sets hierarchical taxonomy terms. 
Format
<pre><code>[$category {category1} {category2} {category3}...]
</code></pre>
When the <code>$category</code> directive is given, the plugin searches for a hierarchical taxonomy associated with the post type of the post and sets the given terms to the post. If a hierarchical taxonomy is not found, no action will be taken. If you have multiple hierarchical taxonomies for a particular post type which supports shortcode directives, use the <code>$taxonomy</code> directive. See the <code>$taxonomy</code> section above.
This adds the <code>Apple</code>, <code>Banana</code>, <code>Apple Pie</code> categories to the post.
<pre><code>[$category Apple Banana "Apple Pie"]
</code></pre>
This removes the <code>Apple</code>, <code>Banana</code>, <code>Apple Pie</code> categories from the post.
<pre><code>[$category Apple Banana "Apple Pie" --action=remove]
</code></pre>
This deletes the <code>Apple</code>, <code>Banana</code>, <code>Apple Pie</code> categories from the database if they are assigned to the post.
<pre><code>[$category --action=delete Apple Banana "Apple Pie"]
</code></pre>
This removes all the categories associated with the post.
<pre><code>[$category --action=remove_all]
</code></pre>
This deletes all the categories associated with the post from the database.
<pre><code>[$category --action=delete_all]
</code></pre>
Option: –action 
The same action values with the <code>$taxonomy</code> directive are supported.
Option: –to 
The same option values are supported described in the <code>$post_status</code> section above.
$comment
Performs certain actions againt a replying comment. If commented on a post, the action applied to all the comments which belong to the post. So be careful not to do that when you want to do someting on a single comment.
Format
<pre><code>[$comment {sub-command}]
</code></pre>
Sub-commands 
– delete|remove: deletes the comment 
– hold|disapprove: changes the comment status to <code>hold</code>. 
– trash: moves the comment to trash 
– spam: mark the commet as spam 
– convert: converts the comment to a child post.
Replying to an existent comment with the following deletes the comment.
<pre><code>[$comment delete]
</code></pre>
For hierarchical post types, the <code>convert</code> sub-command can help bulk-convert comments in to posts.
Commenting on a post (not an existent comment) converts all the comments belonging to the post into posts by keeping the hirarchical relationships.
<pre><code>[$comment convert]
</code></pre>

Alternatives to Shortcode Directives

Top alternatives