WordPress.org

1.2.6

• Updating to use Blizzard's current API

1.2.5

• Fixed the bug with rezdays coming back as unix epoch
• Added filter for display names

1.2.4

• Fixing some issues with unserializing API keys
• Tweaking the code that handles the EVE API responses

1.2.3

• Checking for EVE API error code 201

1.2.2

• Checking for EVE API error code 106

1.2.1

• Added error feedback to EVE Online plugin
• Fixing a bug preventing admin fields from appearing (which is required for EVE Online).

1.2

• Fixed bugs with the widget JavaScript
• Updated screenshots, showing off the widgets & shortcode content in the Twenty Ten theme.

1.1.1

• Disabled last-modified check for Second Life identities
• Verified compatibility with WordPress 3.0
• Trimming all names (cleaner HTML source, negates any potential issues with css white-space property)
• Made sure html output was correctly escaped

1.1.0

• Fixed Champions Online biographies
• Fixed Second Life profiles (Linden Lab are actually using valid HTML now)
• Changed mv_id_stats to use Countable and Iterator interfaces
• Added support for Star Trek Online

1.0.3

• Updated location of WoW images

1.0.2

• Fixed a bug in the Free Realms plugin.
• Removed Metaplace plugin

1.0.1

• Removed create_function in favour of static function.

1.0

• Gave admin-level users ability to delete/update all IDs.
• Decided to remove the hCard/hResume parser from the to-do list since the chances of an MMO developer having the sense to use hcard/hResume in the web profiles for player characters is slim to none.
• Refactored & cleaned up some code.

0.15.1

• Fixed bug with shortcode output

0.15.0

• Added EverQuest & EverQuest II support.

0.14.1

• Added shortcode parameter to display metaverse name as html h1-6 tag.

0.14.0

• Added shortcode support
• Switched all instances of "global $wpdb" inside the mv_id_plugin class to use mv_id_plugin::wpdb() static method.

0.13.2

• Fixed bug with Champions Online character images.

0.13.1

• Fixed bug with Champions Online character biographies.

0.13.0

• Added support for problem reporting.
• Added support for Champions Online.
• Changed "Progress Quest" skill to stat.
• Added support for displaying stats.

0.12.0

• Added an option to switch between the WordPress HTTP API and the custom one used in previous versions of MV-ID.
• Fixed a bug with parsing the WoW Armory.
• Fixed a bug that caused the incorrect character image to be displayed.
• Added display support for guild/group insignias.

0.11.0

• Switched to the HTTP API found in WP 2.8 (no more requirement for curl to be installed)

0.10.0

• Added select boxes to widget options, allowing one widget per ID.
• Fixed some minor bugs
• Converted Denis de Bernardy & Semilogic's "Autolink URI" plugin to a filter in order to implement a feature suggested by Will Norris
• Converted some logic to WP's Actions & Filters, added a filter for plugins to modify widget output (post_output_mv_id_vcard)
• Converted widgets to use WP 2.8's Widget facilities

0.9.5

• Cleaned up class name left over from using hListing
• Changed semantics of character creation dates after discussion with Tantek Çelik
  • We agreed that using the bday property wasn't quite right, so I suggested using an hCalendar event block

0.9.4

• Added support for EVE Online
• Added support for Metaverses that require API configuration in order to use.

0.9.2/3

• Fixed a bug with PHP safe mode/open_basedir interfering with CURLOPT_FOLLOWLOCATION

0.9.1

• Delete IDs when user is demoted to subscriber or deleted
  • partially implemented, demoting a user from the batch-edit screen doesn't delete the IDs.

0.9

• Moved Metaverse ID page from Settings to Users section
• Users above subscriber-level get seperate IDs
• Widget output strips duplicate IDs

0.8

• Added Skills & Stats support.
• Stats are currently only used to supply account creation dates via the hCard bday property.

0.7

• Switched from hListing with self-review to hResume
  • adding guilds/groups as "affiliations".

0.6

• Optimised the UI by using javascript to dynamically add more fields instead of using a fixed list of fields (which would take up more and more space with every metaverse that was added).