Fabio Cicerchia

This script is useful during the development of WordPress, because will extend with a set of functions.
<h3>Usage</h3>
class <code>WP_Dev_Utilities</code>:
<ul>
<li>_debug() – A function to print variable only if the user logged as administrator</li>
<li>_retrieve_user_data() – Retrive user data informations only if user is logged in</li>
<li>count_num_pages_post($id) – Returns the number of pages of a post</li>
<li>get_current_execution_time($precision = 3) – Get the current execution time</li>
<li>get_logged_username() – Returns the name of the user logged on</li>
<li>get_post_content_from_id($id) – Return the content of the post from his id</li>
<li>get_post_content_from_permalink($permalink) – Return the contents of the post permalink</li>
<li>get_post_id_from_permalink($permalink) – Return the id of the post permalink</li>
<li>is_administrator() – Check if logged user has the administrator privileges</li>
<li>get_web_browser($shortname = false, $uppercase = false) – Returns the user’s browser name</li>
<li>get_web_server($uppercase = false) – Returns the web server is use</li>
<li>get_wp_version() – Get the current wordpress version</li>
<li>get_tag_slug($title) – Get the tag slug from tag title</li>
<li>get_current_tag_slug($title) – Get the tag slug from the current tag title</li>
</ul>

WP Development Utilities

Extends the template tags with more functions that are very useful.

loonpwn

Whoops error handling, no password logins, template hints, no indexing, flush rewrites, everything a developer needs for their local development environment.
Components
<ul>
<li>Disallow Indexing Turn off the public blog option. This will modify the robots.txt generation to block all search engines</li>
<li>Flush Rewrites No more weird redirection problems when working on custom post types or taxonomies.</li>
<li>No Password Logins Just stick the user in you want to login as, write anything in the password field, and it will login! Only works when connecting from local host</li>
<li>Whoops Error Handling The error screen from laravel, now in your WordPress setup</li>
<li>Template Hints See which templates are loading for the page you are on</li>
</ul>
The goal is to exchange security for ease of use, for that reason it’s important that you take the security measures needed 
to ensure that someone can’t take advantage of the site with this plugin enabled.
If you’re running on a staging environment ensure you have setup a <a href="http://www.htaccesstools.com/htpasswd-generator/" rel="nofollow ugc">htpasswd</a>
<h4>Filters</h4>
Set Environment
<pre><code>development-environment/is-development
</code></pre>
Dynamically set how the plugin detects if the environment is development based on your own criteria.
Stop a component from loading
<pre><code>development-environment/require-component-$component
</code></pre>
Disable require of a component if you don’t want to use it. Possible values are:
<pre><code>disallow-indexing, `flush-rewrites`, `no-password-logins`, `whoops-error-handling`
</code></pre>

Development Environment

- quote from user -

"When an error is thrown it's so easy to find it and quickly debug why it happened, and the no password login makes my day so much easier 

No More Headaches!

Whoops error handling, no password logins, template hints, no indexing, flush rewrites, everything a developer needs for their local development envir …

WP Development Utilities vs Development Environment