Posts Tagged ‘changes’

Attention All Plugin Authors

29
responses
by
on
June 20th, 2009
in
WordPress

Today is the day of changelogs for plugins in the WordPress plugin repository. Back on June 15th, I vented about the fact that most Plugins didn’t provide an easily accessible changlog that notified me of why I should upgrade to the latest version of their plugin. Some plugins provided this information in the description tab while others placed it within the Other Notes link. Still others linked directly to a blog post explaining what had changed. The end user experience of trying to figure out why a plugin should be upgraded was a nightmare which is why I proposed that a new top level link be added along side Installation, Other Notes, etc called Changelog which provides a short and sweet history of version numbers and changes. This idea had been proposed before but no one managed to find time to address it. Thanks to some great work by Peter […]

[Continue Reading...]

Why 2.7 Is Not 3.0

71
responses
by
on
November 19th, 2008
in
WordPress

Over the past few weeks, I’ve witnessed many discussions throughout the WordPress community pertaining to the version number of WordPress. Many think that because of the reworked user interface and the large number of features that this version (2.7) will contain, this should allow the software to be bumped up to version 3.0 I asked the WP-Testers mailing list to see if I could get a word from either Ryan or Matt to tell me if 2.7 would remain or if it would be bumped up to 3.0.  Jane Wells chimed in saying that Matt doesn’t want to skip version numbers anymore, and that there will be ten increments between integers, so 2.9 > 3.0, not 2.9 > 2.10. Yes, 2.7 is a major change, but the numbers are based on timing, not volume or significance of change. So there you have it. WordPress 2.7 will be, WordPress 2.7. 2.8 […]

[Continue Reading...]

2.3 to 2.5 Database Changes

50
responses
by
on
March 23rd, 2008
in
WordPress

I’ve seen a number of people tell others that WordPress 2.5 will have little to no database schema changes. It looks like that is no longer the case as MichaelH has pointed out. Changes to database schema from Version 2.3 to 2.5. *Table: comments Changed ‘comment_approved’ to varchar(20) NOT NULL default ‘1’ Added KEY ‘comment_approved_date_gmt’ (comment_approved, comment_date_gmt) Added KEY ‘comment_date_gmt’ (comment_date_gmt) *Table: links Changed ‘link_visible’ to varchar(20) NOT NULL default ‘Y’ *Table: options Changed ‘autoload’ to varchar(20) NOT NULL default ‘yes’ *Table: posts Changed ‘post_status’ to varchar(20) NOT NULL default ‘publish’ Changed ‘comment_status’ to varchar(20) NOT NULL default ‘open’ Changed ‘ping_status’ to varchar(20) NOT NULL default ‘open’ *Table: term_relationships Added ‘term_order’ int(11) NOT NULL default 0 Thanks to MichaelH for putting these changes together. This information is especially useful to plugin and theme authors as it lets them know if their particular project will break.

[Continue Reading...]



Obviously Powered by WordPress. © 2003-2013

page counter
css.php