WordPress.org

1.2.0

• Remove .profiling_enabled file, store profiling flag as a WordPress option
• Remove code that writes to .htaccess file
• Removed fix-flag-file page, no longer necessary
• Added a link to the "no visits recorded" message pointing to the help page
• Bugfix - with the manual profile "I'm done" button not showing the intended scan
• On upgrade, remove .htaccess auto_prepend_file code
• On upgrade, delete .profiling_enabled file
• Include a data point for all visits for all plugins on the detailed chart (If no data point exists, mark it as 0 to keep the line connected)
• Add Debug log feature to help diagnose why scans aren't recording properly on some sites
• Opcode optimizer detection / documentation
• Opcode optimizer compatibility
• Update the list of random URLs to scan - use 4 random categories, 4 random tags, 4 random posts, a random search word from the blog description, and the home page
• Don't include the site's RSS feed in the automated scan, it's causing problems in some browsers which expect the feed to be loaded as a document
• Support HTTP_X_REAL_IP
• Remove file locking, it's preventing the profiles from being saved on some hosts
• Removing calls to filter_var, some 5.2.x builds use --disable-filter so this isn't reliable
• Bugfix - Pausing a scan and clicking "View results" showed an error message
• Bugfix - Avoid using "../" for compatibility with open_basedir
• Upgrade routine was being done in the wrong order

1.1.3

• Bugfix - regression bug re-introduced in v 1.1.2. Thanks to user adamf for finding this so quickly!

1.1.2

• Don't show screen options if there is no table
• Show a "rate us / tweet us" box
• Add an option to circumvent browser cache
• Bugfix - Properly work with encrypted plugins (eval based obfuscation)
• Bugfix - Work with suhosin/safe mode where ini_set / set_time_limit are disabled
• Bugfix - Remove "Options -Indexes" because it's causing 500 error in some apache setups
• Bugfix - Fix a warning with theme name detection if the theme is no longer installed

1.1.1

• Bugfix - Plugin names with apostrophes broke the UI
• Bugfix - Fix a deprecated warning with callt-ime pass by reference

1.1.0

• Including plugin usage percentage / seconds in e-mail report
• Including theme name in e-mail report. Profiles created in older versions will show "unknown"
• Grammar / wording changes
• Remembering "disable opcode cache" in options table
• New option for "use my IP." If this is set, the current user's IP address will be used, if not, the stored IP pattern will be used
• IP patterns will be stored as an option
• Fixed: IP patterns were incorrectly escaped
• Now displaying profile name in the top right
• If the profile didn't record any visits (e.g. wrong IP pattern) then an error will be displayed
• Fixing pagination on the history page
• Made the legends on the charts a bit wider for sites with a lot of plugins and plugins with long names
• Added the ability to toggle series on/off in the "detailed timeline" chart
• Removed network wide activation code - each site will be "activated" when the admin logs in
• Removed "sync all profile folders whenever a blog is added/deleted" code. Profile folders will be added when admins log in, removed when blogs are removed
• When uninstalling, all profile folders and options will be removed
• Using get_plugin_data() to get plugin names. If the plugin doesn't exist anymore, or there's a problem getting the plugin name, the old formatting code is used

1.0.5

• Security - Fixed a path disclosure vulnerability
• Security - sanitized user input before it gets back to the browser
• Thanks to Julio Potier from Boiteaweb.fr

1.0.4

• Bugfix - uninstalling the plugin when it hasn't been activated can result in an error message

1.0.3

• Enforcing WordPress 3.3 requirement during activation
• Documented warning about usort() and php bug

1.0.2

• Fixed an error message when clicking "stop scan" too fast
• Brought plugin version from php file in line with version from readme.txt and tag

1.0.1

• readme.txt changes

1.0

• Automatic site profiling
• Manual site profiling
• Profile history
• Continue a profile session
• Clear opcode caches (if possible) to improve plugin function detection
• Limit profiling by IP address (regex pattern)
• Limit profiling by site URL (for MS compatibility)
• Rewrite http URLs to https to avoid SSL warnings when using wp-admin over SSL
• Hide the admin toolbar on the front-end when profiling to prevent extra plugin scripts/styles from loading
• In-app help / glossary page
• Activate / deactivate hooks to try different loader methods so the profiler runs as early as possible
• Uninstall hooks to clean up profiles
• Hooks add/delete blog to clean up profiles
• Send profile summary via e-mail