Wp Php Console Versions Save

• Misc: Add note about Chrome extension unavailability in web store
• Misc: Add plugin admin action links
• Misc: Improved settings handler
• Misc: Updated PHP Console core library to v3.1.8

• Fix: Temporarily suppress PHP warnings while connecting with PHP Console to avoid headers already sent warnings, then restore all errors reporting
• Misc: Improved PHP and WordPress compatibility loader

• Fix: Try to get rid of PHP errors related to "Unable to set PHP Console server cookie" and "Cannot modify header information - headers already sent"
• Misc: Require PHP 5.6

• Misc: Updates PHP Console core library to v3.1.7

• Misc: Bump WordPress compatibility to mark support for the latest versions

• Fix: Fixes "PHP Warning: session_start(): Cannot send session cache limiter - headers already sent" notice in logs
• Misc: Internal changes, new Settings class, deprecated methods and properties in main Plugin class
• Misc: Updated PHP Console Library to 3.1.6
• Misc: Tested up to WordPress 4.5.2

• Improved error and exception handling
• Internal changes, improved usage of Composer in plugin development
• Support for WordPress language packs
• Updated PHP Console Library to 3.1.5
• Tested up to WordPress 4.4.1

Next step will be to make the plugin more composer friendly, remove /vendor and make a better build process in grunt.

maintenance release - alternate PHP version check using WP Requirements, automated SVN deploys (experimenting with grunt to deploy automatically a new release to wordpress.org svn - doesn't really affect plugin behaviour

There were reports of PHP errors thrown when WP PHP Console was used with other plugins, particularly errors related to 'headers sent' #11. This might be due to the fact that when PHP Console is used as a WordPress plugin, being a plugin the headers are sent already and also there's no dependency management in WordPress between plugins. A workaround was found, but consists of writing the session data captured by PHP Console to a file inside WP PHP Console installation. The filename is secured by a md5 hash but this is another occasion to remind you that PHP Console shouldn't be used on a live production environment but rather to do your debugging and code analysis on a local machine.