Meet WordPress coding standards on Sublime Text – SublimePhpTidy

I made the move from Coda to Sublime Text this week.

After only a week, I really, really like Sublime Text – it’s fast, pretty and customizable with a wide range of plugins available via the Package Manager.

Here are 9 reasons Sublime Text is only mighty!

I came across an old Coda plugin that I did some work on years ago that is now available on Sublime Text; the plugin helps to tidy and format your code to meet WordPress coding standards.

The plugin is available here – https://github.com/welovewordpress/SublimePhpTidy

It is pretty cool to see something you did a few years ago being picked up by someone else, improved upon and ported to a new editor that you happen to move to :).

WordPress Debug Log without Deprecated Notices

You turn on WordPress debugging only to find the log full of deprecated notices that make the log difficult to parse. Bummer.

You could spend time going through each deprecated notice and updating the offending piece of code. Or you could ask WordPress to ignore these deprecated notices (at least in the short term) by doing the following;
Weiterlesen „WordPress Debug Log without Deprecated Notices“

How to debug your WordPress plugin

If you are developing a plugin on WordPress, you will need to debug your code as you go.

To enable debugging, go to your wp-config.php file.

Find the line…
[source language=“php“]define(‚WP_DEBUG‘, false);[/source]

Replace the line above with the following…
[source language=“php“]
// Turns WordPress debugging on
define(‚WP_DEBUG‘, true);

// Tells WordPress to log everything to the /wp-content/debug.log file
define(‚WP_DEBUG_LOG‘, true);

// Doesn’t force the PHP ‚display_errors‘ variable to be on
define(‚WP_DEBUG_DISPLAY‘, false);

// Hides errors from being displayed on-screen
@ini_set(‚display_errors‘, 0);
[/source]

Now you all warnings and errors will show up in the /wp-content/debug.log file, including WordPress warnings of deprecated functions.

You can write directly to this log from your plugin using the error_log() function.

Typically…
[source language=“php“]
//output some debug string
error_log( ‚this works yo‘ );

//output some array/object
error_log( print_r( $some_obj_or_array, 1 ) );
[/source]

Kudos to this post. It has some good plugin development tips, including how to enable debugging on WordPress.