__group__,ticket,summary,reporter,owner,component,_version,priority,severity,type,_status,workflow,_created,modified,_description,_reporter Has Patch / Needs Testing,14368,"make the 'orderby' argument in get_posts() accept all ""post"" fields",wjm,,Query,3.0,normal,normal,enhancement,reopened,has-patch,2010-07-20T23:58:41Z,2022-08-01T15:09:02Z,"Right now, some post's fields were not accepted when retrieving posts (even though they were documented in codex . for example ""name"" (slug) was missing). this patch sorts the elements in the $allow_keys array (in the same order as the db' s columns) and adds the missing ones, I added every field except the ones that were long text fields (content, excerpt, etc) ",wjm Needs Patch,14513,Time for a wp_post_relationships table?,mikeschinkel,,"Posts, Post Types",3.0.1,normal,normal,feature request,reopened,,2010-08-03T00:10:30Z,2023-05-30T15:04:16Z,"Now that we have custom post types the obvious next step for people using them is to start relating post types using parent-child and/or many-to-many relationships. I've implemented a taxonomy-mirrored-posts plugin but am starting to discover [http://lists.automattic.com/pipermail/wp-hackers/2010-July/033510.html many of the problems that @prettyboymp has pointed out on wp-hackers] and think it might be time we consider adding a new table to allow us to relate post and to allow us to build functionality around this table such as related post pickers, etc. I'd like to offer a [http://en.wikipedia.org/wiki/Straw_man_proposal straw man proposal] to start discussions of a potential `wp_post_relationships` table added to WordPress 3.1 with three fields: `parent_id`, `post_id` and `term_taxonomy_id.` This allows us to relate any two post records and optionally associate at taxonomy+term to classify the relationship (here's the SQL to create the table): {{{ CREATE TABLE `wp_post_relationships` ( `parent_id` bigint(20) unsigned NOT NULL, `post_id` bigint(20) unsigned NOT NULL, `term_taxonomy_id` bigint(20) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`parent_id`,`post_id`,`term_taxonomy_id`), KEY `term_taxonomy_id` (`term_taxonomy_id`), KEY `post_id` (`post_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; }}} Looking forward to your feedback.",mikeschinkel Has Patch / Needs Testing,11538,Unbundle Hello Dolly,caesarsgrunt,westi,Plugins,3.0,normal,normal,enhancement,reopened,has-patch,2009-12-20T22:47:27Z,2024-03-02T21:23:22Z,"Now that WordPress is a mature platform, having Hello Dolly as a default plugin is really a bit of an embarrassment. With the impending focus on canonical plugins, this strikes me as a good opportunity to remove Hello Dolly and replace it with a plugin which is actually useful. Hello Dolly could be kept in the repo for the sake of nostalgia if it's wanted by anyone...",caesarsgrunt Needs Reporter Feedback / Steps To Reproduce,14110,Expose height and width attributes to 'wp_get_attachment_image_attributes' filter,divinenephron,adamsilverstein,Media,3.0,normal,minor,enhancement,assigned,reporter-feedback,2010-06-27T00:54:46Z,2023-10-11T13:51:39Z,"The filter 'wp_get_attachment_image_attributes' allows you to alter the attributes of embedded images. However the height and width attributes aren't passed to this filter. These would be useful to have – I'm making a theme with a fluid layout where I have to remove all height and width attributes to ensure that the browser maintains the attribute of images when they're resized. I've attached a patch with a fix. In it I've also changed the function 'get_image_tag' so that I could remove the immensely pointless 'hwstring' function.",divinenephron Needs Patch,20602,Replace media,PorridgeBear,,Media,3.3.1,normal,normal,enhancement,reopened,,2012-05-02T13:29:45Z,2023-10-18T23:58:59Z,"I have been developing themes for clients lately that require the same image across the theme in varying places. A good example is an event site where the image is a badge/sticker showing the price of the tickets. This gets output on various pages in varying locations. get_attachment_link is perfect as I can plugin a single ID and use the graphic wherever. However, the ticket prices change as the event gets closer and the graphic needs to be updated which breaks the theme in production when my client does so as a new ID is generated. This doesn't make too much sense to me. I've worked with and developed CMSs of all kinds and usually the ID is preserved. I would at least like the option, perhaps a checkbox, to indicate I want to reupload a new image. I think it's more common that an update on a media item would be to modify the same logical graphic rather than just replacing it with something entirely new. I found the following plugin but I feel this really ought to be core. http://wordpress.org/extend/plugins/enable-media-replace/ Thanks for your consideration.",PorridgeBear Has Patch / Needs Testing,18330,Add a Class functionality to wpautop(),wpsmith,,Formatting,,normal,normal,enhancement,reopened,has-patch,2011-08-04T20:17:29Z,2023-07-25T16:42:17Z,"It would be nice to be able to add a class to
with wpauto as an optional arg. ",wpsmith Has Patch / Needs Testing,10404,dbDelta creates duplicate indexes when index definition contains spaces,Denis-de-Bernardy,,Database,2.8.1,normal,normal,enhancement,reopened,has-patch,2009-07-14T10:59:54Z,2023-01-21T16:01:09Z,"I was adding a much needed index in wp_object_term_relationships, and testing revealed it was getting added multiple times. This works as intended: {{{ CREATE TABLE $wpdb->term_relationships ( object_id bigint(20) unsigned NOT NULL default 0, term_taxonomy_id bigint(20) unsigned NOT NULL default 0, term_order int(11) NOT NULL default 0, PRIMARY KEY (object_id,term_taxonomy_id), UNIQUE KEY reverse_pkey (term_taxonomy_id,object_id), KEY term_taxonomy_id (term_taxonomy_id) ) $charset_collate;""); }}} This doesn't: {{{ CREATE TABLE $wpdb->term_relationships ( object_id bigint(20) unsigned NOT NULL default 0, term_taxonomy_id bigint(20) unsigned NOT NULL default 0, term_order int(11) NOT NULL default 0, PRIMARY KEY (object_id,term_taxonomy_id), UNIQUE KEY reverse_pkey (term_taxonomy_id, object_id), KEY term_taxonomy_id (term_taxonomy_id) ) $charset_collate;""); }}} the only difference between the two is a space in the reverse_pkey column list. we should remove spaces in there to avoid potential bugs.",Denis-de-Bernardy Needs Patch,8857,Make WP MySQL strict mode compliant,ghostks,,Database,6.4.2,lowest,normal,enhancement,reopened,,2009-01-14T11:25:26Z,2024-01-22T08:45:43Z,"Incorrect Mysql scheme during WordPress installation on DBMS with strict date/datetime format settings will result in errors and will be unable to finish succesfully. Existing default date and datetime values are '0000-00-00' and '0000-00-00 00:00:00' which are not supported any more. Please see official Mysql dev documentation for more information: {{{ The DATE type is used when you need only a date value, without a time part. MySQL retrieves and displays DATE values in 'YYYY-MM-DD' format. The supported range is '1000-01-01' to '9999-12-31'. }}} http://dev.mysql.com/doc/refman/5.0/en/datetime.html ",ghostks