# WordPress MySQL database backup # # Generated: Sunday 10. February 2008 17:24 CET # Hostname: localhost # Database: `nmu_wordpress` # -------------------------------------------------------- # -------------------------------------------------------- # Table: `wp_comments` # -------------------------------------------------------- # # Delete any existing table `wp_comments` # DROP TABLE IF EXISTS `wp_comments`; # # Table structure of table `wp_comments` # CREATE TABLE `wp_comments` ( `comment_ID` bigint(20) unsigned NOT NULL auto_increment, `comment_post_ID` int(11) NOT NULL default '0', `comment_author` tinytext collate utf8_swedish_ci NOT NULL, `comment_author_email` varchar(100) collate utf8_swedish_ci NOT NULL default '', `comment_author_url` varchar(200) collate utf8_swedish_ci NOT NULL default '', `comment_author_IP` varchar(100) collate utf8_swedish_ci NOT NULL default '', `comment_date` datetime NOT NULL default '0000-00-00 00:00:00', `comment_date_gmt` datetime NOT NULL default '0000-00-00 00:00:00', `comment_content` text collate utf8_swedish_ci NOT NULL, `comment_karma` int(11) NOT NULL default '0', `comment_approved` enum('0','1','spam') collate utf8_swedish_ci NOT NULL default '1', `comment_agent` varchar(255) collate utf8_swedish_ci NOT NULL default '', `comment_type` varchar(20) collate utf8_swedish_ci NOT NULL default '', `comment_parent` bigint(20) NOT NULL default '0', `user_id` bigint(20) NOT NULL default '0', PRIMARY KEY (`comment_ID`), KEY `comment_approved` (`comment_approved`), KEY `comment_post_ID` (`comment_post_ID`) ) ENGINE=MyISAM AUTO_INCREMENT=3 DEFAULT CHARSET=utf8 COLLATE=utf8_swedish_ci ; # # Data contents of table `wp_comments` # # # End of data contents of table `wp_comments` # -------------------------------------------------------- # -------------------------------------------------------- # Table: `wp_links` # -------------------------------------------------------- # # Delete any existing table `wp_links` # DROP TABLE IF EXISTS `wp_links`; # # Table structure of table `wp_links` # CREATE TABLE `wp_links` ( `link_id` bigint(20) NOT NULL auto_increment, `link_url` varchar(255) collate utf8_swedish_ci NOT NULL default '', `link_name` varchar(255) collate utf8_swedish_ci NOT NULL default '', `link_image` varchar(255) collate utf8_swedish_ci NOT NULL default '', `link_target` varchar(25) collate utf8_swedish_ci NOT NULL default '', `link_category` bigint(20) NOT NULL default '0', `link_description` varchar(255) collate utf8_swedish_ci NOT NULL default '', `link_visible` enum('Y','N') collate utf8_swedish_ci NOT NULL default 'Y', `link_owner` int(11) NOT NULL default '1', `link_rating` int(11) NOT NULL default '0', `link_updated` datetime NOT NULL default '0000-00-00 00:00:00', `link_rel` varchar(255) collate utf8_swedish_ci NOT NULL default '', `link_notes` mediumtext collate utf8_swedish_ci NOT NULL, `link_rss` varchar(255) collate utf8_swedish_ci NOT NULL default '', PRIMARY KEY (`link_id`), KEY `link_category` (`link_category`), KEY `link_visible` (`link_visible`) ) ENGINE=MyISAM AUTO_INCREMENT=8 DEFAULT CHARSET=utf8 COLLATE=utf8_swedish_ci ; # # Data contents of table `wp_links` # # # End of data contents of table `wp_links` # -------------------------------------------------------- # -------------------------------------------------------- # Table: `wp_options` # -------------------------------------------------------- # # Delete any existing table `wp_options` # DROP TABLE IF EXISTS `wp_options`; # # Table structure of table `wp_options` # CREATE TABLE `wp_options` ( `option_id` bigint(20) NOT NULL auto_increment, `blog_id` int(11) NOT NULL default '0', `option_name` varchar(64) collate utf8_swedish_ci NOT NULL default '', `option_value` longtext collate utf8_swedish_ci NOT NULL, `autoload` enum('yes','no') collate utf8_swedish_ci NOT NULL default 'yes', PRIMARY KEY (`option_id`,`blog_id`,`option_name`), KEY `option_name` (`option_name`) ) ENGINE=MyISAM AUTO_INCREMENT=203 DEFAULT CHARSET=utf8 COLLATE=utf8_swedish_ci ; # # Data contents of table `wp_options` # INSERT INTO `wp_options` VALUES (1, 0, 'siteurl', 'http://nmu_w', 'yes') ; INSERT INTO `wp_options` VALUES (2, 0, 'blogname', 'Norsk målungdom', 'yes') ; INSERT INTO `wp_options` VALUES (3, 0, 'blogdescription', 'NMU, for nynorsk og alt som er bra', 'yes') ; INSERT INTO `wp_options` VALUES (65, 0, 'wp_user_roles', 'a:5:{s:13:"administrator";a:2:{s:4:"name";s:13:"Administrator";s:12:"capabilities";a:49:{s:13:"switch_themes";b:1;s:11:"edit_themes";b:1;s:16:"activate_plugins";b:1;s:12:"edit_plugins";b:1;s:10:"edit_users";b:1;s:10:"edit_files";b:1;s:14:"manage_options";b:1;s:17:"moderate_comments";b:1;s:17:"manage_categories";b:1;s:12:"manage_links";b:1;s:12:"upload_files";b:1;s:6:"import";b:1;s:15:"unfiltered_html";b:1;s:10:"edit_posts";b:1;s:17:"edit_others_posts";b:1;s:20:"edit_published_posts";b:1;s:13:"publish_posts";b:1;s:10:"edit_pages";b:1;s:4:"read";b:1;s:8:"level_10";b:1;s:7:"level_9";b:1;s:7:"level_8";b:1;s:7:"level_7";b:1;s:7:"level_6";b:1;s:7:"level_5";b:1;s:7:"level_4";b:1;s:7:"level_3";b:1;s:7:"level_2";b:1;s:7:"level_1";b:1;s:7:"level_0";b:1;s:17:"edit_others_pages";b:1;s:20:"edit_published_pages";b:1;s:13:"publish_pages";b:1;s:12:"delete_pages";b:1;s:19:"delete_others_pages";b:1;s:22:"delete_published_pages";b:1;s:12:"delete_posts";b:1;s:19:"delete_others_posts";b:1;s:22:"delete_published_posts";b:1;s:20:"delete_private_posts";b:1;s:18:"edit_private_posts";b:1;s:18:"read_private_posts";b:1;s:20:"delete_private_pages";b:1;s:18:"edit_private_pages";b:1;s:18:"read_private_pages";b:1;s:12:"delete_users";b:1;s:12:"create_users";b:1;s:17:"unfiltered_upload";b:1;s:11:"simple_tags";b:1;}}s:6:"editor";a:2:{s:4:"name";s:6:"Editor";s:12:"capabilities";a:34:{s:17:"moderate_comments";b:1;s:17:"manage_categories";b:1;s:12:"manage_links";b:1;s:12:"upload_files";b:1;s:15:"unfiltered_html";b:1;s:10:"edit_posts";b:1;s:17:"edit_others_posts";b:1;s:20:"edit_published_posts";b:1;s:13:"publish_posts";b:1;s:10:"edit_pages";b:1;s:4:"read";b:1;s:7:"level_7";b:1;s:7:"level_6";b:1;s:7:"level_5";b:1;s:7:"level_4";b:1;s:7:"level_3";b:1;s:7:"level_2";b:1;s:7:"level_1";b:1;s:7:"level_0";b:1;s:17:"edit_others_pages";b:1;s:20:"edit_published_pages";b:1;s:13:"publish_pages";b:1;s:12:"delete_pages";b:1;s:19:"delete_others_pages";b:1;s:22:"delete_published_pages";b:1;s:12:"delete_posts";b:1;s:19:"delete_others_posts";b:1;s:22:"delete_published_posts";b:1;s:20:"delete_private_posts";b:1;s:18:"edit_private_posts";b:1;s:18:"read_private_posts";b:1;s:20:"delete_private_pages";b:1;s:18:"edit_private_pages";b:1;s:18:"read_private_pages";b:1;}}s:6:"author";a:2:{s:4:"name";s:6:"Author";s:12:"capabilities";a:10:{s:12:"upload_files";b:1;s:10:"edit_posts";b:1;s:20:"edit_published_posts";b:1;s:13:"publish_posts";b:1;s:4:"read";b:1;s:7:"level_2";b:1;s:7:"level_1";b:1;s:7:"level_0";b:1;s:12:"delete_posts";b:1;s:22:"delete_published_posts";b:1;}}s:11:"contributor";a:2:{s:4:"name";s:11:"Contributor";s:12:"capabilities";a:5:{s:10:"edit_posts";b:1;s:4:"read";b:1;s:7:"level_1";b:1;s:7:"level_0";b:1;s:12:"delete_posts";b:1;}}s:10:"subscriber";a:2:{s:4:"name";s:10:"Subscriber";s:12:"capabilities";a:2:{s:4:"read";b:1;s:7:"level_0";b:1;}}}', 'yes') ; INSERT INTO `wp_options` VALUES (5, 0, 'users_can_register', '', 'yes') ; INSERT INTO `wp_options` VALUES (6, 0, 'admin_email', 'heimesida@nynorsk.no', 'yes') ; INSERT INTO `wp_options` VALUES (7, 0, 'start_of_week', '1', 'yes') ; INSERT INTO `wp_options` VALUES (8, 0, 'use_balanceTags', '', 'yes') ; INSERT INTO `wp_options` VALUES (9, 0, 'use_smilies', '', 'yes') ; INSERT INTO `wp_options` VALUES (10, 0, 'require_name_email', '1', 'yes') ; INSERT INTO `wp_options` VALUES (11, 0, 'comments_notify', '1', 'yes') ; INSERT INTO `wp_options` VALUES (12, 0, 'posts_per_rss', '10', 'yes') ; INSERT INTO `wp_options` VALUES (13, 0, 'rss_excerpt_length', '50', 'yes') ; INSERT INTO `wp_options` VALUES (14, 0, 'rss_use_excerpt', '0', 'yes') ; INSERT INTO `wp_options` VALUES (15, 0, 'mailserver_url', 'mail.example.com', 'yes') ; INSERT INTO `wp_options` VALUES (16, 0, 'mailserver_login', 'login@example.com', 'yes') ; INSERT INTO `wp_options` VALUES (17, 0, 'mailserver_pass', 'password', 'yes') ; INSERT INTO `wp_options` VALUES (18, 0, 'mailserver_port', '110', 'yes') ; INSERT INTO `wp_options` VALUES (19, 0, 'default_category', '1', 'yes') ; INSERT INTO `wp_options` VALUES (20, 0, 'default_comment_status', 'closed', 'yes') ; INSERT INTO `wp_options` VALUES (21, 0, 'default_ping_status', 'open', 'yes') ; INSERT INTO `wp_options` VALUES (22, 0, 'default_pingback_flag', '1', 'yes') ; INSERT INTO `wp_options` VALUES (23, 0, 'default_post_edit_rows', '10', 'yes') ; INSERT INTO `wp_options` VALUES (24, 0, 'posts_per_page', '10', 'yes') ; INSERT INTO `wp_options` VALUES (25, 0, 'what_to_show', 'posts', 'yes') ; INSERT INTO `wp_options` VALUES (26, 0, 'date_format', 'Y-m-d', 'yes') ; INSERT INTO `wp_options` VALUES (27, 0, 'time_format', 'G:i', 'yes') ; INSERT INTO `wp_options` VALUES (28, 0, 'links_updated_date_format', 'F j, Y g:i a', 'yes') ; INSERT INTO `wp_options` VALUES (29, 0, 'links_recently_updated_prepend', '', 'yes') ; INSERT INTO `wp_options` VALUES (30, 0, 'links_recently_updated_append', '', 'yes') ; INSERT INTO `wp_options` VALUES (31, 0, 'links_recently_updated_time', '120', 'yes') ; INSERT INTO `wp_options` VALUES (32, 0, 'comment_moderation', '', 'yes') ; INSERT INTO `wp_options` VALUES (33, 0, 'moderation_notify', '1', 'yes') ; INSERT INTO `wp_options` VALUES (34, 0, 'permalink_structure', '/%category%/%postname%/', 'yes') ; INSERT INTO `wp_options` VALUES (35, 0, 'gzipcompression', '1', 'yes') ; INSERT INTO `wp_options` VALUES (36, 0, 'hack_file', '0', 'yes') ; INSERT INTO `wp_options` VALUES (37, 0, 'blog_charset', 'UTF-8', 'yes') ; INSERT INTO `wp_options` VALUES (38, 0, 'moderation_keys', '', 'no') ; INSERT INTO `wp_options` VALUES (39, 0, 'active_plugins', 'a:7:{i:0;s:33:"Cimy_Navigator/cimy_navigator.php";i:1;s:12:"calendar.php";i:2;s:9:"hello.php";i:3;s:23:"postlists/postlists.php";i:4;s:27:"simple-tags/simple-tags.php";i:5;s:33:"top-level-cats/top-level-cats.php";i:6;s:16:"wp-db-backup.php";}', 'yes') ; INSERT INTO `wp_options` VALUES (40, 0, 'home', 'http://nmu_w', 'yes') ; INSERT INTO `wp_options` VALUES (41, 0, 'category_base', '/', 'yes') ; INSERT INTO `wp_options` VALUES (42, 0, 'ping_sites', 'http://rpc.pingomatic.com/', 'yes') ; INSERT INTO `wp_options` VALUES (43, 0, 'advanced_edit', '0', 'yes') ; INSERT INTO `wp_options` VALUES (44, 0, 'comment_max_links', '2', 'yes') ; INSERT INTO `wp_options` VALUES (45, 0, 'gmt_offset', '1', 'yes') ; INSERT INTO `wp_options` VALUES (46, 0, 'default_email_category', '1', 'yes') ; INSERT INTO `wp_options` VALUES (47, 0, 'recently_edited', 'a:4:{i:0;s:35:"wp-content/themes/default/style.css";i:1;s:38:"wp-content/plugins/akismet/akismet.php";i:2;s:34:"wp-content/themes/nmu_v2/style.css";i:3;s:0:"";}', 'no') ; INSERT INTO `wp_options` VALUES (48, 0, 'use_linksupdate', '0', 'yes') ; INSERT INTO `wp_options` VALUES (49, 0, 'template', 'nmu_v2', 'yes') ; INSERT INTO `wp_options` VALUES (50, 0, 'stylesheet', 'nmu_v2', 'yes') ; INSERT INTO `wp_options` VALUES (51, 0, 'comment_whitelist', '1', 'yes') ; INSERT INTO `wp_options` VALUES (181, 0, 'page_uris', 'a:4:{s:8:"artiklar";i:12;s:12:"organisasjon";i:9;s:8:"politikk";i:7;s:6:"om_nmu";i:2;}', 'yes') ; INSERT INTO `wp_options` VALUES (53, 0, 'blacklist_keys', '', 'no') ; INSERT INTO `wp_options` VALUES (54, 0, 'comment_registration', '', 'yes') ; INSERT INTO `wp_options` VALUES (55, 0, 'open_proxy_check', '0', 'yes') ; INSERT INTO `wp_options` VALUES (56, 0, 'rss_language', 'en', 'yes') ; INSERT INTO `wp_options` VALUES (57, 0, 'html_type', 'text/html', 'yes') ; INSERT INTO `wp_options` VALUES (58, 0, 'use_trackback', '0', 'yes') ; INSERT INTO `wp_options` VALUES (59, 0, 'default_role', 'subscriber', 'yes') ; INSERT INTO `wp_options` VALUES (61, 0, 'db_version', '6124', 'yes') ; INSERT INTO `wp_options` VALUES (62, 0, 'uploads_use_yearmonth_folders', '1', 'yes') ; INSERT INTO `wp_options` VALUES (63, 0, 'upload_path', 'wp-content/uploads', 'yes') ; INSERT INTO `wp_options` VALUES (64, 0, 'secret', '88937f7c0dda012a1166b0565fdd37fd', 'yes') ; INSERT INTO `wp_options` VALUES (82, 0, 'widget_categories', 'a:2:{s:6:"number";i:1;i:1;b:0;}', 'yes') ; INSERT INTO `wp_options` VALUES (83, 0, 'update_core', 'O:8:"stdClass":4:{s:12:"last_checked";i:1202632376;s:15:"version_checked";s:5:"2.3.1";s:8:"response";s:7:"upgrade";s:3:"url";s:30:"http://wordpress.org/download/";}', 'yes') ; INSERT INTO `wp_options` VALUES (106, 0, 'cron', 'a:1:{s:7:"version";i:2;}', 'yes') ; INSERT INTO `wp_options` VALUES (75, 0, 'stp_options', 'a:44:{s:19:"version_for_install";s:5:"1.6.1";s:10:"tags_table";s:8:"stp_tags";s:17:"admin_max_suggest";s:2:"30";s:19:"admin_tag_suggested";s:1:"1";s:14:"admin_tag_sort";s:5:"alpha";s:13:"query_varname";s:3:"tag";s:14:"trailing_slash";s:1:"0";s:8:"template";s:30:"pagetemplate.simpletagging.php";s:9:"usehyphen";s:1:"0";s:13:"use_feed_cats";s:1:"1";s:15:"meta_autoheader";s:1:"1";s:19:"meta_always_include";s:0:"";s:16:"meta_includecats";s:7:"default";s:15:"post_linkformat";s:76:"";s:17:"post_tagseparator";s:2:", ";s:16:"post_includecats";s:1:"0";s:15:"post_notagstext";s:4:"none";s:16:"cloud_linkformat";s:91:"
  • %tagname%
    • ";s:18:"cloud_tagseparator";s:1:" ";s:17:"cloud_includecats";s:1:"0";s:15:"cloud_sortorder";s:7:"natural";s:16:"cloud_displaymax";s:2:"12";s:16:"cloud_displaymin";s:1:"1";s:14:"cloud_scalemax";s:1:"5";s:14:"cloud_scalemin";s:1:"1";s:16:"cloud_notagstext";s:49:"No tags were found that match the criteria given.";s:14:"related_format";s:67:"
  • %title%
    • ";s:22:"related_postsseparator";s:1:" ";s:17:"related_sortorder";s:9:"date-desc";s:17:"related_limit_qty";s:1:"5";s:18:"related_limit_days";s:4:"3650";s:18:"related_dateformat";s:5:"Y-m-d";s:20:"related_nothingfound";s:14:"
  • Ingen
    • ";s:20:"related_includepages";s:1:"1";s:18:"relatedtags_format";s:94:"
  • %count% + %tagname%
    • ";s:24:"relatedtags_tagseparator";s:1:" ";s:21:"relatedtags_sortorder";s:9:"alpha-asc";s:24:"relatedtags_nonfoundtext";s:22:"No related tags found.";s:25:"relatedtags_remove_format";s:53:"
  • » remove %tagname%
    • ";s:28:"relatedtags_remove_separator";s:1:" ";s:31:"relatedtags_remove_nonfoundtext";s:15:"
  •  
    • ";s:13:"tag_embed_use";s:1:"0";s:15:"tag_embed_start";s:6:"[tags]";s:13:"tag_embed_end";s:7:"[/tags]";}', 'yes') ; INSERT INTO `wp_options` VALUES (85, 0, 'blog_public', '1', 'yes') ; INSERT INTO `wp_options` VALUES (86, 0, 'default_link_category', '4', 'yes') ; INSERT INTO `wp_options` VALUES (87, 0, 'show_on_front', 'posts', 'yes') ; INSERT INTO `wp_options` VALUES (88, 0, 'tag_base', '/merkelapp', 'yes') ; INSERT INTO `wp_options` VALUES (91, 0, 'rss_14a2caba8be2c42cf8a8bd338079b1e0', 'O:9:"MagpieRSS":17:{s:6:"parser";i:0;s:12:"current_item";a:0:{}s:5:"items";a:0:{}s:7:"channel";a:4:{s:5:"title";s:38:"Google Blog Search: link:http://nmu_w/";s:4:"link";s:115:"http://blogsearch.google.com/blogsearch?hl=en&scoring=d&ie=ISO-8859-1&num=10&partner=wordpress&q=link:http://nmu_w/";s:11:"description";s:73:"Your search - link:http://nmu_w/ - did not match any documents. ";s:7:"tagline";s:73:"Your search - link:http://nmu_w/ - did not match any documents. ";}s:9:"textinput";a:0:{}s:5:"image";a:0:{}s:9:"feed_type";s:3:"RSS";s:12:"feed_version";s:3:"2.0";s:5:"stack";a:0:{}s:9:"inchannel";b:0;s:6:"initem";b:0;s:9:"incontent";b:0;s:11:"intextinput";b:0;s:7:"inimage";b:0;s:13:"current_field";s:0:"";s:17:"current_namespace";b:0;s:19:"_CONTENT_CONSTRUCTS";a:6:{i:0;s:7:"content";i:1;s:7:"summary";i:2;s:4:"info";i:3;s:5:"title";i:4;s:7:"tagline";i:5;s:9:"copyright";}}', 'no') ; INSERT INTO `wp_options` VALUES (92, 0, 'rss_14a2caba8be2c42cf8a8bd338079b1e0_ts', '1202658548', 'no') ; INSERT INTO `wp_options` VALUES (93, 0, 'rss_0ff4b43bd116a9d8720d689c80e7dfd4', 'O:9:"MagpieRSS":19:{s:6:"parser";i:0;s:12:"current_item";a:0:{}s:5:"items";a:10:{i:0;a:12:{s:5:"title";s:15:"WordPress 2.3.3";s:4:"link";s:55:"http://wordpress.org/development/2008/02/wordpress-233/";s:8:"comments";s:64:"http://wordpress.org/development/2008/02/wordpress-233/#comments";s:7:"pubdate";s:31:"Tue, 05 Feb 2008 05:02:45 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Ryan";}s:8:"category";s:11:"Development";s:4:"guid";s:39:"http://wordpress.org/development/?p=225";s:11:"description";s:307:"WordPress 2.3.3 is an urgent security release. If you have registration enabled a flaw was found in the XML-RPC implementation such that a specially crafted request would allow a user to edit posts of other users on that blog. In addition to fixing this security flaw, 2.3.3 fixes a few minor bugs. [...]";s:7:"content";a:1:{s:7:"encoded";s:1208:"

    WordPress 2.3.3 is an urgent security release. If you have registration enabled a flaw was found in the XML-RPC implementation such that a specially crafted request would allow a user to edit posts of other users on that blog. In addition to fixing this security flaw, 2.3.3 fixes a few minor bugs. If you are interested only in the security fix, download the fixed version of xmlrpc.php and copy it over your existing xmlrpc.php. Otherwise, you can get the entire release here.

    \n

    Also, there is a vulnerability in the WP-Forum plugin that is being actively exploited right now. If you are using this plugin, please remove it until an update is available from its author.

    \n

    Since we are talking security, remember to use strong passwords and change them regularly.  While you’re updating WP and your plugins, consider refreshing your passwords.

    \n";}s:3:"wfw";a:1:{s:10:"commentrss";s:60:"http://wordpress.org/development/2008/02/wordpress-233/feed/";}s:7:"summary";s:307:"WordPress 2.3.3 is an urgent security release. If you have registration enabled a flaw was found in the XML-RPC implementation such that a specially crafted request would allow a user to edit posts of other users on that blog. In addition to fixing this security flaw, 2.3.3 fixes a few minor bugs. [...]";s:12:"atom_content";s:1208:"

    WordPress 2.3.3 is an urgent security release. If you have registration enabled a flaw was found in the XML-RPC implementation such that a specially crafted request would allow a user to edit posts of other users on that blog. In addition to fixing this security flaw, 2.3.3 fixes a few minor bugs. If you are interested only in the security fix, download the fixed version of xmlrpc.php and copy it over your existing xmlrpc.php. Otherwise, you can get the entire release here.

    \n

    Also, there is a vulnerability in the WP-Forum plugin that is being actively exploited right now. If you are using this plugin, please remove it until an update is available from its author.

    \n

    Since we are talking security, remember to use strong passwords and change them regularly.  While you’re updating WP and your plugins, consider refreshing your passwords.

    \n";}i:1;a:12:{s:5:"title";s:15:"WordPress 2.3.2";s:4:"link";s:55:"http://wordpress.org/development/2007/12/wordpress-232/";s:8:"comments";s:64:"http://wordpress.org/development/2007/12/wordpress-232/#comments";s:7:"pubdate";s:31:"Sat, 29 Dec 2007 22:44:09 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Ryan";}s:8:"category";s:8:"Releases";s:4:"guid";s:55:"http://wordpress.org/development/2007/12/wordpress-232/";s:11:"description";s:325:"WordPress 2.3.2 is an urgent security release that fixes a bug that can be used to expose your draft posts. 2.3.2 also suppresses some error messages that can give away information about your database table structure and limits and stops some information leaks in the XML-RPC and APP implementations. Get 2.3.2 now to [...]";s:7:"content";a:1:{s:7:"encoded";s:1243:"

    WordPress 2.3.2 is an urgent security release that fixes a bug that can be used to expose your draft posts. 2.3.2 also suppresses some error messages that can give away information about your database table structure and limits and stops some information leaks in the XML-RPC and APP implementations. Get 2.3.2 now to protect your blog from these disclosures.

    \n

    As a little bonus, 2.3.2 allows you to define a custom DB error page. Place your custom template at wp-content/db-error.php. If WP has a problem connecting to your database, this page will displayed rather than the default error message.

    \n

    For more detail on what’s new in 2.3.2, view the list of fixed bugs and see the changes between 2.3.1 and 2.3.2.

    \n

    Special thanks to Alex Concha for his help on this release.

    \n";}s:3:"wfw";a:1:{s:10:"commentrss";s:60:"http://wordpress.org/development/2007/12/wordpress-232/feed/";}s:7:"summary";s:325:"WordPress 2.3.2 is an urgent security release that fixes a bug that can be used to expose your draft posts. 2.3.2 also suppresses some error messages that can give away information about your database table structure and limits and stops some information leaks in the XML-RPC and APP implementations. Get 2.3.2 now to [...]";s:12:"atom_content";s:1243:"

    WordPress 2.3.2 is an urgent security release that fixes a bug that can be used to expose your draft posts. 2.3.2 also suppresses some error messages that can give away information about your database table structure and limits and stops some information leaks in the XML-RPC and APP implementations. Get 2.3.2 now to protect your blog from these disclosures.

    \n

    As a little bonus, 2.3.2 allows you to define a custom DB error page. Place your custom template at wp-content/db-error.php. If WP has a problem connecting to your database, this page will displayed rather than the default error message.

    \n

    For more detail on what’s new in 2.3.2, view the list of fixed bugs and see the changes between 2.3.1 and 2.3.2.

    \n

    Special thanks to Alex Concha for his help on this release.

    \n";}i:2;a:12:{s:5:"title";s:27:"Stay Warm, WordPress Hoodie";s:4:"link";s:58:"http://wordpress.org/development/2007/12/wordpress-hoodie/";s:8:"comments";s:67:"http://wordpress.org/development/2007/12/wordpress-hoodie/#comments";s:7:"pubdate";s:31:"Sat, 29 Dec 2007 18:39:05 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:8:"category";s:27:"Storefirefoxschwagwordpress";s:4:"guid";s:58:"http://wordpress.org/development/2007/12/wordpress-hoodie/";s:11:"description";s:371:"A least for those of your in the Northern hemisphere, it’s been a little chilly recently. If you’re like me you’re thinking, “WordPress keeps my servers running hot, couldn’t it warm me too?”\nYes, it can.\n\nYou can now buy hip WordPress hoodies in our store so when you’re not blogging you can loiter around the neighborhood [...]";s:7:"content";a:1:{s:7:"encoded";s:1059:"

    A least for those of your in the Northern hemisphere, it’s been a little chilly recently. If you’re like me you’re thinking, “WordPress keeps my servers running hot, couldn’t it warm me too?”

    \n

    Yes, it can.

    \n

    WordPress Hoodies

    \n

    You can now buy hip WordPress hoodies in our store so when you’re not blogging you can loiter around the neighborhood like the people in the picture above. As before, we ship locally and internationally.

    \n

    If you find you’re still in the Open Source Hoodie mood afterward, you can check out this cool Firefox one from our friends at Mozilla.

    \n

    Hint: Buy the hoodie a size larger than you normally would, they run small. They’ll begin processing the orders on January 2nd.

    \n";}s:3:"wfw";a:1:{s:10:"commentrss";s:63:"http://wordpress.org/development/2007/12/wordpress-hoodie/feed/";}s:7:"summary";s:371:"A least for those of your in the Northern hemisphere, it’s been a little chilly recently. If you’re like me you’re thinking, “WordPress keeps my servers running hot, couldn’t it warm me too?”\nYes, it can.\n\nYou can now buy hip WordPress hoodies in our store so when you’re not blogging you can loiter around the neighborhood [...]";s:12:"atom_content";s:1059:"

    A least for those of your in the Northern hemisphere, it’s been a little chilly recently. If you’re like me you’re thinking, “WordPress keeps my servers running hot, couldn’t it warm me too?”

    \n

    Yes, it can.

    \n

    WordPress Hoodies

    \n

    You can now buy hip WordPress hoodies in our store so when you’re not blogging you can loiter around the neighborhood like the people in the picture above. As before, we ship locally and internationally.

    \n

    If you find you’re still in the Open Source Hoodie mood afterward, you can check out this cool Firefox one from our friends at Mozilla.

    \n

    Hint: Buy the hoodie a size larger than you normally would, they run small. They’ll begin processing the orders on January 2nd.

    \n";}i:3;a:12:{s:5:"title";s:15:"WordPress 2.3.1";s:4:"link";s:55:"http://wordpress.org/development/2007/10/wordpress-231/";s:8:"comments";s:64:"http://wordpress.org/development/2007/10/wordpress-231/#comments";s:7:"pubdate";s:31:"Fri, 26 Oct 2007 20:55:30 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Ryan";}s:8:"category";s:8:"Releases";s:4:"guid";s:55:"http://wordpress.org/development/2007/10/wordpress-231/";s:11:"description";s:367:"WordPress 2.3.1 is now available. 2.3.1 is a bug-fix and security release for the 2.3 series.\n2.3.1 fixes over twenty bugs. Some of the notable fixes are:\n\n Tagging support for Windows Live Writer\nFixes for a login bug that affected those with a Blog Address different than\ntheir WordPress Address\nFaster taxonomy database queries, especially tag intersection [...]";s:7:"content";a:1:{s:7:"encoded";s:1357:"

    WordPress 2.3.1 is now available. 2.3.1 is a bug-fix and security release for the 2.3 series.

    \n

    2.3.1 fixes over twenty bugs. Some of the notable fixes are:

    \n\n

    Unfortunately, some security issues were found in 2.3. Janek Vind found an XSS problem that can be exploited if your php setup has register_globals enabled. For this reason, upgrading to 2.3.1 is advised.

    \n

    The full set of changes between 2.3 and 2.3.1 is available for viewing on trac.

    \n

    Get 2.3.1 from the download page and enjoy.

    \n";}s:3:"wfw";a:1:{s:10:"commentrss";s:60:"http://wordpress.org/development/2007/10/wordpress-231/feed/";}s:7:"summary";s:367:"WordPress 2.3.1 is now available. 2.3.1 is a bug-fix and security release for the 2.3 series.\n2.3.1 fixes over twenty bugs. Some of the notable fixes are:\n\n Tagging support for Windows Live Writer\nFixes for a login bug that affected those with a Blog Address different than\ntheir WordPress Address\nFaster taxonomy database queries, especially tag intersection [...]";s:12:"atom_content";s:1357:"

    WordPress 2.3.1 is now available. 2.3.1 is a bug-fix and security release for the 2.3 series.

    \n

    2.3.1 fixes over twenty bugs. Some of the notable fixes are:

    \n\n

    Unfortunately, some security issues were found in 2.3. Janek Vind found an XSS problem that can be exploited if your php setup has register_globals enabled. For this reason, upgrading to 2.3.1 is advised.

    \n

    The full set of changes between 2.3 and 2.3.1 is available for viewing on trac.

    \n

    Get 2.3.1 from the download page and enjoy.

    \n";}i:4;a:12:{s:5:"title";s:35:"WordPress 2.3.1 Release Candidate 1";s:4:"link";s:75:"http://wordpress.org/development/2007/10/wordpress-231-release-candidate-1/";s:8:"comments";s:84:"http://wordpress.org/development/2007/10/wordpress-231-release-candidate-1/#comments";s:7:"pubdate";s:31:"Wed, 24 Oct 2007 22:53:59 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Ryan";}s:8:"category";s:8:"Releases";s:4:"guid";s:75:"http://wordpress.org/development/2007/10/wordpress-231-release-candidate-1/";s:11:"description";s:319:"WordPress 2.3.1 is almost ready to go. Before we send it out the door, we’re making a release candidate available so everyone can give it a last look.\n2.3.1 fixes over twenty bugs. Some of the notable fixes are:\n\n Tagging support for Windows Live Writer\nA login bug that affected those with a Blog Address [...]";s:7:"content";a:1:{s:7:"encoded";s:1398:"

    WordPress 2.3.1 is almost ready to go. Before we send it out the door, we’re making a release candidate available so everyone can give it a last look.

    \n

    2.3.1 fixes over twenty bugs. Some of the notable fixes are:

    \n\n

    More details will be provided in the final release announcement. Until then, download RC1 and let us know if it fixes a particular bug in 2.3 that was annoying you. If you find that something has broken since 2.3, please open a ticket so we can address the problem before the final 2.3.1 release.

    \n";}s:3:"wfw";a:1:{s:10:"commentrss";s:80:"http://wordpress.org/development/2007/10/wordpress-231-release-candidate-1/feed/";}s:7:"summary";s:319:"WordPress 2.3.1 is almost ready to go. Before we send it out the door, we’re making a release candidate available so everyone can give it a last look.\n2.3.1 fixes over twenty bugs. Some of the notable fixes are:\n\n Tagging support for Windows Live Writer\nA login bug that affected those with a Blog Address [...]";s:12:"atom_content";s:1398:"

    WordPress 2.3.1 is almost ready to go. Before we send it out the door, we’re making a release candidate available so everyone can give it a last look.

    \n

    2.3.1 fixes over twenty bugs. Some of the notable fixes are:

    \n\n

    More details will be provided in the final release announcement. Until then, download RC1 and let us know if it fixes a particular bug in 2.3 that was annoying you. If you find that something has broken since 2.3, please open a ticket so we can address the problem before the final 2.3.1 release.

    \n";}i:5;a:12:{s:5:"title";s:13:"WordPress 2.3";s:4:"link";s:54:"http://wordpress.org/development/2007/09/wordpress-23/";s:8:"comments";s:63:"http://wordpress.org/development/2007/09/wordpress-23/#comments";s:7:"pubdate";s:31:"Tue, 25 Sep 2007 01:22:54 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:8:"category";s:66:"DevelopmentReleasestaggingtaxonomyupdate notificationwordpress 2.3";s:4:"guid";s:54:"http://wordpress.org/development/2007/09/wordpress-23/";s:11:"description";s:379:"I’m thrilled to announce that Version 2.3 “Dexter” of WordPress is now ready for the world. This release includes native tagging support, plugin update notification, URL handling improvements, and much more. This release is named for the great tenor saxophonist Dexter Gordon.\nThe entire team is really proud of this release, and I’m happy that this [...]";s:7:"content";a:1:{s:7:"encoded";s:4883:"

    I’m thrilled to announce that Version 2.3 “Dexter” of WordPress is now ready for the world. This release includes native tagging support, plugin update notification, URL handling improvements, and much more. This release is named for the great tenor saxophonist Dexter Gordon.

    \n

    The entire team is really proud of this release, and I’m happy that this is our second on-time release under our new development schedule. The grand experiment of a more agile WordPress with significant features in the hands of users more often is working. I could write a blog post about each new feature, but I’ll try to be brief:

    \n
      \n
    1. Native tagging support allows you to use tags in addition to categories on your posts, if you so choose. We’ve included importers for the Ultimate Tag Warrior, Jerome’s Keywords, Simple Tags, and Bunny’s Technorati Tag plugins so if you’ve already been using a tagging plugin you can bring your data into the new system. The tagging system is also wicked-fast, so your host won’t mind.
      2. \n
    2. Our new update notification lets you know when there is a new release of WordPress or when any of the plugins you use has an update available. It works by sending your blog URL, plugins, and version information to our new api.wordpress.org service which then compares it to the plugin database and tells you whats the latest and greatest you can use.
      3. \n
    3. We’ve cleaned up URLs a bunch in a feature we call canonical URLs which does things like enforce your no-www preference, redirect posts with changed slugs so a link never goes bad, redirect URLs that get cut off in emails on similar to the correct post, and much more. This helps your users, and it also helps your search engine optimization, as search engines like for each page to be available in one canonical location. More info here.
      4. \n
    4. Our new pending review feature will be great for multi-author blogs. It allows authors to submit a post for review by an editor or administrator, where before they would just have to save a draft and hope someone noticed it.
      5. \n
    5. There is new advanced WYSIWYG functionality (we call it the kitchen sink button) that allows you to access some features of TinyMCE that were previously hidden.
      6. \n
    \n

    You’ll notice that two of those features are straight out of the most-voted for ideas list. That’s just the user facing stuff, if you’re a developer you’ll be interested in:

    \n
      \n
    1. Full and complete Atom 1.0 support, including the publishing protocol.
      2. \n
    2. We’re using the new jQuery which is “800% faster.”
      3. \n
    3. Behind the user-facing tags system is a really kickass taxonomy system, which adds a ton of flexibility. It’s probably the biggest schema upgrade since version 1.5.
      4. \n
    4. The importers have been revamped to be more memory efficient, and you can now add an importer through a plugin.
      5. \n
    5. Through hooks and filters you can now override the update system, the dashboard RSS feeds, the feed parser, and tons more than you could in 2.2.
      6. \n
    6. The new $wpdb->prepare() way of doing SQL queries.
      7. \n
    7. Finally there were over 351 tickets in Trac closed for this release, with over a hundred people contributing. This is the polish, the hundreds of tiny bug fixes and features that make WordPress what it is.
      8. \n
    \n

    You can view the Codex for more information about the release and some screenshots. And of course the place to download is always the same. Before you upgrade you may want to check out our Preparing for 2.3 post and the list of compatible plugins on the Codex.

    \n

    A number of people are hosting upgrade parties around the world, including myself in San Francisco. If you are let me know and I’ll promote it on my blog.

    \n";}s:3:"wfw";a:1:{s:10:"commentrss";s:59:"http://wordpress.org/development/2007/09/wordpress-23/feed/";}s:7:"summary";s:379:"I’m thrilled to announce that Version 2.3 “Dexter” of WordPress is now ready for the world. This release includes native tagging support, plugin update notification, URL handling improvements, and much more. This release is named for the great tenor saxophonist Dexter Gordon.\nThe entire team is really proud of this release, and I’m happy that this [...]";s:12:"atom_content";s:4883:"

    I’m thrilled to announce that Version 2.3 “Dexter” of WordPress is now ready for the world. This release includes native tagging support, plugin update notification, URL handling improvements, and much more. This release is named for the great tenor saxophonist Dexter Gordon.

    \n

    The entire team is really proud of this release, and I’m happy that this is our second on-time release under our new development schedule. The grand experiment of a more agile WordPress with significant features in the hands of users more often is working. I could write a blog post about each new feature, but I’ll try to be brief:

    \n
      \n
    1. Native tagging support allows you to use tags in addition to categories on your posts, if you so choose. We’ve included importers for the Ultimate Tag Warrior, Jerome’s Keywords, Simple Tags, and Bunny’s Technorati Tag plugins so if you’ve already been using a tagging plugin you can bring your data into the new system. The tagging system is also wicked-fast, so your host won’t mind.
      2. \n
    2. Our new update notification lets you know when there is a new release of WordPress or when any of the plugins you use has an update available. It works by sending your blog URL, plugins, and version information to our new api.wordpress.org service which then compares it to the plugin database and tells you whats the latest and greatest you can use.
      3. \n
    3. We’ve cleaned up URLs a bunch in a feature we call canonical URLs which does things like enforce your no-www preference, redirect posts with changed slugs so a link never goes bad, redirect URLs that get cut off in emails on similar to the correct post, and much more. This helps your users, and it also helps your search engine optimization, as search engines like for each page to be available in one canonical location. More info here.
      4. \n
    4. Our new pending review feature will be great for multi-author blogs. It allows authors to submit a post for review by an editor or administrator, where before they would just have to save a draft and hope someone noticed it.
      5. \n
    5. There is new advanced WYSIWYG functionality (we call it the kitchen sink button) that allows you to access some features of TinyMCE that were previously hidden.
      6. \n
    \n

    You’ll notice that two of those features are straight out of the most-voted for ideas list. That’s just the user facing stuff, if you’re a developer you’ll be interested in:

    \n
      \n
    1. Full and complete Atom 1.0 support, including the publishing protocol.
      2. \n
    2. We’re using the new jQuery which is “800% faster.”
      3. \n
    3. Behind the user-facing tags system is a really kickass taxonomy system, which adds a ton of flexibility. It’s probably the biggest schema upgrade since version 1.5.
      4. \n
    4. The importers have been revamped to be more memory efficient, and you can now add an importer through a plugin.
      5. \n
    5. Through hooks and filters you can now override the update system, the dashboard RSS feeds, the feed parser, and tons more than you could in 2.2.
      6. \n
    6. The new $wpdb->prepare() way of doing SQL queries.
      7. \n
    7. Finally there were over 351 tickets in Trac closed for this release, with over a hundred people contributing. This is the polish, the hundreds of tiny bug fixes and features that make WordPress what it is.
      8. \n
    \n

    You can view the Codex for more information about the release and some screenshots. And of course the place to download is always the same. Before you upgrade you may want to check out our Preparing for 2.3 post and the list of compatible plugins on the Codex.

    \n

    A number of people are hosting upgrade parties around the world, including myself in San Francisco. If you are let me know and I’ll promote it on my blog.

    \n";}i:6;a:12:{s:5:"title";s:9:"New Faces";s:4:"link";s:51:"http://wordpress.org/development/2007/09/new-faces/";s:8:"comments";s:60:"http://wordpress.org/development/2007/09/new-faces/#comments";s:7:"pubdate";s:31:"Mon, 24 Sep 2007 05:41:14 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:8:"category";s:50:"DevelopmentMetamark jaquithpeter westwoodwordpress";s:4:"guid";s:51:"http://wordpress.org/development/2007/09/new-faces/";s:11:"description";s:332:"If you follow WordPress development closely you’ve probably noticed a few new faces around lately, or to be more accurate a few old faces who are taking on bigger roles in the community. I would like to take this opportunity to announce and publicly congratulate Mark Jaquith and Peter Westwood who have both become lead [...]";s:7:"content";a:1:{s:7:"encoded";s:1398:"

    If you follow WordPress development closely you’ve probably noticed a few new faces around lately, or to be more accurate a few old faces who are taking on bigger roles in the community. I would like to take this opportunity to announce and publicly congratulate Mark Jaquith and Peter Westwood who have both become lead developers, the highest development honor on WordPress.org.

    \n

    Mark Jaquith has been using and contributing to WordPress since 2004. Mark especially enjoys watching people use WordPress to express themselves in areas of the world where free expression is suppressed. But, being a voracious consumer of information, he probably reads your cat blog too.

    \n

    Peter works as an Embedded Software Engineer developing a web-enabled BMS controller. Using WordPress since version 1.0.1, Peter spends his spare time triaging bugs on Trac and investigating new open source tools. When not at the computer Peter can often be found photographing flowers, animals and cars and listening to a wide variety of music.

    \n";}s:3:"wfw";a:1:{s:10:"commentrss";s:56:"http://wordpress.org/development/2007/09/new-faces/feed/";}s:7:"summary";s:332:"If you follow WordPress development closely you’ve probably noticed a few new faces around lately, or to be more accurate a few old faces who are taking on bigger roles in the community. I would like to take this opportunity to announce and publicly congratulate Mark Jaquith and Peter Westwood who have both become lead [...]";s:12:"atom_content";s:1398:"

    If you follow WordPress development closely you’ve probably noticed a few new faces around lately, or to be more accurate a few old faces who are taking on bigger roles in the community. I would like to take this opportunity to announce and publicly congratulate Mark Jaquith and Peter Westwood who have both become lead developers, the highest development honor on WordPress.org.

    \n

    Mark Jaquith has been using and contributing to WordPress since 2004. Mark especially enjoys watching people use WordPress to express themselves in areas of the world where free expression is suppressed. But, being a voracious consumer of information, he probably reads your cat blog too.

    \n

    Peter works as an Embedded Software Engineer developing a web-enabled BMS controller. Using WordPress since version 1.0.1, Peter spends his spare time triaging bugs on Trac and investigating new open source tools. When not at the computer Peter can often be found photographing flowers, animals and cars and listening to a wide variety of music.

    \n";}i:7;a:12:{s:5:"title";s:17:"Preparing for 2.3";s:4:"link";s:58:"http://wordpress.org/development/2007/09/preparing-for-23/";s:8:"comments";s:67:"http://wordpress.org/development/2007/09/preparing-for-23/#comments";s:7:"pubdate";s:31:"Sat, 22 Sep 2007 10:00:30 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:8:"category";s:4:"Meta";s:4:"guid";s:58:"http://wordpress.org/development/2007/09/preparing-for-23/";s:11:"description";s:288:"In just a few short days WordPress 2.3 will be coming out with tons of new features that (hopefully) will make you want to upgrade right away. Well while you have a bit of time over this lovely weekend, here are some things you can do to help yourself prepare for the big upgrade on [...]";s:7:"content";a:1:{s:7:"encoded";s:1693:"

    In just a few short days WordPress 2.3 will be coming out with tons of new features that (hopefully) will make you want to upgrade right away. Well while you have a bit of time over this lovely weekend, here are some things you can do to help yourself prepare for the big upgrade on Monday:

    \n\n

    If you have any other ideas put them on your blog and pingback this post.

    \n";}s:3:"wfw";a:1:{s:10:"commentrss";s:63:"http://wordpress.org/development/2007/09/preparing-for-23/feed/";}s:7:"summary";s:288:"In just a few short days WordPress 2.3 will be coming out with tons of new features that (hopefully) will make you want to upgrade right away. Well while you have a bit of time over this lovely weekend, here are some things you can do to help yourself prepare for the big upgrade on [...]";s:12:"atom_content";s:1693:"

    In just a few short days WordPress 2.3 will be coming out with tons of new features that (hopefully) will make you want to upgrade right away. Well while you have a bit of time over this lovely weekend, here are some things you can do to help yourself prepare for the big upgrade on Monday:

    \n\n

    If you have any other ideas put them on your blog and pingback this post.

    \n";}i:8;a:12:{s:5:"title";s:33:"WordPress 2.3 Release Candidate 1";s:4:"link";s:74:"http://wordpress.org/development/2007/09/wordpress-23-release-candidate-1/";s:8:"comments";s:83:"http://wordpress.org/development/2007/09/wordpress-23-release-candidate-1/#comments";s:7:"pubdate";s:31:"Wed, 19 Sep 2007 04:50:10 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Ryan";}s:8:"category";s:8:"Releases";s:4:"guid";s:74:"http://wordpress.org/development/2007/09/wordpress-23-release-candidate-1/";s:11:"description";s:300:"The first release candidate for WordPress 2.3 is now available. We’ve spent the week since beta 3 fixing bugs and shaping RC1 into release candidate material. If you would like try RC1 and help us get 2.3 ready for its final release on Monday the 24th, download RC1 here and report any [...]";s:7:"content";a:1:{s:7:"encoded";s:871:"

    The first release candidate for WordPress 2.3 is now available. We’ve spent the week since beta 3 fixing bugs and shaping RC1 into release candidate material. If you would like try RC1 and help us get 2.3 ready for its final release on Monday the 24th, download RC1 here and report any bugs you find. Although we consider this release candidate to be stable, keep in mind that this is still pre-release software. You may find some lingering bugs. Please back up your database before upgrading. If you have problems with RC1, you will not be able to revert back to your previous release without a database backup.

    \n

    And a big thanks to those of you who have been testing the betas and now the RC. Your efforts make 2.3 better for everyone.

    \n";}s:3:"wfw";a:1:{s:10:"commentrss";s:79:"http://wordpress.org/development/2007/09/wordpress-23-release-candidate-1/feed/";}s:7:"summary";s:300:"The first release candidate for WordPress 2.3 is now available. We’ve spent the week since beta 3 fixing bugs and shaping RC1 into release candidate material. If you would like try RC1 and help us get 2.3 ready for its final release on Monday the 24th, download RC1 here and report any [...]";s:12:"atom_content";s:871:"

    The first release candidate for WordPress 2.3 is now available. We’ve spent the week since beta 3 fixing bugs and shaping RC1 into release candidate material. If you would like try RC1 and help us get 2.3 ready for its final release on Monday the 24th, download RC1 here and report any bugs you find. Although we consider this release candidate to be stable, keep in mind that this is still pre-release software. You may find some lingering bugs. Please back up your database before upgrading. If you have problems with RC1, you will not be able to revert back to your previous release without a database backup.

    \n

    And a big thanks to those of you who have been testing the betas and now the RC. Your efforts make 2.3 better for everyone.

    \n";}i:9;a:12:{s:5:"title";s:20:"WordPress 2.3 Beta 3";s:4:"link";s:61:"http://wordpress.org/development/2007/09/wordpress-23-beta-3/";s:8:"comments";s:70:"http://wordpress.org/development/2007/09/wordpress-23-beta-3/#comments";s:7:"pubdate";s:31:"Tue, 11 Sep 2007 03:24:42 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Ryan";}s:8:"category";s:8:"Releases";s:4:"guid";s:61:"http://wordpress.org/development/2007/09/wordpress-23-beta-3/";s:11:"description";s:311:"Beta 3, the third and final beta for WordPress 2.3, is now available. Many bugs have been fixed since the second beta, and we could use your help finding and fixing more bugs in preparation for the first Release Candidate due next Monday. The standard disclaimer for betas applies. Beta 3 is pre-release [...]";s:7:"content";a:1:{s:7:"encoded";s:644:"

    Beta 3, the third and final beta for WordPress 2.3, is now available. Many bugs have been fixed since the second beta, and we could use your help finding and fixing more bugs in preparation for the first Release Candidate due next Monday. The standard disclaimer for betas applies. Beta 3 is pre-release software that is still being tested. If you would like try out Beta 3 and help report bugs, join the wp-testers mailing list and download beta 3 here.

    \n";}s:3:"wfw";a:1:{s:10:"commentrss";s:66:"http://wordpress.org/development/2007/09/wordpress-23-beta-3/feed/";}s:7:"summary";s:311:"Beta 3, the third and final beta for WordPress 2.3, is now available. Many bugs have been fixed since the second beta, and we could use your help finding and fixing more bugs in preparation for the first Release Candidate due next Monday. The standard disclaimer for betas applies. Beta 3 is pre-release [...]";s:12:"atom_content";s:644:"

    Beta 3, the third and final beta for WordPress 2.3, is now available. Many bugs have been fixed since the second beta, and we could use your help finding and fixing more bugs in preparation for the first Release Candidate due next Monday. The standard disclaimer for betas applies. Beta 3 is pre-release software that is still being tested. If you would like try out Beta 3 and help report bugs, join the wp-testers mailing list and download beta 3 here.

    \n";}}s:7:"channel";a:7:{s:5:"title";s:26:"WordPress Development Blog";s:4:"link";s:32:"http://wordpress.org/development";s:11:"description";s:33:"WordPress development and updates";s:7:"pubdate";s:31:"Tue, 05 Feb 2008 16:14:37 +0000";s:9:"generator";s:36:"http://wordpress.org/?v=2.4-bleeding";s:8:"language";s:2:"en";s:7:"tagline";s:33:"WordPress development and updates";}s:9:"textinput";a:0:{}s:5:"image";a:0:{}s:9:"feed_type";s:3:"RSS";s:12:"feed_version";s:3:"2.0";s:5:"stack";a:0:{}s:9:"inchannel";b:0;s:6:"initem";b:0;s:9:"incontent";b:0;s:11:"intextinput";b:0;s:7:"inimage";b:0;s:13:"current_field";s:0:"";s:17:"current_namespace";b:0;s:19:"_CONTENT_CONSTRUCTS";a:6:{i:0;s:7:"content";i:1;s:7:"summary";i:2;s:4:"info";i:3;s:5:"title";i:4;s:7:"tagline";i:5;s:9:"copyright";}s:13:"last_modified";s:31:"Tue, 05 Feb 2008 16:14:37 GMT\r\n";s:4:"etag";s:36:""6ff372acf476df272c01ba460dfbcec0"\r\n";}', 'no') ; INSERT INTO `wp_options` VALUES (94, 0, 'rss_0ff4b43bd116a9d8720d689c80e7dfd4_ts', '1202658547', 'no') ; INSERT INTO `wp_options` VALUES (95, 0, 'rss_867bd5c64f85878d03a060509cd2f92c', 'O:9:"MagpieRSS":19:{s:6:"parser";i:0;s:12:"current_item";a:0:{}s:5:"items";a:50:{i:0;a:7:{s:5:"title";s:25:"Matt: Nice smbfs tutorial";s:4:"guid";s:41:"http://ma.tt/2008/02/nice-smbfs-tutorial/";s:4:"link";s:41:"http://ma.tt/2008/02/nice-smbfs-tutorial/";s:11:"description";s:125:"

    Mounting remote filesystems with smbfs, good tutorial.

    ";s:7:"pubdate";s:31:"Sat, 09 Feb 2008 20:31:04 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:7:"summary";s:125:"

    Mounting remote filesystems with smbfs, good tutorial.

    ";}i:1;a:7:{s:5:"title";s:75:"Weblog Tools Collection: Adding Your Plugin to WP Extend Plugins With a Mac";s:4:"guid";s:104:"http://weblogtoolscollection.com/archives/2008/02/09/adding-your-plugin-to-wp-extend-plugins-with-a-mac/";s:4:"link";s:104:"http://weblogtoolscollection.com/archives/2008/02/09/adding-your-plugin-to-wp-extend-plugins-with-a-mac/";s:11:"description";s:9032:"

    A while back I wrote about listing your plugin to the official WordPress plugins directory. The tutorial was for windows and I have been on the look-out for a Mac version. Since I have been unable to find one, I will present to you a step-by-step tutorial on how to add and modify your WordPress Plugin using a Mac.

    \n

    To begin this tutorial, I first have to make some assumptions.

    \n

    My Assumptions

    \n
      \n
    1. Your plugin has already been approved over at WP Extend Plugins.
      2. \n
    2. You are running at least OSX Tiger
      3. \n
    3. You have WordPress locally installed. If not, please read Jeff’s tutorial on installing WordPress locally.
      4. \n
    4. You already have Subversion installed. If not, here’s a good tutorial on installing Subversion on a Mac. If you have Leopard, Subversion is already installed.
      5. \n
    5. You have downloaded and installed svnX. svnX has a nice GUI for those who don’t like to use Terminal commands.
      6. \n
    \n

    Step 1. Ensure the Subversion (svn) Path is Correct

    \n

    After you’ve installed svnX, go to its Preferences screen and ensure the path to your svn install is correct. Mine is set up at ‘/usr/local/bin‘, but yours may be different.

    \n

    Subversion Path
    \nSubversion Path Interface

    \n

    Step 2. Access Your Subversion Repository

    \n

    Using svnX, open up the “Repositories” window and add the path to your plugin using the “+” button.

    \n

    From there, enter your plugin information:

    \n\n

    Add Repository Using svnX
    \nAccessing Your Repository

    \n

    After you’ve entered your information, double-click your repository to open it up. You should now see a screen (assuming your credentials are correct) similar to the screenshot below:

    \n

    Repository View svnX
    \nRepository View

    \n

    If you have never added your plugin before, the directories will be empty.

    \n

    Step 3. Check Out Your Repository

    \n

    Select the “trunk” directory and right-click it. You’ll want to select “Browse as sub-repository“.

    \n

    Sub-repository View svnX

    \n

    After selecting to view as a sub-repository, you should see a view of only your trunk’s contents. If you have never added your plugin before, this directory will be empty.

    \n

    Sub-repository View svnX
    \nSub-Repository View in svnX

    \n

    Once in the sub-repository view, you can now check out your repository. Click the “svn checkout” button to check out your repository.

    \n

    svnX Checkout Button

    \n

    From there, browse to your local WordPress installation’s plugins folder, and add a new folder and give it the name of your plugin. Please note that this should be the same folder name you would normally give your plugin prior to a release.

    \n

    Checking out into a new folder - svnX
    \nAdd a new folder to your plugin’s directory.

    \n

    After adding the new folder, click the “Open” button. The “Working Copies” window for svnX should now be showing.

    \n

    Working Copy Window - svnX
    \nWorking Copies Window after a Checkout

    \n

    Make sure you update your User and Pass to reflect those on WP Extend.

    \n

    Step 4. Add or Modify Files

    \n

    In the case of my plugin, I am just editing a few files. In your case, you may be adding plugin files for the first time.

    \n

    Double-click your plugin in the “Working Copies” window. You should now see a screen similar to the one shown in the screenshot below:

    \n

    Working Copy View - svnX
    \nWorking Copies Window

    \n

    The best way to edit or add your plugin is through Finder. Click the “Reveal in Finder” button.

    \n

    Reveal in Finder button - svnX

    \n

    From there, add or modify your plugin files.

    \n

    Step 5. Commit the Changes

    \n

    After adding and/or modifying files, hit the “Refresh” button after you have opened up your Working Copy.

    \n

    If the file is new, you will need to add the file to the repository by clicking the “Add” button. If an existing file is modified, it will show a “M” next to it.

    \n

    To commit the changes, select the files you want to commit and select the “Commit” button. Type in a detailed message and click “Commit” again.

    \n

    Please see the screenshot below for the commit screen:

    \n

    Commit Dialog - svnX
    \nWorking Copy Commit Dialog

    \n

    Step 6. Tag Your Release

    \n

    Assuming you have prepared your plugin’s readme file (see this tutorial, Step 7), head over to your plugin’s repository (Open the Repositories Window in svnX and open your plugin - See Step 2 above).

    \n

    You should see the changes you have just committed. If not, try clicking the “Refresh” button (a very small circular arrow).

    \n

    To “tag” your release, select your “trunk” directory and click “svn copy” in the repository window.

    \n

    svn copy button - svnxX

    \n

    To successfully tag your release, follow these steps:

    \n
      \n
    1. Select the “tags” directory.
      2. \n
    2. Add an appropriate version number for the “Target Name”. This should match the stable version in your plugin’s readme file.
      3. \n
    3. Add in a commit message. You can just state that you are tagging a release.
      4. \n
    \n

    Tagging Dialog - svnX
    \nTagging Your Release

    \n

    Step 7. Verify Everything Worked

    \n

    Head over to WP Extend Plugins and browse to your plugin (wait about fifteen minutes after you’ve tagged your plugin).

    \n

    Make sure the versions match and that the changes you made were indeed captured. If everything is good, then you’re done.

    \n

    Conclusion

    \n

    Within this article, I demonstrated how to modify or add your plugin to the WordPress plugin repository using a Mac and svnX.

    \n

    If you have any questions or suggestions on how to make this tutorial better, please leave a comment below.

    ";s:7:"pubdate";s:31:"Sat, 09 Feb 2008 12:00:25 +0000";s:2:"dc";a:1:{s:7:"creator";s:14:"Ronald Huereca";}s:7:"summary";s:9032:"

    A while back I wrote about listing your plugin to the official WordPress plugins directory. The tutorial was for windows and I have been on the look-out for a Mac version. Since I have been unable to find one, I will present to you a step-by-step tutorial on how to add and modify your WordPress Plugin using a Mac.

    \n

    To begin this tutorial, I first have to make some assumptions.

    \n

    My Assumptions

    \n
      \n
    1. Your plugin has already been approved over at WP Extend Plugins.
      2. \n
    2. You are running at least OSX Tiger
      3. \n
    3. You have WordPress locally installed. If not, please read Jeff’s tutorial on installing WordPress locally.
      4. \n
    4. You already have Subversion installed. If not, here’s a good tutorial on installing Subversion on a Mac. If you have Leopard, Subversion is already installed.
      5. \n
    5. You have downloaded and installed svnX. svnX has a nice GUI for those who don’t like to use Terminal commands.
      6. \n
    \n

    Step 1. Ensure the Subversion (svn) Path is Correct

    \n

    After you’ve installed svnX, go to its Preferences screen and ensure the path to your svn install is correct. Mine is set up at ‘/usr/local/bin‘, but yours may be different.

    \n

    Subversion Path
    \nSubversion Path Interface

    \n

    Step 2. Access Your Subversion Repository

    \n

    Using svnX, open up the “Repositories” window and add the path to your plugin using the “+” button.

    \n

    From there, enter your plugin information:

    \n\n

    Add Repository Using svnX
    \nAccessing Your Repository

    \n

    After you’ve entered your information, double-click your repository to open it up. You should now see a screen (assuming your credentials are correct) similar to the screenshot below:

    \n

    Repository View svnX
    \nRepository View

    \n

    If you have never added your plugin before, the directories will be empty.

    \n

    Step 3. Check Out Your Repository

    \n

    Select the “trunk” directory and right-click it. You’ll want to select “Browse as sub-repository“.

    \n

    Sub-repository View svnX

    \n

    After selecting to view as a sub-repository, you should see a view of only your trunk’s contents. If you have never added your plugin before, this directory will be empty.

    \n

    Sub-repository View svnX
    \nSub-Repository View in svnX

    \n

    Once in the sub-repository view, you can now check out your repository. Click the “svn checkout” button to check out your repository.

    \n

    svnX Checkout Button

    \n

    From there, browse to your local WordPress installation’s plugins folder, and add a new folder and give it the name of your plugin. Please note that this should be the same folder name you would normally give your plugin prior to a release.

    \n

    Checking out into a new folder - svnX
    \nAdd a new folder to your plugin’s directory.

    \n

    After adding the new folder, click the “Open” button. The “Working Copies” window for svnX should now be showing.

    \n

    Working Copy Window - svnX
    \nWorking Copies Window after a Checkout

    \n

    Make sure you update your User and Pass to reflect those on WP Extend.

    \n

    Step 4. Add or Modify Files

    \n

    In the case of my plugin, I am just editing a few files. In your case, you may be adding plugin files for the first time.

    \n

    Double-click your plugin in the “Working Copies” window. You should now see a screen similar to the one shown in the screenshot below:

    \n

    Working Copy View - svnX
    \nWorking Copies Window

    \n

    The best way to edit or add your plugin is through Finder. Click the “Reveal in Finder” button.

    \n

    Reveal in Finder button - svnX

    \n

    From there, add or modify your plugin files.

    \n

    Step 5. Commit the Changes

    \n

    After adding and/or modifying files, hit the “Refresh” button after you have opened up your Working Copy.

    \n

    If the file is new, you will need to add the file to the repository by clicking the “Add” button. If an existing file is modified, it will show a “M” next to it.

    \n

    To commit the changes, select the files you want to commit and select the “Commit” button. Type in a detailed message and click “Commit” again.

    \n

    Please see the screenshot below for the commit screen:

    \n

    Commit Dialog - svnX
    \nWorking Copy Commit Dialog

    \n

    Step 6. Tag Your Release

    \n

    Assuming you have prepared your plugin’s readme file (see this tutorial, Step 7), head over to your plugin’s repository (Open the Repositories Window in svnX and open your plugin - See Step 2 above).

    \n

    You should see the changes you have just committed. If not, try clicking the “Refresh” button (a very small circular arrow).

    \n

    To “tag” your release, select your “trunk” directory and click “svn copy” in the repository window.

    \n

    svn copy button - svnxX

    \n

    To successfully tag your release, follow these steps:

    \n
      \n
    1. Select the “tags” directory.
      2. \n
    2. Add an appropriate version number for the “Target Name”. This should match the stable version in your plugin’s readme file.
      3. \n
    3. Add in a commit message. You can just state that you are tagging a release.
      4. \n
    \n

    Tagging Dialog - svnX
    \nTagging Your Release

    \n

    Step 7. Verify Everything Worked

    \n

    Head over to WP Extend Plugins and browse to your plugin (wait about fifteen minutes after you’ve tagged your plugin).

    \n

    Make sure the versions match and that the changes you made were indeed captured. If everything is good, then you’re done.

    \n

    Conclusion

    \n

    Within this article, I demonstrated how to modify or add your plugin to the WordPress plugin repository using a Mac and svnX.

    \n

    If you have any questions or suggestions on how to make this tutorial better, please leave a comment below.

    ";}i:2;a:7:{s:5:"title";s:23:"Matt: Upcoming Speaking";s:4:"guid";s:20:"http://ma.tt/?p=3190";s:4:"link";s:39:"http://ma.tt/2008/02/upcoming-speaking/";s:11:"description";s:410:"

    Coming soon to a town near you. I’ll be doing a keynote at Northern Voice in Vancouver, speaking at Future of Web Apps in Miami, and on a panel at SxSW Interactive in Austin, and kicking off WordCamp in Dallas.

    ";s:7:"pubdate";s:31:"Sat, 09 Feb 2008 04:07:54 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:7:"summary";s:410:"

    Coming soon to a town near you. I’ll be doing a keynote at Northern Voice in Vancouver, speaking at Future of Web Apps in Miami, and on a panel at SxSW Interactive in Austin, and kicking off WordCamp in Dallas.

    ";}i:3;a:7:{s:5:"title";s:37:"Ryan Boren: Steaming Mug of WordPress";s:4:"guid";s:23:"http://boren.nu/?p=1536";s:4:"link";s:62:"http://boren.nu/archives/2008/02/08/steaming-mug-of-wordpress/";s:11:"description";s:454:"

    WordPress mugs are now for sale. Here’s a shot of mine.  They’re cobalt blue and over-sized.

    \n

    WP Mug

    ";s:7:"pubdate";s:31:"Sat, 09 Feb 2008 01:52:07 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Ryan";}s:7:"summary";s:454:"

    WordPress mugs are now for sale. Here’s a shot of mine.  They’re cobalt blue and over-sized.

    \n

    WP Mug

    ";}i:4;a:7:{s:5:"title";s:41:"Peter Westwood: WordPress 2.3.3 in detail";s:4:"guid";s:32:"http://westi.wordpress.com/?p=29";s:4:"link";s:62:"http://westi.wordpress.com/2008/02/08/wordpress-233-in-detail/";s:11:"description";s:357:"WordPress 2.3.3 has been released and includes a number of changes including one security fix, here is a list of most of the changes in detail:\n\nReversion of the change to sent the “Sender” in wp_mail() (#5273).\nChanges to the magic number detection for gettext file loading for better support of 64bit systems (#3780).\nA fix in install-helper.php [...]";s:7:"pubdate";s:31:"Fri, 08 Feb 2008 22:10:56 +0000";s:2:"dc";a:1:{s:7:"creator";s:14:"Peter Westwood";}s:7:"summary";s:357:"WordPress 2.3.3 has been released and includes a number of changes including one security fix, here is a list of most of the changes in detail:\n\nReversion of the change to sent the “Sender” in wp_mail() (#5273).\nChanges to the magic number detection for gettext file loading for better support of 64bit systems (#3780).\nA fix in install-helper.php [...]";}i:5;a:7:{s:5:"title";s:53:"Weblog Tools Collection: New Translation Of WordPress";s:4:"guid";s:82:"http://weblogtoolscollection.com/archives/2008/02/08/new-translation-of-wordpress/";s:4:"link";s:82:"http://weblogtoolscollection.com/archives/2008/02/08/new-translation-of-wordpress/";s:11:"description";s:1149:"

    Kazakhstan

    \n

    There is some great news today for those that live in or around Kazakhstan and use WordPress. WordPress.org software, which has already been translated into a number of different languages, can lay claim to having a Kazakh translated version. Kazakh is the native language of Kazakhstan. According to a press release, the number of Kazakh bloggers has grown considerably, mostly due in part to a Google Group that was created which explained how the software works.

    \n

    Up to this point, WordPress has been translated into 57 different languages (not counting the OTHERS category). This would make number 58. To see all of the various translations that have occurred thus far, check out the Codex Article labeled, WordPress In Your Language

    ";s:7:"pubdate";s:31:"Fri, 08 Feb 2008 13:45:05 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jeffro2pt0";}s:7:"summary";s:1149:"

    Kazakhstan

    \n

    There is some great news today for those that live in or around Kazakhstan and use WordPress. WordPress.org software, which has already been translated into a number of different languages, can lay claim to having a Kazakh translated version. Kazakh is the native language of Kazakhstan. According to a press release, the number of Kazakh bloggers has grown considerably, mostly due in part to a Google Group that was created which explained how the software works.

    \n

    Up to this point, WordPress has been translated into 57 different languages (not counting the OTHERS category). This would make number 58. To see all of the various translations that have occurred thus far, check out the Codex Article labeled, WordPress In Your Language

    ";}i:6;a:7:{s:5:"title";s:50:"WordPress Podcast: WordCamp Dallas - March 29 & 30";s:4:"guid";s:63:"http://wp-community.org/2008/02/07/wordcamp-dallas-march-29-30/";s:4:"link";s:63:"http://wp-community.org/2008/02/07/wordcamp-dallas-march-29-30/";s:11:"description";s:930:"

    Saturday, March 29th and Sunday, March 30th a lot of WordPress users and coders will be gathering at the George A. Purefoy Municipal Center at 6101 Frisco Square Boulevard in Frisco, Texas, North of Dallas along the Dallas North Tollway to participate in that area’s first WordCamp.

    \n

    We have a great lineup of speakers, with several being from the DFW area. For only $20 attendees can come both days, get fed lunch, have a great time, learn from some of the best minds in new media and walk away with a WordCamp t-shirt.

    \n

    For more information and registration, visit the official blog at dallas.wordcamp.org.

    ";s:7:"pubdate";s:31:"Fri, 08 Feb 2008 00:30:03 +0000";s:2:"dc";a:1:{s:7:"creator";s:17:"Charles Stricklin";}s:7:"summary";s:930:"

    Saturday, March 29th and Sunday, March 30th a lot of WordPress users and coders will be gathering at the George A. Purefoy Municipal Center at 6101 Frisco Square Boulevard in Frisco, Texas, North of Dallas along the Dallas North Tollway to participate in that area’s first WordCamp.

    \n

    We have a great lineup of speakers, with several being from the DFW area. For only $20 attendees can come both days, get fed lunch, have a great time, learn from some of the best minds in new media and walk away with a WordCamp t-shirt.

    \n

    For more information and registration, visit the official blog at dallas.wordcamp.org.

    ";}i:7;a:7:{s:5:"title";s:60:"Weblog Tools Collection: Extending WordPress Beyond the Blog";s:4:"guid";s:89:"http://weblogtoolscollection.com/archives/2008/02/07/extending-wordpress-beyond-the-blog/";s:4:"link";s:89:"http://weblogtoolscollection.com/archives/2008/02/07/extending-wordpress-beyond-the-blog/";s:11:"description";s:1287:"

    Extending WordPress Beyond the Blog: A good article on extending WordPress beyond “just a blog” with examples and a developer’s trials and tribulations along the way. Custom Fields in WordPress are the bomb. I have worked extensively with this feature set and used it to my advantage many times. WordPress Jobs makes use of the custom fields to store and produce the job listings. Our recent post on WordPress as a contact manager also uses Custom Fields. Heck there was a Contest at one point that awarded prizes to the best new use of WordPress’ Custom Fields. Along those lines, Andrew asks a question at the end of the linked article that caught my fancy and I wanted to ask our readers the same question. We might find some new uses for old code and spark new ideas.

    \n

    Which are your favorite non-traditional sites that use WordPress as their publishing platform?

    ";s:7:"pubdate";s:31:"Thu, 07 Feb 2008 23:30:08 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Mark Ghosh";}s:7:"summary";s:1287:"

    Extending WordPress Beyond the Blog: A good article on extending WordPress beyond “just a blog” with examples and a developer’s trials and tribulations along the way. Custom Fields in WordPress are the bomb. I have worked extensively with this feature set and used it to my advantage many times. WordPress Jobs makes use of the custom fields to store and produce the job listings. Our recent post on WordPress as a contact manager also uses Custom Fields. Heck there was a Contest at one point that awarded prizes to the best new use of WordPress’ Custom Fields. Along those lines, Andrew asks a question at the end of the linked article that caught my fancy and I wanted to ask our readers the same question. We might find some new uses for old code and spark new ideas.

    \n

    Which are your favorite non-traditional sites that use WordPress as their publishing platform?

    ";}i:8;a:7:{s:5:"title";s:24:"Matt: Wither Dreamweaver";s:4:"guid";s:20:"http://ma.tt/?p=3189";s:4:"link";s:40:"http://ma.tt/2008/02/wither-dreamweaver/";s:11:"description";s:1071:"

    I’ve done my coding in Dreamweaver for 5+ years now. I think I’m the only one who does so at Automattic, but it’s a good fit for me with the network/SFTP integration, decent PHP highlight, regex search/replace, and good project support. It was a natural transition for me from Homesite. I know there are a thousand other editors that I could use, and I know I shouldn’t be on Windows most of the time, but that’s not what this post is about. I’m utterly appalled by how bad Dreamweaver CS3 is. I paid hundreds of dollars to upgrade to something that consistently crashes when I edit certain parts of PHP files and CTRL + F no longer opens a search box unless I have a document open.

    \n

    Dear Dreamweaver team, I’ve been putting up with these bugs for close to a year now. I will come down to San Jose and show you the bugs personally. Just please do something, or feign the appearance of movement. For now, I’m switching from CS3 to version 8, which is just sad.

    ";s:7:"pubdate";s:31:"Thu, 07 Feb 2008 18:47:11 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:7:"summary";s:1071:"

    I’ve done my coding in Dreamweaver for 5+ years now. I think I’m the only one who does so at Automattic, but it’s a good fit for me with the network/SFTP integration, decent PHP highlight, regex search/replace, and good project support. It was a natural transition for me from Homesite. I know there are a thousand other editors that I could use, and I know I shouldn’t be on Windows most of the time, but that’s not what this post is about. I’m utterly appalled by how bad Dreamweaver CS3 is. I paid hundreds of dollars to upgrade to something that consistently crashes when I edit certain parts of PHP files and CTRL + F no longer opens a search box unless I have a document open.

    \n

    Dear Dreamweaver team, I’ve been putting up with these bugs for close to a year now. I will come down to San Jose and show you the bugs personally. Just please do something, or feign the appearance of movement. For now, I’m switching from CS3 to version 8, which is just sad.

    ";}i:9;a:7:{s:5:"title";s:17:"Matt: SVASE Panel";s:4:"guid";s:33:"http://ma.tt/2008/02/svase-panel/";s:4:"link";s:33:"http://ma.tt/2008/02/svase-panel/";s:11:"description";s:508:"

    Tonight I’ll be on a SVASE panel with Mike Cassidy, Naval Ravikant, and Peter Yared down in Palo Alto speaking on “How To Build A High Growth Startup Fast And Cheap.” Get all the details here. Zoli Erdos has some more information.

    ";s:7:"pubdate";s:31:"Thu, 07 Feb 2008 17:05:24 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:7:"summary";s:508:"

    Tonight I’ll be on a SVASE panel with Mike Cassidy, Naval Ravikant, and Peter Yared down in Palo Alto speaking on “How To Build A High Growth Startup Fast And Cheap.” Get all the details here. Zoli Erdos has some more information.

    ";}i:10;a:7:{s:5:"title";s:52:"Weblog Tools Collection: 2 Plugin Security Bulletins";s:4:"guid";s:81:"http://weblogtoolscollection.com/archives/2008/02/07/2-plugin-security-bulletins/";s:4:"link";s:81:"http://weblogtoolscollection.com/archives/2008/02/07/2-plugin-security-bulletins/";s:11:"description";s:1888:"

    NBBN has discovered some cross site scripting vulnerabilities for the WP-Footnotes plugin version 2.2 for WordPress.

    \n

    Input passed to the “pre_footnotes”, “priority”, “post_footnotes”, and “style_rules” array elements in the “wp_footnotes_current_settings[]” array in the admin_panel.php script is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user’s browser session in context of an affected site.

    \n

    The good news this time around is that, ‘register_globals‘ must be turned on for exploitation to occur. If you are using this plugin on your site, it is advised that you disable the plugin until a security patch has been released. According to the security bulletin, the solution is to edit the plugin source code to ensure that input is properly sanitized.

    \n

    Again, if you know that your webserver has register_globals turned off, you are in the clear.

    \n

    S@BUN has reported an “id” based SQL injection vulnerability within the WordsPew plugin version 3.x for WordPress.

    \n

    Input passed to the parameter “id” in wordspew-rss.php is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.

    \n

    The solution again is to edit the source code of the plugin to make sure that input is sanitized.

    ";s:7:"pubdate";s:31:"Thu, 07 Feb 2008 13:00:08 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jeffro2pt0";}s:7:"summary";s:1888:"

    NBBN has discovered some cross site scripting vulnerabilities for the WP-Footnotes plugin version 2.2 for WordPress.

    \n

    Input passed to the “pre_footnotes”, “priority”, “post_footnotes”, and “style_rules” array elements in the “wp_footnotes_current_settings[]” array in the admin_panel.php script is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user’s browser session in context of an affected site.

    \n

    The good news this time around is that, ‘register_globals‘ must be turned on for exploitation to occur. If you are using this plugin on your site, it is advised that you disable the plugin until a security patch has been released. According to the security bulletin, the solution is to edit the plugin source code to ensure that input is properly sanitized.

    \n

    Again, if you know that your webserver has register_globals turned off, you are in the clear.

    \n

    S@BUN has reported an “id” based SQL injection vulnerability within the WordsPew plugin version 3.x for WordPress.

    \n

    Input passed to the parameter “id” in wordspew-rss.php is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.

    \n

    The solution again is to edit the source code of the plugin to make sure that input is sanitized.

    ";}i:11;a:7:{s:5:"title";s:59:"Donncha: How China Digital Times moved from MT to WordPress";s:4:"guid";s:29:"http://ocaoimh.ie/?p=89493573";s:4:"link";s:78:"http://ocaoimh.ie/2008/02/07/how-china-daily-times-moved-from-mt-to-wordpress/";s:11:"description";s:1493:"

    Can you improve performance when moving from a statically generated site to a dynamic environment? You can if the conditions are right. In the case of CDT, publishing times were a nightmare with Movable Type. Search performance was horrible, and the comment spam problem caused such a drag on the server that we’d had to disable commenting altogether. Now, with the site fully tag-enabled, searchable and comment-able, loads are down dramatically and publishing times have dropped from 15 minutes to a few seconds.

    \n

    Notes on a massive WordPress migration. Scot moved the China Digital Times site with 16,000 posts and 6,000 tags from Movable Type to WordPress and saw a huge performance increase. Nice.

    \n

    Related Posts

    ";s:7:"pubdate";s:31:"Thu, 07 Feb 2008 10:15:03 +0000";s:2:"dc";a:1:{s:7:"creator";s:7:"Donncha";}s:7:"summary";s:1493:"

    Can you improve performance when moving from a statically generated site to a dynamic environment? You can if the conditions are right. In the case of CDT, publishing times were a nightmare with Movable Type. Search performance was horrible, and the comment spam problem caused such a drag on the server that we’d had to disable commenting altogether. Now, with the site fully tag-enabled, searchable and comment-able, loads are down dramatically and publishing times have dropped from 15 minutes to a few seconds.

    \n

    Notes on a massive WordPress migration. Scot moved the China Digital Times site with 16,000 posts and 6,000 tags from Movable Type to WordPress and saw a huge performance increase. Nice.

    \n

    Related Posts

    ";}i:12;a:7:{s:5:"title";s:73:"Peter Westwood: WordPress weekly digest 28th January to 3rd February 2008";s:4:"guid";s:32:"http://westi.wordpress.com/?p=28";s:4:"link";s:96:"http://westi.wordpress.com/2008/02/07/wordpress-weekly-digest-28th-january-to-3rd-february-2008/";s:11:"description";s:352:"It has been a busy week again for WordPress 2.5, the changes this week were:\n\nA Tag Searching interface for the Tag Editor (#5684).\nRemoval of any old compatibility functions for PHP 4.2 and 4.3 (#5415).\nI18N updates for the new widgets interface (#5583).\nChanges to increase the memory limit for PHP (#3141).\nComment feed fixes to ensure that we [...]";s:7:"pubdate";s:31:"Thu, 07 Feb 2008 08:29:47 +0000";s:2:"dc";a:1:{s:7:"creator";s:14:"Peter Westwood";}s:7:"summary";s:352:"It has been a busy week again for WordPress 2.5, the changes this week were:\n\nA Tag Searching interface for the Tag Editor (#5684).\nRemoval of any old compatibility functions for PHP 4.2 and 4.3 (#5415).\nI18N updates for the new widgets interface (#5583).\nChanges to increase the memory limit for PHP (#3141).\nComment feed fixes to ensure that we [...]";}i:13;a:7:{s:5:"title";s:30:"Matt: Rocky Mountain Interview";s:4:"guid";s:46:"http://ma.tt/2008/02/rocky-mountain-interview/";s:4:"link";s:46:"http://ma.tt/2008/02/rocky-mountain-interview/";s:11:"description";s:204:"

    I did a video interview with Brad Baldwin of Rocky Mountain Voices while in Utah.

    ";s:7:"pubdate";s:31:"Thu, 07 Feb 2008 03:37:23 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:7:"summary";s:204:"

    I did a video interview with Brad Baldwin of Rocky Mountain Voices while in Utah.

    ";}i:14;a:7:{s:5:"title";s:55:"Weblog Tools Collection: WordPress as a Contact Manager";s:4:"guid";s:84:"http://weblogtoolscollection.com/archives/2008/02/06/wordpress-as-a-contact-manager/";s:4:"link";s:84:"http://weblogtoolscollection.com/archives/2008/02/06/wordpress-as-a-contact-manager/";s:11:"description";s:870:"

    WP Contact Manager: The versatility of WordPress continues to amaze me. Design Canopy has released a theme/set of instructions for WordPress that would allow you to run a WordPress install as a taggable, searchable contact manager that can be made into a Members Only system and display related contacts. Now mind you, it is not a stand alone theme, needs extra plugins to be downloaded and installed and they outline detailed instructions on how to set it up. However, the setup looks relatively easy and the results are definitely pretty cool. I would have liked to see a Prologue like custom posting interface for logged in users but that could be an easy add on or plugin once the thing is set up.

    ";s:7:"pubdate";s:31:"Wed, 06 Feb 2008 16:45:06 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Mark Ghosh";}s:7:"summary";s:870:"

    WP Contact Manager: The versatility of WordPress continues to amaze me. Design Canopy has released a theme/set of instructions for WordPress that would allow you to run a WordPress install as a taggable, searchable contact manager that can be made into a Members Only system and display related contacts. Now mind you, it is not a stand alone theme, needs extra plugins to be downloaded and installed and they outline detailed instructions on how to set it up. However, the setup looks relatively easy and the results are definitely pretty cool. I would have liked to see a Prologue like custom posting interface for logged in users but that could be an easy add on or plugin once the thing is set up.

    ";}i:15;a:7:{s:5:"title";s:27:"Donncha: WordPress MU 1.3.3";s:4:"guid";s:29:"http://ocaoimh.ie/?p=89493572";s:4:"link";s:46:"http://ocaoimh.ie/2008/02/05/wordpress-mu-133/";s:11:"description";s:1099:"

    I just released WordPress MU 1.3.3 and it’s now available for download. This is a critical security release based on WordPress 2.3.3 and everyone is encouraged to upgrade.

    \n

    Here is the forum announcement. I also listed the 3 security fixes that were the reason for 1.3.2. If you haven’t upgraded yet, please do.

    \n

    Related Posts

    ";s:7:"pubdate";s:31:"Tue, 05 Feb 2008 17:30:06 +0000";s:2:"dc";a:1:{s:7:"creator";s:7:"Donncha";}s:7:"summary";s:1099:"

    I just released WordPress MU 1.3.3 and it’s now available for download. This is a critical security release based on WordPress 2.3.3 and everyone is encouraged to upgrade.

    \n

    Here is the forum announcement. I also listed the 3 security fixes that were the reason for 1.3.2. If you haven’t upgraded yet, please do.

    \n

    Related Posts

    ";}i:16;a:7:{s:5:"title";s:20:"Matt: Conrad Johnson";s:4:"guid";s:20:"http://ma.tt/?p=3186";s:4:"link";s:36:"http://ma.tt/2008/02/conrad-johnson/";s:11:"description";s:273:"

    Conrad Johnson, one of the centers of gravity in the Houston jazz scene, passed away on Sunday. I had only a few lessons with Prof and he kicked my butt, he must have been 80-something at the time.

    ";s:7:"pubdate";s:31:"Tue, 05 Feb 2008 17:17:49 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:7:"summary";s:273:"

    Conrad Johnson, one of the centers of gravity in the Houston jazz scene, passed away on Sunday. I had only a few lessons with Prof and he kicked my butt, he must have been 80-something at the time.

    ";}i:17;a:7:{s:5:"title";s:25:"Dev Blog: WordPress 2.3.3";s:4:"guid";s:39:"http://wordpress.org/development/?p=225";s:4:"link";s:55:"http://wordpress.org/development/2008/02/wordpress-233/";s:11:"description";s:1207:"

    WordPress 2.3.3 is an urgent security release. If you have registration enabled a flaw was found in the XML-RPC implementation such that a specially crafted request would allow a user to edit posts of other users on that blog. In addition to fixing this security flaw, 2.3.3 fixes a few minor bugs. If you are interested only in the security fix, download the fixed version of xmlrpc.php and copy it over your existing xmlrpc.php. Otherwise, you can get the entire release here.

    \n

    Also, there is a vulnerability in the WP-Forum plugin that is being actively exploited right now. If you are using this plugin, please remove it until an update is available from its author.

    \n

    Since we are talking security, remember to use strong passwords and change them regularly.  While you’re updating WP and your plugins, consider refreshing your passwords.

    ";s:7:"pubdate";s:31:"Tue, 05 Feb 2008 05:02:45 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Ryan";}s:7:"summary";s:1207:"

    WordPress 2.3.3 is an urgent security release. If you have registration enabled a flaw was found in the XML-RPC implementation such that a specially crafted request would allow a user to edit posts of other users on that blog. In addition to fixing this security flaw, 2.3.3 fixes a few minor bugs. If you are interested only in the security fix, download the fixed version of xmlrpc.php and copy it over your existing xmlrpc.php. Otherwise, you can get the entire release here.

    \n

    Also, there is a vulnerability in the WP-Forum plugin that is being actively exploited right now. If you are using this plugin, please remove it until an update is available from its author.

    \n

    Since we are talking security, remember to use strong passwords and change them regularly.  While you’re updating WP and your plugins, consider refreshing your passwords.

    ";}i:18;a:7:{s:5:"title";s:51:"Weblog Tools Collection: Utterz: Post from anywhere";s:4:"guid";s:79:"http://weblogtoolscollection.com/archives/2008/02/04/utterz-post-from-anywhere/";s:4:"link";s:79:"http://weblogtoolscollection.com/archives/2008/02/04/utterz-post-from-anywhere/";s:11:"description";s:1294:"

    Utterz: is a Web-based service that posts to all of the above, from anywhere, even by phone, whether it’s text, photos, video, voice, or a mash-up of all the above. Same with PCs. You can just e-mail or SMS the posts to Utterz, or make a phone call to leave a voice record. After the content is received, it’s forwarded to the blog or blogs you specify in about 10 minutes. This online tools brings us one step closer to having a personal Twitter. If you setup your own WordPress blog (hosted or on WordPress.com) and use the Prologue theme (new zipped release by popular request, thanks Joseph Scott), you can have many of the flexible posting features of Twitter on your own platform. Since Utterz is a remotely hosted service, I am not sure the benefit of a “personal” Twitter are realized quite as well, but it is definitely a start and provides much broader flexibility and control than Twitter. I am quite hooked on Prologue and have started to use it on wltc.net. I have left registration open for authors on wltc.net for those that are interested (probably a bad idea, time will tell).

    ";s:7:"pubdate";s:31:"Mon, 04 Feb 2008 23:45:09 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Mark Ghosh";}s:7:"summary";s:1294:"

    Utterz: is a Web-based service that posts to all of the above, from anywhere, even by phone, whether it’s text, photos, video, voice, or a mash-up of all the above. Same with PCs. You can just e-mail or SMS the posts to Utterz, or make a phone call to leave a voice record. After the content is received, it’s forwarded to the blog or blogs you specify in about 10 minutes. This online tools brings us one step closer to having a personal Twitter. If you setup your own WordPress blog (hosted or on WordPress.com) and use the Prologue theme (new zipped release by popular request, thanks Joseph Scott), you can have many of the flexible posting features of Twitter on your own platform. Since Utterz is a remotely hosted service, I am not sure the benefit of a “personal” Twitter are realized quite as well, but it is definitely a start and provides much broader flexibility and control than Twitter. I am quite hooked on Prologue and have started to use it on wltc.net. I have left registration open for authors on wltc.net for those that are interested (probably a bad idea, time will tell).

    ";}i:19;a:7:{s:5:"title";s:26:"Gravatar: Gravatars in ASP";s:4:"guid";s:35:"http://gravatar.wordpress.com/?p=45";s:4:"link";s:53:"http://blog.gravatar.com/2008/02/04/gravatars-in-asp/";s:11:"description";s:1795:"

    Michal, over at WebDevPros has put together the necessary information (and an md5 include) for using gravatars in your classic ASP applications. Check out the article here: http://www.webdevbros.net/2007/12/29/using-gravatar-in-classic-asp/. As always we’re thrilled to see more and more ways to make gravatar universally implementable. Great job, Michal!

    \n
    ";s:7:"pubdate";s:31:"Mon, 04 Feb 2008 18:58:40 +0000";s:2:"dc";a:1:{s:7:"creator";s:11:"apokalyptik";}s:7:"summary";s:1795:"

    Michal, over at WebDevPros has put together the necessary information (and an md5 include) for using gravatars in your classic ASP applications. Check out the article here: http://www.webdevbros.net/2007/12/29/using-gravatar-in-classic-asp/. As always we’re thrilled to see more and more ways to make gravatar universally implementable. Great job, Michal!

    \n
    ";}i:20;a:7:{s:5:"title";s:42:"Lorelle on WP: Content Theft and WordPress";s:4:"guid";s:36:"http://lorelle.wordpress.com/?p=2334";s:4:"link";s:68:"http://lorelle.wordpress.com/2008/02/04/content-theft-and-wordpress/";s:11:"description";s:3076:"

    WordPress.com NewsI and many WordPress “representatives”, along with the developers and staff of and , are getting more and more complaints and requests for help dealing with content theft issues. We all need to clear this up and spread the word about how this works in relationship to WordPress.

    \n

    In order to go after a copyright violation of your content, you have to contact the site owner first. When that fails, you ask the web host for assistance, in accordance with the DMCA, to contact the site owner and deal with the copyright violation. Herein lies the problem.

    \n

    As Mark Jaquith recently stated, there is a lot of name confusion between a blog and a blog. Since a web host in the United States is required to assist with copyright infringement issues when contacted, when is WordPress the host and when is it not? After all, it’s all WordPress, right?

    \n

    Not.
    \n (more…)

    \n
    ";s:7:"pubdate";s:31:"Mon, 04 Feb 2008 11:28:55 +0000";s:2:"dc";a:1:{s:7:"creator";s:17:"Lorelle VanFossen";}s:7:"summary";s:3076:"

    WordPress.com NewsI and many WordPress “representatives”, along with the developers and staff of and , are getting more and more complaints and requests for help dealing with content theft issues. We all need to clear this up and spread the word about how this works in relationship to WordPress.

    \n

    In order to go after a copyright violation of your content, you have to contact the site owner first. When that fails, you ask the web host for assistance, in accordance with the DMCA, to contact the site owner and deal with the copyright violation. Herein lies the problem.

    \n

    As Mark Jaquith recently stated, there is a lot of name confusion between a blog and a blog. Since a web host in the United States is required to assist with copyright infringement issues when contacted, when is WordPress the host and when is it not? After all, it’s all WordPress, right?

    \n

    Not.
    \n (more…)

    \n
    ";}i:21;a:7:{s:5:"title";s:104:"WordPress Podcast: Episode 33: WordPress 2.3.2 released, WordPress 2.4 missed and changes to the podcast";s:4:"guid";s:116:"http://wp-community.org/2008/02/04/episode-33-wordpress-232-released-wordpress-24-missed-and-changes-to-the-podcast/";s:4:"link";s:46:"http://wp-community.org/2008/02/04/episode-33/";s:11:"description";s:5947:"

    Discussed in this long-overdue and extremely lengthy episode are such subjects as:

    \n
      \n
    1. Changes coming for the podcast
      2. \n
    2. WordPress 2.3.2 released and is considered an urgent security release.
      3. \n
    3. WordPress 2.4 is a missed release, WordPress 2.5 in the works: Westi on WordPress, David Peralty’s Admin Overview and Liz Danzico’s WordCamp session on the admin overhaul (including her slides).
      4. \n
    4. WordPress Developers Considering Change to Release Schedule
      5. \n
    5. Automattic Receives $29.5M in Series B Funding
      6. \n
    6. WordPress wins Crunchie for “Most Likely to Succeed”, Toni Schneider “Best Startup CEO”
      7. \n
    7. Blog security gains attention: David Airey hacked using a GMail exploit,