From wp-trac at lists.automattic.com Wed Nov 1 00:07:56 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 00:08:04 2006 Subject: [wp-trac] Re: [WordPress Trac] #1334: Wrong date-format in the RSS-feed In-Reply-To: <066.34ce617c7662cb3d62d94040aba4bca6@lists.automattic.com> References: <066.34ce617c7662cb3d62d94040aba4bca6@lists.automattic.com> Message-ID: <075.13b2e0b9e50259e79516f0cd137bec74@lists.automattic.com> #1334: Wrong date-format in the RSS-feed ---------------------+------------------------------------------------------ Reporter: jowra | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: General | Version: 1.5.1 Severity: minor | Resolution: worksforme Keywords: | ---------------------+------------------------------------------------------ Changes (by foolswisdom): * status: new => closed * resolution: => worksforme Comment: Closing WORKSFORME without testing. I am assuming this has been fixed a long time ago, otherwise would continue to see this issue reported. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 01:08:19 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 01:08:32 2006 Subject: [wp-trac] [WordPress Trac] #3312: Capital Z in HTML editor triggers new line Message-ID: <066.2fe574f41a0a824c470e1babc14e7e5b@lists.automattic.com> #3312: Capital Z in HTML editor triggers new line ----------------------------+----------------------------------------------- Reporter: foolswisdom | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Keywords: ----------------------------+----------------------------------------------- Capital Z in HTML editor triggers new line when you switch to the Visual editor ENV: WP trunk r6805 REPRO: always STEPS[[br]] 1. In HTML (quick tag) editor enter {{{Zebra}}} [[BR]] 2. Click Editor (Visual) tab ACTUAL RESULTS[[br]] Test has become:[[br]] Z[[br]] ebra ADDITIONAL DETAILS Entering {{{ZYX}}} becomes[[br]] Z[[br]]YX[[br]] with those being two links to the same site -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 01:08:53 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 01:08:59 2006 Subject: [wp-trac] Re: [WordPress Trac] #3295: customizable open proxy scanner for comments In-Reply-To: <066.a926f1445b0c897bd0d7ad7e79c2f1ee@lists.automattic.com> References: <066.a926f1445b0c897bd0d7ad7e79c2f1ee@lists.automattic.com> Message-ID: <075.8655df2ccbd49fd0fee5cf1c26f94d9f@lists.automattic.com> #3295: customizable open proxy scanner for comments ----------------------------+----------------------------------------------- Reporter: tandilboy | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Resolution: invalid Keywords: | ----------------------------+----------------------------------------------- Changes (by JeremyVisser): * status: new => closed * resolution: => invalid Comment: WordPress already does this. Go to Options > Discussion and tick the "Blacklist comments from open and insecure proxies" box. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 01:09:40 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 01:09:55 2006 Subject: [wp-trac] Re: [WordPress Trac] #3297: split comments into pages In-Reply-To: <066.0eacf53d238098c5639ed731abab2d30@lists.automattic.com> References: <066.0eacf53d238098c5639ed731abab2d30@lists.automattic.com> Message-ID: <075.713fe8469fe4f98a789fa0be61f9222d@lists.automattic.com> #3297: split comments into pages ----------------------------+----------------------------------------------- Reporter: tandilboy | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Resolution: invalid Keywords: | ----------------------------+----------------------------------------------- Comment (by JeremyVisser): http://www.keyvan.net/code/paged-comments/ -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 02:35:37 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 02:35:45 2006 Subject: [wp-trac] Re: [WordPress Trac] #1374: Page loses archives/link.php template field when edited In-Reply-To: <066.096a67ea1fa1a99941ca3e6ff4243465@lists.automattic.com> References: <066.096a67ea1fa1a99941ca3e6ff4243465@lists.automattic.com> Message-ID: <075.3a3991007c9ec9ceb8c04d9c36a82024@lists.automattic.com> #1374: Page loses archives/link.php template field when edited -----------------------------+---------------------------------------------- Reporter: YellowSwordfish | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Administration | Version: 2.1 Severity: minor | Resolution: wontfix Keywords: | -----------------------------+---------------------------------------------- Changes (by foolswisdom): * status: new => closed * version: 1.5.1 => 2.1 * resolution: => wontfix Comment: Closing WONTFIX seeing as no comments in a year. ENV: WP trunk r4438 [[br]] Behavior is still as described. Saving a post/page without any title or content does not seem generally useful. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 02:38:56 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 02:39:03 2006 Subject: [wp-trac] Re: [WordPress Trac] #1363: A Way to check if page is children In-Reply-To: <066.5d7774bf759822a452688f11b0147e66@lists.automattic.com> References: <066.5d7774bf759822a452688f11b0147e66@lists.automattic.com> Message-ID: <075.56aaea4ad4700de8c9fb8160d2ec66d7@lists.automattic.com> #1363: A Way to check if page is children --------------------------+------------------------------------------------- Reporter: DeadPOet | Owner: ryan Type: enhancement | Status: closed Priority: normal | Milestone: Component: Optimization | Version: 1.5.1.1 Severity: normal | Resolution: wontfix Keywords: | --------------------------+------------------------------------------------- Changes (by foolswisdom): * status: new => closed * resolution: => wontfix Comment: Closing bug as WONTFIX. No update in a year. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 04:55:44 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 04:55:53 2006 Subject: [wp-trac] Re: [WordPress Trac] #3253: Give parnent of current page/category a CSS class In-Reply-To: <066.ab604d74b632ef6256c5ca47b5fd7f69@lists.automattic.com> References: <066.ab604d74b632ef6256c5ca47b5fd7f69@lists.automattic.com> Message-ID: <075.0afa7ee75164d51ec5f6dcbac47bc4d7@lists.automattic.com> #3253: Give parnent of current page/category a CSS class ----------------------+----------------------------------------------------- Reporter: mdawaffe | Owner: markjaquith Type: defect | Status: assigned Priority: normal | Milestone: 2.1 Component: Template | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by markjaquith): * status: new => assigned * owner: anonymous => markjaquith Comment: Should probably pass by reference for {{{get_page()}}} and {{{get_category}}} Let's stick with the underscore... I don't like them being different and changing them to dashes would break countless themes and plugins. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 06:47:11 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 06:47:20 2006 Subject: [wp-trac] Re: [WordPress Trac] #3295: customizable open proxy scanner for comments In-Reply-To: <066.a926f1445b0c897bd0d7ad7e79c2f1ee@lists.automattic.com> References: <066.a926f1445b0c897bd0d7ad7e79c2f1ee@lists.automattic.com> Message-ID: <075.61bb25edf2722cd78a0a8e403ebf5088@lists.automattic.com> #3295: customizable open proxy scanner for comments ----------------------------+----------------------------------------------- Reporter: tandilboy | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Resolution: invalid Keywords: | ----------------------------+----------------------------------------------- Comment (by markjaquith): This feature has been removed in 2.1, so this is now plugin territory. SK2 supports it, but a standalone proxy checker might be of some use. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 11:39:27 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 11:39:36 2006 Subject: [wp-trac] [WordPress Trac] #3313: "Under Maintenance" Page Message-ID: <066.e2bc9819eec5d749ce042c301cea25d3@lists.automattic.com> #3313: "Under Maintenance" Page -------------------------+-------------------------------------------------- Reporter: bryanveloso | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.2 Component: General | Version: Severity: normal | Keywords: -------------------------+-------------------------------------------------- There should be a toggle (maybe in options) to allow for WP to go into "maintenance mode", say when template edits are being done. I know this can kinda-sorta be done with the theme change plugins, but there should be something a little more reliable. Sort of like WP.com's server maintenance page. This could be set to match sites in a maintenance.php template file. It would just make things a lot easier for template authors to make live changes without having people peek in too early. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 12:11:56 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 12:12:16 2006 Subject: [wp-trac] Re: [WordPress Trac] #3313: "Under Maintenance" Page In-Reply-To: <066.e2bc9819eec5d749ce042c301cea25d3@lists.automattic.com> References: <066.e2bc9819eec5d749ce042c301cea25d3@lists.automattic.com> Message-ID: <075.d9462702c7f91dc23ebe573076a6b143@lists.automattic.com> #3313: "Under Maintenance" Page -------------------------+-------------------------------------------------- Reporter: bryanveloso | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.2 Component: General | Version: Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Comment (by westi): Is this not really a job for a plugin? There are a number of maintenance mode plugins which allow backend access while disabling access to the front end. To support theme changes any code would have to allow some users to still get the real site while everyone else gets the maintenance page. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 19:23:19 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 19:24:16 2006 Subject: [wp-trac] [WordPress Trac] #3314: typo in wp-login.php Message-ID: <066.c7a9ba72f86b19ba099fb276c180e06a@lists.automattic.com> #3314: typo in wp-login.php ----------------------------+----------------------------------------------- Reporter: schulte | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: 2.1 Severity: trivial | Keywords: ----------------------------+----------------------------------------------- Line 135 of wp-login.php has 'recieve' instead of 'receive.' -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 19:55:28 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 19:56:16 2006 Subject: [wp-trac] Re: [WordPress Trac] #3314: typo in wp-login.php In-Reply-To: <066.c7a9ba72f86b19ba099fb276c180e06a@lists.automattic.com> References: <066.c7a9ba72f86b19ba099fb276c180e06a@lists.automattic.com> Message-ID: <075.11a0025b3ce0ae642d69cb269dcd43d6@lists.automattic.com> #3314: typo in wp-login.php ----------------------------+----------------------------------------------- Reporter: schulte | Owner: Nazgul Type: defect | Status: assigned Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: trivial | Resolution: Keywords: has-patch | ----------------------------+----------------------------------------------- Changes (by Nazgul): * keywords: => has-patch * status: new => assigned * owner: anonymous => Nazgul * milestone: => 2.1 Comment: Patch for the typo. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 20:26:19 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 20:27:16 2006 Subject: [wp-trac] [WordPress Trac] #3315: Language files in wp-content Message-ID: <066.50df9fb2010b793418c774d1b660d7ff@lists.automattic.com> #3315: Language files in wp-content -------------------------+-------------------------------------------------- Reporter: Nazgul | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Keywords: -------------------------+-------------------------------------------------- Currently language files have to be stored in wp-include/languages, while other "user content" like plugins and themes are in wp-content. It makes more sense (to me at least) to place language files in wp-content as well. This also simplifies upgrading, because you don't have to remember to save/backup your language files, before deleting the wp-includes folder, as per the installation instructions. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 20:29:31 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 20:30:27 2006 Subject: [wp-trac] Re: [WordPress Trac] #3315: Language files in wp-content In-Reply-To: <066.50df9fb2010b793418c774d1b660d7ff@lists.automattic.com> References: <066.50df9fb2010b793418c774d1b660d7ff@lists.automattic.com> Message-ID: <075.0bd9859acceb5bd764ae78a9c1f7306d@lists.automattic.com> #3315: Language files in wp-content -------------------------+-------------------------------------------------- Reporter: Nazgul | Owner: Nazgul Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch | -------------------------+-------------------------------------------------- Changes (by Nazgul): * keywords: => has-patch * status: new => assigned * owner: anonymous => Nazgul Comment: Attached patch uses wp-content/languages folder if it exists and falls back to wp-includes/languages if it doesn't. This fallback keeps existing installations working. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 20:48:11 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 20:48:29 2006 Subject: [wp-trac] Re: [WordPress Trac] #3312: Capital Z in HTML editor triggers new line In-Reply-To: <066.2fe574f41a0a824c470e1babc14e7e5b@lists.automattic.com> References: <066.2fe574f41a0a824c470e1babc14e7e5b@lists.automattic.com> Message-ID: <075.5e46ab09b2df919567d3e1c59b748989@lists.automattic.com> #3312: Capital Z in HTML editor triggers new line ----------------------------+----------------------------------------------- Reporter: foolswisdom | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: needs-patch | ----------------------------+----------------------------------------------- Changes (by Nazgul): * keywords: => needs-patch Comment: The following line is the culprit (578 of wp- includes/js/tinymce/plugins/wordpress/editor_plugin.js): {{{ pee = pee.replace(new RegExp('\n*([^\Z]+?)\\n{2}', 'mg'), "

$1

\n"); }}} I don't know how to fix it, because I don't have a clue what that line is supposed to do. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 21:38:16 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 21:38:34 2006 Subject: [wp-trac] Re: [WordPress Trac] #3303: Comments feed should specify the comment author In-Reply-To: <066.edd744050697b2b088a76215b5eb3231@lists.automattic.com> References: <066.edd744050697b2b088a76215b5eb3231@lists.automattic.com> Message-ID: <075.2c0c85039fdf25786ece51a310dcb63e@lists.automattic.com> #3303: Comments feed should specify the comment author ----------------------------+----------------------------------------------- Reporter: markjaquith | Owner: Nazgul Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.4 Severity: normal | Resolution: Keywords: has-patch | ----------------------------+----------------------------------------------- Changes (by Nazgul): * keywords: => has-patch * status: new => assigned * owner: anonymous => Nazgul Comment: Attached patch adds the element to comments in the comments rss. Do we want to change the current 'author in comment title' behaviour as well? -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 21:42:07 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 21:42:21 2006 Subject: [wp-trac] Re: [WordPress Trac] #3312: Capital Z in HTML editor triggers new line In-Reply-To: <066.2fe574f41a0a824c470e1babc14e7e5b@lists.automattic.com> References: <066.2fe574f41a0a824c470e1babc14e7e5b@lists.automattic.com> Message-ID: <075.ced1b78a56d78288e4cba63f8d1a9906@lists.automattic.com> #3312: Capital Z in HTML editor triggers new line ----------------------------+----------------------------------------------- Reporter: foolswisdom | Owner: andy Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: needs-patch | ----------------------------+----------------------------------------------- Changes (by andy): * owner: anonymous => andy Comment: That line -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 21:45:02 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 21:45:15 2006 Subject: [wp-trac] Re: [WordPress Trac] #3312: Capital Z in HTML editor triggers new line In-Reply-To: <066.2fe574f41a0a824c470e1babc14e7e5b@lists.automattic.com> References: <066.2fe574f41a0a824c470e1babc14e7e5b@lists.automattic.com> Message-ID: <075.bf16593a4b57d803eeda408643526989@lists.automattic.com> #3312: Capital Z in HTML editor triggers new line ----------------------------+----------------------------------------------- Reporter: foolswisdom | Owner: andy Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: needs-patch | ----------------------------+----------------------------------------------- Comment (by andy): That line is meant to grab everything up to a double line ending and put it in a paragraph. Backslash-Z should mean "all characters not being the end boundary of a line." I'll work out a better pattern. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 21:49:41 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 21:49:48 2006 Subject: [wp-trac] [WordPress Trac] #3316: Protected post password is plain text in cookie Message-ID: <066.606d1560e324c9972a45fb54875220bc@lists.automattic.com> #3316: Protected post password is plain text in cookie ----------------------+----------------------------------------------------- Reporter: dosa | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.0.5 Component: Security | Version: 2.1 Severity: normal | Keywords: ----------------------+----------------------------------------------------- Once a password is entered for a protected post it is stored as plain text in the cookie for all to see. Surely simply keeping some kind of hash would be better? -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 21:53:33 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 21:53:45 2006 Subject: [wp-trac] [WordPress Trac] #3317: Protected posts should not be found in searches Message-ID: <066.024421f98be888b39ddced82bd065861@lists.automattic.com> #3317: Protected posts should not be found in searches ---------------------+------------------------------------------------------ Reporter: dosa | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.0.5 Component: General | Version: 2.1 Severity: normal | Keywords: ---------------------+------------------------------------------------------ By listing password protected posts in search results nosey users can fish for the post content - eg trying their own name if they think the post might be about them. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 22:00:12 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 22:00:43 2006 Subject: [wp-trac] [WordPress Trac] #3318: Missing version 2.0.5 in Trac Message-ID: <066.caf050715a9ac3181ca94e0de9de4184@lists.automattic.com> #3318: Missing version 2.0.5 in Trac ---------------------------+------------------------------------------------ Reporter: Nazgul | Owner: matt Type: task | Status: new Priority: normal | Milestone: Component: WordPress.org | Version: Severity: normal | Keywords: ---------------------------+------------------------------------------------ We're missing version 2.0.5 in Trac. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 22:07:30 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 22:07:37 2006 Subject: [wp-trac] [WordPress Trac] #3319: Export sends Content-Type twice Message-ID: <066.10ceaca50a9b3f30716c90dbd23d5dec@lists.automattic.com> #3319: Export sends Content-Type twice ----------------------------+----------------------------------------------- Reporter: Nazgul | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Keywords: ----------------------------+----------------------------------------------- The export module sends the Content-Type header twice. Once as application /octet-stream, the other as text/xml. {{{ header('Content-Description: File Transfer'); header('Content-Type: application/octet-stream'); header("Content-Disposition: attachment; filename=$filename"); header('Content-type: text/xml; charset=' . get_option('blog_charset'), true); }}} -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 22:35:36 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 22:35:43 2006 Subject: [wp-trac] Re: [WordPress Trac] #3316: Protected post password is plain text in cookie In-Reply-To: <066.606d1560e324c9972a45fb54875220bc@lists.automattic.com> References: <066.606d1560e324c9972a45fb54875220bc@lists.automattic.com> Message-ID: <075.4235d6f5b9c7ae949479b522d6401c5f@lists.automattic.com> #3316: Protected post password is plain text in cookie ----------------------+----------------------------------------------------- Reporter: dosa | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Security | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by ryan): * milestone: 2.0.5 => 2.1 -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 22:35:23 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 22:37:25 2006 Subject: [wp-trac] Re: [WordPress Trac] #3317: Protected posts should not be found in searches In-Reply-To: <066.024421f98be888b39ddced82bd065861@lists.automattic.com> References: <066.024421f98be888b39ddced82bd065861@lists.automattic.com> Message-ID: <075.29729788609bc67ab74d4ee33c2763c9@lists.automattic.com> #3317: Protected posts should not be found in searches ---------------------+------------------------------------------------------ Reporter: dosa | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: | ---------------------+------------------------------------------------------ Changes (by ryan): * milestone: 2.0.5 => 2.1 -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 23:20:21 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 23:20:43 2006 Subject: [wp-trac] Re: [WordPress Trac] #3318: Missing version 2.0.5 in Trac In-Reply-To: <066.caf050715a9ac3181ca94e0de9de4184@lists.automattic.com> References: <066.caf050715a9ac3181ca94e0de9de4184@lists.automattic.com> Message-ID: <075.7bd4b03724effa9d8db7a79ba07c6c68@lists.automattic.com> #3318: Missing version 2.0.5 in Trac ---------------------------+------------------------------------------------ Reporter: Nazgul | Owner: matt Type: task | Status: closed Priority: normal | Milestone: Component: WordPress.org | Version: 2.0.5 Severity: normal | Resolution: fixed Keywords: | ---------------------------+------------------------------------------------ Changes (by foolswisdom): * status: new => closed * version: => 2.0.5 * resolution: => fixed Comment: Fixed thank you. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 23:36:28 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 23:36:44 2006 Subject: [wp-trac] Re: [WordPress Trac] #3313: "Under Maintenance" Page In-Reply-To: <066.e2bc9819eec5d749ce042c301cea25d3@lists.automattic.com> References: <066.e2bc9819eec5d749ce042c301cea25d3@lists.automattic.com> Message-ID: <075.a9b9dc13754c0ff9d16e6b1b82760bfa@lists.automattic.com> #3313: "Under Maintenance" Page -------------------------+-------------------------------------------------- Reporter: bryanveloso | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: 2.2 Component: General | Version: Severity: normal | Resolution: wontfix Keywords: | -------------------------+-------------------------------------------------- Changes (by Viper007Bond): * status: new => closed * resolution: => wontfix Comment: Replying to [comment:1 westi]: > Is this not really a job for a plugin? That it is. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 23:38:20 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 23:38:42 2006 Subject: [wp-trac] Re: [WordPress Trac] #3314: typo in wp-login.php In-Reply-To: <066.c7a9ba72f86b19ba099fb276c180e06a@lists.automattic.com> References: <066.c7a9ba72f86b19ba099fb276c180e06a@lists.automattic.com> Message-ID: <075.3e564cecfdbdbebb08f5c5aa8f2e82f1@lists.automattic.com> #3314: typo in wp-login.php ----------------------------+----------------------------------------------- Reporter: schulte | Owner: Nazgul Type: defect | Status: assigned Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: trivial | Resolution: Keywords: has-patch | ----------------------------+----------------------------------------------- Comment (by Viper007Bond): I before E except after C. My bad. :( -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 23:39:05 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 23:39:11 2006 Subject: [wp-trac] Re: [WordPress Trac] #3315: Language files in wp-content In-Reply-To: <066.50df9fb2010b793418c774d1b660d7ff@lists.automattic.com> References: <066.50df9fb2010b793418c774d1b660d7ff@lists.automattic.com> Message-ID: <075.a72dcb0abe2195c6fab3b54a8fe0db20@lists.automattic.com> #3315: Language files in wp-content -------------------------+-------------------------------------------------- Reporter: Nazgul | Owner: Nazgul Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch | -------------------------+-------------------------------------------------- Comment (by Viper007Bond): Good thinking. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 23:40:30 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 23:40:36 2006 Subject: [wp-trac] Re: [WordPress Trac] #3316: Protected post password is plain text in cookie In-Reply-To: <066.606d1560e324c9972a45fb54875220bc@lists.automattic.com> References: <066.606d1560e324c9972a45fb54875220bc@lists.automattic.com> Message-ID: <075.9f7a406db48f6667d74008fae583582b@lists.automattic.com> #3316: Protected post password is plain text in cookie ----------------------+----------------------------------------------------- Reporter: dosa | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Security | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by Viper007Bond): "for all to see" Well it's not like other sites can access the cookie or anything. ;) But yeah, hashing the cookie value isn't a bad idea. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 1 23:42:21 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 1 23:42:30 2006 Subject: [wp-trac] Re: [WordPress Trac] #3225: Export file does not download in FF In-Reply-To: <066.c6ba1a3b130cbdb1bf3f267ce7680516@lists.automattic.com> References: <066.c6ba1a3b130cbdb1bf3f267ce7680516@lists.automattic.com> Message-ID: <075.fb17b1910192873361ec4231eed3bfe9@lists.automattic.com> #3225: Export file does not download in FF ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: markjaquith Type: defect | Status: assigned Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by Viper007Bond): Latest stable of course (2.0). ;) -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 2 00:40:33 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 2 00:40:41 2006 Subject: [wp-trac] [WordPress Trac] #3320: Comments page should have paging Message-ID: <066.7e80bc195f5d58e823dbb16d1225c390@lists.automattic.com> #3320: Comments page should have paging ----------------------------+----------------------------------------------- Reporter: matt | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: Severity: normal | Keywords: ----------------------------+----------------------------------------------- edit-comments.php shows a list of recent comments which is handy, but it'd be nice if we could give it paging like we have a few other places like the Akismet plugin. If anyone wants to take a whack at this a patch would be welcome. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 2 01:19:20 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 2 01:19:35 2006 Subject: [wp-trac] Re: [WordPress Trac] #3252: Wrap Category Name in CDATA In-Reply-To: <066.8111890881153313108403607ea04c6c@lists.automattic.com> References: <066.8111890881153313108403607ea04c6c@lists.automattic.com> Message-ID: <075.af3bebd06e5e03ef68c28c35f41549c9@lists.automattic.com> #3252: Wrap Category Name in CDATA -------------------------+-------------------------------------------------- Reporter: alexkingorg | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch | -------------------------+-------------------------------------------------- Comment (by matt): +1 -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 2 01:20:07 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 2 01:20:25 2006 Subject: [wp-trac] Re: [WordPress Trac] #3246: make menu items in menu-headers.php relative In-Reply-To: <066.31298a3cbd5c06d5d9f8c6c2496391bc@lists.automattic.com> References: <066.31298a3cbd5c06d5d9f8c6c2496391bc@lists.automattic.com> Message-ID: <075.1b23ece72f6c77337562710d65f6797a@lists.automattic.com> #3246: make menu items in menu-headers.php relative ------------------------------+--------------------------------------------- Reporter: bmontgom | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: SSL dev-feedback | ------------------------------+--------------------------------------------- Comment (by matt): No opinion. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 2 01:36:56 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 2 01:37:13 2006 Subject: [wp-trac] [WordPress Trac] #3321: Empty list item in default theme's sidebar Message-ID: <066.11bcbeeb1070458348ddc8a0d5ed6fe2@lists.automattic.com> #3321: Empty list item in default theme's sidebar -------------------------+-------------------------------------------------- Reporter: idle | Owner: anonymous Type: enhancement | Status: new Priority: lowest | Milestone: 2.1 Component: Template | Version: 2.1 Severity: trivial | Keywords: -------------------------+-------------------------------------------------- In theme Default, the "You are currently browsing..." section is sometimes empty, resulting in an empty list item. Tried it with a fresh installation of 2.0.5 as well as 2.1-alpha3 from SVN. Attached is a patch that'll take care of the empty LI by surrounding each "currently browsing..." part with LIs, rather than the entire section whereas the conditions may return false. Pardon the nitpicking. ;) -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 2 03:00:25 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 2 03:00:51 2006 Subject: [wp-trac] Re: [WordPress Trac] #3317: Protected posts should not be found in searches In-Reply-To: <066.024421f98be888b39ddced82bd065861@lists.automattic.com> References: <066.024421f98be888b39ddced82bd065861@lists.automattic.com> Message-ID: <075.b4a5f2c098e8e7ea7e2ccd6fa714da57@lists.automattic.com> #3317: Protected posts should not be found in searches ---------------------+------------------------------------------------------ Reporter: dosa | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: worksforme Keywords: | ---------------------+------------------------------------------------------ Changes (by markjaquith): * status: new => closed * resolution: => worksforme Comment: Could not duplicate on trunk. I couldn't get private posts to show up in search results for non-logged-in users or logged-in users who didn't write the private post. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 2 06:02:39 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 2 06:02:47 2006 Subject: [wp-trac] Re: [WordPress Trac] #3315: Language files in wp-content In-Reply-To: <066.50df9fb2010b793418c774d1b660d7ff@lists.automattic.com> References: <066.50df9fb2010b793418c774d1b660d7ff@lists.automattic.com> Message-ID: <075.14217ffd97037b6db08e36c98835c9ee@lists.automattic.com> #3315: Language files in wp-content -------------------------+-------------------------------------------------- Reporter: Nazgul | Owner: Nazgul Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch | -------------------------+-------------------------------------------------- Comment (by markjaquith): I like it. No modified files or directories should be in {{{wp-admin}}} or {{{wp-includes}}} -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 2 06:08:31 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 2 06:08:39 2006 Subject: [wp-trac] Re: [WordPress Trac] #3315: Language files in wp-content In-Reply-To: <066.50df9fb2010b793418c774d1b660d7ff@lists.automattic.com> References: <066.50df9fb2010b793418c774d1b660d7ff@lists.automattic.com> Message-ID: <075.41f7c7c0a9e2943d8858ee9aacde1d69@lists.automattic.com> #3315: Language files in wp-content -------------------------+-------------------------------------------------- Reporter: Nazgul | Owner: Nazgul Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch | -------------------------+-------------------------------------------------- Comment (by ryan): Why not. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 2 06:17:13 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 2 06:17:33 2006 Subject: [wp-trac] Re: [WordPress Trac] #3299: @ character stripped from mailto link, http:// inserted in string In-Reply-To: <066.90cfe49bbacf0fedca564b6a10d47f3e@lists.automattic.com> References: <066.90cfe49bbacf0fedca564b6a10d47f3e@lists.automattic.com> Message-ID: <075.8a64392e562cfb1c306421a796e60a0f@lists.automattic.com> #3299: @ character stripped from mailto link, http:// inserted in string ----------------------+----------------------------------------------------- Reporter: redclown | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: General | Version: 2.0.5 Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by JeremyVisser): * version: => 2.0.5 * component: Template => General Comment: I encounter this also when changing my Blog and WordPress addresses (Options > General) to be relative addresses, which shows it is not a templating problem. For example, I had a WordPress running on localhost, which had the address {{{http://localhost/wordpress}}} as the address. Of course, when I navigated to that WP from another computer, all the stylesheets and links were broken because they were still pointing to {{{localhost}}}. What saved me in early 2.0 versions was simply changing the {{{http://localhost/wordpress}}} to {{{/wordpress}}}, and that worked fine. Well, the RSS feed links broke but that didn't matter. Something's changed in the URL validation in 2.0.5 (it may have been 2.0.4 or 2.0.3, I don't know. It worked in 2.0.2, though) that forces all URLs to have a {{{http://}}} at the beginning. I had a valid reason for not having a {{{http://}}}, so WP shouldn't be forcing me to. ''P.S. I had to manually edit my MySQL tables after the above saga, because I couldn't log on because WP tried to load {{{http:///wp- login.php}}}.'' -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 2 10:41:59 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 2 10:42:16 2006 Subject: [wp-trac] [WordPress Trac] #3322: Problems with non latin characters in user names Message-ID: <066.5bb4adba297de16bbc64079a0a4c0e2b@lists.automattic.com> #3322: Problems with non latin characters in user names ----------------------------+----------------------------------------------- Reporter: sotirios | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Keywords: ----------------------------+----------------------------------------------- Hi guys. I reported following problem in the support forum and people suggested i report it as a bug. The problem: user names in my blog were all in greek. I didnt have a problem, until now. But the last months (possibly after an upgrade to wordpress 2) whenever i try to change a user's profile i get a silly message ERROR: This username is invalid. Please enter a valid username. Can anyone help? -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 2 12:18:27 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 2 12:18:42 2006 Subject: [wp-trac] [WordPress Trac] #3323: Admin menu shows item user can't use Message-ID: <066.a4f7c2523a6d08894d604715adef6bf7@lists.automattic.com> #3323: Admin menu shows item user can't use ----------------------------+----------------------------------------------- Reporter: ovgray | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Keywords: ----------------------------+----------------------------------------------- K2 and the sidebar widgets plugin both add submenu items to the Presentation (theme.php) admin menu item by calling add_submenu_page() with an access level parameter of '5' rather than one of the newer capabilities. When either K2 or the widgets plugin is active in a version 2.1alpha3 site, a user with 'editor' capabilities (which include access level 5) will see a 'Presentation' link to themes.php in the admin menu, but on clicking that link the user sees "You do not have sufficient permissions to access this page." -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 2 12:27:50 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 2 12:28:05 2006 Subject: [wp-trac] [WordPress Trac] #3324: Admin menu shows item user can't use Message-ID: <066.3301ac6bb6e708b3fd4aeb9741422c6b@lists.automattic.com> #3324: Admin menu shows item user can't use ----------------------------+----------------------------------------------- Reporter: ovgray | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Keywords: ----------------------------+----------------------------------------------- K2 and the sidebar widgets plugin both add submenu items to the Presentation (theme.php) admin menu item by calling add_submenu_page() with an access level parameter of '5' rather than one of the newer capabilities. When either K2 or the widgets plugin is active in a version 2.1alpha3 site, a user with 'editor' capabilities (which include access level '5') will see a 'Presentation' link to themes.php in the admin menu, but on clicking that link the user sees "You do not have sufficient permissions to access this page." -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 2 12:28:35 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 2 12:28:45 2006 Subject: [wp-trac] [WordPress Trac] #3325: Admin menu shows item user can't use Message-ID: <066.c755d5a58068b2360f49312fbf9b5825@lists.automattic.com> #3325: Admin menu shows item user can't use ----------------------------+----------------------------------------------- Reporter: ovgray | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: 2.1 Severity: normal | Keywords: ----------------------------+----------------------------------------------- K2 and the sidebar widgets plugin both add submenu items to the Presentation (theme.php) admin menu item by calling add_submenu_page() with an access level parameter of '5' rather than one of the newer capabilities. When either K2 or the widgets plugin is active in a version 2.1alpha3 site, a user with 'editor' capabilities (which include access level '5') will see a 'Presentation' link to themes.php in the admin menu, but on clicking that link the user sees "You do not have sufficient permissions to access this page." -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 2 12:30:27 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 2 12:30:34 2006 Subject: [wp-trac] Re: [WordPress Trac] #3325: Admin menu shows item user can't use In-Reply-To: <066.c755d5a58068b2360f49312fbf9b5825@lists.automattic.com> References: <066.c755d5a58068b2360f49312fbf9b5825@lists.automattic.com> Message-ID: <075.6baed8e89560de45270cd4d1a163b196@lists.automattic.com> #3325: Admin menu shows item user can't use ----------------------------+----------------------------------------------- Reporter: ovgray | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Administration | Version: 2.1 Severity: normal | Resolution: duplicate Keywords: | ----------------------------+----------------------------------------------- Changes (by westi): * status: new => closed * resolution: => duplicate Comment: Duplicate of #3323 -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 2 12:30:37 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 2 12:30:45 2006 Subject: [wp-trac] Re: [WordPress Trac] #3324: Admin menu shows item user can't use In-Reply-To: <066.3301ac6bb6e708b3fd4aeb9741422c6b@lists.automattic.com> References: <066.3301ac6bb6e708b3fd4aeb9741422c6b@lists.automattic.com> Message-ID: <075.61ab95389594986e42f865eae4b0849a@lists.automattic.com> #3324: Admin menu shows item user can't use ----------------------------+----------------------------------------------- Reporter: ovgray | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Resolution: duplicate Keywords: | ----------------------------+----------------------------------------------- Changes (by westi): * status: new => closed * resolution: => duplicate Comment: Duplicate of #3323 -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 2 17:31:16 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 2 17:31:26 2006 Subject: [wp-trac] Re: [WordPress Trac] #3312: Capital Z in HTML editor triggers new line In-Reply-To: <066.2fe574f41a0a824c470e1babc14e7e5b@lists.automattic.com> References: <066.2fe574f41a0a824c470e1babc14e7e5b@lists.automattic.com> Message-ID: <075.0f74c182d058b0158eb2b7fd80c5556c@lists.automattic.com> #3312: Capital Z in HTML editor triggers new line -------------------------------------+-------------------------------------- Reporter: foolswisdom | Owner: andy Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch needs-testing | -------------------------------------+-------------------------------------- Changes (by andy): * keywords: needs-patch => has-patch needs-testing -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 2 17:36:03 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 2 17:36:13 2006 Subject: [wp-trac] [WordPress Trac] #3326: Mark milestone 2.0.5 complete in Trac Message-ID: <066.c5c9530dab5385fff45386a0db3e88f2@lists.automattic.com> #3326: Mark milestone 2.0.5 complete in Trac ---------------------------+------------------------------------------------ Reporter: Nazgul | Owner: matt Type: task | Status: new Priority: normal | Milestone: Component: WordPress.org | Version: Severity: normal | Keywords: ---------------------------+------------------------------------------------ The 2.0.5 milestone should be marked as complete in Trac. This way it won't show up in the Roadmap anymore. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 2 17:41:27 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 2 17:41:38 2006 Subject: [wp-trac] Re: [WordPress Trac] #3326: Mark milestone 2.0.5 complete in Trac In-Reply-To: <066.c5c9530dab5385fff45386a0db3e88f2@lists.automattic.com> References: <066.c5c9530dab5385fff45386a0db3e88f2@lists.automattic.com> Message-ID: <075.cf42e05a987b22bcf8c98a2962fda306@lists.automattic.com> #3326: Mark milestone 2.0.5 complete in Trac ---------------------------+------------------------------------------------ Reporter: Nazgul | Owner: matt Type: task | Status: closed Priority: normal | Milestone: Component: WordPress.org | Version: Severity: normal | Resolution: fixed Keywords: | ---------------------------+------------------------------------------------ Changes (by ryan): * status: new => closed * resolution: => fixed Comment: Done. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 2 17:43:50 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 2 17:44:14 2006 Subject: [wp-trac] Re: [WordPress Trac] #3322: Problems with non latin characters in user names In-Reply-To: <066.5bb4adba297de16bbc64079a0a4c0e2b@lists.automattic.com> References: <066.5bb4adba297de16bbc64079a0a4c0e2b@lists.automattic.com> Message-ID: <075.0f13118375dcd9d38115278632871b55@lists.automattic.com> #3322: Problems with non latin characters in user names ----------------------------+----------------------------------------------- Reporter: sotirios | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.5 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by Viper007Bond): * version: => 2.0.5 * milestone: => 2.1 Comment: Usernames need to be A-Z and 0-9 plus a couple other standard characters I think like - and _. This is for code and other reasons to ensure one can login no matter the charset and things like that (stubs too). Display names exist so that you can show users in a different way with whatever characters you want. However, the change profile page probably shouldn't check the username since the field is disabled and for backwards compatibility such as this. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 3 01:30:16 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 3 01:30:24 2006 Subject: [wp-trac] Re: [WordPress Trac] #3321: Empty list item in default theme's sidebar In-Reply-To: <066.11bcbeeb1070458348ddc8a0d5ed6fe2@lists.automattic.com> References: <066.11bcbeeb1070458348ddc8a0d5ed6fe2@lists.automattic.com> Message-ID: <075.27bf1499f2343fb1eba5bbf7bcd1b3f6@lists.automattic.com> #3321: Empty list item in default theme's sidebar -------------------------+-------------------------------------------------- Reporter: idle | Owner: anonymous Type: enhancement | Status: new Priority: lowest | Milestone: 2.1 Component: Template | Version: 2.0.5 Severity: trivial | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by idle): * version: 2.1 => 2.0.5 -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 3 01:37:06 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 3 01:37:16 2006 Subject: [wp-trac] Re: [WordPress Trac] #3315: Language files in wp-content In-Reply-To: <066.50df9fb2010b793418c774d1b660d7ff@lists.automattic.com> References: <066.50df9fb2010b793418c774d1b660d7ff@lists.automattic.com> Message-ID: <075.85b3b56bff3ecacc725edb9d6fedda7f@lists.automattic.com> #3315: Language files in wp-content -------------------------+-------------------------------------------------- Reporter: Nazgul | Owner: Nazgul Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch | -------------------------+-------------------------------------------------- Comment (by idle): In response to Ryan's comment: Because future upgrades will overwrite the modified files, '''unless''' you want to manually update your files. Adding new files to wp-includes or wp-admin is a whole different arm, however. Personally, I never delete my wp-includes directory, but keep my global functions in a file of its own inside that directory. Anyway, I like this patch. Nice work, Nazgul! -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 3 02:45:39 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 3 02:47:17 2006 Subject: [wp-trac] Re: [WordPress Trac] #3215: Login & Update functions everything is broken In-Reply-To: <049.6066b63c1044229dd67a636989ac05fd@lists.automattic.com> References: <049.6066b63c1044229dd67a636989ac05fd@lists.automattic.com> Message-ID: <058.f2c60cd72c1f7277107943882e3e512a@lists.automattic.com> #3215: Login & Update functions everything is broken --------------------------------------------+------------------------------- Reporter: Xmion | Owner: markjaquith Type: defect | Status: assigned Priority: highest | Milestone: 2.1 Component: General | Version: 2.1 Severity: critical | Resolution: Keywords: Blank page 302 maint-candidate | --------------------------------------------+------------------------------- Changes (by markjaquith): * status: new => assigned Comment: (In [4445]) possible solution for #3215 angelpb, ev3rywh3re, Xmion, Can you please try trunk revision 4445, with any workaround solutions removed? [http://wordpress.org/support/topic/67416?replies=9 This thread] lead me to believe that this might solve the problem. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 3 11:17:31 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 3 11:17:39 2006 Subject: [wp-trac] Re: [WordPress Trac] #2830: Change the way t he domain is being retrieved for sending e-mails from wordpress@.. In-Reply-To: <044.c2fd3680c97abffc7ec4d21317369a65@lists.automattic.com> References: <044.c2fd3680c97abffc7ec4d21317369a65@lists.automattic.com> Message-ID: <053.2175fe5377634931ce504d915ca7966c@lists.automattic.com> #2830: Change the way t he domain is being retrieved for sending e-mails from wordpress@.. -----------------------+---------------------------------------------------- Reporter: Woudloper | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.0.3 Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Changes (by tacker): * cc: tacker (added) Comment: There are many cases where the detected email address may be invalid, so please make this a configurable value. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 3 11:28:27 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 3 11:28:38 2006 Subject: [wp-trac] Re: [WordPress Trac] #2830: Change the way t he domain is being retrieved for sending e-mails from wordpress@.. In-Reply-To: <044.c2fd3680c97abffc7ec4d21317369a65@lists.automattic.com> References: <044.c2fd3680c97abffc7ec4d21317369a65@lists.automattic.com> Message-ID: <053.7eb0840cb06bd6e613c8cf3dc8b857c7@lists.automattic.com> #2830: Change the way t he domain is being retrieved for sending e-mails from wordpress@.. -----------------------+---------------------------------------------------- Reporter: Woudloper | Owner: westi Type: defect | Status: assigned Priority: normal | Milestone: 2.1 Component: General | Version: 2.0.3 Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Changes (by westi): * status: new => assigned * owner: anonymous => westi Comment: I don't think this needs to be a core feature. A very simple plugin (untested but should work fine) can be used to replace the builtin wp_mail function with one that sends from another address: {{{ /* Plugin Name: Override Email Address Description: Allows you to override the email address used by wp_mail Author: Peter Westwood Version: 0.01 Author URI: http://blog.ftwr.co.uk/ */ function wp_mail($to, $subject, $message, $headers = '') { if( $headers == '' ) { $headers = "MIME-Version: 1.0\n" . "From: user@domain \n" . "Content-Type: text/plain; charset=\"" . get_settings('blog_charset') . "\"\n"; } return @mail($to, $subject, $message, $headers); } }}} Replacing user@domain in the above plugin and activating it will allow you to pick the email address you want the emails to originate from. This plugin works because wp_mail is one of the pluggable functions that a plugin can override by defining it before WordPress -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 3 12:10:04 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 3 12:10:13 2006 Subject: [wp-trac] Re: [WordPress Trac] #2830: Change the way t he domain is being retrieved for sending e-mails from wordpress@.. In-Reply-To: <044.c2fd3680c97abffc7ec4d21317369a65@lists.automattic.com> References: <044.c2fd3680c97abffc7ec4d21317369a65@lists.automattic.com> Message-ID: <053.659d08d4ced08cd4b480937ccf68b42c@lists.automattic.com> #2830: Change the way t he domain is being retrieved for sending e-mails from wordpress@.. -----------------------+---------------------------------------------------- Reporter: Woudloper | Owner: westi Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: General | Version: 2.0.3 Severity: normal | Resolution: wontfix Keywords: | -----------------------+---------------------------------------------------- Changes (by Nazgul): * status: assigned => closed * resolution: => wontfix Comment: I agree with westi. I'd rather see this implemented as a plugin than cluttering the core with an option that only a small subset of the users will ever use. I've taken westi's example one step further and added a configuration page to it, so you can set the email adres from the admin section. (The largly untested statement still stands though) -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 3 19:43:19 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 3 19:43:29 2006 Subject: [wp-trac] Re: [WordPress Trac] #3315: Language files in wp-content In-Reply-To: <066.50df9fb2010b793418c774d1b660d7ff@lists.automattic.com> References: <066.50df9fb2010b793418c774d1b660d7ff@lists.automattic.com> Message-ID: <075.51242f665f53a36af892e8f2a0895eda@lists.automattic.com> #3315: Language files in wp-content -------------------------+-------------------------------------------------- Reporter: Nazgul | Owner: Nazgul Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch | -------------------------+-------------------------------------------------- Comment (by ryan): By why not I meant, +1. :-) -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 3 21:13:39 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 3 21:13:47 2006 Subject: [wp-trac] Re: [WordPress Trac] #3221:
Missing in user-edit.php In-Reply-To: <066.d1ed05d03e032fedd027205b17ca09b2@lists.automattic.com> References: <066.d1ed05d03e032fedd027205b17ca09b2@lists.automattic.com> Message-ID: <075.0b62073f8f69de695340872b15efb21f@lists.automattic.com> #3221:
Missing in user-edit.php ----------------------------+----------------------------------------------- Reporter: Xmion | Owner: Nazgul Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch | ----------------------------+----------------------------------------------- Changes (by Nazgul): * keywords: => has-patch * status: new => assigned * owner: anonymous => Nazgul Comment: Patch which adds the two missing
tags added. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 3 21:28:30 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 3 21:28:39 2006 Subject: [wp-trac] Re: [WordPress Trac] #3200: Saving empty bookmarks apears to work In-Reply-To: <066.64ecde99e0abd0018992946a2ba94c45@lists.automattic.com> References: <066.64ecde99e0abd0018992946a2ba94c45@lists.automattic.com> Message-ID: <075.d95df76ded3d8e217a252aee9104392c@lists.automattic.com> #3200: Saving empty bookmarks apears to work ----------------------------+----------------------------------------------- Reporter: Nazgul | Owner: Nazgul Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch | ----------------------------+----------------------------------------------- Changes (by Nazgul): * keywords: needs-patch => has-patch * status: new => assigned * owner: anonymous => Nazgul Comment: Attached post stops the "Link added." message from being shown, even though the link wasn't added, because the title wasn't specified. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 3 22:08:05 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 3 22:08:12 2006 Subject: [wp-trac] Re: [WordPress Trac] #2144: linking error numbers to reference In-Reply-To: <066.b1e55c8684602085edc3dfddee4c9190@lists.automattic.com> References: <066.b1e55c8684602085edc3dfddee4c9190@lists.automattic.com> Message-ID: <075.82a099f24fd2b9d30960448ad141bee2@lists.automattic.com> #2144: linking error numbers to reference ------------------------------+--------------------------------------------- Reporter: johnjosephbachir | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: General | Version: 2.0 Severity: normal | Resolution: wontfix Keywords: | ------------------------------+--------------------------------------------- Changes (by Nazgul): * status: new => closed * resolution: => wontfix Comment: Because it's only "developers and weekend hackers" that see mysql errors (and even they shouldn't be seeing them often), it's only a very small user group that would benefit from this addition. And for those power users it's easy enough to just copy and past the error to Google, if they don't know what it means already. Furthermore, we don't have any control whatsoever on the content on that site, so I'm not in favor of including links to it in core. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 4 01:18:33 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 4 01:18:41 2006 Subject: [wp-trac] Re: [WordPress Trac] #2372: References: <066.159f13dd046b2ff1d776a0c474e33a9d@lists.automattic.com> Message-ID: <075.380a7356035c0aedd585b6b72f9dc815@lists.automattic.com> #2372: reopened * version: 2.0 => 2.0.4 * resolution: worksforme => * milestone: 2.1 => 2.0.4 Comment: Happens to me and my contributors of my WP install. WP 2.0.4, Firefox 2.0. ''type'' {{{ }}} you get {{{ }}} -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 4 01:25:24 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 4 01:25:32 2006 Subject: [wp-trac] Re: [WordPress Trac] #2372: References: <066.159f13dd046b2ff1d776a0c474e33a9d@lists.automattic.com> Message-ID: <075.307a40e9332616afbece21a6ae7cf0bc@lists.automattic.com> #2372: * severity: major => minor * milestone: 2.0.4 => Comment: Replying to [comment:13 intellivision]: > Happens to me and my contributors of my WP install. WP 2.0.4, Firefox 2.0. > > ''type'' > > {{{ > > }}} > > > you get > > {{{ > > }}} -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 4 03:17:34 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 4 03:17:43 2006 Subject: [wp-trac] Re: [WordPress Trac] #2372: References: <066.159f13dd046b2ff1d776a0c474e33a9d@lists.automattic.com> Message-ID: <075.319f6690ad8e99c6ca10d9f57e1e8397@lists.automattic.com> #2372: closed * version: => 2.0.4 * resolution: => worksforme * milestone: => 2.1 Comment: 2.0.4 is old (please use the latest version) and the 2.0.x line will be seeing no more releases as far as I know. In 2.1, this is not an issue as there is no more HTML button. Closing, please don't reopen. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 4 05:13:00 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 4 05:13:06 2006 Subject: [wp-trac] Re: [WordPress Trac] #3315: Language files in wp-content In-Reply-To: <066.50df9fb2010b793418c774d1b660d7ff@lists.automattic.com> References: <066.50df9fb2010b793418c774d1b660d7ff@lists.automattic.com> Message-ID: <075.2936b737b85cb0e30a11f1a6944e0aae@lists.automattic.com> #3315: Language files in wp-content -------------------------+-------------------------------------------------- Reporter: Nazgul | Owner: Nazgul Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch | -------------------------+-------------------------------------------------- Comment (by markjaquith): Newer patch with more streamlined logic... no need to nest those ifs so deep. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 4 05:15:02 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 4 05:15:09 2006 Subject: [wp-trac] Re: [WordPress Trac] #2372: References: <066.159f13dd046b2ff1d776a0c474e33a9d@lists.automattic.com> Message-ID: <075.f52df881b39490baf4f79e743a4b6389@lists.automattic.com> #2372: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 4 08:29:23 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 4 08:29:31 2006 Subject: [wp-trac] Re: [WordPress Trac] #2372: References: <066.159f13dd046b2ff1d776a0c474e33a9d@lists.automattic.com> Message-ID: <075.364fb54e1879e4f752e9e6dcb87098cd@lists.automattic.com> #2372: 2.0.x still has life left in it. Oh, well ignore me then. :P -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 4 11:37:33 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 4 11:37:40 2006 Subject: [wp-trac] [WordPress Trac] #3327: Reorganizing language files and functions Message-ID: <066.57bdc4c4e46e671eefee35931331d484@lists.automattic.com> #3327: Reorganizing language files and functions -------------------------+-------------------------------------------------- Reporter: pandem | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Keywords: i18n has-patch -------------------------+-------------------------------------------------- Just to take advantage of the changes proposed in #3315, it could be a good idea to centralize all language files in one folder. I'd do the same with TinyMCE js files if possible as this would be a great improvement for us translators, but it'd probably be a hassle for coders. I know i18n of themes is not encouraged but, as the use of WordPress as CMS increases, also does the i18nalizing needs, therefore my proposal. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 4 20:37:17 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 4 20:37:24 2006 Subject: [wp-trac] [WordPress Trac] #3328: wp_specialchars mishandles /&&/ and /&$/ Message-ID: <066.7b8c140fbfd82bbca466ee44f146fe55@lists.automattic.com> #3328: wp_specialchars mishandles /&&/ and /&$/ ----------------------------+----------------------------------------------- Reporter: andy | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.5 Severity: normal | Keywords: ----------------------------+----------------------------------------------- wp_specialchars('&& ') == '&& ' wp_specialchars(' &') == ' &' -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 4 20:41:06 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 4 20:41:14 2006 Subject: [wp-trac] [WordPress Trac] #3329: Url wrong generated if topic has % symbol Message-ID: <066.b7e23c8b480b568472d36eb8b48f2182@lists.automattic.com> #3329: Url wrong generated if topic has % symbol ----------------------------+----------------------------------------------- Reporter: Heyneken | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: 2.0.4 Severity: normal | Keywords: ----------------------------+----------------------------------------------- I made an article with "x = 18,98 * y - %10" as title, and this generated http://www.example.com/blog/2006/11/03/x-1898-y-%10/ which doesn't work. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 00:41:34 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 00:41:42 2006 Subject: [wp-trac] [WordPress Trac] #3330: tinymce spell checker does not work when php server reports all errors Message-ID: <066.21e926a39d3818220574eff72d002d30@lists.automattic.com> #3330: tinymce spell checker does not work when php server reports all errors ----------------------------+----------------------------------------------- Reporter: ovgray | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Keywords: tinymce ----------------------------+----------------------------------------------- In testing with a server that has error reporting turned up to max to include Notices, I got "Could not execute AJAX call, server didn't return valid a xml" errors when clicking the spell check button. I found this problem discussed at == http://tinymce.moxiecode.com/punbb/viewtopic.php?id=3383 == The changes to tinyspell.php described by 'sbirtwistle' near the end of that thread solve this problem. I assume that a version of tinymce more recent than what's in wp2.1 (and wpmu 1.0) will pick up those amendments, but if they were applied in wp2.1 in the meantime it would solve this problem for any others experiencing it. -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 01:20:36 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 01:20:43 2006 Subject: [wp-trac] [WordPress Trac] #3331: Interoperability -- Trackback does not work with MSN Spaces Message-ID: <066.50a285f563a7dae8a605031a3b227878@lists.automattic.com> #3331: Interoperability -- Trackback does not work with MSN Spaces -------------------------+-------------------------------------------------- Reporter: nobrain2000 | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: XML-RPC | Version: 2.0.4 Severity: normal | Keywords: MSN trackback -------------------------+-------------------------------------------------- If you have MSN Space ping a permanent link of a WP blog, the ping is ignored by WP. The other way (WP ping MSN Space permanent link) works fine. I did some investigation of this problem. There are two problems that prevents WP from processing trackback pings from MSN. 1. MSN does not seem to conform to the trackback protocol. Specifically, it does not POST the title field, which is required by WordPress. While does sounds like an MSN Space problem, the embarassing fact is that all other blogging software, including Typepad and MT, works with MSN just fine. Below is my workaround: In wp-trackback.php, add the following: 
 if(empty($title)){
     $title=$excerpt;
     if(preg_match("/spaces\.live\.com/i",$tb_url))
     {
       $excerpt="";

     }
 }
 if(empty($title)) $title="No title";
Now that you added the above code, you will see the trackback entry in your blog, but the URL (to the MSN Space permanent link) is wrong. This is because of the second problem. See below: 2. WP removes all the !'s in URLs, and MSN permanent link URLs have !'s in them. I worked around this by chainging clean_url() in comment-functions.php so that it does not remove ! from URLs. Below is the code: 
 function clean_url( $url ) {
    if ('' == $url) return $url;
    #note ! is added to the regexp below.
    $url = preg_replace('|[^a-z0-9-~+_.?#=!&;,/:]|i', '', $url);
    $url = str_replace(';//', '://', $url);
    $url = (!strstr($url, '://')) ? 'http://'.$url : $url;
    $url = preg_replace('/&([^#])(?![a-z]{2,8};)/', '&$1', $url);
    return $url;
 }
-- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 02:21:23 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 02:21:28 2006 Subject: [wp-trac] [WordPress Trac] #3332: Delete comment broken Message-ID: <066.6a33d5e1beeb0311159a55075ae27f4b@lists.automattic.com> #3332: Delete comment broken ----------------------------+----------------------------------------------- Reporter: tinyau | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: major | Keywords: ----------------------------+----------------------------------------------- Revision: 4448 Whenever I tried to delete a comment, the following message is shown. '''Oops, no comment with this ID. Go back! -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 05:58:58 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 05:59:06 2006 Subject: [wp-trac] Re: [WordPress Trac] #3331: Interoperability -- Trackback does not work with MSN Spaces In-Reply-To: <066.50a285f563a7dae8a605031a3b227878@lists.automattic.com> References: <066.50a285f563a7dae8a605031a3b227878@lists.automattic.com> Message-ID: <075.3a1b61ccbea2a2a27ef0f7fcd396b1b3@lists.automattic.com> #3331: Interoperability -- Trackback does not work with MSN Spaces ---------------------------+------------------------------------------------ Reporter: nobrain2000 | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: XML-RPC | Version: 2.0.4 Severity: normal | Resolution: Keywords: MSN trackback | ---------------------------+------------------------------------------------ Old description: > If you have MSN Space ping a permanent link of a WP blog, the ping is > ignored by WP. The other way (WP ping MSN Space permanent link) works > fine. > > I did some investigation of this problem. There are two problems that > prevents WP from processing trackback pings from MSN. > > 1. MSN does not seem to conform to the trackback protocol. Specifically, > it does not POST the title field, which is required by WordPress. While > does sounds like an MSN Space problem, the embarassing fact is that all > other blogging software, including Typepad and MT, works with MSN just > fine. > > Below is my workaround: > > In wp-trackback.php, add the following: > 
> if(empty($title)){
>     $title=$excerpt;
>     if(preg_match("/spaces\.live\.com/i",$tb_url))
>     {
>       $excerpt="";
>
>     }
> }
> if(empty($title)) $title="No title";
>
> > Now that you added the above code, you will see the trackback entry in > your blog, but the URL (to the MSN Space permanent link) is wrong. This > is because of the second problem. See below: > > 2. WP removes all the !'s in URLs, and MSN permanent link URLs have !'s > in them. > > I worked around this by chainging clean_url() in comment-functions.php so > that it does not remove ! from URLs. Below is the code: > > 
> function clean_url( $url ) {
>    if ('' == $url) return $url;
>    #note ! is added to the regexp below.
>    $url = preg_replace('|[^a-z0-9-~+_.?#=!&;,/:]|i', '', $url);
>    $url = str_replace(';//', '://', $url);
>    $url = (!strstr($url, '://')) ? 'http://'.$url : $url;
>    $url = preg_replace('/&([^#])(?![a-z]{2,8};)/', '&$1', $url);
>    return $url;
> }
>
New description: If you have MSN Space ping a permanent link of a WP blog, the ping is ignored by WP. The other way (WP ping MSN Space permanent link) works fine. I did some investigation of this problem. There are two problems that prevents WP from processing trackback pings from MSN. 1. MSN does not seem to conform to the trackback protocol. Specifically, it does not POST the title field, which is required by WordPress. While does sounds like an MSN Space problem, the embarassing fact is that all other blogging software, including Typepad and MT, works with MSN just fine. Below is my workaround: In wp-trackback.php, add the following: {{{ if(empty($title)){ $title=$excerpt; if(preg_match("/spaces\.live\.com/i",$tb_url)) { $excerpt=""; } } if(empty($title)) $title="No title"; }}} Now that you added the above code, you will see the trackback entry in your blog, but the URL (to the MSN Space permanent link) is wrong. This is because of the second problem. See below: 2. WP removes all the !'s in URLs, and MSN permanent link URLs have !'s in them. I worked around this by chainging clean_url() in comment-functions.php so that it does not remove ! from URLs. Below is the code: {{{ function clean_url( $url ) { if ('' == $url) return $url; #note ! is added to the regexp below. $url = preg_replace('|[^a-z0-9-~+_.?#=!&;,/:]|i', '', $url); $url = str_replace(';//', '://', $url); $url = (!strstr($url, '://')) ? 'http://'.$url : $url; $url = preg_replace('/&([^#])(?![a-z]{2,8};)/', '&$1', $url); return $url; } }}} Comment (by markjaquith): Just updating the code wrapping to work with WikiFormatting -- Ticket URL: WordPress Trac WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 06:10:58 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 06:11:05 2006 Subject: [wp-trac] Re: [WordPress Trac] #3331: Interoperability -- Trackback does not work with MSN Spaces In-Reply-To: <066.50a285f563a7dae8a605031a3b227878@lists.automattic.com> References: <066.50a285f563a7dae8a605031a3b227878@lists.automattic.com> Message-ID: <075.a6e2966fc4ffe3488b9e4a0ed89dd8fa@lists.automattic.com> #3331: Interoperability -- Trackback does not work with MSN Spaces ---------------------------+------------------------------------------------ Reporter: nobrain2000 | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: XML-RPC | Version: 2.0.4 Severity: normal | Resolution: Keywords: MSN trackback | ---------------------------+------------------------------------------------ Comment (by markjaquith): The [http://www.sixapart.com/pronet/docs/trackback_spec Trackback technical specification] says that {{{title}}} is optional... so that should be fixed (generally... not just with MSN-specific code). I don't think that there was a specific reason for filtering ! out (it was probably just forgotten, since it works with a list of ''allowed'' characters), so unless anyone objects, that should go in, too. The only thing I'm not sure about is what to use at the title if the trackback title is omitted. If we leave it blank, the templates will show a blank hyperlink. We could visit the URL and extract the {{{}}} ... -- Ticket URL: <http://trac.wordpress.org/ticket/3331#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 06:11:41 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 06:11:47 2006 Subject: [wp-trac] Re: [WordPress Trac] #3331: Interoperability -- Trackback does not work with MSN Spaces In-Reply-To: <066.50a285f563a7dae8a605031a3b227878@lists.automattic.com> References: <066.50a285f563a7dae8a605031a3b227878@lists.automattic.com> Message-ID: <075.39b5391fe99a0cd0cb32055ea6274b9a@lists.automattic.com> #3331: Interoperability -- Trackback does not work with MSN Spaces ---------------------------+------------------------------------------------ Reporter: nobrain2000 | Owner: markjaquith Type: defect | Status: assigned Priority: normal | Milestone: 2.1 Component: XML-RPC | Version: 2.0.4 Severity: normal | Resolution: Keywords: MSN trackback | ---------------------------+------------------------------------------------ Changes (by markjaquith): * status: new => assigned * owner: anonymous => markjaquith * milestone: => 2.1 -- Ticket URL: <http://trac.wordpress.org/ticket/3331#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 06:13:17 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 06:13:23 2006 Subject: [wp-trac] Re: [WordPress Trac] #3332: Delete comment broken In-Reply-To: <066.6a33d5e1beeb0311159a55075ae27f4b@lists.automattic.com> References: <066.6a33d5e1beeb0311159a55075ae27f4b@lists.automattic.com> Message-ID: <075.144472432a4ac792598fc3d8870c08b1@lists.automattic.com> #3332: Delete comment broken ----------------------------+----------------------------------------------- Reporter: tinyau | Owner: markjaquith Type: defect | Status: assigned Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: major | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by markjaquith): * status: new => assigned * owner: anonymous => markjaquith Comment: Need more information. There are about 5 different places you can delete a comment. What URL? JS on or off? -- Ticket URL: <http://trac.wordpress.org/ticket/3332#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 07:21:44 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 07:21:51 2006 Subject: [wp-trac] Re: [WordPress Trac] #3332: Delete comment broken In-Reply-To: <066.6a33d5e1beeb0311159a55075ae27f4b@lists.automattic.com> References: <066.6a33d5e1beeb0311159a55075ae27f4b@lists.automattic.com> Message-ID: <075.afa49a108ee084850d799622245ff2a2@lists.automattic.com> #3332: Delete comment broken ----------------------------+----------------------------------------------- Reporter: tinyau | Owner: markjaquith Type: defect | Status: assigned Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: major | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by tinyau): Inside "Manage" -> "Comments" -- Ticket URL: <http://trac.wordpress.org/ticket/3332#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 07:31:01 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 07:31:08 2006 Subject: [wp-trac] Re: [WordPress Trac] #3332: Delete comment broken In-Reply-To: <066.6a33d5e1beeb0311159a55075ae27f4b@lists.automattic.com> References: <066.6a33d5e1beeb0311159a55075ae27f4b@lists.automattic.com> Message-ID: <075.bad12b08229662e5299c8d818f07b9e2@lists.automattic.com> #3332: Delete comment broken ----------------------------+----------------------------------------------- Reporter: tinyau | Owner: markjaquith Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: major | Resolution: worksforme Keywords: | ----------------------------+----------------------------------------------- Changes (by markjaquith): * status: assigned => closed * resolution: => worksforme Comment: Works for me on revision 4448, both with and without JavaScript. 1. Click "Manage" 2. Click "Comments" 3. Click "Delete" next to a comment 4. Click "Manage" 5. Click "Comments" 6. Verify that deleted comment is no longer in the list -- Ticket URL: <http://trac.wordpress.org/ticket/3332#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 07:32:10 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 07:32:16 2006 Subject: [wp-trac] Re: [WordPress Trac] #3332: Delete comment broken In-Reply-To: <066.6a33d5e1beeb0311159a55075ae27f4b@lists.automattic.com> References: <066.6a33d5e1beeb0311159a55075ae27f4b@lists.automattic.com> Message-ID: <075.769413cf3f148e5c01ff3ff6d5da8dbd@lists.automattic.com> #3332: Delete comment broken ----------------------------+----------------------------------------------- Reporter: tinyau | Owner: markjaquith Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: major | Resolution: worksforme Keywords: | ----------------------------+----------------------------------------------- Comment (by markjaquith): Grr, I hate this Wiki syntax 1. Click "Manage" 1. Click "Comments" 1. Click "Delete" next to a comment 1. Click "Manage" 1. Click "Comments" 1. Verify that deleted comment is no longer in the list -- Ticket URL: <http://trac.wordpress.org/ticket/3332#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 08:13:25 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 08:13:31 2006 Subject: [wp-trac] Re: [WordPress Trac] #3213: Option sub-menus disappear off the screen to the right In-Reply-To: <066.2d844f695782d1e9e54289c80f7c0a0a@lists.automattic.com> References: <066.2d844f695782d1e9e54289c80f7c0a0a@lists.automattic.com> Message-ID: <075.e791264ca343f2ac8e076731ba88e73c@lists.automattic.com> #3213: Option sub-menus disappear off the screen to the right ------------------------------------+--------------------------------------- Reporter: filosofo | Owner: markjaquith Type: defect | Status: new Priority: highest | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: blocker | Resolution: Keywords: has-patch css sub-menu | ------------------------------------+--------------------------------------- Changes (by Viper007Bond): * owner: anonymous => markjaquith -- Ticket URL: <http://trac.wordpress.org/ticket/3213#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 08:12:53 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 08:15:00 2006 Subject: [wp-trac] Re: [WordPress Trac] #3213: Option sub-menus disappear off the screen to the right In-Reply-To: <066.2d844f695782d1e9e54289c80f7c0a0a@lists.automattic.com> References: <066.2d844f695782d1e9e54289c80f7c0a0a@lists.automattic.com> Message-ID: <075.8c8f0844fa00d3b46c0d41fa3f270898@lists.automattic.com> #3213: Option sub-menus disappear off the screen to the right ------------------------------------+--------------------------------------- Reporter: filosofo | Owner: anonymous Type: defect | Status: new Priority: highest | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: blocker | Resolution: Keywords: has-patch css sub-menu | ------------------------------------+--------------------------------------- Changes (by Viper007Bond): * priority: normal => highest * severity: normal => blocker Comment: This is major and needs to be fixed ASAP. We can't release 2.1 without fixing this. -- Ticket URL: <http://trac.wordpress.org/ticket/3213#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 08:14:59 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 08:15:07 2006 Subject: [wp-trac] [WordPress Trac] #3333: wp-admin/upload.php?action=edit shows strange screen Message-ID: <066.40d9398d87f24d35dad239c009854e5e@lists.automattic.com> #3333: wp-admin/upload.php?action=edit shows strange screen ----------------------------+----------------------------------------------- Reporter: markjaquith | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Keywords: ----------------------------+----------------------------------------------- {{{ wp-admin/upload.php?action=edit }}} Shows a strange screen... not sure if there are any security issues. -- Ticket URL: <http://trac.wordpress.org/ticket/3333> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 08:36:44 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 08:36:52 2006 Subject: [wp-trac] Re: [WordPress Trac] #3149: The underlined menu items looks ugly In-Reply-To: <066.b35f93053449fdd178aedf5f32f492e6@lists.automattic.com> References: <066.b35f93053449fdd178aedf5f32f492e6@lists.automattic.com> Message-ID: <075.fee52f35e552b555592211a8a1ddbd37@lists.automattic.com> #3149: The underlined menu items looks ugly ----------------------------------+----------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: fixed Keywords: admin menu has-patch | ----------------------------------+----------------------------------------- Changes (by markjaquith): * status: new => closed * resolution: => fixed Comment: (In [4449]) Allow submenu tabs to wrap. Props filosofo. fixes #3213 this bug was also fixed by [4449]... such is the mystery of CSS. -- Ticket URL: <http://trac.wordpress.org/ticket/3149#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 08:44:38 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 08:44:46 2006 Subject: [wp-trac] Re: [WordPress Trac] #3213: Option sub-menus disappear off the screen to the right In-Reply-To: <066.2d844f695782d1e9e54289c80f7c0a0a@lists.automattic.com> References: <066.2d844f695782d1e9e54289c80f7c0a0a@lists.automattic.com> Message-ID: <075.75543ce05afc9c88bce1232ac83afb48@lists.automattic.com> #3213: Option sub-menus disappear off the screen to the right ------------------------------------+--------------------------------------- Reporter: filosofo | Owner: markjaquith Type: defect | Status: closed Priority: highest | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: blocker | Resolution: fixed Keywords: has-patch css sub-menu | ------------------------------------+--------------------------------------- Comment (by Viper007Bond): lol, that was quick. Mark is the man. 8) -- Ticket URL: <http://trac.wordpress.org/ticket/3213#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 09:48:45 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 09:48:53 2006 Subject: [wp-trac] Re: [WordPress Trac] #3332: Delete comment broken In-Reply-To: <066.6a33d5e1beeb0311159a55075ae27f4b@lists.automattic.com> References: <066.6a33d5e1beeb0311159a55075ae27f4b@lists.automattic.com> Message-ID: <075.e8c00a6535724db8fea6477590e624a6@lists.automattic.com> #3332: Delete comment broken ----------------------------+----------------------------------------------- Reporter: tinyau | Owner: markjaquith Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: major | Resolution: worksforme Keywords: | ----------------------------+----------------------------------------------- Comment (by tinyau): Sorry Mark, the problem was caused by Paged Comment Edit plugin. Please keep the ticket closed. -- Ticket URL: <http://trac.wordpress.org/ticket/3332#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 09:51:00 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 09:51:06 2006 Subject: [wp-trac] Re: [WordPress Trac] #3333: wp-admin/upload.php?action=edit shows strange screen In-Reply-To: <066.40d9398d87f24d35dad239c009854e5e@lists.automattic.com> References: <066.40d9398d87f24d35dad239c009854e5e@lists.automattic.com> Message-ID: <075.ca379ec579d546507610192078dc7b9e@lists.automattic.com> #3333: wp-admin/upload.php?action=edit shows strange screen ----------------------------+----------------------------------------------- Reporter: markjaquith | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by westi): That looks like it could be a useful screen with a bit of pretification. Some way of easying editing the uploaded images/files information. The whole page is protected by the ''upload_files'' cap so it should be sage security wise (http://trac.wordpress.org/browser/trunk/wp- admin/upload.php#L6) -- Ticket URL: <http://trac.wordpress.org/ticket/3333#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 15:07:14 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 15:07:33 2006 Subject: [wp-trac] Re: [WordPress Trac] #3333: wp-admin/upload.php?action=edit shows strange screen In-Reply-To: <066.40d9398d87f24d35dad239c009854e5e@lists.automattic.com> References: <066.40d9398d87f24d35dad239c009854e5e@lists.automattic.com> Message-ID: <075.cbde68841144c8c7a20a570b199d8d79@lists.automattic.com> #3333: wp-admin/upload.php?action=edit shows strange screen ----------------------------+----------------------------------------------- Reporter: markjaquith | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by markjaquith): The things I'm seeing there aren't files... they're regular posts! -- Ticket URL: <http://trac.wordpress.org/ticket/3333#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 15:10:32 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 15:10:48 2006 Subject: [wp-trac] Re: [WordPress Trac] #3333: wp-admin/upload.php?action=edit shows strange screen In-Reply-To: <066.40d9398d87f24d35dad239c009854e5e@lists.automattic.com> References: <066.40d9398d87f24d35dad239c009854e5e@lists.automattic.com> Message-ID: <075.1534b617ffc8c2bcdcc81bb863e90c14@lists.automattic.com> #3333: wp-admin/upload.php?action=edit shows strange screen ----------------------------+----------------------------------------------- Reporter: markjaquith | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by westi): Replying to [comment:2 markjaquith]: > The things I'm seeing there aren't files... they're regular posts! So they are! I should look at the junk in my trunk install more carefully - I assumed I was looking at files :-( -- Ticket URL: <http://trac.wordpress.org/ticket/3333#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 17:23:49 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 17:23:59 2006 Subject: [wp-trac] Re: [WordPress Trac] #2316: Custom Fields disappearing and "_encloseme" and "_pingme" entries in the database over and over In-Reply-To: <066.853257d53007395a6cf8ecd0d71d4031@lists.automattic.com> References: <066.853257d53007395a6cf8ecd0d71d4031@lists.automattic.com> Message-ID: <075.e951b14f65a3af838016d1d6bcddf186@lists.automattic.com> #2316: Custom Fields disappearing and "_encloseme" and "_pingme" entries in the database over and over --------------------------------------------------------------------------------------------+ Reporter: cnc137 | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: 2.0 Severity: normal | Resolution: Keywords: bg|reporter-feedback custom fields encloseme pingme disappear hidden has-patch | --------------------------------------------------------------------------------------------+ Changes (by tenpura): * keywords: bg|reporter-feedback custom fields encloseme pingme disappear hidden => bg|reporter-feedback custom fields encloseme pingme disappear hidden has-patch -- Ticket URL: <http://trac.wordpress.org/ticket/2316#comment:10> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 17:29:38 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 17:29:53 2006 Subject: [wp-trac] Re: [WordPress Trac] #2316: Custom Fields disappearing and "_encloseme" and "_pingme" entries in the database over and over In-Reply-To: <066.853257d53007395a6cf8ecd0d71d4031@lists.automattic.com> References: <066.853257d53007395a6cf8ecd0d71d4031@lists.automattic.com> Message-ID: <075.c6af933789793aa1a71dfd33126ee3c9@lists.automattic.com> #2316: Custom Fields disappearing and "_encloseme" and "_pingme" entries in the database over and over --------------------------------------------------------------------------------------------+ Reporter: cnc137 | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.5 Severity: normal | Resolution: Keywords: bg|reporter-feedback custom fields encloseme pingme disappear hidden has-patch | --------------------------------------------------------------------------------------------+ Changes (by tenpura): * version: 2.0 => 2.0.5 * milestone: => 2.1 -- Ticket URL: <http://trac.wordpress.org/ticket/2316#comment:11> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 18:07:16 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 19:26:17 2006 Subject: [wp-trac] Re: [WordPress Trac] #2478: the_meta() doesn't hide hidden meta keys In-Reply-To: <066.980cdf0ce85b8456dcfd863255763621@lists.automattic.com> References: <066.980cdf0ce85b8456dcfd863255763621@lists.automattic.com> Message-ID: <075.d4a3b79ab2b25921e981cce716c8b632@lists.automattic.com> #2478: the_meta() doesn't hide hidden meta keys ------------------------------+--------------------------------------------- Reporter: MattRead | Owner: markjaquith Type: defect | Status: closed Priority: low | Milestone: 2.0.5 Component: Template | Version: 2.0.1 Severity: trivial | Resolution: fixed Keywords: commit has-patch | ------------------------------+--------------------------------------------- Comment (by tenpura): This should be fixed too.[[BR]] http://trac.wordpress.org/attachment/ticket/2316/2316.diff -- Ticket URL: <http://trac.wordpress.org/ticket/2478#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 20:18:16 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 20:18:26 2006 Subject: [wp-trac] Re: [WordPress Trac] #3329: %postname% permalink wrong generated if title has %[digit][digit] In-Reply-To: <066.b7e23c8b480b568472d36eb8b48f2182@lists.automattic.com> References: <066.b7e23c8b480b568472d36eb8b48f2182@lists.automattic.com> Message-ID: <075.790a535e662571397db0f36b6092578a@lists.automattic.com> #3329: %postname% permalink wrong generated if title has %[digit][digit] ----------------------------+----------------------------------------------- Reporter: Heyneken | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.5 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by foolswisdom): * summary: Url wrong generated if topic has % symbol => %postname% permalink wrong generated if title has %[digit][digit] * version: 2.0.4 => 2.0.5 * milestone: => 2.1 Comment: Heyneken thank you for reporting this problem! Thank you for participating in WordPress development! ENV: WP 2.0.5 reproduced problem [[br]] Also WP trunk r4449 repro problem The bug seems to be caused if the percentage symbol followed by two or more digits. -- Ticket URL: <http://trac.wordpress.org/ticket/3329#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 21:43:09 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 21:43:18 2006 Subject: [wp-trac] Re: [WordPress Trac] #3306: saving post takes me to the wrong page In-Reply-To: <066.e9d5ff8f3d152b5414ae752f89cb6343@lists.automattic.com> References: <066.e9d5ff8f3d152b5414ae752f89cb6343@lists.automattic.com> Message-ID: <075.4df7d083dd72aa24219571dc8df6f8a3@lists.automattic.com> #3306: saving post takes me to the wrong page ----------------------------+----------------------------------------------- Reporter: lschiere | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by lschiere): Is any additional information needed here? -- Ticket URL: <http://trac.wordpress.org/ticket/3306#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 23:11:54 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 23:12:02 2006 Subject: [wp-trac] Re: [WordPress Trac] #1336: Blockquote button inserts extra newlines In-Reply-To: <066.406ef20378843c7d3678d8504815d19b@lists.automattic.com> References: <066.406ef20378843c7d3678d8504815d19b@lists.automattic.com> Message-ID: <075.392463ec37987b128e1422e9d8d7779b@lists.automattic.com> #1336: Blockquote button inserts extra newlines -----------------------------+---------------------------------------------- Reporter: anonymousbugger | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Administration | Version: 1.5.1 Severity: minor | Resolution: invalid Keywords: | -----------------------------+---------------------------------------------- Changes (by foolswisdom): * status: new => closed * resolution: => invalid Comment: Closing INVALID, assuming this was done on purpose and no update to the ticket in a year. ENV: WP trunk r4449 Behavior as described. -- Ticket URL: <http://trac.wordpress.org/ticket/1336#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 6 23:45:10 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 6 23:45:20 2006 Subject: [wp-trac] Re: [WordPress Trac] #1337: Timestamps in notification emails and rss-feeds are in wrong In-Reply-To: <066.95e25c01a082fd52318a07337391d33b@lists.automattic.com> References: <066.95e25c01a082fd52318a07337391d33b@lists.automattic.com> Message-ID: <075.8e668258b315e51748d514dd4ac8ae91@lists.automattic.com> #1337: Timestamps in notification emails and rss-feeds are in wrong -----------------------------+---------------------------------------------- Reporter: anonymousbugger | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Administration | Version: 1.5.1 Severity: minor | Resolution: wontfix Keywords: | -----------------------------+---------------------------------------------- Changes (by foolswisdom): * status: new => closed * resolution: => wontfix Comment: Closing WONTFIX, no update in a year. ENV: WP trunk r4427 Although the time in WordPress' admin on my hosted server shows UTC, the email it sends are for my "-0800 (PST)". This suggests to that the notification emails are configured "below WordPress". Possibly, this can be influenced by a parameter to the PHP mail functionality used... -- Ticket URL: <http://trac.wordpress.org/ticket/1337#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 7 00:00:22 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 7 00:00:31 2006 Subject: [wp-trac] Re: [WordPress Trac] #1340: why even admin does not see all private posts In-Reply-To: <066.f56ca73a7cf11da250ed639ffb092d4f@lists.automattic.com> References: <066.f56ca73a7cf11da250ed639ffb092d4f@lists.automattic.com> Message-ID: <075.05f9b1e1a066760b4cb0d17bd692dd01@lists.automattic.com> #1340: why even admin does not see all private posts -----------------------------+---------------------------------------------- Reporter: anonymousbugger | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: Component: Security | Version: 1.5.1 Severity: normal | Resolution: worksforme Keywords: | -----------------------------+---------------------------------------------- Changes (by foolswisdom): * status: new => closed * resolution: => worksforme Comment: Closing bug as WORKSFORME ENV: WP trunk r4449 I am not sure what role "level 1 or higher" means, but I tried a number of tests and admin can see both other people's drafts and other people's private posts in the manage tab. -- Ticket URL: <http://trac.wordpress.org/ticket/1340#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 7 00:02:16 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 7 00:02:22 2006 Subject: [wp-trac] [WordPress Trac] #3334: Ajax Tweaks for plugins Message-ID: <066.5fdb7beeefa96f3391f3d0eb44c581ca@lists.automattic.com> #3334: Ajax Tweaks for plugins ----------------------------+----------------------------------------------- Reporter: mdawaffe | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Keywords: listman ajax js has-patch 2nd-opinion needs-testing ----------------------------+----------------------------------------------- Attached 1. Fixes bug in WP_Ajax_Response PHP class 1. WPAjax (JS class) uses /wp-admin/admin-ajax.php by default (which plugins can already easily hook into). 1. List Manipulation could throw errors when AJAX updating (not when AJAX adding) under some very strange situations. No Longer (or at least, the situations under which it throws errors are now even stranger). Version numbers in script-loader.php need to be changed. -- Ticket URL: <http://trac.wordpress.org/ticket/3334> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 7 02:24:56 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 7 02:25:04 2006 Subject: [wp-trac] [WordPress Trac] #3335: Add condition function(s) for page templates Message-ID: <066.2266ddd7729bef57206685c7173ac88f@lists.automattic.com> #3335: Add condition function(s) for page templates ----------------------------+----------------------------------------------- Reporter: jimisola | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: minor | Keywords: ----------------------------+----------------------------------------------- There does not exist a condition function for Page Templates like there is for Page etc (see http://codex.wordpress.org/Conditional_Tags). Not only me seem to be missing this functionality: http://wordpress.org/support/topic/55378?replies=5 -- Ticket URL: <http://trac.wordpress.org/ticket/3335> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 7 12:18:14 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 7 12:18:22 2006 Subject: [wp-trac] [WordPress Trac] #3336: Change administration submenu link's colors and/or background colors Message-ID: <066.a4b77555d70231af2b5cce9b94b04f95@lists.automattic.com> #3336: Change administration submenu link's colors and/or background colors ----------------------------+----------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Keywords: administration, menu, submenu, bar ----------------------------+----------------------------------------------- There's a problem with colors of links in the submenu. If we have only a row of submenus, these are lighter on a darker blue stripe. But if our submenus are too much, they go a row below in the bottom light- backgrounded page. So: light link, light backgorund, we lose submenus until rollover with mouse on them. Should be solved with dark background for the container element. -- Ticket URL: <http://trac.wordpress.org/ticket/3336> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 7 20:53:33 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 7 20:57:32 2006 Subject: [wp-trac] Re: [WordPress Trac] #3336: Change administration submenu link's colors and/or background colors In-Reply-To: <066.a4b77555d70231af2b5cce9b94b04f95@lists.automattic.com> References: <066.a4b77555d70231af2b5cce9b94b04f95@lists.automattic.com> Message-ID: <075.2fd12946b16bb3fa7d1dbbe4d3233ee0@lists.automattic.com> #3336: Change administration submenu link's colors and/or background colors ------------------------------------------------+--------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: worksforme Keywords: administration, menu, submenu, bar | ------------------------------------------------+--------------------------- Changes (by markjaquith): * status: new => closed * resolution: => worksforme Comment: Cannot reproduce in latest trunk with FF 2.0 I get this: [[Image(http://img501.imageshack.us/img501/7711/submenuoverflowzu5.png)]] Looks fine to me. Re-open if you can reproduce on latest trunk. Please provide browser information as well. -- Ticket URL: <http://trac.wordpress.org/ticket/3336#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 7 22:16:04 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 7 22:16:14 2006 Subject: [wp-trac] Re: [WordPress Trac] #2713: patch wptexturize to leave text inside (code|pre|kbd|style|script|samp) tags alone In-Reply-To: <066.689c8d87cd7a695bde688075ab3ff605@lists.automattic.com> References: <066.689c8d87cd7a695bde688075ab3ff605@lists.automattic.com> Message-ID: <075.5fd39353244827799f01fb5bbc5a42d8@lists.automattic.com> #2713: patch wptexturize to leave text inside (code|pre|kbd|style|script|samp) tags alone ----------------------+----------------------------------------------------- Reporter: n8v | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Template | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by n8v): I reapplied this patch to my WordPress 2.1-alpha3 release (from the Subversion trunk) but I guess it should apply to 'wp- includes/formatting.php' now, instead of functions-formatting.php as the diff suggests. This is the Unix syntax to apply the patch: {{{ cd wp-includes patch formatting.php detexturize_patch.diff }}} -- Ticket URL: <http://trac.wordpress.org/ticket/2713#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 7 23:18:45 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 7 23:18:53 2006 Subject: [wp-trac] Re: [WordPress Trac] #3255: _encloseme: 1 _pingme: 1 In-Reply-To: <066.c6746271cec066919b7111cfb5505f62@lists.automattic.com> References: <066.c6746271cec066919b7111cfb5505f62@lists.automattic.com> Message-ID: <075.b6593f928d313d4d41087d88734a0f4b@lists.automattic.com> #3255: _encloseme: 1 _pingme: 1 ----------------------------+----------------------------------------------- Reporter: DebbieAC | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Administration | Version: 2.0.4 Severity: normal | Resolution: duplicate Keywords: | ----------------------------+----------------------------------------------- Changes (by foolswisdom): * status: new => closed * resolution: => duplicate Comment: No response to my questions. Closing as duplicate of #2478. -- Ticket URL: <http://trac.wordpress.org/ticket/3255#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 7 23:50:28 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 7 23:50:36 2006 Subject: [wp-trac] Re: [WordPress Trac] #3260: XML output (rss, atom, rdf ...) should always use UTF-8 or CDATA for user input In-Reply-To: <066.ce06a8b0981127974cd65852b312d721@lists.automattic.com> References: <066.ce06a8b0981127974cd65852b312d721@lists.automattic.com> Message-ID: <075.506c0e8355b11c4ab0b14d94a318ef4f@lists.automattic.com> #3260: XML output (rss, atom, rdf ...) should always use UTF-8 or CDATA for user input --------------------------+------------------------------------------------- Reporter: deremder | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Optimization | Version: 2.0.4 Severity: normal | Resolution: Keywords: | --------------------------+------------------------------------------------- Comment (by foolswisdom): #3252 seems to deal with the category element. -- Ticket URL: <http://trac.wordpress.org/ticket/3260#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 7 23:51:02 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 7 23:51:13 2006 Subject: [wp-trac] Re: [WordPress Trac] #3252: Wrap Category Name in CDATA In-Reply-To: <066.8111890881153313108403607ea04c6c@lists.automattic.com> References: <066.8111890881153313108403607ea04c6c@lists.automattic.com> Message-ID: <075.104c4d0b543e9436b19d005b9a3e4c2a@lists.automattic.com> #3252: Wrap Category Name in CDATA -------------------------+-------------------------------------------------- Reporter: alexkingorg | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch | -------------------------+-------------------------------------------------- Comment (by foolswisdom): #3260 seems to describe other areas with the same issue. -- Ticket URL: <http://trac.wordpress.org/ticket/3252#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 00:03:03 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 00:03:12 2006 Subject: [wp-trac] Re: [WordPress Trac] #3267: PHP Error in template-functions-links.php In-Reply-To: <066.97b86b0b408bf07c28238df7bab36379@lists.automattic.com> References: <066.97b86b0b408bf07c28238df7bab36379@lists.automattic.com> Message-ID: <075.99cb55d5eeba44fffae1ce4c42a7c31d@lists.automattic.com> #3267: PHP Error in template-functions-links.php -------------------------+-------------------------------------------------- Reporter: Mike_Koepke | Owner: markjaquith Type: defect | Status: assigned Priority: high | Milestone: 2.1 Component: General | Version: 2.0.4 Severity: normal | Resolution: Keywords: commit | -------------------------+-------------------------------------------------- Changes (by foolswisdom): * keywords: reporter-feedback => commit Comment: Mark, how about checking in that change to trunk now then? -- Ticket URL: <http://trac.wordpress.org/ticket/3267#comment:12> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 00:09:15 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 00:09:23 2006 Subject: [wp-trac] Re: [WordPress Trac] #3210: Remove in 1.4 In-Reply-To: <066.38e8702e813e32968345823fa61f0f15@lists.automattic.com> References: <066.38e8702e813e32968345823fa61f0f15@lists.automattic.com> Message-ID: <075.ac8e5b4118d567c002782252a27c5e78@lists.automattic.com> #3210: Remove in 1.4 -------------------------+-------------------------------------------------- Reporter: Nazgul | Owner: anonymous Type: enhancement | Status: new Priority: lowest | Milestone: 2.1 Component: General | Version: 2.1 Severity: trivial | Resolution: Keywords: needs-patch | -------------------------+-------------------------------------------------- Comment (by ryan): Axe the comment. -- Ticket URL: <http://trac.wordpress.org/ticket/3210#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 01:50:11 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 01:50:20 2006 Subject: [wp-trac] Re: [WordPress Trac] #3210: Remove in 1.4 In-Reply-To: <066.38e8702e813e32968345823fa61f0f15@lists.automattic.com> References: <066.38e8702e813e32968345823fa61f0f15@lists.automattic.com> Message-ID: <075.4f126dc4f569d544d53ed77d0174066d@lists.automattic.com> #3210: Remove in 1.4 ------------------------------+--------------------------------------------- Reporter: Nazgul | Owner: anonymous Type: enhancement | Status: new Priority: lowest | Milestone: 2.1 Component: General | Version: 2.1 Severity: trivial | Resolution: Keywords: has-patch commit | ------------------------------+--------------------------------------------- Changes (by foolswisdom): * keywords: needs-patch => has-patch commit -- Ticket URL: <http://trac.wordpress.org/ticket/3210#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 01:58:00 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 01:58:08 2006 Subject: [wp-trac] Re: [WordPress Trac] #3233: 'Editor' tab title needs clarifier for translation In-Reply-To: <066.f7167cb4c9c07333eeade5db020e2bbd@lists.automattic.com> References: <066.f7167cb4c9c07333eeade5db020e2bbd@lists.automattic.com> Message-ID: <075.deb7dc799becb7476a90f95e14abd5ca@lists.automattic.com> #3233: 'Editor' tab title needs clarifier for translation ----------------------------+----------------------------------------------- Reporter: foolswisdom | Owner: foolswisdom Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by foolswisdom): * owner: anonymous => foolswisdom Comment: No longer indifferent as RTE are often referred as HTML editor (gmail for example), so Visual / Code seems like the winningest to me. I will attach the trivial patch. -- Ticket URL: <http://trac.wordpress.org/ticket/3233#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 02:09:31 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 02:09:37 2006 Subject: [wp-trac] [WordPress Trac] #3337: gettext string disambiguation Message-ID: <066.bb162066acc0fcd8d1503e887d6dd57b@lists.automattic.com> #3337: gettext string disambiguation ----------------------------+----------------------------------------------- Reporter: ryan | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Keywords: gettext i18n ----------------------------+----------------------------------------------- Provide context for gettext strings as discussed in [http://comox.textdrive.com/pipermail/wp-polyglots/2006- October/001076.html this thread]. I'm thinking the glib style "|" context and maybe a special context function would be good. -- Ticket URL: <http://trac.wordpress.org/ticket/3337> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 03:06:06 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 03:06:13 2006 Subject: [wp-trac] Re: [WordPress Trac] #3251: wordpress.org/search each page displays same results and sometimes no results are found In-Reply-To: <066.de9809e02cf587db15ad16173608be75@lists.automattic.com> References: <066.de9809e02cf587db15ad16173608be75@lists.automattic.com> Message-ID: <075.0f0260091f2bf605c662c890401928da@lists.automattic.com> #3251: wordpress.org/search each page displays same results and sometimes no results are found ---------------------------+------------------------------------------------ Reporter: foolswisdom | Owner: matt Type: defect | Status: closed Priority: normal | Milestone: Component: WordPress.org | Version: Severity: major | Resolution: fixed Keywords: | ---------------------------+------------------------------------------------ Changes (by foolswisdom): * status: reopened => closed * resolution: => fixed Comment: Verified fixed by mdawaffe. -- Ticket URL: <http://trac.wordpress.org/ticket/3251#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 07:44:49 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 07:45:02 2006 Subject: [wp-trac] Re: [WordPress Trac] #3286: Handling of escape sequences is muddled and non-compatible In-Reply-To: <066.741e61b0c97d3621e7dd9f135e6ee024@lists.automattic.com> References: <066.741e61b0c97d3621e7dd9f135e6ee024@lists.automattic.com> Message-ID: <075.4a23a86ba8a2520f706523f8360aafa1@lists.automattic.com> #3286: Handling of escape sequences is muddled and non-compatible ----------------------+----------------------------------------------------- Reporter: cdavies | Owner: anonymous Type: defect | Status: new Priority: high | Milestone: Component: Security | Version: 2.0.4 Severity: major | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by ryan): So escape only single quotes and escape them in the '' fashion. Also, make sure $wpdb->escape() is used only when escaping on the way to the DB, and use addslashes() when escaping for things like HTML and JS. -- Ticket URL: <http://trac.wordpress.org/ticket/3286#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 07:47:47 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 07:47:55 2006 Subject: [wp-trac] Re: [WordPress Trac] #3286: Handling of escape sequences is muddled and non-compatible In-Reply-To: <066.741e61b0c97d3621e7dd9f135e6ee024@lists.automattic.com> References: <066.741e61b0c97d3621e7dd9f135e6ee024@lists.automattic.com> Message-ID: <075.fc20eee3c3f7cfc4114142a7aba88eaa@lists.automattic.com> #3286: Handling of escape sequences is muddled and non-compatible ----------------------+----------------------------------------------------- Reporter: cdavies | Owner: anonymous Type: defect | Status: new Priority: high | Milestone: Component: Security | Version: 2.0.4 Severity: major | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by ryan): Oops, trac converts doubled-up single quotes to italics. :-) -- Ticket URL: <http://trac.wordpress.org/ticket/3286#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 08:57:24 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 08:57:34 2006 Subject: [wp-trac] Re: [WordPress Trac] #3225: Export file does not download in FF In-Reply-To: <066.c6ba1a3b130cbdb1bf3f267ce7680516@lists.automattic.com> References: <066.c6ba1a3b130cbdb1bf3f267ce7680516@lists.automattic.com> Message-ID: <075.fc1adb45c667855b438e07c4e34bac15@lists.automattic.com> #3225: Export file does not download in FF ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: markjaquith Type: defect | Status: assigned Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by mdawaffe): 3225.diff 1. Pads export file with helpful comments to fix FireFox 2 issue. 1. Sends ~made-up Content-type: text/wxr+xml to fix Safari Issue. Works in 1. FF 2 1. FF 1.5.0.7 1. Safari 2.0.4 1. Opera 9.02 1. IE 7 Not tested in IE 6 -- Ticket URL: <http://trac.wordpress.org/ticket/3225#comment:8> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 09:24:54 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 09:25:03 2006 Subject: [wp-trac] Re: [WordPress Trac] #3225: Export file does not download in FF In-Reply-To: <066.c6ba1a3b130cbdb1bf3f267ce7680516@lists.automattic.com> References: <066.c6ba1a3b130cbdb1bf3f267ce7680516@lists.automattic.com> Message-ID: <075.f18410b380f66c8b9f48b39d4ad6fe59@lists.automattic.com> #3225: Export file does not download in FF -----------------------------------+---------------------------------------- Reporter: Viper007Bond | Owner: markjaquith Type: defect | Status: assigned Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch 2nd-opinion | -----------------------------------+---------------------------------------- Changes (by mdawaffe): * keywords: => has-patch 2nd-opinion -- Ticket URL: <http://trac.wordpress.org/ticket/3225#comment:9> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 14:06:10 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 14:06:39 2006 Subject: [wp-trac] [WordPress Trac] #3338: Blog Search: Ignore Soft Hyphens Message-ID: <066.1d365df65c10dae132b48a24338ba440@lists.automattic.com> #3338: Blog Search: Ignore Soft Hyphens --------------------------+------------------------------------------------- Reporter: transalpin | Owner: anonymous Type: defect | Status: new Priority: high | Milestone: 2.1 Component: Optimization | Version: 2.0.5 Severity: normal | Keywords: hyphenate, hyphenation, discretionary hyphen, search --------------------------+------------------------------------------------- The W3C and the Unicode Consortium say it: For operations such as searching and sorting, the soft hyphen should always be ignored. To clarify, a search for ?wordpress? should return both ?`WordPress`? and ?`Word­Press`?. Personally, I extensively use the Soft Hyphen character (U+00AD, `­`) for posts written in German, unfortunately making the text unsearchable. It just looks better, even for non-justified alignment. -- Ticket URL: <http://trac.wordpress.org/ticket/3338> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 14:06:10 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 14:06:40 2006 Subject: [wp-trac] [WordPress Trac] #3338: Blog Search: Ignore Soft Hyphens Message-ID: <066.1d365df65c10dae132b48a24338ba440@lists.automattic.com> #3338: Blog Search: Ignore Soft Hyphens --------------------------+------------------------------------------------- Reporter: transalpin | Owner: anonymous Type: defect | Status: new Priority: high | Milestone: 2.1 Component: Optimization | Version: 2.0.5 Severity: normal | Keywords: hyphenate, hyphenation, discretionary hyphen, search --------------------------+------------------------------------------------- The W3C and the Unicode Consortium say it: For operations such as searching and sorting, the soft hyphen should always be ignored. To clarify, a search for ?wordpress? should return both ?`WordPress`? and ?`Word­Press`?. Personally, I extensively use the Soft Hyphen character (U+00AD, `­`) for posts written in German, unfortunately making the text unsearchable. It just looks better, even for non-justified alignment. -- Ticket URL: <http://trac.wordpress.org/ticket/3338> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 17:15:29 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 17:15:40 2006 Subject: [wp-trac] Re: [WordPress Trac] #3306: saving post takes me to the wrong page In-Reply-To: <065.76c33b1764602f38912ffd78dfaeb747@lists.automattic.com> References: <065.76c33b1764602f38912ffd78dfaeb747@lists.automattic.com> Message-ID: <074.51d148a8829b46e446b8ab639aef0487@lists.automattic.com> #3306: saving post takes me to the wrong page ----------------------------+----------------------------------------------- Reporter: lschiere | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by lschiere): * cc: luke-wordpress@schierer.org (added) -- Ticket URL: <http://trac.wordpress.org/ticket/3306#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 18:39:48 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 18:39:58 2006 Subject: [wp-trac] [WordPress Trac] #3339: Mysql error while editing post Message-ID: <066.a07f205387e0a5a127bb5a6c59f03418@lists.automattic.com> #3339: Mysql error while editing post ----------------------------+----------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: major | Keywords: ----------------------------+----------------------------------------------- You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near ')' at line 3 The page is post.php and it happens when editing posts already published. -- Ticket URL: <http://trac.wordpress.org/ticket/3339> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 18:43:36 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 18:43:45 2006 Subject: [wp-trac] [WordPress Trac] #3340: File upload send to editor not valid xhtml code Message-ID: <066.d63c16a55ad60800a8bd17bc848e7716@lists.automattic.com> #3340: File upload send to editor not valid xhtml code ----------------------------+----------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Keywords: ----------------------------+----------------------------------------------- There are single quotes (') instead of double quotes (") in the xhtml code sent to the editor by the inline file upload box. <img src='/myimg.jpg' /> isn't valid xhtml code. -- Ticket URL: <http://trac.wordpress.org/ticket/3340> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 19:35:37 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 19:35:52 2006 Subject: [wp-trac] [WordPress Trac] #3341: Remove paging by days Message-ID: <066.b15a41e0bbab4e451c19cd5445af4ddc@lists.automattic.com> #3341: Remove paging by days ----------------------------+----------------------------------------------- Reporter: ryan | Owner: ryan Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Keywords: paging queries ----------------------------+----------------------------------------------- It's expensive, flaky, and unpopular. -- Ticket URL: <http://trac.wordpress.org/ticket/3341> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 19:36:36 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 19:36:45 2006 Subject: [wp-trac] Re: [WordPress Trac] #3215: Login & Update functions everything is broken In-Reply-To: <049.6066b63c1044229dd67a636989ac05fd@lists.automattic.com> References: <049.6066b63c1044229dd67a636989ac05fd@lists.automattic.com> Message-ID: <058.e7d712754519a4bcb715ef00aa281bf8@lists.automattic.com> #3215: Login & Update functions everything is broken --------------------------------------------+------------------------------- Reporter: Xmion | Owner: markjaquith Type: defect | Status: assigned Priority: highest | Milestone: 2.1 Component: General | Version: 2.1 Severity: critical | Resolution: Keywords: Blank page 302 maint-candidate | --------------------------------------------+------------------------------- Comment (by ev3rywh3re): Just reporting back for this. Using [4455] ( current to date ) still has issues. Removing header_status from wp_redirect in pluggable.php line 273 fixes problem. I know it has to do with php fast cgi version in use at Yahoo hosting, but I am unable to troubleshoot what php_sapi_name() is returning at this time. I may try to see what it's spitting out if I get a chance. -- Ticket URL: <http://trac.wordpress.org/ticket/3215#comment:15> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 20:13:55 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 20:14:06 2006 Subject: [wp-trac] Re: [WordPress Trac] #3338: Blog Search: Ignore Soft Hyphens In-Reply-To: <066.1d365df65c10dae132b48a24338ba440@lists.automattic.com> References: <066.1d365df65c10dae132b48a24338ba440@lists.automattic.com> Message-ID: <075.38361515f5fa4e92eef6dc6816f16bed@lists.automattic.com> #3338: Blog Search: Ignore Soft Hyphens ------------------------------------------------------------------+--------- Reporter: transalpin | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: hyphenate, hyphenation, discretionary hyphen, search | ------------------------------------------------------------------+--------- Changes (by foolswisdom): * priority: high => normal -- Ticket URL: <http://trac.wordpress.org/ticket/3338#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 20:41:43 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 20:41:51 2006 Subject: [wp-trac] Re: [WordPress Trac] #3340: File upload send to editor not valid xhtml code In-Reply-To: <066.d63c16a55ad60800a8bd17bc848e7716@lists.automattic.com> References: <066.d63c16a55ad60800a8bd17bc848e7716@lists.automattic.com> Message-ID: <075.5f6a8852e44713b0cc4c4552d370ba1a@lists.automattic.com> #3340: File upload send to editor not valid xhtml code ----------------------------+----------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: invalid Keywords: | ----------------------------+----------------------------------------------- Changes (by skeltoac): * status: new => closed * resolution: => invalid Comment: tassoman: single quotes are valid for xhtml attributes. the only thing wrong with the markup you posted here is a missing attribute. -- Ticket URL: <http://trac.wordpress.org/ticket/3340#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 20:44:26 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 20:44:36 2006 Subject: [wp-trac] Re: [WordPress Trac] #3339: Mysql error while editing post In-Reply-To: <066.a07f205387e0a5a127bb5a6c59f03418@lists.automattic.com> References: <066.a07f205387e0a5a127bb5a6c59f03418@lists.automattic.com> Message-ID: <075.ff99d76161355b3b1ce0d4beb6d6da4c@lists.automattic.com> #3339: Mysql error while editing post ----------------------------+----------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: major | Resolution: worksforme Keywords: | ----------------------------+----------------------------------------------- Changes (by skeltoac): * status: new => closed * resolution: => worksforme Comment: Nothing can be done about this until more information is given. Closing until you provide info and re-open. Please give the content of your post and any other information that might be relevant: browser version and extensions, OS, all installed WP plugins, the query that has the error. -- Ticket URL: <http://trac.wordpress.org/ticket/3339#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 20:52:19 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 20:52:36 2006 Subject: [wp-trac] [WordPress Trac] #3342: users.php redirects to users_php on post actions Message-ID: <066.59c2d2ad7e68ed8eb1565c7e2749699a@lists.automattic.com> #3342: users.php redirects to users_php on post actions ----------------------------+----------------------------------------------- Reporter: mdawaffe | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: Severity: major | Keywords: ----------------------------+----------------------------------------------- add_query_arg doesn't like the urlencoded stuff. We shouldn't be urlencoding everything anyway, just the values. Attached. -- Ticket URL: <http://trac.wordpress.org/ticket/3342> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 20:53:14 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 20:53:24 2006 Subject: [wp-trac] Re: [WordPress Trac] #3342: users.php redirects to users_php on post actions In-Reply-To: <066.59c2d2ad7e68ed8eb1565c7e2749699a@lists.automattic.com> References: <066.59c2d2ad7e68ed8eb1565c7e2749699a@lists.automattic.com> Message-ID: <075.ed710a6dc2fd130ae762a2444192a9d7@lists.automattic.com> #3342: users.php redirects to users_php on post actions -----------------------------------+---------------------------------------- Reporter: mdawaffe | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: major | Resolution: Keywords: has-patch 2nd-opinion | -----------------------------------+---------------------------------------- Changes (by mdawaffe): * keywords: => has-patch 2nd-opinion * version: => 2.1 -- Ticket URL: <http://trac.wordpress.org/ticket/3342#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 22:15:10 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 22:15:18 2006 Subject: [wp-trac] [WordPress Trac] #3343: Add/Delete categories bug in last trunks Message-ID: <066.5314b9625f6b86ea30a04b93db2b365d@lists.automattic.com> #3343: Add/Delete categories bug in last trunks ----------------------------+----------------------------------------------- Reporter: dan-daemon | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Keywords: ----------------------------+----------------------------------------------- Hello guys, Can you give me solution for bugs I described here: http://wordpress.org/support/topic/93417?replies=2 Thanks, Dan -- Ticket URL: <http://trac.wordpress.org/ticket/3343> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 22:16:16 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 22:16:23 2006 Subject: [wp-trac] Re: [WordPress Trac] #3343: Add/Delete categories bug in last trunks In-Reply-To: <066.5314b9625f6b86ea30a04b93db2b365d@lists.automattic.com> References: <066.5314b9625f6b86ea30a04b93db2b365d@lists.automattic.com> Message-ID: <075.aed9976e78d8ea2777b852b35a5ebbc5@lists.automattic.com> #3343: Add/Delete categories bug in last trunks ----------------------------+----------------------------------------------- Reporter: dan-daemon | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by dan-daemon): * version: => 2.1 * milestone: => 2.1 -- Ticket URL: <http://trac.wordpress.org/ticket/3343#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 22:53:58 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 22:54:10 2006 Subject: [wp-trac] [WordPress Trac] #3344: Allow author.php to show even if author has 0 posts. Message-ID: <066.0f7dcea5f3b046e014e206e866895d05@lists.automattic.com> #3344: Allow author.php to show even if author has 0 posts. ----------------------+----------------------------------------------------- Reporter: ruckerz | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Template | Version: 2.0.4 Severity: normal | Keywords: author no posts ----------------------+----------------------------------------------------- Loading /author/username will return a 404 if author has no posts. It is desirable to show something, in my case, author profiles and let author.php decide what to do if the author has 0 posts. -- Ticket URL: <http://trac.wordpress.org/ticket/3344> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 22:56:40 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 22:56:49 2006 Subject: [wp-trac] [WordPress Trac] #3345: Allow author.php to show even if author has 0 posts. Message-ID: <066.5010bee4865a48f113f4f1ce70351da4@lists.automattic.com> #3345: Allow author.php to show even if author has 0 posts. ----------------------+----------------------------------------------------- Reporter: ruckerz | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Template | Version: 2.0.4 Severity: normal | Keywords: author no posts ----------------------+----------------------------------------------------- Loading /author/username will return a 404 if author has no posts. It is desirable to show something, in my case, author profiles and let author.php decide what to do if the author has 0 posts. Rewrote handle_404() to... if ( (0 == count($wp_query->posts)) && (!isset($wp_query->query_vars['cat']) || $wp_query->query_vars['cat']== 0) && (!isset($wp_query->query_vars['author']) || $wp_query->query_vars['author'] == 0) && !is_404() && !is_search() && ( $this->did_permalink || (!empty($_SERVER['QUERY_STRING']) && (false === strpos($_SERVER['REQUEST_URI'], '?'))) ) ) { Note this includes patches from Trac #1969 (Check for category and author page existence) and also solves final comment by _ck_. -- Ticket URL: <http://trac.wordpress.org/ticket/3345> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 22:56:44 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 22:56:52 2006 Subject: [wp-trac] [WordPress Trac] #3346: Allow author.php to show even if author has 0 posts. Message-ID: <066.b34e737168171a711d85c4eb138dcfe6@lists.automattic.com> #3346: Allow author.php to show even if author has 0 posts. ----------------------+----------------------------------------------------- Reporter: ruckerz | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Template | Version: 2.0.4 Severity: normal | Keywords: author no posts ----------------------+----------------------------------------------------- Loading /author/username will return a 404 if author has no posts. It is desirable to show something, in my case, author profiles and let author.php decide what to do if the author has 0 posts. Rewrote handle_404() to... if ( (0 == count($wp_query->posts)) && (!isset($wp_query->query_vars['cat']) || $wp_query->query_vars['cat']== 0) && (!isset($wp_query->query_vars['author']) || $wp_query->query_vars['author'] == 0) && !is_404() && !is_search() && ( $this->did_permalink || (!empty($_SERVER['QUERY_STRING']) && (false === strpos($_SERVER['REQUEST_URI'], '?'))) ) ) { Note this includes patches from Trac #1969 (Check for category and author page existence) and also solves final comment by _ck_. -- Ticket URL: <http://trac.wordpress.org/ticket/3346> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 23:02:12 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 23:02:29 2006 Subject: [wp-trac] Re: [WordPress Trac] #3345: Allow author.php to show even if author has 0 posts. In-Reply-To: <066.5010bee4865a48f113f4f1ce70351da4@lists.automattic.com> References: <066.5010bee4865a48f113f4f1ce70351da4@lists.automattic.com> Message-ID: <075.e23fc76852d88c868f6404496d6995b6@lists.automattic.com> #3345: Allow author.php to show even if author has 0 posts. -----------------------------+---------------------------------------------- Reporter: ruckerz | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Template | Version: 2.0.4 Severity: normal | Resolution: Keywords: author no posts | -----------------------------+---------------------------------------------- Comment (by markjaquith): would that show author.php for authors who don't exist? -- Ticket URL: <http://trac.wordpress.org/ticket/3345#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 23:13:26 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 23:13:36 2006 Subject: [wp-trac] Re: [WordPress Trac] #137: Comments feed modification time is based on posts, not comments In-Reply-To: <066.9745b146a23628672a8b77956dd04490@lists.automattic.com> References: <066.9745b146a23628672a8b77956dd04490@lists.automattic.com> Message-ID: <075.58cf757e996a83ae2fa0f6551561dbf4@lists.automattic.com> #137: Comments feed modification time is based on posts, not comments --------------------------------------+------------------------------------- Reporter: kelson | Owner: ryan Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.0 Severity: minor | Resolution: Keywords: has-patch, needs-testing | --------------------------------------+------------------------------------- Comment (by mdawaffe): 137.diff 1. adds 'withoutcomments' query var 1. send_headers() checks last modified comment if withcomments or if !withoutcomments and one of the is_sigular query vars is set. -- Ticket URL: <http://trac.wordpress.org/ticket/137#comment:14> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 23:13:26 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 23:13:44 2006 Subject: [wp-trac] Re: [WordPress Trac] #137: Comments feed modification time is based on posts, not comments In-Reply-To: <066.9745b146a23628672a8b77956dd04490@lists.automattic.com> References: <066.9745b146a23628672a8b77956dd04490@lists.automattic.com> Message-ID: <075.58cf757e996a83ae2fa0f6551561dbf4@lists.automattic.com> #137: Comments feed modification time is based on posts, not comments --------------------------------------+------------------------------------- Reporter: kelson | Owner: ryan Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.0 Severity: minor | Resolution: Keywords: has-patch, needs-testing | --------------------------------------+------------------------------------- Comment (by mdawaffe): 137.diff 1. adds 'withoutcomments' query var 1. send_headers() checks last modified comment if withcomments or if !withoutcomments and one of the is_sigular query vars is set. -- Ticket URL: <http://trac.wordpress.org/ticket/137#comment:14> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 23:18:24 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 23:18:32 2006 Subject: [wp-trac] Re: [WordPress Trac] #3344: Allow author.php to show even if author has 0 posts. In-Reply-To: <066.0f7dcea5f3b046e014e206e866895d05@lists.automattic.com> References: <066.0f7dcea5f3b046e014e206e866895d05@lists.automattic.com> Message-ID: <075.3b555c6dcaa749bfddae9b37c2acccb5@lists.automattic.com> #3344: Allow author.php to show even if author has 0 posts. -----------------------------+---------------------------------------------- Reporter: ruckerz | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Template | Version: 2.0.4 Severity: normal | Resolution: duplicate Keywords: author no posts | -----------------------------+---------------------------------------------- Changes (by mdawaffe): * status: new => closed * resolution: => duplicate Comment: #3345 -- Ticket URL: <http://trac.wordpress.org/ticket/3344#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 8 23:18:52 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 8 23:19:01 2006 Subject: [wp-trac] Re: [WordPress Trac] #3346: Allow author.php to show even if author has 0 posts. In-Reply-To: <066.b34e737168171a711d85c4eb138dcfe6@lists.automattic.com> References: <066.b34e737168171a711d85c4eb138dcfe6@lists.automattic.com> Message-ID: <075.3c1cb989496dba0ccda9aef67af98717@lists.automattic.com> #3346: Allow author.php to show even if author has 0 posts. -----------------------------+---------------------------------------------- Reporter: ruckerz | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Template | Version: 2.0.4 Severity: normal | Resolution: duplicate Keywords: author no posts | -----------------------------+---------------------------------------------- Changes (by mdawaffe): * status: new => closed * resolution: => duplicate Comment: #3345 -- Ticket URL: <http://trac.wordpress.org/ticket/3346#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 9 13:39:24 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 9 13:39:48 2006 Subject: [wp-trac] Re: [WordPress Trac] #3305: save new page and edit pages is broken In-Reply-To: <066.a0cc15220b1faf418065dd29269b9443@lists.automattic.com> References: <066.a0cc15220b1faf418065dd29269b9443@lists.automattic.com> Message-ID: <075.aa5a5159c1197b83d83d398fd8f4ef02@lists.automattic.com> #3305: save new page and edit pages is broken ----------------------------+----------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: closed Priority: high | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: critical | Resolution: worksforme Keywords: | ----------------------------+----------------------------------------------- Comment (by tassoman): The problem were Bad-Behavior plugin. -- Ticket URL: <http://trac.wordpress.org/ticket/3305#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 9 13:59:42 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 9 14:00:40 2006 Subject: [wp-trac] Re: [WordPress Trac] #3336: Change administration submenu link's colors and/or background colors In-Reply-To: <066.a4b77555d70231af2b5cce9b94b04f95@lists.automattic.com> References: <066.a4b77555d70231af2b5cce9b94b04f95@lists.automattic.com> Message-ID: <075.89fb4f1b5b32e9037ce86f9f892535cf@lists.automattic.com> #3336: Change administration submenu link's colors and/or background colors ------------------------------------------------+--------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: worksforme Keywords: administration, menu, submenu, bar | ------------------------------------------------+--------------------------- Comment (by tassoman): ok solved at revision 4460 -- Ticket URL: <http://trac.wordpress.org/ticket/3336#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 9 13:53:51 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 9 14:03:26 2006 Subject: [wp-trac] Re: [WordPress Trac] #3340: File upload send to editor not valid xhtml code In-Reply-To: <066.d63c16a55ad60800a8bd17bc848e7716@lists.automattic.com> References: <066.d63c16a55ad60800a8bd17bc848e7716@lists.automattic.com> Message-ID: <075.92210db69225897e88c383fc51e35d2f@lists.automattic.com> #3340: File upload send to editor not valid xhtml code ----------------------------+----------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: reopened Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by tassoman): * status: closed => reopened * resolution: invalid => Comment: Ok it validates strict also with single quote, but there's too much single quotes after rel= attribute rel='attachment wp-att-509'' -- Ticket URL: <http://trac.wordpress.org/ticket/3340#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 9 15:00:34 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 9 15:00:54 2006 Subject: [wp-trac] Re: [WordPress Trac] #3307: Add i18n support to function get_archives() In-Reply-To: <066.3d8d033666ec8824e0395d60fc092589@lists.automattic.com> References: <066.3d8d033666ec8824e0395d60fc092589@lists.automattic.com> Message-ID: <075.cbf29b7e903bf51d11a98f10181bd6b9@lists.automattic.com> #3307: Add i18n support to function get_archives() ----------------------------+----------------------------------------------- Reporter: yskins | Owner: anonymous Type: defect | Status: new Priority: lowest | Milestone: 2.1 Component: Administration | Version: 2.0.4 Severity: normal | Resolution: Keywords: i18n | ----------------------------+----------------------------------------------- Comment (by drssay): same to #1540 -- Ticket URL: <http://trac.wordpress.org/ticket/3307#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 9 16:24:28 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 9 16:24:46 2006 Subject: [wp-trac] [WordPress Trac] #3347: Changeset 4455 - SELECT FOUND_ROWS() faster than count()? Message-ID: <066.cbd2be2649a6cf1b7a199e7bbfebad6d@lists.automattic.com> #3347: Changeset 4455 - SELECT FOUND_ROWS() faster than count()? -------------------------+-------------------------------------------------- Reporter: alexkingorg | Owner: ryan Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Keywords: -------------------------+-------------------------------------------------- This change looks like it resolves ticket 3274 in a different way than the patch. I'm wondering if an additional query is faster/slower than counting the array we already have as a PHP variable. http://trac.wordpress.org/ticket/3274 -- Ticket URL: <http://trac.wordpress.org/ticket/3347> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 9 16:24:28 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 9 16:24:47 2006 Subject: [wp-trac] [WordPress Trac] #3347: Changeset 4455 - SELECT FOUND_ROWS() faster than count()? Message-ID: <066.cbd2be2649a6cf1b7a199e7bbfebad6d@lists.automattic.com> #3347: Changeset 4455 - SELECT FOUND_ROWS() faster than count()? -------------------------+-------------------------------------------------- Reporter: alexkingorg | Owner: ryan Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Keywords: -------------------------+-------------------------------------------------- This change looks like it resolves ticket 3274 in a different way than the patch. I'm wondering if an additional query is faster/slower than counting the array we already have as a PHP variable. http://trac.wordpress.org/ticket/3274 -- Ticket URL: <http://trac.wordpress.org/ticket/3347> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 9 17:56:14 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 9 17:56:41 2006 Subject: [wp-trac] Re: [WordPress Trac] #3340: File upload send to editor not valid xhtml code In-Reply-To: <066.d63c16a55ad60800a8bd17bc848e7716@lists.automattic.com> References: <066.d63c16a55ad60800a8bd17bc848e7716@lists.automattic.com> Message-ID: <075.2abed20a5463ef9bd02c11821503887d@lists.automattic.com> #3340: File upload send to editor not valid xhtml code ------------------------------+--------------------------------------------- Reporter: tassoman | Owner: mdawaffe Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch commit | ------------------------------+--------------------------------------------- Changes (by mdawaffe): * keywords: => has-patch commit * status: reopened => new * owner: anonymous => mdawaffe Comment: Patch attached. Will need to bump JS version number. -- Ticket URL: <http://trac.wordpress.org/ticket/3340#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 9 18:00:59 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 9 18:01:18 2006 Subject: [wp-trac] Re: [WordPress Trac] #3347: Changeset 4455 - SELECT FOUND_ROWS() faster than count()? In-Reply-To: <066.cbd2be2649a6cf1b7a199e7bbfebad6d@lists.automattic.com> References: <066.cbd2be2649a6cf1b7a199e7bbfebad6d@lists.automattic.com> Message-ID: <075.79853dbcab70f0ff82deb6589f80564b@lists.automattic.com> #3347: Changeset 4455 - SELECT FOUND_ROWS() faster than count()? -------------------------+-------------------------------------------------- Reporter: alexkingorg | Owner: ryan Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Comment (by ryan): In my testing, SELECT FOUND_ROWS() is extremely fast, and adding SQL_CALC_FOUND_ROWS to the post query has minimal overhead. Overall, it's faster for me than doing another SELECT FROM. What are your impressions so far? -- Ticket URL: <http://trac.wordpress.org/ticket/3347#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 9 18:56:21 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 9 18:56:36 2006 Subject: [wp-trac] Re: [WordPress Trac] #3347: Changeset 4455 - SELECT FOUND_ROWS() faster than count()? In-Reply-To: <066.cbd2be2649a6cf1b7a199e7bbfebad6d@lists.automattic.com> References: <066.cbd2be2649a6cf1b7a199e7bbfebad6d@lists.automattic.com> Message-ID: <075.6eaa6214cac7b504aec3263ccb1e80b3@lists.automattic.com> #3347: Changeset 4455 - SELECT FOUND_ROWS() faster than count()? -------------------------+-------------------------------------------------- Reporter: alexkingorg | Owner: ryan Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Comment (by markjaquith): Austin Matzko on wp-hackers notes that SQL_CALC_FOUND_ROWS requires MySQL 4.0, while WordPress up 'til now has worked on MySQL 3.23.23 Just as FYI. I'm fine leaving MySQL 3 in the dust. Matt may feel differently. -- Ticket URL: <http://trac.wordpress.org/ticket/3347#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 9 20:41:57 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 9 20:42:18 2006 Subject: [wp-trac] [WordPress Trac] #3348: Admin Screen Changes Message-ID: <066.2070f296eabd040d96864f952b9b41a4@lists.automattic.com> #3348: Admin Screen Changes ----------------------------+----------------------------------------------- Reporter: bryanveloso | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Keywords: has-patch commit ----------------------------+----------------------------------------------- Some changes made to the WP.com login screen that I want put back into core. <ul> on the page has been moved out of the main box for the sake of not breaking during translations. Less CSS too. :] Diffs are included. -- Ticket URL: <http://trac.wordpress.org/ticket/3348> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 9 20:49:02 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 9 20:49:21 2006 Subject: [wp-trac] Re: [WordPress Trac] #3348: Admin (Login) Screen Changes In-Reply-To: <066.2070f296eabd040d96864f952b9b41a4@lists.automattic.com> References: <066.2070f296eabd040d96864f952b9b41a4@lists.automattic.com> Message-ID: <075.512d1ac0752472af15d94129941b7de1@lists.automattic.com> #3348: Admin (Login) Screen Changes ------------------------------+--------------------------------------------- Reporter: bryanveloso | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch commit | ------------------------------+--------------------------------------------- Changes (by bryanveloso): * summary: Admin Screen Changes => Admin (Login) Screen Changes -- Ticket URL: <http://trac.wordpress.org/ticket/3348#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 9 20:49:02 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 9 20:49:22 2006 Subject: [wp-trac] Re: [WordPress Trac] #3348: Admin (Login) Screen Changes In-Reply-To: <066.2070f296eabd040d96864f952b9b41a4@lists.automattic.com> References: <066.2070f296eabd040d96864f952b9b41a4@lists.automattic.com> Message-ID: <075.512d1ac0752472af15d94129941b7de1@lists.automattic.com> #3348: Admin (Login) Screen Changes ------------------------------+--------------------------------------------- Reporter: bryanveloso | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch commit | ------------------------------+--------------------------------------------- Changes (by bryanveloso): * summary: Admin Screen Changes => Admin (Login) Screen Changes -- Ticket URL: <http://trac.wordpress.org/ticket/3348#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 9 21:13:13 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 9 21:13:22 2006 Subject: [wp-trac] [WordPress Trac] #3349: wp-config pickup consistency fixes Message-ID: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> #3349: wp-config pickup consistency fixes --------------------------+------------------------------------------------- Reporter: RuddO | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Optimization | Version: 2.0.5 Severity: normal | Keywords: --------------------------+------------------------------------------------- What this patch does: * calls WP's wp-config.php consistently throughout WP (before it was a mixture of ../'s and dirname(__FILE__)'s) * lets anyone use a WordPress tree composed out of symlinks without issues (perfect for those who host hundreds of WPs in a single server for hundreds of customers, and who by any reasons won't use WP-MU) These fixes work OK on my setup, and should work OK on others' setups. Just tested creating a new blog and it's all good. -- Ticket URL: <http://trac.wordpress.org/ticket/3349> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 9 21:15:11 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 9 21:15:19 2006 Subject: [wp-trac] Re: [WordPress Trac] #3349: wp-config pickup consistency fixes In-Reply-To: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> References: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> Message-ID: <075.d2fc8a87f9a9298f1c1ea46dce1d9917@lists.automattic.com> #3349: wp-config pickup consistency fixes --------------------------+------------------------------------------------- Reporter: RuddO | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.1 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: | --------------------------+------------------------------------------------- Changes (by RuddO): * type: defect => enhancement -- Ticket URL: <http://trac.wordpress.org/ticket/3349#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 9 21:53:11 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 9 21:53:21 2006 Subject: [wp-trac] Re: [WordPress Trac] #3348: Admin (Login) Screen Changes In-Reply-To: <066.2070f296eabd040d96864f952b9b41a4@lists.automattic.com> References: <066.2070f296eabd040d96864f952b9b41a4@lists.automattic.com> Message-ID: <075.2639f8e6a87d2a57f3ac401d8612f9fe@lists.automattic.com> #3348: Admin (Login) Screen Changes ----------------------------+----------------------------------------------- Reporter: bryanveloso | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch | ----------------------------+----------------------------------------------- Changes (by Viper007Bond): * keywords: has-patch commit => has-patch Comment: http://wordpress.com/wp-login.php -1 to this patch. I get where it's coming from (the translations), but putting the links outside the box and leaving them basically unstyled is really ugly IMO. I think a better solution would be to just better style them in the box so that they can easily line wrap and stuff without going all ugly. And careful with at least the wp-admin.css patch. If applied, it'll undo at least one recent commit I believe (the height of the submenu in the admin area). It also introduces more validation errors, but there are already others there, so I guess we don't care. bryanveloso: update your SVN copy next time before making a patch. ;) -- Ticket URL: <http://trac.wordpress.org/ticket/3348#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 9 21:58:51 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 9 21:59:04 2006 Subject: [wp-trac] Re: [WordPress Trac] #3348: Admin (Login) Screen Changes In-Reply-To: <066.2070f296eabd040d96864f952b9b41a4@lists.automattic.com> References: <066.2070f296eabd040d96864f952b9b41a4@lists.automattic.com> Message-ID: <075.c3832c584f39a9a1ad6686b46d55c2c0@lists.automattic.com> #3348: Admin (Login) Screen Changes ----------------------------+----------------------------------------------- Reporter: bryanveloso | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch | ----------------------------+----------------------------------------------- Comment (by westi): Replying to [comment:2 Viper007Bond]: > http://wordpress.com/wp-login.php > > -1 to this patch. I get where it's coming from (the translations), but putting the links outside the box and leaving them basically unstyled is really ugly IMO. I think a better solution would be to just better style them in the box so that they can easily line wrap and stuff without going all ugly. > I think if you do a hard refresh on that page to pickup the new css it looks a lot nicer. -- Ticket URL: <http://trac.wordpress.org/ticket/3348#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 9 23:31:12 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 9 23:31:22 2006 Subject: [wp-trac] Re: [WordPress Trac] #3348: Admin (Login) Screen Changes In-Reply-To: <066.2070f296eabd040d96864f952b9b41a4@lists.automattic.com> References: <066.2070f296eabd040d96864f952b9b41a4@lists.automattic.com> Message-ID: <075.ea9b5ed501610b406526a3e544057a69@lists.automattic.com> #3348: Admin (Login) Screen Changes ----------------------------+----------------------------------------------- Reporter: bryanveloso | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch | ----------------------------+----------------------------------------------- Comment (by Viper007Bond): I did and I still think it looks rather... well, unprofessional I guess is the word I'd use. I mean, the login form is so nicely styled with a background image and everything and then there are just two very plain links stuck there at the bottom. -- Ticket URL: <http://trac.wordpress.org/ticket/3348#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 10 04:18:57 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 10 04:19:04 2006 Subject: [wp-trac] Re: [WordPress Trac] #3349: wp-config pickup consistency fixes In-Reply-To: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> References: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> Message-ID: <075.927fbf8bef2a2fc7be4347eec94a4527@lists.automattic.com> #3349: wp-config pickup consistency fixes --------------------------+------------------------------------------------- Reporter: RuddO | Owner: markjaquith Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: 2nd-opinion | --------------------------+------------------------------------------------- Changes (by markjaquith): * keywords: => 2nd-opinion * status: new => assigned * owner: anonymous => markjaquith Comment: At first glance, this looks fine. -- Ticket URL: <http://trac.wordpress.org/ticket/3349#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 10 06:01:40 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 10 06:03:25 2006 Subject: [wp-trac] Re: [WordPress Trac] #3349: wp-config pickup consistency fixes In-Reply-To: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> References: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> Message-ID: <075.b0a70a97da76c38f63513e5967a63479@lists.automattic.com> #3349: wp-config pickup consistency fixes --------------------------+------------------------------------------------- Reporter: RuddO | Owner: markjaquith Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: 2nd-opinion | --------------------------+------------------------------------------------- Comment (by RuddO): Thanks, Mark. I did work on other plugins and submitted them to their respective authors. The last author I will contact is the wonderful FireStats plugin's, where my fixes initially didn't work because the "offending file" was already being included via a dirname(FILE), thus I had to use getcwd(). It worked with getcwd() though. -- Ticket URL: <http://trac.wordpress.org/ticket/3349#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 10 13:50:18 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 10 16:14:47 2006 Subject: [wp-trac] [WordPress Trac] #3350: TinyMCE has plugin with 0-byte file(s) Message-ID: <066.3debe17c61e741c9e427ecdec71c63c3@lists.automattic.com> #3350: TinyMCE has plugin with 0-byte file(s) ----------------------------+----------------------------------------------- Reporter: Yosemite | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: 2.0.5 Severity: normal | Keywords: tinymce 0-byte ----------------------------+----------------------------------------------- In the current 2.0.5 distribution, all files in wp- includes\js\tinymce\plugins\inlinepopups\ are 0-byte. -- Ticket URL: <http://trac.wordpress.org/ticket/3350> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 10 19:43:27 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 10 19:43:38 2006 Subject: [wp-trac] Re: [WordPress Trac] #3349: wp-config pickup consistency fixes In-Reply-To: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> References: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> Message-ID: <075.5ab0fccc6f645e84917604394fe6aef1@lists.automattic.com> #3349: wp-config pickup consistency fixes --------------------------+------------------------------------------------- Reporter: RuddO | Owner: markjaquith Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: 2nd-opinion | --------------------------+------------------------------------------------- Comment (by foolswisdom): +1 on consistency -1 on ./ it is obtuse, leads me to do a double take to ensure it is not ../ -- Ticket URL: <http://trac.wordpress.org/ticket/3349#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 10 20:42:37 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 10 20:42:45 2006 Subject: [wp-trac] Re: [WordPress Trac] #3349: wp-config pickup consistency fixes In-Reply-To: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> References: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> Message-ID: <075.cdc37a1df035207e7bc558aa7fceca90@lists.automattic.com> #3349: wp-config pickup consistency fixes --------------------------+------------------------------------------------- Reporter: RuddO | Owner: markjaquith Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: 2nd-opinion | --------------------------+------------------------------------------------- Comment (by masquerade): +-0 for consistency, the whole codebase is inconsistent, and I don't care any more. -1 for anything that requires any plugin under any condition to have to use getcwd. Its not reliable. -- Ticket URL: <http://trac.wordpress.org/ticket/3349#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 10 23:34:19 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 10 23:34:28 2006 Subject: [wp-trac] [WordPress Trac] #3351: page_for_posts shows all posts Message-ID: <066.155c00db50e51200954b9f1ba80a87b5@lists.automattic.com> #3351: page_for_posts shows all posts ----------------------------+----------------------------------------------- Reporter: mdawaffe | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Keywords: ----------------------------+----------------------------------------------- page_for_posts shows ''all'' posts. Need to set {{{is_singular = false;}}} -- Ticket URL: <http://trac.wordpress.org/ticket/3351> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 10 23:34:52 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 10 23:34:59 2006 Subject: [wp-trac] Re: [WordPress Trac] #3351: page_for_posts shows all posts In-Reply-To: <066.155c00db50e51200954b9f1ba80a87b5@lists.automattic.com> References: <066.155c00db50e51200954b9f1ba80a87b5@lists.automattic.com> Message-ID: <075.a34f9ee45fac1acf5fc98968cd284db3@lists.automattic.com> #3351: page_for_posts shows all posts ------------------------------+--------------------------------------------- Reporter: mdawaffe | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch commit | ------------------------------+--------------------------------------------- Changes (by mdawaffe): * keywords: => has-patch commit -- Ticket URL: <http://trac.wordpress.org/ticket/3351#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 10 23:58:14 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 10 23:58:21 2006 Subject: [wp-trac] Re: [WordPress Trac] #3350: TinyMCE has plugin with 0-byte file(s) In-Reply-To: <066.3debe17c61e741c9e427ecdec71c63c3@lists.automattic.com> References: <066.3debe17c61e741c9e427ecdec71c63c3@lists.automattic.com> Message-ID: <075.9cdc0289da5117edfae1ea426ca876fa@lists.automattic.com> #3350: TinyMCE has plugin with 0-byte file(s) ----------------------------+----------------------------------------------- Reporter: Yosemite | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: 2.0.5 Severity: normal | Resolution: Keywords: tinymce 0-byte | ----------------------------+----------------------------------------------- Comment (by Viper007Bond): No they aren't... http://trac.wordpress.org/browser/trunk/wp- includes/js/tinymce/plugins/inlinepopups Only `editor_plugin_src.js` and `readme.txt` are. -- Ticket URL: <http://trac.wordpress.org/ticket/3350#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 11 00:00:39 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 11 00:00:50 2006 Subject: [wp-trac] Re: [WordPress Trac] #3350: TinyMCE has plugin with 0-byte file(s) In-Reply-To: <066.3debe17c61e741c9e427ecdec71c63c3@lists.automattic.com> References: <066.3debe17c61e741c9e427ecdec71c63c3@lists.automattic.com> Message-ID: <075.5cde32165ee665c32b37451bcd5e3121@lists.automattic.com> #3350: TinyMCE has plugin with 0-byte file(s) ----------------------------+----------------------------------------------- Reporter: Yosemite | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: 2.0.5 Severity: normal | Resolution: Keywords: tinymce 0-byte | ----------------------------+----------------------------------------------- Comment (by Viper007Bond): Oh, right, 2.0.5, not 2.1. Whoops! :) http://trac.wordpress.org/browser/branches/2.0/wp- includes/js/tinymce/plugins/inlinepopups -- Ticket URL: <http://trac.wordpress.org/ticket/3350#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 11 00:10:38 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 11 00:10:47 2006 Subject: [wp-trac] Re: [WordPress Trac] #3351: page_for_posts shows all posts In-Reply-To: <066.155c00db50e51200954b9f1ba80a87b5@lists.automattic.com> References: <066.155c00db50e51200954b9f1ba80a87b5@lists.automattic.com> Message-ID: <075.3e12130de0db9258002a360f4178192c@lists.automattic.com> #3351: page_for_posts shows all posts ------------------------------+--------------------------------------------- Reporter: mdawaffe | Owner: mdawaffe Type: defect | Status: assigned Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch commit | ------------------------------+--------------------------------------------- Changes (by mdawaffe): * status: new => assigned * owner: anonymous => mdawaffe -- Ticket URL: <http://trac.wordpress.org/ticket/3351#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 11 08:40:48 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 11 08:40:56 2006 Subject: [wp-trac] Re: [WordPress Trac] #3339: Mysql error while editing post In-Reply-To: <066.a07f205387e0a5a127bb5a6c59f03418@lists.automattic.com> References: <066.a07f205387e0a5a127bb5a6c59f03418@lists.automattic.com> Message-ID: <075.64b0587134e32ad498e76db4d7535a80@lists.automattic.com> #3339: Mysql error while editing post ----------------------------+----------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: major | Resolution: worksforme Keywords: | ----------------------------+----------------------------------------------- Comment (by tassoman): The problem was the Sitemap plugin at: http://www.arnebrachhold.de/2005/06/05/google-sitemaps-generator-v2-final -- Ticket URL: <http://trac.wordpress.org/ticket/3339#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 12 01:03:25 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 12 01:03:34 2006 Subject: [wp-trac] Re: [WordPress Trac] #3234: Feed inconsistencies when page_on_front and page_for_posts set In-Reply-To: <066.33c3e938ebac8961ec0b61b7f4eaf503@lists.automattic.com> References: <066.33c3e938ebac8961ec0b61b7f4eaf503@lists.automattic.com> Message-ID: <075.80b371b8121c818180d324f1a51088bb@lists.automattic.com> #3234: Feed inconsistencies when page_on_front and page_for_posts set -----------------------------------+---------------------------------------- Reporter: mdawaffe | Owner: mdawaffe Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: fixed Keywords: has-patch 2nd-opinion | -----------------------------------+---------------------------------------- Changes (by mdawaffe): * status: assigned => closed * resolution: => fixed Comment: I seem to have duplicated my own ticket. How embarrassing :) #3351 [4463] Marking as fixed with the caveat that I still don't know what www.example.com/feed shuld contain. -- Ticket URL: <http://trac.wordpress.org/ticket/3234#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 12 05:50:27 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 12 05:50:33 2006 Subject: [wp-trac] [WordPress Trac] #3352: Add scriptaculos drag-n-sort support for categories management Message-ID: <066.e6d8589fcf77b17d955c6150805f928d@lists.automattic.com> #3352: Add scriptaculos drag-n-sort support for categories management ----------------------------+----------------------------------------------- Reporter: tassoman | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Keywords: categories, ajax ----------------------------+----------------------------------------------- Would be so rock n roll adding drag n sort and inline editing for hierachical sorting and priority management of categories in administration? More, with inline name editing. [http://wiki.script.aculo.us/scriptaculous/show/GhostlySortableDemo | This is a demo], but not hierachical. Maybe a rewrite of the categories.php page ? -- Ticket URL: <http://trac.wordpress.org/ticket/3352> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 12 10:05:15 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 12 10:05:24 2006 Subject: [wp-trac] [WordPress Trac] #3353: Always ask for title attribute inserting links in normal editor Message-ID: <066.4b5087ed08f4291bb7529ead66203dc8@lists.automattic.com> #3353: Always ask for title attribute inserting links in normal editor ----------------------------+----------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Keywords: editor, links, accessibility ----------------------------+----------------------------------------------- I think for accessibility and future compatibility it would be better to force the default editor, not tinymce, to ask for title attribute of the link we're inserting. Until now it asks only for teh URI. -- Ticket URL: <http://trac.wordpress.org/ticket/3353> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 12 12:36:00 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 12 12:36:08 2006 Subject: [wp-trac] [WordPress Trac] #3354: PHP 5.2 & Fatal error in cache.php Message-ID: <066.5ee7e3cae8b01e9115acc642c7ec3c4d@lists.automattic.com> #3354: PHP 5.2 & Fatal error in cache.php -----------------------+---------------------------------------------------- Reporter: pulponair | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: General | Version: 2.0.5 Severity: blocker | Keywords: -----------------------+---------------------------------------------------- Since upgrading to php 5.2 i am constantly recieving the following error: PHP Fatal error: Call to a member function get() on a non-object in /var/www/xyz/htdocs/wp-includes/cache.php on line 28. This may be related to the object module changes applied in 5.2 since everthing worked fine using 5.1.6. The error occurs when surfing wordpress without beeing logged in. -- Ticket URL: <http://trac.wordpress.org/ticket/3354> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 12 15:32:34 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 12 15:32:42 2006 Subject: [wp-trac] [WordPress Trac] #3355: e-mail "mark as spam" link shows yes/no dialog even when comment is already spam Message-ID: <066.a6b68d805b0561fa7c64aa97ebbb0ab7@lists.automattic.com> #3355: e-mail "mark as spam" link shows yes/no dialog even when comment is already spam ----------------------------+----------------------------------------------- Reporter: markjaquith | Owner: anonymous Type: defect | Status: new Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: trivial | Keywords: comment spam ----------------------------+----------------------------------------------- Even if a comment is already marked as spam, clicking the "mark as spam" link from the e-mail prompts an AYS dialog. We should just gracefully exit with "This comment has already been marked as spam" message. -- Ticket URL: <http://trac.wordpress.org/ticket/3355> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 12 16:04:57 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 12 16:05:04 2006 Subject: [wp-trac] [WordPress Trac] #3356: FOAF xml support Message-ID: <066.a9136fe6df617edf27969976f51eab7b@lists.automattic.com> #3356: FOAF xml support ----------------------------+----------------------------------------------- Reporter: tandilboy | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Keywords: ----------------------------+----------------------------------------------- a good new feature is add FOAF support http://www.foaf-project.org/2004/web/index.html http://xmlns.com/foaf/0.1/ -- Ticket URL: <http://trac.wordpress.org/ticket/3356> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 12 19:34:00 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 12 19:34:08 2006 Subject: [wp-trac] [WordPress Trac] #3357: wp_die('GLOBALS overwrite attempt detected') before wp_die() included. Message-ID: <066.59adea11c37b51b98ebeeba8dee25036@lists.automattic.com> #3357: wp_die('GLOBALS overwrite attempt detected') before wp_die() included. -----------------------------+---------------------------------------------- Reporter: AlanJCastonguay | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: General | Version: 2.1 Severity: minor | Keywords: globals wp_die -----------------------------+---------------------------------------------- On line 8 of wp-settings.php, wp_die() is used to display a friendly error message if a key named GLOBALS is seen in the request array. Aka, someone is trying to inject variables into the global scope. 8: wp_die('GLOBALS overwrite attempt detected'); wp_die() is defined in WPINC/functions.php, which is required on line 130 of the same file. Thus, the call to wp_die() fails, as it is not yet defined. Should probably by reverted to die(), similar to changeset:4072 -- Ticket URL: <http://trac.wordpress.org/ticket/3357> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 13 17:13:02 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 13 17:13:17 2006 Subject: [wp-trac] Re: [WordPress Trac] #3306: saving post takes me to the wrong page In-Reply-To: <065.76c33b1764602f38912ffd78dfaeb747@lists.automattic.com> References: <065.76c33b1764602f38912ffd78dfaeb747@lists.automattic.com> Message-ID: <074.b124a43c652089b8b77648e13037b4a1@lists.automattic.com> #3306: saving post takes me to the wrong page ----------------------------+----------------------------------------------- Reporter: lschiere | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Resolution: worksforme Keywords: | ----------------------------+----------------------------------------------- Changes (by lschiere): * status: new => closed * resolution: => worksforme Comment: this has randomly disappeared without me having changed anything. Very odd. -- Ticket URL: <http://trac.wordpress.org/ticket/3306#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 13 17:38:01 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 13 17:38:26 2006 Subject: [wp-trac] Re: [WordPress Trac] #3357: wp_die('GLOBALS overwrite attempt detected') before wp_die() included. In-Reply-To: <066.59adea11c37b51b98ebeeba8dee25036@lists.automattic.com> References: <066.59adea11c37b51b98ebeeba8dee25036@lists.automattic.com> Message-ID: <075.4ef2d91a4be10a36471ab88339c6646a@lists.automattic.com> #3357: wp_die('GLOBALS overwrite attempt detected') before wp_die() included. -----------------------------+---------------------------------------------- Reporter: AlanJCastonguay | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: minor | Resolution: fixed Keywords: globals wp_die | -----------------------------+---------------------------------------------- Changes (by ryan): * milestone: => 2.1 -- Ticket URL: <http://trac.wordpress.org/ticket/3357#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 13 21:47:55 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 13 21:48:04 2006 Subject: [wp-trac] [WordPress Trac] #3358: Changing Sort Options in Admin Doesn't Work Message-ID: <066.d13dfc11feb5f3c15ec56ed5cf6eb7e7@lists.automattic.com> #3358: Changing Sort Options in Admin Doesn't Work ----------------------------+----------------------------------------------- Reporter: bryanveloso | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.5 Severity: normal | Keywords: ----------------------------+----------------------------------------------- I changed: {{{ wp('post_type=page&orderby=menu_order&what_to_show=posts&posts_per_page=-1&posts_per_archive_page=-1'); }}} to {{{ wp('post_type=page&orderby=post_title&what_to_show=posts&posts_per_page=-1&posts_per_archive_page=-1'); }}} because my fiance wanted her pages sorted as such, by post title. However, they don't sort by post title after I do this. The sorting mechanism just breaks altogether. I tried this with the SQL statement from 2.0.5, and that also didn't work when I changed it to sort by post title. -- Ticket URL: <http://trac.wordpress.org/ticket/3358> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 13 21:48:57 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 13 21:49:10 2006 Subject: [wp-trac] Re: [WordPress Trac] #3358: Changing Sort Options in Admin Doesn't Work In-Reply-To: <066.d13dfc11feb5f3c15ec56ed5cf6eb7e7@lists.automattic.com> References: <066.d13dfc11feb5f3c15ec56ed5cf6eb7e7@lists.automattic.com> Message-ID: <075.2e358053aca8cdcd8ccb8982684c3c26@lists.automattic.com> #3358: Changing Sort Options in Admin Doesn't Work ----------------------------+----------------------------------------------- Reporter: bryanveloso | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.5 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by bryanveloso): Oh, this line is #22 in edit-pages.php. -- Ticket URL: <http://trac.wordpress.org/ticket/3358#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 13 22:55:53 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 13 22:56:02 2006 Subject: [wp-trac] [WordPress Trac] #3359: Improved get_the_content() Function Message-ID: <066.ece71a488e960be4ea3dec8010b0d451@lists.automattic.com> #3359: Improved get_the_content() Function ----------------------------+----------------------------------------------- Reporter: iacas | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: Component: Administration | Version: 2.0.5 Severity: normal | Keywords: ----------------------------+----------------------------------------------- I believe WordPress could be enhanced by having a better "get_the_content();" function. I've written more about it here: http://nslog.com/2006/11/13/fixing_read_more_links_in_wordpress/ Essentially, I'd like WordPress to allow me to determine how the "Read More..." links are written. Either they could be included in the last sentence of the entry body's last paragraph (without a <br /> tag) or in their own paragraph. The current method produces ugly HTML that isn't very flexible for the user to work with via CSS or other styles. Sample code exists on my site, as does a proposed change to the "get_the_content()" function. I've written more in the URL above, so please have a look. -- Ticket URL: <http://trac.wordpress.org/ticket/3359> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 14 00:06:01 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 14 00:06:15 2006 Subject: [wp-trac] Re: [WordPress Trac] #3356: FOAF xml support In-Reply-To: <066.a9136fe6df617edf27969976f51eab7b@lists.automattic.com> References: <066.a9136fe6df617edf27969976f51eab7b@lists.automattic.com> Message-ID: <075.e3688f86d98fdae6355c8369db054731@lists.automattic.com> #3356: FOAF xml support ----------------------------+----------------------------------------------- Reporter: tandilboy | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Resolution: invalid Keywords: | ----------------------------+----------------------------------------------- Changes (by foolswisdom): * status: new => closed * resolution: => invalid Comment: Closing INVALID General bugs like this are not particularly useful. WordPress has chosen XFN over FOAF in blog roll / links. -- Ticket URL: <http://trac.wordpress.org/ticket/3356#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 14 01:25:23 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 14 01:25:33 2006 Subject: [wp-trac] Re: [WordPress Trac] #3188: Shouldn't use deprecated functions start_wp In-Reply-To: <044.eaf5fdb38ad397846321cda10f551945@lists.automattic.com> References: <044.eaf5fdb38ad397846321cda10f551945@lists.automattic.com> Message-ID: <053.f4d29e31fb36d4dc1db1cacf63af4a07@lists.automattic.com> #3188: Shouldn't use deprecated functions start_wp -------------------------+-------------------------------------------------- Reporter: foolswisdom | Owner: westi Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: fixed Keywords: has-patch | -------------------------+-------------------------------------------------- Comment (by ryan): Didn't include the export changes since the exporter needs to export posts of any status and not just publish. -- Ticket URL: <http://trac.wordpress.org/ticket/3188#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 14 04:13:24 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 14 04:13:31 2006 Subject: [wp-trac] Re: [WordPress Trac] #2525: Restructure wp-includes In-Reply-To: <066.9feb4589cdd04647a66633121ab9b6cb@lists.automattic.com> References: <066.9feb4589cdd04647a66633121ab9b6cb@lists.automattic.com> Message-ID: <075.7701fbdaffafb741ecf3d8b76e73ebe1@lists.automattic.com> #2525: Restructure wp-includes ----------------------------+----------------------------------------------- Reporter: ryan | Owner: ryan Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.1 Severity: normal | Resolution: fixed Keywords: includes | ----------------------------+----------------------------------------------- Changes (by ryan): * status: new => closed * resolution: => fixed -- Ticket URL: <http://trac.wordpress.org/ticket/2525#comment:23> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 14 06:15:16 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 14 06:15:21 2006 Subject: [wp-trac] Re: [WordPress Trac] #3349: wp-config pickup consistency fixes In-Reply-To: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> References: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> Message-ID: <075.ab8fc5b98172d877f2396da8ef84d92b@lists.automattic.com> #3349: wp-config pickup consistency fixes --------------------------+------------------------------------------------- Reporter: RuddO | Owner: markjaquith Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: 2nd-opinion | --------------------------+------------------------------------------------- Comment (by RuddO): foolswisdom: I based the ./ on the fact that some WP files already used it. it seems to work fine, whereas under some (admittedly not common, but possible) conditions, the famed dirname(__FILE__) fails. this patch does not introduce any usage of getcwd(). Only my FireStats patch (mailed to the author) did. As you say, getcwd() is not reliable, but it was the only way I could get FireStats to work, and the getcwd() mod went only into FireStats. -- Ticket URL: <http://trac.wordpress.org/ticket/3349#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 14 06:16:54 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 14 06:17:00 2006 Subject: [wp-trac] Re: [WordPress Trac] #2866: WP can't be used from a single source installation In-Reply-To: <066.f2e78ff058a89707ee2bc5bd5da9b67c@lists.automattic.com> References: <066.f2e78ff058a89707ee2bc5bd5da9b67c@lists.automattic.com> Message-ID: <075.81112fbe2e0b00f04d6c56750f0900c9@lists.automattic.com> #2866: WP can't be used from a single source installation -------------------------+-------------------------------------------------- Reporter: RuddO | Owner: anonymous Type: enhancement | Status: reopened Priority: normal | Milestone: Component: General | Version: Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Comment (by RuddO): westi: hardlinks can't be used because Subversion nukes them. Confirmed behavior. Anyway, I submitted this as a different bug because the newer bug is more to the point and the patch is more concise and doesn't have the drawbacks some pointed on this bug. Feel free to nuke this bug. -- Ticket URL: <http://trac.wordpress.org/ticket/2866#comment:17> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 14 06:19:35 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 14 06:19:42 2006 Subject: [wp-trac] Re: [WordPress Trac] #3349: wp-config pickup consistency fixes In-Reply-To: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> References: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> Message-ID: <075.f83d0a1bad6d416192b153a3b77e5d93@lists.automattic.com> #3349: wp-config pickup consistency fixes --------------------------+------------------------------------------------- Reporter: RuddO | Owner: markjaquith Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: 2nd-opinion | --------------------------+------------------------------------------------- Comment (by masquerade): The fact that we are breaking plugins like this one and maybe others that we don't know about is unacceptable. If getcwd is the only way something will work with this patch applied, thenI don't think it should be applied. -- Ticket URL: <http://trac.wordpress.org/ticket/3349#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 14 08:46:18 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 14 08:46:28 2006 Subject: [wp-trac] Re: [WordPress Trac] #3188: Shouldn't use deprecated functions start_wp In-Reply-To: <044.eaf5fdb38ad397846321cda10f551945@lists.automattic.com> References: <044.eaf5fdb38ad397846321cda10f551945@lists.automattic.com> Message-ID: <053.220520612f1285d14a4632323cc502a0@lists.automattic.com> #3188: Shouldn't use deprecated functions start_wp -------------------------+-------------------------------------------------- Reporter: foolswisdom | Owner: westi Type: defect | Status: reopened Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch | -------------------------+-------------------------------------------------- Changes (by westi): * status: closed => reopened * resolution: fixed => Comment: Replying to [comment:4 ryan]: > Didn't include the export changes since the exporter needs to export posts of any status and not just publish. I tried to fix this with the new query var for post_type=all I guess i missed the post_status check as well. I'll try and put up a patch to fix that one last occurrence by extending wp query to give us a way of getting every post/page back whatever the type /status -- Ticket URL: <http://trac.wordpress.org/ticket/3188#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 14 08:46:23 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 14 08:46:30 2006 Subject: [wp-trac] Re: [WordPress Trac] #3188: Shouldn't use deprecated functions start_wp In-Reply-To: <044.eaf5fdb38ad397846321cda10f551945@lists.automattic.com> References: <044.eaf5fdb38ad397846321cda10f551945@lists.automattic.com> Message-ID: <053.13632b2afb177e2e9c09c3484ca43a3c@lists.automattic.com> #3188: Shouldn't use deprecated functions start_wp -------------------------+-------------------------------------------------- Reporter: foolswisdom | Owner: westi Type: defect | Status: reopened Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by westi): * keywords: has-patch => -- Ticket URL: <http://trac.wordpress.org/ticket/3188#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 14 08:48:30 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 14 08:48:37 2006 Subject: [wp-trac] Re: [WordPress Trac] #739: View by days doesn't work In-Reply-To: <050.e9aacfcc3c93e79b2029996e3895c7e3@lists.automattic.com> References: <050.e9aacfcc3c93e79b2029996e3895c7e3@lists.automattic.com> Message-ID: <059.dfd65774b44c1a646e2c6a4f22d0ffb8@lists.automattic.com> #739: View by days doesn't work --------------------------+------------------------------------------------- Reporter: Technosailor | Owner: westi Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: General | Version: 1.5 Severity: major | Resolution: wontfix Keywords: bg|has-patch | --------------------------+------------------------------------------------- Changes (by westi): * status: assigned => closed * resolution: => wontfix Comment: [4457] Removed "view by days" -- Ticket URL: <http://trac.wordpress.org/ticket/739#comment:11> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 14 09:03:02 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 14 09:03:09 2006 Subject: [wp-trac] Re: [WordPress Trac] #3358: Changing Sort Options in Admin Doesn't Work In-Reply-To: <066.d13dfc11feb5f3c15ec56ed5cf6eb7e7@lists.automattic.com> References: <066.d13dfc11feb5f3c15ec56ed5cf6eb7e7@lists.automattic.com> Message-ID: <075.2caf01eab6b44dbd7e952783bdc783e7@lists.automattic.com> #3358: Changing Sort Options in Admin Doesn't Work ----------------------------+----------------------------------------------- Reporter: bryanveloso | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.5 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by westi): Looking at query.php (in trunk) you don't want to use {{{post_title}}} but just {{{title}}} here: The 'allowed' values are: {{{$allowed_keys = array('author', 'date', 'category', 'title', 'modified', 'menu_order');}}} The relavent code is [http://trac.wordpress.org/browser/trunk/wp- includes/query.php#L891 here] {{{ if ( 'menu_order' != $orderby ) $orderby = 'post_' . $orderby; }}} -- Ticket URL: <http://trac.wordpress.org/ticket/3358#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 14 12:13:07 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 14 12:13:23 2006 Subject: [wp-trac] Re: [WordPress Trac] #3349: wp-config pickup consistency fixes In-Reply-To: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> References: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> Message-ID: <075.8fd602ca647f566aeaf170de4a956e08@lists.automattic.com> #3349: wp-config pickup consistency fixes --------------------------+------------------------------------------------- Reporter: RuddO | Owner: markjaquith Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: 2nd-opinion | --------------------------+------------------------------------------------- Comment (by markjaquith): I think the FireStats issue was a result of him using Symlinks... not this change. Obviously I don't want anything going in that breaks plugins on normal installs. But if this leaves normal installs alone but allows more creative setups, I don't mind it. RuddO, can you clear up the reason for having to use getcwd() ? Because of symlinks or this patch? -- Ticket URL: <http://trac.wordpress.org/ticket/3349#comment:8> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 14 18:10:34 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 14 18:32:29 2006 Subject: [wp-trac] Re: [WordPress Trac] #2866: WP can't be used from a single source installation In-Reply-To: <066.f2e78ff058a89707ee2bc5bd5da9b67c@lists.automattic.com> References: <066.f2e78ff058a89707ee2bc5bd5da9b67c@lists.automattic.com> Message-ID: <075.e44e4ba30da698a75b0073efe43de0e0@lists.automattic.com> #2866: WP can't be used from a single source installation -------------------------+-------------------------------------------------- Reporter: RuddO | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: Component: General | Version: Severity: normal | Resolution: duplicate Keywords: | -------------------------+-------------------------------------------------- Changes (by foolswisdom): * status: reopened => closed * resolution: => duplicate Comment: Ask and you shall receive. Closing bug as DUPLICATE. Continued in ticket:3349 -- Ticket URL: <http://trac.wordpress.org/ticket/2866#comment:18> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 14 20:52:09 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 14 20:53:21 2006 Subject: [wp-trac] Re: [WordPress Trac] #3349: wp-config pickup consistency fixes In-Reply-To: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> References: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> Message-ID: <075.d20a2c9911b47277aaa4501d89fb2b13@lists.automattic.com> #3349: wp-config pickup consistency fixes --------------------------+------------------------------------------------- Reporter: RuddO | Owner: markjaquith Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: 2nd-opinion | --------------------------+------------------------------------------------- Comment (by JeremyVisser): Nothing to do with this particular issue, but the K2 Sidebar Modules broke for me as well, due to the fact that I symlinked the K2 theme directory from my blog to my Dad's blog and was wondering why the "K2 Sidebar Modules" option showed up on my blog, but not Dad's. A long time later, I realised it was because of the dreaded {{{__FILE__}}} which resolved the symlinks and broke the path names. -- Ticket URL: <http://trac.wordpress.org/ticket/3349#comment:9> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 14 23:11:25 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 14 23:11:34 2006 Subject: [wp-trac] [WordPress Trac] #3360: Inline Upload tweaks one last time Message-ID: <066.8a48a0f02f5ace47b099685e4a73d262@lists.automattic.com> #3360: Inline Upload tweaks one last time ----------------------------+----------------------------------------------- Reporter: mdawaffe | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Keywords: ----------------------------+----------------------------------------------- Attached: 1. Make things look purty. 1. Make scrolling work. 1. Fix annoying jumpiness when clicking JS generated links. 1. Allow object methods to define tabs (change function_exists to is_callable): props skeltoac. Tested in: 1. FF 1.5.0.8 1. FF 2 1. IE 7 1. IE 6 1. Opera 9.02 1. Safari 2.0.4 Need to bump version for upload JS -- Ticket URL: <http://trac.wordpress.org/ticket/3360> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 14 23:14:08 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 14 23:14:15 2006 Subject: [wp-trac] Re: [WordPress Trac] #3360: Inline Upload tweaks one last time In-Reply-To: <066.8a48a0f02f5ace47b099685e4a73d262@lists.automattic.com> References: <066.8a48a0f02f5ace47b099685e4a73d262@lists.automattic.com> Message-ID: <075.9c2b417b823426ebcc7aac9e9847c3ad@lists.automattic.com> #3360: Inline Upload tweaks one last time -----------------------------------+---------------------------------------- Reporter: mdawaffe | Owner: mdawaffe Type: defect | Status: assigned Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch 2nd-opinion | -----------------------------------+---------------------------------------- Changes (by mdawaffe): * keywords: => has-patch 2nd-opinion * status: new => assigned * version: => 2.1 * owner: anonymous => mdawaffe * milestone: => 2.1 -- Ticket URL: <http://trac.wordpress.org/ticket/3360#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 14 23:16:11 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 14 23:16:22 2006 Subject: [wp-trac] Re: [WordPress Trac] #3358: Changing Sort Options in Admin Doesn't Work In-Reply-To: <066.d13dfc11feb5f3c15ec56ed5cf6eb7e7@lists.automattic.com> References: <066.d13dfc11feb5f3c15ec56ed5cf6eb7e7@lists.automattic.com> Message-ID: <075.d170626077109824665cb2bb49b0b645@lists.automattic.com> #3358: Changing Sort Options in Admin Doesn't Work ----------------------------+----------------------------------------------- Reporter: bryanveloso | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.5 Severity: normal | Resolution: worksforme Keywords: | ----------------------------+----------------------------------------------- Changes (by bryanveloso): * status: new => closed * resolution: => worksforme Comment: Thanks westi. :) -- Ticket URL: <http://trac.wordpress.org/ticket/3358#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 14 23:19:05 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 14 23:19:12 2006 Subject: [wp-trac] Re: [WordPress Trac] #3194: Upload iframe does not scroll in all browsers In-Reply-To: <066.77b603b9f0eaf258c995a7621fbbd712@lists.automattic.com> References: <066.77b603b9f0eaf258c995a7621fbbd712@lists.automattic.com> Message-ID: <075.0649b41905c3dcc60e1a3bafc20650bf@lists.automattic.com> #3194: Upload iframe does not scroll in all browsers --------------------------------------------------+------------------------- Reporter: mdawaffe | Owner: mdawaffe Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: duplicate Keywords: CSS overflow has-patch needs-testing | --------------------------------------------------+------------------------- Changes (by mdawaffe): * status: assigned => closed * resolution: => duplicate Comment: #3360 -- Ticket URL: <http://trac.wordpress.org/ticket/3194#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 14 23:30:31 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 14 23:30:42 2006 Subject: [wp-trac] [WordPress Trac] #3361: `wp_list_bookmarks()` Should Be Widget Friendly Message-ID: <066.9d69e81367da9899426c8693c25785b7@lists.automattic.com> #3361: `wp_list_bookmarks()` Should Be Widget Friendly -------------------------+-------------------------------------------------- Reporter: bryanveloso | Owner: anonymous Type: defect | Status: new Priority: high | Milestone: 2.1 Component: Template | Version: 2.1 Severity: normal | Keywords: -------------------------+-------------------------------------------------- For the sake of widgets everywhere, this should be fixed. It has been a pain in the ass on WordPress.com. Whenever you call {{{wp_list_bookmarks()}}} it shows something like the following: {{{ <li id="linkcat-1356" class="linkcat"> <h2 class="widgettitle">Blogroll</h2> <ul> [...] </ul> </li> }}} So, when we're working with widgets, it is the only one that doesn't listen to any of the calls given to it (before_widget, after_widget, etc.) So even if a theme author has <div>s instead of a #sidebar <ul>, this <li> will still appear and ruin the styling and semantics. I'm all for standardizing the way that sidebars are done, but an effort like that is pretty much impossible. Everything should be widget friendly and flexible, this seems to be the only culprit. (Hopefully all of that made some sort of sense.) -- Ticket URL: <http://trac.wordpress.org/ticket/3361> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 15 08:34:33 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 15 08:34:42 2006 Subject: [wp-trac] Re: [WordPress Trac] #3361: `wp_list_bookmarks()` Should Be Widget Friendly In-Reply-To: <066.9d69e81367da9899426c8693c25785b7@lists.automattic.com> References: <066.9d69e81367da9899426c8693c25785b7@lists.automattic.com> Message-ID: <075.020b9af19304e584bbe00cbe18b5882b@lists.automattic.com> #3361: `wp_list_bookmarks()` Should Be Widget Friendly -------------------------+-------------------------------------------------- Reporter: bryanveloso | Owner: westi Type: defect | Status: assigned Priority: high | Milestone: 2.1 Component: Template | Version: 2.1 Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by westi): * status: new => assigned * owner: anonymous => westi Comment: I'll take this. I thought that you could use 'category_before' and 'category_after' to customise those? These are there defaults: {{{'category_before' => '<li id="%id" class="%class">'}}} {{{'category_after' => '</li>'}}} -- Ticket URL: <http://trac.wordpress.org/ticket/3361#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 16 02:43:28 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 16 02:43:34 2006 Subject: [wp-trac] Re: [WordPress Trac] #3361: `wp_list_bookmarks()` Should Be Widget Friendly In-Reply-To: <066.9d69e81367da9899426c8693c25785b7@lists.automattic.com> References: <066.9d69e81367da9899426c8693c25785b7@lists.automattic.com> Message-ID: <075.b6be5e79cc1328fd376cc3e37035cbef@lists.automattic.com> #3361: `wp_list_bookmarks()` Should Be Widget Friendly -------------------------+-------------------------------------------------- Reporter: bryanveloso | Owner: westi Type: defect | Status: assigned Priority: high | Milestone: 2.1 Component: Template | Version: 2.1 Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Comment (by bryanveloso): Well if you can do that, then it's not documented. :) I verified that it needed to be a core change with Matt and Andy, just never got to actually creating the ticket for it. I'll try this though, and see what it does. -- Ticket URL: <http://trac.wordpress.org/ticket/3361#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 16 20:46:58 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 16 20:47:24 2006 Subject: [wp-trac] [WordPress Trac] #3362: Missing <p> tag from <blockquote> (as well as extra <br /> sometimes) invalidates xhtml Message-ID: <066.6133ca12e7dd7d35d79259ce0cd6a43b@lists.automattic.com> #3362: Missing <p> tag from <blockquote> (as well as extra <br /> sometimes) invalidates xhtml ----------------------------+----------------------------------------------- Reporter: upekshapriya | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: 2.0.5 Severity: normal | Keywords: blockquote xhtml validation paragraph ----------------------------+----------------------------------------------- Wordpress 2.0.5 always seems to miss off the opening <p> tag inside a <blockquote> (and if it is embedded in text adds a <br /> tag before the <blockquote>) which invalidates XHTML The following text (with a break before the blockquote): Text before blockquote that goes on and on and on and on and on and on and on and on and on and on and on and on and on and on and on: <br /> <blockquote> "Text withing blockquote that also goes on and on and on and on and on and on and on and on and on." </blockquote> Text after block quote that doesn't go on and on.<br /> becomes: <p> Text before blockquote that goes on and on and on and on and on and on and on and on and on and on and on and on and on and on and on: <br /> <br /> <blockquote> "Text withing blockquote that also goes on and on and on and on and on and on and on and on and on." </p></blockquote> <p> Text after block quote that doesn’t go on and on. </p> With a blockquote at the beginning (and no break character before): <blockquote> "Text withing blockquote that also goes on and on and on and on and on and on and on and on and on." </blockquote> Text after block quote that doesn't go on and on. <br /> <br /> Just separated by some break characters becomes: <blockquote> "Text withing blockquote that also goes on and on and on and on and on and on and on and on and on." </p></blockquote> <p> Text after block quote that doesn’t go on and on. </p> <p> Just separated by some break characters </p> Text before blockquote (with a break before the quote): Text before blockquote that goes on and on and on and on and on and on and on and on and on and on and on and on and on and on and on: <br /> <blockquote> "Text withing blockquote that also goes on and on and on and on and on and on and on and on and on." </blockquote> becomes: <p> Text before blockquote that goes on and on and on and on and on and on and on and on and on and on and on and on and on and on and on: <br /> <br /> <blockquote> "Text withing blockquote that also goes on and on and on and on and on and on and on and on and on." </p></blockquote> Blockquote at the end (without a break before the quote): Text before blockquote that goes on and on and on and on and on and on and on and on and on and on and on and on and on and on and on: <blockquote> "Text withing blockquote that also goes on and on and on and on and on and on and on and on and on." </blockquote> becomes: <p> Text before blockquote that goes on and on and on and on and on and on and on and on and on and on and on and on and on and on and on:<br /> <blockquote> "Text withing blockquote that also goes on and on and on and on and on and on and on and on and on." </p></blockquote> Blockquote on its own: <blockquote> "Text withing blockquote that also goes on and on and on and on and on and on and on and on and on." </blockquote> becomes <blockquote> "Text withing blockquote that also goes on and on and on and on and on and on and on and on and on." </p></blockquote> -- Ticket URL: <http://trac.wordpress.org/ticket/3362> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 16 22:47:57 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 16 22:48:13 2006 Subject: [wp-trac] [WordPress Trac] #3363: <em> tags applied across line breaks produce invalid XHTML Message-ID: <066.89630fcf3e9ef3f833335a304a99e8c8@lists.automattic.com> #3363: <em> tags applied across line breaks produce invalid XHTML --------------------------+------------------------------------------------- Reporter: upekshapriya | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: General | Version: 2.0.5 Severity: normal | Keywords: --------------------------+------------------------------------------------- Putting break characters in the middle of <em> italicised text produces invalid XHTML. Wordpress appears to ignore the <em> </em> and treat them as ordinary characters. Some text before an italicised quote. <em> "Some text before a break character. <br /> <br /> Another paragraph that hardly ends.<br /> <br /> Lots more text that goes on and on." </em> becomes: <p> Some text before an italicised quote. <em> "Some text before a break character. </p> <p> Another paragraph that hardly ends.</p> <p> Lots more text that goes on and on." </em> </p> Some more<em> text separated by breaks not put in manually but</em> in the editor becomes: <p>Some more<em> text </p> <p>separated by breaks not put in manually but</em> in the editor </p> -- Ticket URL: <http://trac.wordpress.org/ticket/3363> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 16 22:48:59 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 16 22:49:20 2006 Subject: [wp-trac] Re: [WordPress Trac] #3362: Missing <p> tag from <blockquote> (as well as extra <br /> sometimes) invalidates xhtml In-Reply-To: <066.6133ca12e7dd7d35d79259ce0cd6a43b@lists.automattic.com> References: <066.6133ca12e7dd7d35d79259ce0cd6a43b@lists.automattic.com> Message-ID: <075.065200dd64cf80050145aff30e605fca@lists.automattic.com> #3362: Missing <p> tag from <blockquote> (as well as extra <br /> sometimes) invalidates xhtml ---------------------------------------------------+------------------------ Reporter: upekshapriya | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: General | Version: 2.0.5 Severity: normal | Resolution: Keywords: blockquote xhtml validation paragraph | ---------------------------------------------------+------------------------ Changes (by upekshapriya): * component: Administration => General -- Ticket URL: <http://trac.wordpress.org/ticket/3362#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 17 06:42:21 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 17 06:42:28 2006 Subject: [wp-trac] Re: [WordPress Trac] #2376: Custom 404 page error/conflict with permalinks In-Reply-To: <066.fd4119c8425defcb1c06a1db23286ac4@lists.automattic.com> References: <066.fd4119c8425defcb1c06a1db23286ac4@lists.automattic.com> Message-ID: <075.7deff650575676778206dade5d2ee1d9@lists.automattic.com> #2376: Custom 404 page error/conflict with permalinks -----------------------------------+---------------------------------------- Reporter: vsa | Owner: anonymous Type: defect | Status: reopened Priority: normal | Milestone: Component: General | Version: 2.0 Severity: normal | Resolution: Keywords: 404 custom permalinks | -----------------------------------+---------------------------------------- Changes (by aonicc): * status: closed => reopened * resolution: worksforme => Comment: I'm having the same issue. It seems like the mod_rewrite code is intercepting the "bad urls" and feeding them to index.php. Unfortunately, the only way to solve this is to have wordpress itself recognize bad urls (throw something in that checks to see if the GET parameters are valid posts?) and throw up a 404 on its own. any help on this? -- Ticket URL: <http://trac.wordpress.org/ticket/2376#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 17 07:36:44 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 17 07:36:53 2006 Subject: [wp-trac] Re: [WordPress Trac] #2376: Custom 404 page error/conflict with permalinks In-Reply-To: <066.fd4119c8425defcb1c06a1db23286ac4@lists.automattic.com> References: <066.fd4119c8425defcb1c06a1db23286ac4@lists.automattic.com> Message-ID: <075.61bb375fa4a44bf0c8b9739ec5cb40eb@lists.automattic.com> #2376: Custom 404 page error/conflict with permalinks -----------------------------------+---------------------------------------- Reporter: vsa | Owner: anonymous Type: defect | Status: reopened Priority: normal | Milestone: Component: General | Version: 2.0 Severity: normal | Resolution: Keywords: 404 custom permalinks | -----------------------------------+---------------------------------------- Comment (by RuddO): There's a simple explanation for this. The ErrorDocument stanza in Apache config files is not being executed. A better explanation: The default mod_rewrite stanzas that WordPress feeds into .htaccess say something that, translated in words, roughly means: "Hand every request to index.php for processing, *unless* it's a request for an existing file or directory". Thus, with permalinks enabled, any request for a page not found will go to the index.php file. Deep inside the guts of WP (class WP_Rewrite and class WP, to be exact) there's code to determine if the request was for a post that did not exist (which actually also covers the cases of nonexistant files or directories). When a request is received by WP and WP can't find data to send (posts, pages, etcetera), WP simply uses your _theme's_ 404.php file to display the error in the blog format, and sends it back to the user, along with a 404 Not Found status. So, in other words, ErrorDocument 404 stanzas will never work if you're also using permalinks. Got it? -- Ticket URL: <http://trac.wordpress.org/ticket/2376#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 17 07:38:50 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 17 07:38:56 2006 Subject: [wp-trac] Re: [WordPress Trac] #2376: Custom 404 page error/conflict with permalinks In-Reply-To: <066.fd4119c8425defcb1c06a1db23286ac4@lists.automattic.com> References: <066.fd4119c8425defcb1c06a1db23286ac4@lists.automattic.com> Message-ID: <075.5a5622824ac54407d4ea149c296334ec@lists.automattic.com> #2376: Custom 404 page error/conflict with permalinks -----------------------------------+---------------------------------------- Reporter: vsa | Owner: anonymous Type: defect | Status: reopened Priority: normal | Milestone: Component: General | Version: 2.0 Severity: normal | Resolution: Keywords: 404 custom permalinks | -----------------------------------+---------------------------------------- Comment (by RuddO): In other words, yet again, WP is the one responsible for throwing out nicely blog formatted 404 errors. -- Ticket URL: <http://trac.wordpress.org/ticket/2376#comment:8> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 17 07:40:25 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 17 07:40:32 2006 Subject: [wp-trac] Re: [WordPress Trac] #2376: Custom 404 page error/conflict with permalinks In-Reply-To: <066.fd4119c8425defcb1c06a1db23286ac4@lists.automattic.com> References: <066.fd4119c8425defcb1c06a1db23286ac4@lists.automattic.com> Message-ID: <075.ec0a874eb2e4466a5791c1504393ac89@lists.automattic.com> #2376: Custom 404 page error/conflict with permalinks -----------------------------------+---------------------------------------- Reporter: vsa | Owner: anonymous Type: defect | Status: reopened Priority: normal | Milestone: Component: General | Version: 2.0 Severity: normal | Resolution: Keywords: 404 custom permalinks | -----------------------------------+---------------------------------------- Comment (by RuddO): @martin_hoegh: sure would love you to provide an URL so we can diagnose the problem accurately. error_log and rewrite_log snips would also go a great way, as well as .htaccess and apache config dumps. -- Ticket URL: <http://trac.wordpress.org/ticket/2376#comment:9> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 17 07:42:06 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 17 07:42:13 2006 Subject: [wp-trac] Re: [WordPress Trac] #2376: Custom 404 page error/conflict with permalinks In-Reply-To: <066.fd4119c8425defcb1c06a1db23286ac4@lists.automattic.com> References: <066.fd4119c8425defcb1c06a1db23286ac4@lists.automattic.com> Message-ID: <075.8fe39cfa3a0344cced1a10a388ed8c2c@lists.automattic.com> #2376: Custom 404 page error/conflict with permalinks -----------------------------------+---------------------------------------- Reporter: vsa | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: General | Version: 2.0 Severity: normal | Resolution: invalid Keywords: 404 custom permalinks | -----------------------------------+---------------------------------------- Changes (by RuddO): * status: reopened => closed * resolution: => invalid Comment: Choose permalinks and edit your theme's 404.php page to provide the real 404 error message. -- Ticket URL: <http://trac.wordpress.org/ticket/2376#comment:10> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 17 12:17:49 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 17 12:18:01 2006 Subject: [wp-trac] Re: [WordPress Trac] #2376: Custom 404 page error/conflict with permalinks In-Reply-To: <066.fd4119c8425defcb1c06a1db23286ac4@lists.automattic.com> References: <066.fd4119c8425defcb1c06a1db23286ac4@lists.automattic.com> Message-ID: <075.d4ad6aeefa6ca38598292d042c518cbe@lists.automattic.com> #2376: Custom 404 page error/conflict with permalinks -----------------------------------+---------------------------------------- Reporter: vsa | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: General | Version: 2.0 Severity: normal | Resolution: invalid Keywords: 404 custom permalinks | -----------------------------------+---------------------------------------- Comment (by Viper007Bond): Or just put any rules you want ABOVE WordPress'. I have plenty of rules (including `ErrorDocument 404` one) running on my WordPress site and it works just fine with permalinks enabled. -- Ticket URL: <http://trac.wordpress.org/ticket/2376#comment:11> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 17 16:58:03 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 17 16:58:13 2006 Subject: [wp-trac] [WordPress Trac] #3364: Metadata db improvements Message-ID: <066.71eed7cd9d54c39a681131d98fd3de53@lists.automattic.com> #3364: Metadata db improvements --------------------------+------------------------------------------------- Reporter: dougal | Owner: dougal Type: enhancement | Status: new Priority: low | Milestone: 2.1 Component: Optimization | Version: 2.1 Severity: normal | Keywords: meta, metadata, postmeta, usermeta, catmeta, postcustom, custom --------------------------+------------------------------------------------- Some disussion on the bbPress bbDev mailing list came up about our implementation of postmeta (and of course the other metas, by extension). We currently have a schema that includes 4 fields: {{{meta_id}}}, {{{post_id}}}, {{{meta_key}}}, and {{{meta_value}}}. The {{{meta_id}}} key is really only needed because the {{{post_id}}}+{{{meta_key}}} combination is not unique. I originally designed it this way on purpose, to maximize the flexibility and simplicity of the system. However, if we made {{{post_id}}}+{{{meta_key}}} unique, it could improve the database performance for meta queries. Since the bbPress API is still more liquid, they are planning to go ahead and make this modification. Making a similar change in WP would not only improve the db optimization when fetching metadata, but would maintain consistency between the two sister applications. I think we can do this while maintaining the current API functions, because we already 'smush' duplicate keys in the database into a single cache key with an array of values. Basically, we want to make the database structure mimic the PHP data structure that we're already using. This should be pretty easy to do by just adding a little bit of automatic serialization/deserialization, and using REPLACE instead of INSERT in {{{add_post_meta()}}} and friends. The main concern here is whether it might break existing plugins. But I think we can make the change transparent to code that uses the API functions (rather than direct db queries). And even code that is using direct queries shouldn't require much change, just some magic serialization/deserialization on the values. I'm going to try to find time to work on patches for this, and maybe work up some test cases. In the meantime, I'd appreciate any feedback from anyone who has an opinion on this. -- Ticket URL: <http://trac.wordpress.org/ticket/3364> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 17 17:05:10 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 17 17:05:38 2006 Subject: [wp-trac] Re: [WordPress Trac] #3364: Metadata db improvements In-Reply-To: <066.71eed7cd9d54c39a681131d98fd3de53@lists.automattic.com> References: <066.71eed7cd9d54c39a681131d98fd3de53@lists.automattic.com> Message-ID: <075.db40d38001fb9ad5bbbe6d556c88ebde@lists.automattic.com> #3364: Metadata db improvements -----------------------------------------------------------------------------+ Reporter: dougal | Owner: dougal Type: enhancement | Status: new Priority: low | Milestone: 2.2 Component: Optimization | Version: 2.1 Severity: normal | Resolution: Keywords: meta, metadata, postmeta, usermeta, catmeta, postcustom, custom | -----------------------------------------------------------------------------+ Changes (by westi): * milestone: 2.1 => 2.2 Comment: This sounds like a good idea todo. Should it not be targetted for 2.2 rather than 2.1 though to allow more time for testing etc? -- Ticket URL: <http://trac.wordpress.org/ticket/3364#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 17 17:09:46 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 17 17:10:09 2006 Subject: [wp-trac] [WordPress Trac] #3365: Need to document standard keywords Message-ID: <066.05e0ed24c45b185dd1744a1fa213d626@lists.automattic.com> #3365: Need to document standard keywords ---------------------+------------------------------------------------------ Reporter: dougal | Owner: anonymous Type: task | Status: new Priority: low | Milestone: Component: General | Version: Severity: trivial | Keywords: trac, documentation, keywords, standards ---------------------+------------------------------------------------------ Could someone add a page to the Trac Wiki documenting the use of the various standard keywords (has-patch, needs-patch, needs-testing, etc)? I've lost track of which ones are used for vetting the tickets, and I always forget whether they're hyphenated or not, and things like that. -- Ticket URL: <http://trac.wordpress.org/ticket/3365> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 17 19:10:09 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 17 19:10:21 2006 Subject: [wp-trac] Re: [WordPress Trac] #3365: Need to document standard keywords In-Reply-To: <066.05e0ed24c45b185dd1744a1fa213d626@lists.automattic.com> References: <066.05e0ed24c45b185dd1744a1fa213d626@lists.automattic.com> Message-ID: <075.3c6b376d478d4986b202a89e6718ee12@lists.automattic.com> #3365: Need to document standard keywords ------------------------------------------------------+--------------------- Reporter: dougal | Owner: foolswisdom Type: task | Status: new Priority: low | Milestone: Component: General | Version: Severity: trivial | Resolution: Keywords: trac, documentation, keywords, standards | ------------------------------------------------------+--------------------- Changes (by foolswisdom): * owner: anonymous => foolswisdom -- Ticket URL: <http://trac.wordpress.org/ticket/3365#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 17 19:19:14 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 17 19:19:36 2006 Subject: [wp-trac] Re: [WordPress Trac] #2515: Select page to show as the front page In-Reply-To: <066.9c5d957c7f614e39504e6b8d47a4b20a@lists.automattic.com> References: <066.9c5d957c7f614e39504e6b8d47a4b20a@lists.automattic.com> Message-ID: <075.13135a90944d261f568c286170ca5eaa@lists.automattic.com> #2515: Select page to show as the front page ----------------------------+----------------------------------------------- Reporter: ryan | Owner: ryan Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.1 Severity: normal | Resolution: Keywords: page | ----------------------------+----------------------------------------------- Comment (by mdawaffe): 2515.diff 1. get_page_link() as before. 1. new _get_page_link() used internally when need to ignore page_on_front. -- Ticket URL: <http://trac.wordpress.org/ticket/2515#comment:29> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 17 20:27:12 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 17 20:27:38 2006 Subject: [wp-trac] [WordPress Trac] #3366: images in page titles in wp_list_pages() now appear as html text. Message-ID: <066.41b179598bc6c562cdb6a348e1b70652@lists.automattic.com> #3366: images in page titles in wp_list_pages() now appear as html text. ---------------------+------------------------------------------------------ Reporter: chigh | Owner: anonymous Type: defect | Status: new Priority: low | Milestone: Component: General | Version: 2.0.5 Severity: minor | Keywords: images wp_list_pages() pages ---------------------+------------------------------------------------------ This may not be considered a bug, but I did want to report this change of behaviour in 2.0.5. In previous versions of WP, I was able to place a small image in the title of a page. My example, I would place a small image (12x12) of a lock in the title of password protected pages. In 2.0.4 and prior, the image would be displayed in the list of pages and on the page. In 2.0.5, the behaviour changed. The image is displayed on the page itself and in some other locations, but NOT in the list of pages (such as in the sidebar on the front page - wp_list_pages() ). -- Ticket URL: <http://trac.wordpress.org/ticket/3366> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 17 21:21:48 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 17 21:22:09 2006 Subject: [wp-trac] [WordPress Trac] #3367: Proposed change Message-ID: <066.7f1ae5619b87852d87908f6b9a9e7fa1@lists.automattic.com> #3367: Proposed change ----------------------------+----------------------------------------------- Reporter: WillemGrooters | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: Component: Optimization | Version: 2.0.5 Severity: normal | Keywords: ----------------------------+----------------------------------------------- For having Wordpress run under OpenVMS, I would like to suggest a change to classes.php. lines 600-616: These lines contain a mixture of single and double quotes that the HP-PHP engine cannot handle. It's the only place where strings are delimited by single quotes, and values with double, like this (line 600) if ( $this->is_attachment ) { $where .= ' AND (post_status = "attachment")'; This causes errors in accessing MySQL via PHP; the very same problem arises when the SQL-command is issues within PHPMyAdmin, though MYSQL itself has no trouble with it. If this is changed so strings are delimited by double quotes and the values with single: if ( $this->is_attachment ) { $where .= " AND (post_status = 'attachment')"; the problems are over. Secondly, this is more consistent to the rest of the code, for what I have examined. -- Ticket URL: <http://trac.wordpress.org/ticket/3367> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 17 21:47:38 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 17 21:48:03 2006 Subject: [wp-trac] Re: [WordPress Trac] #2792: front page permalink discrepancy In-Reply-To: <066.9264eb88e17d970b29c7de89ef6c29f8@lists.automattic.com> References: <066.9264eb88e17d970b29c7de89ef6c29f8@lists.automattic.com> Message-ID: <075.8f142baa33b37e5f306d7110ef9a9cad@lists.automattic.com> #2792: front page permalink discrepancy -----------------------------+---------------------------------------------- Reporter: ryanscheuermann | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: duplicate Keywords: front page | -----------------------------+---------------------------------------------- Changes (by mdawaffe): * status: new => closed * resolution: => duplicate Comment: #2515 Not really a dup, but it's all over there. -- Ticket URL: <http://trac.wordpress.org/ticket/2792#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 17 22:08:34 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 17 22:09:03 2006 Subject: [wp-trac] Re: [WordPress Trac] #3367: Single quote around double quote mysql string breaks on OpenVMS HP-PHP In-Reply-To: <066.7f1ae5619b87852d87908f6b9a9e7fa1@lists.automattic.com> References: <066.7f1ae5619b87852d87908f6b9a9e7fa1@lists.automattic.com> Message-ID: <075.81584c2a76a77e2c058d34bde1c5768f@lists.automattic.com> #3367: Single quote around double quote mysql string breaks on OpenVMS HP-PHP ----------------------------+----------------------------------------------- Reporter: WillemGrooters | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.1 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by foolswisdom): * summary: Proposed change => Single quote around double quote mysql string breaks on OpenVMS HP-PHP * milestone: => 2.1 Comment: Hi Willem, thank you for participating in WordPress! "Proposed change" is a really lousy bug Summary. Next time please attach a patch (preferably also against trunk). I am working on patch now. -- Ticket URL: <http://trac.wordpress.org/ticket/3367#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 17 22:27:33 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 17 22:28:02 2006 Subject: [wp-trac] Re: [WordPress Trac] #3367: Single quote around double quote mysql string breaks on OpenVMS HP-PHP In-Reply-To: <066.7f1ae5619b87852d87908f6b9a9e7fa1@lists.automattic.com> References: <066.7f1ae5619b87852d87908f6b9a9e7fa1@lists.automattic.com> Message-ID: <075.7ddbefd799ca86a5c5ea794ed17c1356@lists.automattic.com> #3367: Single quote around double quote mysql string breaks on OpenVMS HP-PHP ----------------------------+----------------------------------------------- Reporter: WillemGrooters | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.0.5 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by foolswisdom): * milestone: 2.1 => 2.0.5 Comment: Problem does not exist in trunk, function is now in wp-includes/query.php and looks like the quotes have been fixed. No milestone 2.0.6, putting ms to 2.0.5 for now. -- Ticket URL: <http://trac.wordpress.org/ticket/3367#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 17 22:32:48 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 17 22:33:02 2006 Subject: [wp-trac] Re: [WordPress Trac] #3367: Single quote around double quote mysql string breaks on OpenVMS HP-PHP In-Reply-To: <066.7f1ae5619b87852d87908f6b9a9e7fa1@lists.automattic.com> References: <066.7f1ae5619b87852d87908f6b9a9e7fa1@lists.automattic.com> Message-ID: <075.d2cbf5c8b761bee5801c4886cc658181@lists.automattic.com> #3367: Single quote around double quote mysql string breaks on OpenVMS HP-PHP ---------------------------------------+------------------------------------ Reporter: WillemGrooters | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.0.5 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: has-patch maint-candidate | ---------------------------------------+------------------------------------ Changes (by foolswisdom): * keywords: => has-patch maint-candidate -- Ticket URL: <http://trac.wordpress.org/ticket/3367#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 17 22:43:24 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 17 22:43:44 2006 Subject: [wp-trac] Re: [WordPress Trac] #3367: Single quote around double quote mysql string breaks on OpenVMS HP-PHP In-Reply-To: <066.7f1ae5619b87852d87908f6b9a9e7fa1@lists.automattic.com> References: <066.7f1ae5619b87852d87908f6b9a9e7fa1@lists.automattic.com> Message-ID: <075.68f27af4cda98072af0f0b5263bb0553@lists.automattic.com> #3367: Single quote around double quote mysql string breaks on OpenVMS HP-PHP ----------------------------+----------------------------------------------- Reporter: WillemGrooters | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.0.6 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: has-patch | ----------------------------+----------------------------------------------- Changes (by foolswisdom): * keywords: has-patch maint-candidate => has-patch * milestone: 2.0.5 => 2.0.6 -- Ticket URL: <http://trac.wordpress.org/ticket/3367#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 17 23:13:16 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 02:22:28 2006 Subject: [wp-trac] Re: [WordPress Trac] #3225: Export file does not download in FF In-Reply-To: <066.c6ba1a3b130cbdb1bf3f267ce7680516@lists.automattic.com> References: <066.c6ba1a3b130cbdb1bf3f267ce7680516@lists.automattic.com> Message-ID: <075.da30e1a19313465baa83f8bfa3ce25de@lists.automattic.com> #3225: Export file does not download in FF ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: markjaquith Type: defect | Status: assigned Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch | ----------------------------+----------------------------------------------- Changes (by foolswisdom): * keywords: has-patch 2nd-opinion => has-patch Comment: Has been deployed on wordpress.com for about a week and no issues identified. Removing '2nd-opinion' keyword though opinions always welcome. -- Ticket URL: <http://trac.wordpress.org/ticket/3225#comment:10> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 03:03:57 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 03:04:08 2006 Subject: [wp-trac] [WordPress Trac] #3368: $wp_query->max_num_pages needs to be ceil()'d Message-ID: <066.ee5f8205f361be71451d9b8dfa15b4e1@lists.automattic.com> #3368: $wp_query->max_num_pages needs to be ceil()'d ----------------------+----------------------------------------------------- Reporter: MattRead | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Template | Version: 2.1 Severity: normal | Keywords: ----------------------+----------------------------------------------------- $wp_query->max_num_pages needs to be ceil()'ed cause it can return things like 1.6, which screw up the paging links, from next_posts_link() etc... I attach a diff for query.php -- Ticket URL: <http://trac.wordpress.org/ticket/3368> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 04:11:59 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 04:12:06 2006 Subject: [wp-trac] Re: [WordPress Trac] #3366: images in page titles in wp_list_pages() now appear as html text. In-Reply-To: <066.41b179598bc6c562cdb6a348e1b70652@lists.automattic.com> References: <066.41b179598bc6c562cdb6a348e1b70652@lists.automattic.com> Message-ID: <075.079160c6a7625fa75432f3ff9d98bc05@lists.automattic.com> #3366: images in page titles in wp_list_pages() now appear as html text. ------------------------------------------+--------------------------------- Reporter: chigh | Owner: anonymous Type: defect | Status: new Priority: low | Milestone: Component: General | Version: 2.0.5 Severity: minor | Resolution: Keywords: images wp_list_pages() pages | ------------------------------------------+--------------------------------- Comment (by JeremyVisser): Shouldn't you create a really simple plugin to filter the {{{the_title}}} filter when the post is protected? That would be a much better solution. +1 for making the behaviour of post title handling consistent, though. -- Ticket URL: <http://trac.wordpress.org/ticket/3366#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 05:05:01 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 05:05:08 2006 Subject: [wp-trac] [WordPress Trac] #3369: Hook for edit category page Message-ID: <066.3e07eb1d7ee25f4a22d92ed566f3247c@lists.automattic.com> #3369: Hook for edit category page ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Keywords: has-patch ----------------------------+----------------------------------------------- I need it for a plugin and why not? Doesn't hurt. :) One should be able to catch the results of any new fields via the existing `edit_category` hook I'd think. -- Ticket URL: <http://trac.wordpress.org/ticket/3369> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 06:06:46 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 06:06:53 2006 Subject: [wp-trac] Re: [WordPress Trac] #3248: Need way to replace WPDB error message In-Reply-To: <066.6a3fe69859b16ddb740687c068bc4cb3@lists.automattic.com> References: <066.6a3fe69859b16ddb740687c068bc4cb3@lists.automattic.com> Message-ID: <075.b00e7a4d5b745f70509fa21db0fb1773@lists.automattic.com> #3248: Need way to replace WPDB error message --------------------------+------------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: closed Priority: low | Milestone: 2.1 Component: General | Version: 2.1 Severity: minor | Resolution: wontfix Keywords: needs-patch | --------------------------+------------------------------------------------- Changes (by matt): * status: reopened => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/3248#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 06:07:21 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 06:07:28 2006 Subject: [wp-trac] Re: [WordPress Trac] #1956: Force unique category URIs In-Reply-To: <066.e39a135ccfdfdb6846781a38b70695ab@lists.automattic.com> References: <066.e39a135ccfdfdb6846781a38b70695ab@lists.automattic.com> Message-ID: <075.4c3f553f36d1e43485583d22a6be7a99@lists.automattic.com> #1956: Force unique category URIs -----------------------------------------+---------------------------------- Reporter: davidhouse | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 1.6 Severity: normal | Resolution: Keywords: categories has-patch commit | -----------------------------------------+---------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1956#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 06:07:32 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 06:07:39 2006 Subject: [wp-trac] Re: [WordPress Trac] #2027: Image Upload - Unwanted Thumbnail In-Reply-To: <066.a29801c45bb2481870f72add21eb18f8@lists.automattic.com> References: <066.a29801c45bb2481870f72add21eb18f8@lists.automattic.com> Message-ID: <075.1a19f44e4d44f8ac918257edf748a5d0@lists.automattic.com> #2027: Image Upload - Unwanted Thumbnail -----------------------------+---------------------------------------------- Reporter: YellowSwordfish | Owner: ryan Type: enhancement | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0 Severity: normal | Resolution: wontfix Keywords: | -----------------------------+---------------------------------------------- Changes (by matt): * status: new => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/2027#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 06:08:01 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 06:08:09 2006 Subject: [wp-trac] Re: [WordPress Trac] #1626: user_nicename should be unique In-Reply-To: <058.5b63244fcc200761a21788c4a554666b@lists.automattic.com> References: <058.5b63244fcc200761a21788c4a554666b@lists.automattic.com> Message-ID: <067.267fa71a4be74f748a7a8ca49ab38d84@lists.automattic.com> #1626: user_nicename should be unique -------------------------+-------------------------------------------------- Reporter: claudem | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: General | Version: 1.5.1.2 Severity: normal | Resolution: Keywords: needs-patch | -------------------------+-------------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1626#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 06:08:29 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 06:08:35 2006 Subject: [wp-trac] Re: [WordPress Trac] #3352: Add scriptaculos drag-n-sort support for categories management In-Reply-To: <066.e6d8589fcf77b17d955c6150805f928d@lists.automattic.com> References: <066.e6d8589fcf77b17d955c6150805f928d@lists.automattic.com> Message-ID: <075.ccaa73809c228e1dbf015249ae68038f@lists.automattic.com> #3352: Add scriptaculos drag-n-sort support for categories management ------------------------------+--------------------------------------------- Reporter: tassoman | Owner: anonymous Type: enhancement | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: wontfix Keywords: categories, ajax | ------------------------------+--------------------------------------------- Changes (by matt): * status: new => closed * resolution: => wontfix Comment: Not for now. -- Ticket URL: <http://trac.wordpress.org/ticket/3352#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 06:08:54 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 06:09:02 2006 Subject: [wp-trac] Re: [WordPress Trac] #2447: Database Upgrade requires too many clicks In-Reply-To: <066.fbb38e3fc5e1120763cbbd2d690b8c3f@lists.automattic.com> References: <066.fbb38e3fc5e1120763cbbd2d690b8c3f@lists.automattic.com> Message-ID: <075.5b0e1e364c1b82333d9dffeb83c50f1e@lists.automattic.com> #2447: Database Upgrade requires too many clicks -----------------------------------+---------------------------------------- Reporter: markjaquith | Owner: markjaquith Type: enhancement | Status: assigned Priority: low | Milestone: 2.2 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch 2nd-opinion | -----------------------------------+---------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2447#comment:9> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 06:12:01 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 06:12:12 2006 Subject: [wp-trac] Re: [WordPress Trac] #2699: Make option_name index unique In-Reply-To: <066.814043087edebb67a8efe6b00d7968de@lists.automattic.com> References: <066.814043087edebb67a8efe6b00d7968de@lists.automattic.com> Message-ID: <075.a0df0d4dc25844c6f54bb19966d9969e@lists.automattic.com> #2699: Make option_name index unique ------------------------------+--------------------------------------------- Reporter: johnjosephbachir | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.2 Component: Optimization | Version: 2.0.2 Severity: normal | Resolution: Keywords: has-patch | ------------------------------+--------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2699#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 07:00:11 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 07:00:18 2006 Subject: [wp-trac] [WordPress Trac] #3370: Do not have permission to add category. Message-ID: <066.70d47b11909d090da6f4f0afcfd8da92@lists.automattic.com> #3370: Do not have permission to add category. ----------------------------+----------------------------------------------- Reporter: computerwolf | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: 2.0.5 Severity: normal | Keywords: category permission adding ----------------------------+----------------------------------------------- Ever since upgrading from 2.0.4 to 2.0.5, whenever I attempt to add a category, I get the message, "You don't have permission to do that." when on the page to add a new post. I am the administrator and can add categories fine from the category area in the admin. I have already attempted a fresh install of 2.0.5, and still receive the error. -- Ticket URL: <http://trac.wordpress.org/ticket/3370> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 20:24:58 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 20:25:09 2006 Subject: [wp-trac] Re: [WordPress Trac] #3337: gettext string disambiguation In-Reply-To: <066.bb162066acc0fcd8d1503e887d6dd57b@lists.automattic.com> References: <066.bb162066acc0fcd8d1503e887d6dd57b@lists.automattic.com> Message-ID: <075.a61a8a5518c8988569b5213d56625b0d@lists.automattic.com> #3337: gettext string disambiguation ----------------------------+----------------------------------------------- Reporter: ryan | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: gettext i18n | ----------------------------+----------------------------------------------- Changes (by ryan): * milestone: 2.1 => 2.2 Comment: We changed some strings to make them unambiguous, so let's postpone this until we really need it. -- Ticket URL: <http://trac.wordpress.org/ticket/3337#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 20:27:20 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 20:27:38 2006 Subject: [wp-trac] Re: [WordPress Trac] #1329: Support for summer time / DST In-Reply-To: <044.4288b46692d6570bf16c999d4a0406d9@lists.automattic.com> References: <044.4288b46692d6570bf16c999d4a0406d9@lists.automattic.com> Message-ID: <053.b774f1578014bea1e8dcde792e1860b8@lists.automattic.com> #1329: Support for summer time / DST -----------------------------+---------------------------------------------- Reporter: anonymousbugger | Owner: ryan Type: enhancement | Status: assigned Priority: normal | Milestone: 2.2 Component: Administration | Version: 1.5.2 Severity: normal | Resolution: Keywords: DST | -----------------------------+---------------------------------------------- Changes (by ryan): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1329#comment:25> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 20:28:09 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 20:28:23 2006 Subject: [wp-trac] Re: [WordPress Trac] #2499: Rework Link Categories In-Reply-To: <066.8e320c7f55582e0ce536587009a7f88f@lists.automattic.com> References: <066.8e320c7f55582e0ce536587009a7f88f@lists.automattic.com> Message-ID: <075.ffe173831294ef9fa922066cca878143@lists.automattic.com> #2499: Rework Link Categories -----------------------------+---------------------------------------------- Reporter: ryan | Owner: ryan Type: defect | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.0.1 Severity: normal | Resolution: fixed Keywords: links has-patch | -----------------------------+---------------------------------------------- Changes (by ryan): * status: new => closed * resolution: => fixed Comment: Let's track further issues in separate bugs. Closing this one. -- Ticket URL: <http://trac.wordpress.org/ticket/2499#comment:40> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 20:30:03 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 20:30:10 2006 Subject: [wp-trac] Re: [WordPress Trac] #3347: Changeset 4455 - SELECT FOUND_ROWS() faster than count()? In-Reply-To: <066.cbd2be2649a6cf1b7a199e7bbfebad6d@lists.automattic.com> References: <066.cbd2be2649a6cf1b7a199e7bbfebad6d@lists.automattic.com> Message-ID: <075.c88d530e1034d7c441d1c8a4acdc7915@lists.automattic.com> #3347: Changeset 4455 - SELECT FOUND_ROWS() faster than count()? -------------------------+-------------------------------------------------- Reporter: alexkingorg | Owner: ryan Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by ryan): * status: new => closed * resolution: => fixed Comment: We're going to bump the MySQL requirement for 2.1. So far this is proving useful on wordpress.com. I'll resolve as fixed. -- Ticket URL: <http://trac.wordpress.org/ticket/3347#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 20:31:08 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 20:31:15 2006 Subject: [wp-trac] Re: [WordPress Trac] #3274: "Limit Posts to Category" breaks paging In-Reply-To: <066.9ccee3ae24318688ba14f4228568cf23@lists.automattic.com> References: <066.9ccee3ae24318688ba14f4228568cf23@lists.automattic.com> Message-ID: <075.bbc32dfd8b8d4c6a78eefd2cbd0ee0a1@lists.automattic.com> #3274: "Limit Posts to Category" breaks paging -------------------------+-------------------------------------------------- Reporter: alexkingorg | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by ryan): * status: new => closed * resolution: => fixed Comment: Fixed in a different fashion in [4455]. See #3347. -- Ticket URL: <http://trac.wordpress.org/ticket/3274#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 20:33:05 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 20:33:25 2006 Subject: [wp-trac] Re: [WordPress Trac] #3037: Styles & Code ( Make it beauty ) In-Reply-To: <066.143b2ef30f6447b16cc2cea0c3eb33c7@lists.automattic.com> References: <066.143b2ef30f6447b16cc2cea0c3eb33c7@lists.automattic.com> Message-ID: <075.636df204d33f44adbd85a08e68c0cdfc@lists.automattic.com> #3037: Styles & Code ( Make it beauty ) ----------------------------+----------------------------------------------- Reporter: Xmion | Owner: bryanveloso Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: Styles & Code | ----------------------------+----------------------------------------------- Changes (by ryan): * owner: ryan => bryanveloso -- Ticket URL: <http://trac.wordpress.org/ticket/3037#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 20:34:36 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 20:34:44 2006 Subject: [wp-trac] Re: [WordPress Trac] #3136: RTL Support In-Reply-To: <066.773b81c293cadf6803b137630011fd2d@lists.automattic.com> References: <066.773b81c293cadf6803b137630011fd2d@lists.automattic.com> Message-ID: <075.ad2c0955d415d976e7609278621eef40@lists.automattic.com> #3136: RTL Support ----------------------------+----------------------------------------------- Reporter: ryan | Owner: ryan Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: fixed Keywords: i18n RTL | ----------------------------+----------------------------------------------- Changes (by ryan): * status: reopened => closed * resolution: => fixed Comment: The basic framework is in. Let's handle further issues in separate bugs. Resolving this one. -- Ticket URL: <http://trac.wordpress.org/ticket/3136#comment:41> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 20:35:22 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 20:35:44 2006 Subject: [wp-trac] Re: [WordPress Trac] #2715: Future Posting Functionality Broken In-Reply-To: <066.111b14371636ef6c2c67e24117135217@lists.automattic.com> References: <066.111b14371636ef6c2c67e24117135217@lists.automattic.com> Message-ID: <075.1df5fe638b8a330b337d4395dd81e9af@lists.automattic.com> #2715: Future Posting Functionality Broken ----------------------------------------+----------------------------------- Reporter: bloodylamer | Owner: ryan Type: defect | Status: new Priority: high | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: major | Resolution: Keywords: future-posting future post | ----------------------------------------+----------------------------------- Comment (by ryan): Working okay for me now. Re-open if there are still issues. -- Ticket URL: <http://trac.wordpress.org/ticket/2715#comment:13> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 20:35:28 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 20:35:52 2006 Subject: [wp-trac] Re: [WordPress Trac] #2715: Future Posting Functionality Broken In-Reply-To: <066.111b14371636ef6c2c67e24117135217@lists.automattic.com> References: <066.111b14371636ef6c2c67e24117135217@lists.automattic.com> Message-ID: <075.d1cf7ebcfc32df162ccd265fc0452345@lists.automattic.com> #2715: Future Posting Functionality Broken ----------------------------------------+----------------------------------- Reporter: bloodylamer | Owner: ryan Type: defect | Status: closed Priority: high | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: major | Resolution: fixed Keywords: future-posting future post | ----------------------------------------+----------------------------------- Changes (by ryan): * status: new => closed * resolution: => fixed -- Ticket URL: <http://trac.wordpress.org/ticket/2715#comment:14> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 20:37:13 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 20:37:21 2006 Subject: [wp-trac] Re: [WordPress Trac] #3000: warning returned in xmlrpc.php on pingback In-Reply-To: <066.069221e870a10dbe540f5f20ba98ff8c@lists.automattic.com> References: <066.069221e870a10dbe540f5f20ba98ff8c@lists.automattic.com> Message-ID: <075.34d90fd8254f7e498295e79059f1f059@lists.automattic.com> #3000: warning returned in xmlrpc.php on pingback ---------------------+------------------------------------------------------ Reporter: _ck_ | Owner: ryan Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: XML-RPC | Version: 2.0 Severity: normal | Resolution: fixed Keywords: | ---------------------+------------------------------------------------------ Changes (by ryan): * status: new => closed * resolution: => fixed Comment: Should be fixed now. We were passing scalars instead of arrays in a few places. -- Ticket URL: <http://trac.wordpress.org/ticket/3000#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 21:44:13 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 21:44:24 2006 Subject: [wp-trac] [WordPress Trac] #3371: Request for additional $before and $after parameters to wp_list_cats() Message-ID: <066.4a62aad0beb4ab519051a72b8f07e378@lists.automattic.com> #3371: Request for additional $before and $after parameters to wp_list_cats() ------------------------+--------------------------------------------------- Reporter: vdzhuvinov | Owner: anonymous Type: defect | Status: new Priority: low | Milestone: 2.0.6 Component: Template | Version: 2.0.5 Severity: trivial | Keywords: ------------------------+--------------------------------------------------- Listing template functions such as get_archives() or get_links() normally include parameters to include custom HTML code before or after the listed items. I need a $before parameter because certain browsers still have poor support for the CSS :before directive and such a feature would circumvent this problem. [suggestion initially posted on the wp-hackers list] -- Ticket URL: <http://trac.wordpress.org/ticket/3371> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 21:44:39 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 21:44:54 2006 Subject: [wp-trac] Re: [WordPress Trac] #3371: Request for additional $before and $after parameters to wp_list_cats() In-Reply-To: <066.4a62aad0beb4ab519051a72b8f07e378@lists.automattic.com> References: <066.4a62aad0beb4ab519051a72b8f07e378@lists.automattic.com> Message-ID: <075.369f8bfac7f3ed0182904efb4c0dfb5d@lists.automattic.com> #3371: Request for additional $before and $after parameters to wp_list_cats() -------------------------+-------------------------------------------------- Reporter: vdzhuvinov | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.0.6 Component: Template | Version: 2.0.5 Severity: trivial | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by vdzhuvinov): * type: defect => enhancement -- Ticket URL: <http://trac.wordpress.org/ticket/3371#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 21:50:09 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 21:50:17 2006 Subject: [wp-trac] Re: [WordPress Trac] #3371: Request for additional $before and $after parameters to wp_list_cats() In-Reply-To: <066.4a62aad0beb4ab519051a72b8f07e378@lists.automattic.com> References: <066.4a62aad0beb4ab519051a72b8f07e378@lists.automattic.com> Message-ID: <075.2d372b23de5f9f0997a9397e9cc1faf9@lists.automattic.com> #3371: Request for additional $before and $after parameters to wp_list_cats() -------------------------+-------------------------------------------------- Reporter: vdzhuvinov | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.1 Component: Template | Version: 2.0.5 Severity: trivial | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by foolswisdom): * milestone: 2.0.6 => 2.1 Comment: Please look at the code in trunk (2.1) as some work as been done in wp_list_bookmarks which I think relates, but I am a novice. Does this relate to ticket:3361 ? -- Ticket URL: <http://trac.wordpress.org/ticket/3371#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 22:12:24 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 22:12:44 2006 Subject: [wp-trac] Re: [WordPress Trac] #3369: Hook for edit category page In-Reply-To: <066.3e07eb1d7ee25f4a22d92ed566f3247c@lists.automattic.com> References: <066.3e07eb1d7ee25f4a22d92ed566f3247c@lists.automattic.com> Message-ID: <075.9a4315329a3fd67ba4d19a72eb781b93@lists.automattic.com> #3369: Hook for edit category page ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: duplicate Keywords: has-patch | ----------------------------+----------------------------------------------- Changes (by Viper007Bond): * status: new => closed * resolution: => duplicate Comment: #2717 -- Ticket URL: <http://trac.wordpress.org/ticket/3369#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 22:14:10 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 22:14:19 2006 Subject: [wp-trac] Re: [WordPress Trac] #2717: categories.php - Add edit form hook In-Reply-To: <066.9add21c3da4269c57d18cabc8507d566@lists.automattic.com> References: <066.9add21c3da4269c57d18cabc8507d566@lists.automattic.com> Message-ID: <075.bccb57134df285d7c50a9340bd1bba26@lists.automattic.com> #2717: categories.php - Add edit form hook ----------------------------+----------------------------------------------- Reporter: seek3r | Owner: ryan Type: enhancement | Status: reopened Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.2 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by Viper007Bond): * status: closed => reopened * type: defect => enhancement * resolution: fixed => Comment: I agree with seek3r that the hook would be better placed before the submit button, ideally right before the `</table>` so that it matches the other inputs. -- Ticket URL: <http://trac.wordpress.org/ticket/2717#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 23:48:11 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 23:48:20 2006 Subject: [wp-trac] Re: [WordPress Trac] #2717: categories.php - Add edit form hook In-Reply-To: <066.9add21c3da4269c57d18cabc8507d566@lists.automattic.com> References: <066.9add21c3da4269c57d18cabc8507d566@lists.automattic.com> Message-ID: <075.b17253cb9629dcd9fa7e150b7b250ae7@lists.automattic.com> #2717: categories.php - Add edit form hook ----------------------------+----------------------------------------------- Reporter: seek3r | Owner: ryan Type: enhancement | Status: reopened Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.2 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by ryan): All of our form hooks are below the fold. -- Ticket URL: <http://trac.wordpress.org/ticket/2717#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 23:49:55 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 23:50:05 2006 Subject: [wp-trac] Re: [WordPress Trac] #2717: categories.php - Add edit form hook In-Reply-To: <066.9add21c3da4269c57d18cabc8507d566@lists.automattic.com> References: <066.9add21c3da4269c57d18cabc8507d566@lists.automattic.com> Message-ID: <075.a888f6ea1659c10fab64ae8ab0e6e66f@lists.automattic.com> #2717: categories.php - Add edit form hook ----------------------------+----------------------------------------------- Reporter: seek3r | Owner: ryan Type: enhancement | Status: reopened Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.2 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by ryan): True about the table though. Hmmmm... -- Ticket URL: <http://trac.wordpress.org/ticket/2717#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 23:50:31 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 23:50:37 2006 Subject: [wp-trac] Re: [WordPress Trac] #3371: Request for additional $before and $after parameters to wp_list_cats() In-Reply-To: <066.4a62aad0beb4ab519051a72b8f07e378@lists.automattic.com> References: <066.4a62aad0beb4ab519051a72b8f07e378@lists.automattic.com> Message-ID: <075.3c6bed87c68f2e8d92ee47e3d06c28e3@lists.automattic.com> #3371: Request for additional $before and $after parameters to wp_list_cats() -------------------------+-------------------------------------------------- Reporter: vdzhuvinov | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.1 Component: Template | Version: 2.0.5 Severity: trivial | Resolution: Keywords: | -------------------------+-------------------------------------------------- Comment (by ryan): Something similar can be done here, yes. -- Ticket URL: <http://trac.wordpress.org/ticket/3371#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 18 23:56:17 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 18 23:56:26 2006 Subject: [wp-trac] Re: [WordPress Trac] #3354: PHP 5.2 & Fatal error in cache.php In-Reply-To: <066.5ee7e3cae8b01e9115acc642c7ec3c4d@lists.automattic.com> References: <066.5ee7e3cae8b01e9115acc642c7ec3c4d@lists.automattic.com> Message-ID: <075.591fa0cd4342655390eb617629bc97fc@lists.automattic.com> #3354: PHP 5.2 & Fatal error in cache.php -----------------------+---------------------------------------------------- Reporter: pulponair | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: General | Version: 2.0.5 Severity: blocker | Resolution: Keywords: | -----------------------+---------------------------------------------------- Comment (by ryan): See http://bugs.php.net/bug.php?id=39381 -- Ticket URL: <http://trac.wordpress.org/ticket/3354#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 19 00:08:27 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 19 00:08:37 2006 Subject: [wp-trac] Re: [WordPress Trac] #3225: Export file does not download in FF In-Reply-To: <066.c6ba1a3b130cbdb1bf3f267ce7680516@lists.automattic.com> References: <066.c6ba1a3b130cbdb1bf3f267ce7680516@lists.automattic.com> Message-ID: <075.b6cb028824e0f2e8f278214193e7c134@lists.automattic.com> #3225: Export file does not download in FF --------------------------------+------------------------------------------- Reporter: Viper007Bond | Owner: markjaquith Type: defect | Status: reopened Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: 2nd-opinion export | --------------------------------+------------------------------------------- Changes (by random): * keywords: has-patch => 2nd-opinion export * status: closed => reopened * resolution: fixed => Comment: As posted [http://comox.textdrive.com/pipermail/wp-hackers/2006- November/009583.html at wp-hackers], I don't think `text/wxr+xml` is a good choice of media type. I'd recommend something like `application/prs.wordpress.export+xml`. (Or `application/vnd.automattic.wxr+xml`, or whatever. There are plenty of options.) For background, check out [http://tools.ietf.org/html/rfc4288 RFC4288] and the [http://www.iana.org/assignments/media-types/ IANA media type registry]. -- Ticket URL: <http://trac.wordpress.org/ticket/3225#comment:12> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 19 00:54:18 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 19 00:54:25 2006 Subject: [wp-trac] Re: [WordPress Trac] #2696: add_menu_page doesn't respect "access level". In-Reply-To: <066.f28c2c1a554a999a26be0e3403878f38@lists.automattic.com> References: <066.f28c2c1a554a999a26be0e3403878f38@lists.automattic.com> Message-ID: <075.1aea8ba38f1ac16a69588da9413f4d8b@lists.automattic.com> #2696: add_menu_page doesn't respect "access level". ----------------------------+----------------------------------------------- Reporter: denney | Owner: westi Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: fixed Keywords: bg|needs-patch | ----------------------------+----------------------------------------------- Changes (by ryan): * status: reopened => closed * resolution: => fixed * milestone: => 2.1 -- Ticket URL: <http://trac.wordpress.org/ticket/2696#comment:12> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 19 01:00:27 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 19 01:00:42 2006 Subject: [wp-trac] Re: [WordPress Trac] #3320: Comments page should have paging In-Reply-To: <066.7e80bc195f5d58e823dbb16d1225c390@lists.automattic.com> References: <066.7e80bc195f5d58e823dbb16d1225c390@lists.automattic.com> Message-ID: <075.81ee5cf9ebe56995a934999b261b439d@lists.automattic.com> #3320: Comments page should have paging ----------------------------+----------------------------------------------- Reporter: matt | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.5 Severity: normal | Resolution: fixed Keywords: | ----------------------------+----------------------------------------------- Changes (by ryan): * status: new => closed * version: => 2.0.5 * resolution: => fixed Comment: [4479] -- Ticket URL: <http://trac.wordpress.org/ticket/3320#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 19 01:09:12 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 19 01:09:20 2006 Subject: [wp-trac] Re: [WordPress Trac] #2717: categories.php - Add edit form hook In-Reply-To: <066.9add21c3da4269c57d18cabc8507d566@lists.automattic.com> References: <066.9add21c3da4269c57d18cabc8507d566@lists.automattic.com> Message-ID: <075.dccf3858e970a1b69e13894b293f953d@lists.automattic.com> #2717: categories.php - Add edit form hook ----------------------------+----------------------------------------------- Reporter: seek3r | Owner: ryan Type: enhancement | Status: reopened Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.2 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by Viper007Bond): I just ended up doing adding in my input via `ob_start()`. Easier and I needed it to work with v2.0.x. But anyway, yeah, I do agree that hooks should usually be outta the way, but the only point of that hook is to add new fields, so therefore it should be where new fields would usually go IMO. -- Ticket URL: <http://trac.wordpress.org/ticket/2717#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 19 01:18:56 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 19 01:19:13 2006 Subject: [wp-trac] Re: [WordPress Trac] #3267: PHP Error in template-functions-links.php In-Reply-To: <066.97b86b0b408bf07c28238df7bab36379@lists.automattic.com> References: <066.97b86b0b408bf07c28238df7bab36379@lists.automattic.com> Message-ID: <075.5fff9fc619fc8aebf63559218ec129bc@lists.automattic.com> #3267: PHP Error in template-functions-links.php -------------------------+-------------------------------------------------- Reporter: Mike_Koepke | Owner: markjaquith Type: defect | Status: closed Priority: high | Milestone: 2.1 Component: General | Version: 2.0.5 Severity: normal | Resolution: fixed Keywords: commit | -------------------------+-------------------------------------------------- Changes (by ryan): * status: assigned => closed * version: 2.0.4 => 2.0.5 * resolution: => fixed Comment: [4487], [4486], [4460] -- Ticket URL: <http://trac.wordpress.org/ticket/3267#comment:13> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 19 01:19:15 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 19 01:19:23 2006 Subject: [wp-trac] Re: [WordPress Trac] #3267: PHP Error in template-functions-links.php In-Reply-To: <066.97b86b0b408bf07c28238df7bab36379@lists.automattic.com> References: <066.97b86b0b408bf07c28238df7bab36379@lists.automattic.com> Message-ID: <075.f7c74a4bdf3149507e3770c52b5bca87@lists.automattic.com> #3267: PHP Error in template-functions-links.php -------------------------+-------------------------------------------------- Reporter: Mike_Koepke | Owner: markjaquith Type: defect | Status: closed Priority: high | Milestone: 2.0.6 Component: General | Version: 2.0.4 Severity: normal | Resolution: fixed Keywords: commit | -------------------------+-------------------------------------------------- Changes (by ryan): * milestone: 2.0.5 => 2.0.6 -- Ticket URL: <http://trac.wordpress.org/ticket/3267#comment:15> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 19 01:19:08 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 19 01:19:38 2006 Subject: [wp-trac] Re: [WordPress Trac] #3267: PHP Error in template-functions-links.php In-Reply-To: <066.97b86b0b408bf07c28238df7bab36379@lists.automattic.com> References: <066.97b86b0b408bf07c28238df7bab36379@lists.automattic.com> Message-ID: <075.dc79932d72bc36203380ca7ffa15be7b@lists.automattic.com> #3267: PHP Error in template-functions-links.php -------------------------+-------------------------------------------------- Reporter: Mike_Koepke | Owner: markjaquith Type: defect | Status: closed Priority: high | Milestone: 2.0.5 Component: General | Version: 2.0.4 Severity: normal | Resolution: fixed Keywords: commit | -------------------------+-------------------------------------------------- Changes (by ryan): * version: 2.0.5 => 2.0.4 * milestone: 2.1 => 2.0.5 -- Ticket URL: <http://trac.wordpress.org/ticket/3267#comment:14> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 19 01:23:49 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 19 01:23:57 2006 Subject: [wp-trac] Re: [WordPress Trac] #3224: wp-admin/upload-js.php uninternationalized In-Reply-To: <066.9f375b9d287c5c48f15ed6f4aee950b2@lists.automattic.com> References: <066.9f375b9d287c5c48f15ed6f4aee950b2@lists.automattic.com> Message-ID: <075.88ef229e773c9b3b8ad35eb96ba5b90e@lists.automattic.com> #3224: wp-admin/upload-js.php uninternationalized -----------------------------------+---------------------------------------- Reporter: nbachiyski | Owner: markjaquith Type: defect | Status: assigned Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch 2nd-opinion | -----------------------------------+---------------------------------------- Comment (by ryan): Also, let's include raquo in the gettext. -- Ticket URL: <http://trac.wordpress.org/ticket/3224#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 19 01:24:54 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 19 01:25:02 2006 Subject: [wp-trac] Re: [WordPress Trac] #3215: Login & Update functions everything is broken In-Reply-To: <049.6066b63c1044229dd67a636989ac05fd@lists.automattic.com> References: <049.6066b63c1044229dd67a636989ac05fd@lists.automattic.com> Message-ID: <058.64d7c20a49e5753475ae78d8d959b103@lists.automattic.com> #3215: Login & Update functions everything is broken --------------------------------------------+------------------------------- Reporter: Xmion | Owner: markjaquith Type: defect | Status: assigned Priority: highest | Milestone: 2.0.6 Component: General | Version: 2.1 Severity: critical | Resolution: Keywords: Blank page 302 maint-candidate | --------------------------------------------+------------------------------- Changes (by ryan): * milestone: 2.1 => 2.0.6 -- Ticket URL: <http://trac.wordpress.org/ticket/3215#comment:16> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 19 01:27:28 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 19 01:27:39 2006 Subject: [wp-trac] Re: [WordPress Trac] #3181: i18n issue in quicktags In-Reply-To: <066.816e0ecc22e8ccc628d96b279905694c@lists.automattic.com> References: <066.816e0ecc22e8ccc628d96b279905694c@lists.automattic.com> Message-ID: <075.646026c11a5e77e15aa5004f0719c0a9@lists.automattic.com> #3181: i18n issue in quicktags --------------------------------------+------------------------------------- Reporter: Nazgul | Owner: Sewar Type: defect | Status: assigned Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: Keywords: i18n quicktags has-patch | --------------------------------------+------------------------------------- Comment (by ryan): Use js_escape() instead of addslashes for escaping inside JS. -- Ticket URL: <http://trac.wordpress.org/ticket/3181#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 19 01:33:03 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 19 01:33:12 2006 Subject: [wp-trac] Re: [WordPress Trac] #3104: Selected categories should always be at top In-Reply-To: <066.6f6cb8980164036e40305e2e374e50de@lists.automattic.com> References: <066.6f6cb8980164036e40305e2e374e50de@lists.automattic.com> Message-ID: <075.a2d5a34a32cdfb537afb738ef0b53a02@lists.automattic.com> #3104: Selected categories should always be at top ----------------------------+----------------------------------------------- Reporter: matt | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by ryan): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/3104#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 19 01:34:56 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 19 01:35:04 2006 Subject: [wp-trac] Re: [WordPress Trac] #3065: Ampersand in URL patch (needed as rss validation failed in a syndicated blog) In-Reply-To: <066.4a8363d6de54789f194ddeaa8397901d@lists.automattic.com> References: <066.4a8363d6de54789f194ddeaa8397901d@lists.automattic.com> Message-ID: <075.5c208d72aebf560fb82e7a6c206397a4@lists.automattic.com> #3065: Ampersand in URL patch (needed as rss validation failed in a syndicated blog) ----------------------------+----------------------------------------------- Reporter: murky | Owner: anonymous Type: defect | Status: reopened Priority: normal | Milestone: 2.1 Component: Administration | Version: Severity: normal | Resolution: Keywords: has-patch | ----------------------------+----------------------------------------------- Changes (by ryan): * milestone: => 2.1 -- Ticket URL: <http://trac.wordpress.org/ticket/3065#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 19 03:40:07 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 19 03:46:09 2006 Subject: [wp-trac] Re: [WordPress Trac] #2980: Improvements to wptexturize In-Reply-To: <066.eadfc5956a95ef5fd98df2bad037e851@lists.automattic.com> References: <066.eadfc5956a95ef5fd98df2bad037e851@lists.automattic.com> Message-ID: <075.bdc5df1abfe4117eb19d148d75dd6065@lists.automattic.com> #2980: Improvements to wptexturize ----------------------------------+----------------------------------------- Reporter: ecb29 | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.2 Component: Optimization | Version: 2.0.3 Severity: normal | Resolution: Keywords: wptexturize optimize | ----------------------------------+----------------------------------------- Comment (by ecb29): It should be equivalent to the old function, as far as I can tell. -- Ticket URL: <http://trac.wordpress.org/ticket/2980#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 19 04:39:23 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 19 04:39:33 2006 Subject: [wp-trac] [WordPress Trac] #3372: Consolidated JavaScript/CSS Plugin API Message-ID: <066.3822605294f4b937960fe980ff535512@lists.automattic.com> #3372: Consolidated JavaScript/CSS Plugin API -----------------------------+---------------------------------------------- Reporter: robertaccettura | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: Component: Optimization | Version: Severity: normal | Keywords: -----------------------------+---------------------------------------------- WordPress plugins are great, they really are. One problem with them is they often include their own styles and scripts. The problem here is that several plugins with useful features mean a browser needs to download 10+ javascripts and stylesheets. This isn't good for page load. It's awful. See: http://www.die.net/musings/page_load_time/ My suggestion would be an API that allows all plugin/css to be included in 1 PHP generated CSS and Javascript. This would drastically consolidate requests. For performance reasons it should ideally be cached so that it's only regenerated when a plugin is loaded/reloaded. This is becoming a bigger issue as plugins become more common and useful. I hope a solution is found that gives plugin authors the freedom they need, and blog owners the performance they want, without having to sacrifice features. I think channeling all the requests into 1 JS and 1 CSS file would achieve that. They could use a numerical ranking system to calculate position in the file (to avoid conflicts) similar to how (iirc) filter work. -- Ticket URL: <http://trac.wordpress.org/ticket/3372> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 19 04:51:14 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 19 04:51:26 2006 Subject: [wp-trac] Re: [WordPress Trac] #3372: Consolidated JavaScript/CSS Plugin API In-Reply-To: <066.3822605294f4b937960fe980ff535512@lists.automattic.com> References: <066.3822605294f4b937960fe980ff535512@lists.automattic.com> Message-ID: <075.489df63dbfe81afec6f93fd021ee7faa@lists.automattic.com> #3372: Consolidated JavaScript/CSS Plugin API -----------------------------+---------------------------------------------- Reporter: robertaccettura | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.2 Component: Optimization | Version: 2.1 Severity: minor | Resolution: Keywords: | -----------------------------+---------------------------------------------- Changes (by Viper007Bond): * priority: normal => low * version: => 2.1 * severity: normal => minor * milestone: => 2.2 Comment: Not a bad idea IMO, but large changes such as this are best discussed via the [http://codex.wordpress.org/Mailing_Lists#Hackers wp-hackers mailing list] first. Much easier to discuss, propose solutions, etc. :) -- Ticket URL: <http://trac.wordpress.org/ticket/3372#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 19 08:00:24 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 19 08:00:44 2006 Subject: [wp-trac] Re: [WordPress Trac] #2267: '%' in comment author's URLs is incorrectly stripped out. In-Reply-To: <066.8c41e05da61d60abadc1c63ba3e13f49@lists.automattic.com> References: <066.8c41e05da61d60abadc1c63ba3e13f49@lists.automattic.com> Message-ID: <075.b43f1639288694b1c2f032963462a832@lists.automattic.com> #2267: '%' in comment author's URLs is incorrectly stripped out. ---------------------------------------------------------+------------------ Reporter: gzfelix@gmail.com | Owner: anonymous Type: defect | Status: new Priority: high | Milestone: 2.0.5 Component: General | Version: 2.0.5 Severity: normal | Resolution: Keywords: has-patch 2nd-opinion dev-feedback security | ---------------------------------------------------------+------------------ Changes (by ryan): * version: 2.0 => 2.0.5 * milestone: 2.1 => 2.0.5 Comment: Fixed awhile ago. -- Ticket URL: <http://trac.wordpress.org/ticket/2267#comment:8> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 19 08:12:06 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 19 08:12:17 2006 Subject: [wp-trac] Re: [WordPress Trac] #3016: 1970 time for page drafts In-Reply-To: <066.a196c80bed5e3a926e39bead713f410d@lists.automattic.com> References: <066.a196c80bed5e3a926e39bead713f410d@lists.automattic.com> Message-ID: <075.71b026eec8bb4ba345ca4500cc19c32a@lists.automattic.com> #3016: 1970 time for page drafts ----------------------------+----------------------------------------------- Reporter: markjaquith | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: fixed Keywords: has-patch | ----------------------------+----------------------------------------------- Changes (by ryan): * status: new => closed * resolution: => fixed Comment: [4491] -- Ticket URL: <http://trac.wordpress.org/ticket/3016#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 19 12:19:31 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 19 12:19:53 2006 Subject: [wp-trac] Re: [WordPress Trac] #3371: Request for additional $before and $after parameters to wp_list_cats() In-Reply-To: <066.4a62aad0beb4ab519051a72b8f07e378@lists.automattic.com> References: <066.4a62aad0beb4ab519051a72b8f07e378@lists.automattic.com> Message-ID: <075.979fccc319abaf0b55bea743c98bf175@lists.automattic.com> #3371: Request for additional $before and $after parameters to wp_list_cats() -------------------------+-------------------------------------------------- Reporter: vdzhuvinov | Owner: westi Type: enhancement | Status: assigned Priority: low | Milestone: 2.1 Component: Template | Version: 2.0.5 Severity: trivial | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by westi): * status: new => assigned * owner: anonymous => westi Comment: We can easyily add wp_list_bookmarks alike $before and $after support to wp_list_categories in trunk (wp_list_cats is deprecated). However, for now you may be able to get what you want by adding style=none to the arguments for the function call. The before and after li tags are toggled by this: http://trac.wordpress.org/browser/trunk/wp-includes/category- template.php#L231 {{{ if ( $title_li && 'list' == $style ) $output = '<li class="categories">' . $r['title_li'] . '<ul>'; }}} And http://trac.wordpress.org/browser/trunk/wp-includes/category- template.php#L250 {{{ if ( $title_li && 'list' == $style ) $output .= '</ul></li>'; }}} I'll add the before and after support to my todo list. -- Ticket URL: <http://trac.wordpress.org/ticket/3371#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 19 14:13:30 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 19 14:14:25 2006 Subject: [wp-trac] [WordPress Trac] #3373: Better get_page_uri Message-ID: <066.1cbeb52aa6774f154bd62f5af9b204bc@lists.automattic.com> #3373: Better get_page_uri -----------------------------+---------------------------------------------- Reporter: ryanscheuermann | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Optimization | Version: 2.1 Severity: normal | Keywords: get_page_uri -----------------------------+---------------------------------------------- Upon testing the queries on some of my sites, I found that there were a LOT more queries for pages that were deeper/farther down in the page hierarchy. I am using get_page_link to get the link for pages on the navigation. This function calls get_page_uri which in turn calls get_page over and over until it builds the tree. When you call get_page, you run a SELECT * FROM wp_posts query. List all your pages, and you've now SELECT *'d every single page. I've attached a patch that builds the hierarchy from 1 query instead of multiple. -- Ticket URL: <http://trac.wordpress.org/ticket/3373> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 19 14:24:58 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 19 14:25:29 2006 Subject: [wp-trac] Re: [WordPress Trac] #3373: Better get_page_uri In-Reply-To: <066.1cbeb52aa6774f154bd62f5af9b204bc@lists.automattic.com> References: <066.1cbeb52aa6774f154bd62f5af9b204bc@lists.automattic.com> Message-ID: <075.44330fa2abbb0880b8116821e5b633fa@lists.automattic.com> #3373: Better get_page_uri -----------------------------+---------------------------------------------- Reporter: ryanscheuermann | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: get_page_uri | -----------------------------+---------------------------------------------- Changes (by ryanscheuermann): * version: 2.1 => 2.0.5 Comment: This ticket could also be modified and applied to 2.0.6. I've attached that patch also. -- Ticket URL: <http://trac.wordpress.org/ticket/3373#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 20 00:27:24 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 20 00:27:33 2006 Subject: [wp-trac] Re: [WordPress Trac] #3372: Consolidated JavaScript/CSS Plugin API In-Reply-To: <066.3822605294f4b937960fe980ff535512@lists.automattic.com> References: <066.3822605294f4b937960fe980ff535512@lists.automattic.com> Message-ID: <075.2cec9abd4ca13d8d771aafbbc549851f@lists.automattic.com> #3372: Consolidated JavaScript/CSS Plugin API -----------------------------+---------------------------------------------- Reporter: robertaccettura | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.2 Component: Optimization | Version: 2.1 Severity: minor | Resolution: Keywords: | -----------------------------+---------------------------------------------- Comment (by RuddO): This is a GREAT idea! And it would also free plugin writers from having to do the wp- content/plugins/plugin_basename(__FILE__) chicanery. All that's needed, in my opinion, would be functions "plugin_add_css", "plugin_add_js", and then on wp_head() WP can inject an URL that points to an internal file which releases the added CSS and JS. This function could be loaded as part of the plugin initialization trigger (can't recall its name right now). This has definitive advantages to feeding JS and CSS inline on wp_head() directly. Note that, due to the nature of the requests, it's impossible to make distinctions based on which page the reader is visiting, because the custom CSS and JS is released to the browser separately from the original request. -- Ticket URL: <http://trac.wordpress.org/ticket/3372#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 20 00:30:12 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 20 00:30:22 2006 Subject: [wp-trac] Re: [WordPress Trac] #3372: Consolidated JavaScript/CSS Plugin API In-Reply-To: <066.3822605294f4b937960fe980ff535512@lists.automattic.com> References: <066.3822605294f4b937960fe980ff535512@lists.automattic.com> Message-ID: <075.0f98febe239b85c9ab4952ccc31afff1@lists.automattic.com> #3372: Consolidated JavaScript/CSS Plugin API -----------------------------+---------------------------------------------- Reporter: robertaccettura | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.2 Component: Optimization | Version: 2.1 Severity: minor | Resolution: Keywords: | -----------------------------+---------------------------------------------- Comment (by foolswisdom): robertaccettura, thanks for participating in WordPress! I love what you have done with Mozilla particularly Report a Website. Viper007Bond suggestion is a good one, variations of this topic have come up before, but like Mozilla's Bugzilla having an enhancement ticket seldom moves the idea into implementation, so please don't let that frustrate you or leave it at that. -- Ticket URL: <http://trac.wordpress.org/ticket/3372#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 20 01:28:03 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 20 01:28:09 2006 Subject: [wp-trac] Re: [WordPress Trac] #3372: Consolidated JavaScript/CSS Plugin API In-Reply-To: <066.3822605294f4b937960fe980ff535512@lists.automattic.com> References: <066.3822605294f4b937960fe980ff535512@lists.automattic.com> Message-ID: <075.e1d2b412dcb350f9ea57a7826d41b2cb@lists.automattic.com> #3372: Consolidated JavaScript/CSS Plugin API -----------------------------+---------------------------------------------- Reporter: robertaccettura | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.2 Component: Optimization | Version: 2.1 Severity: minor | Resolution: Keywords: | -----------------------------+---------------------------------------------- Comment (by ryan): 2.1 has a script loader API. http://trac.wordpress.org/browser/trunk/wp-includes/script-loader.php It doesn't group scripts into one big script, however. Extending it to do that probably wouldn't be too hard, though, if someone wants to take a crack at it. -- Ticket URL: <http://trac.wordpress.org/ticket/3372#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 20 01:36:48 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 20 01:36:57 2006 Subject: [wp-trac] Re: [WordPress Trac] #2366: uploading fails with safe_mode turned In-Reply-To: <066.b9babd7dcb51b3cc80e537a01b5b3ac3@lists.automattic.com> References: <066.b9babd7dcb51b3cc80e537a01b5b3ac3@lists.automattic.com> Message-ID: <075.db160b36a962de021c78a1641f93dd9e@lists.automattic.com> #2366: uploading fails with safe_mode turned -------------------------------+-------------------------------------------- Reporter: BjornW | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Administration | Version: 2.0 Severity: normal | Resolution: fixed Keywords: upload, safe_mode | -------------------------------+-------------------------------------------- Changes (by ryan): * status: new => closed * resolution: => fixed Comment: I think we worked around all of the safe_mode problems. Resolving. -- Ticket URL: <http://trac.wordpress.org/ticket/2366#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 20 01:38:57 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 20 01:39:07 2006 Subject: [wp-trac] Re: [WordPress Trac] #2408: Next/Previous page links get messed up if a plugin makes certain changes to the WP_Query->request In-Reply-To: <066.974694682b1c7658d8fddce6d0a0f580@lists.automattic.com> References: <066.974694682b1c7658d8fddce6d0a0f580@lists.automattic.com> Message-ID: <075.328fb60c07d579db30e9ed1a2b185539@lists.automattic.com> #2408: Next/Previous page links get messed up if a plugin makes certain changes to the WP_Query->request --------------------------------------------------------+------------------- Reporter: isaacschlueter | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: General | Version: 2.0.1 Severity: normal | Resolution: fixed Keywords: WP_Query, plugin, next page link, bug, fix | --------------------------------------------------------+------------------- Changes (by ryan): * status: new => closed * resolution: => fixed * milestone: => 2.1 Comment: We've redone how max_num_pages is computed and removed paging by days, so this should be fixed. -- Ticket URL: <http://trac.wordpress.org/ticket/2408#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 20 01:39:55 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 20 01:40:05 2006 Subject: [wp-trac] Re: [WordPress Trac] #2657: No way to show next 20 comments in edit-comments.php In-Reply-To: <066.62a52a5b61c893a2b0d221be85ecfdd1@lists.automattic.com> References: <066.62a52a5b61c893a2b0d221be85ecfdd1@lists.automattic.com> Message-ID: <075.b52238bfdd1ae768cb06804aef4ba67d@lists.automattic.com> #2657: No way to show next 20 comments in edit-comments.php ----------------------------+----------------------------------------------- Reporter: rwh | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: fixed Keywords: bg|has-patch | ----------------------------+----------------------------------------------- Changes (by ryan): * status: new => closed * resolution: => fixed * milestone: => 2.1 Comment: Fixed in 2.1. -- Ticket URL: <http://trac.wordpress.org/ticket/2657#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 20 01:42:49 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 20 01:42:56 2006 Subject: [wp-trac] Re: [WordPress Trac] #2754: get_comment_time / get_comment_date filter should pass the format string In-Reply-To: <066.298e9ee535a86a168c6214b6c14acd23@lists.automattic.com> References: <066.298e9ee535a86a168c6214b6c14acd23@lists.automattic.com> Message-ID: <075.4d872f5587f8984c9053357f1548b483@lists.automattic.com> #2754: get_comment_time / get_comment_date filter should pass the format string ---------------------+------------------------------------------------------ Reporter: sdiz | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: | ---------------------+------------------------------------------------------ Changes (by ryan): * milestone: => 2.1 -- Ticket URL: <http://trac.wordpress.org/ticket/2754#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 20 01:53:50 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 20 01:53:59 2006 Subject: [wp-trac] Re: [WordPress Trac] #3323: Admin menu shows item user can't use In-Reply-To: <066.a4f7c2523a6d08894d604715adef6bf7@lists.automattic.com> References: <066.a4f7c2523a6d08894d604715adef6bf7@lists.automattic.com> Message-ID: <075.79ae06e2030e80248189b22b9991fd91@lists.automattic.com> #3323: Admin menu shows item user can't use ----------------------------+----------------------------------------------- Reporter: ovgray | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: Severity: normal | Resolution: fixed Keywords: | ----------------------------+----------------------------------------------- Changes (by ryan): * status: new => closed * resolution: => fixed * milestone: => 2.1 Comment: Hopefully fixed by [4481]. -- Ticket URL: <http://trac.wordpress.org/ticket/3323#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 20 02:05:14 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 20 02:05:22 2006 Subject: [wp-trac] Re: [WordPress Trac] #2980: Improvements to wptexturize In-Reply-To: <066.eadfc5956a95ef5fd98df2bad037e851@lists.automattic.com> References: <066.eadfc5956a95ef5fd98df2bad037e851@lists.automattic.com> Message-ID: <075.0e824f5a7d0cd023cb2c48442e42da4f@lists.automattic.com> #2980: Improvements to wptexturize ----------------------------------+----------------------------------------- Reporter: ecb29 | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.2 Component: Optimization | Version: 2.0.3 Severity: normal | Resolution: Keywords: wptexturize optimize | ----------------------------------+----------------------------------------- Comment (by ryan): The first six items in static_characters and static_replacements look like they should be swapped. -- Ticket URL: <http://trac.wordpress.org/ticket/2980#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 20 04:05:01 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 20 04:05:09 2006 Subject: [wp-trac] Re: [WordPress Trac] #3312: Capital Z in HTML editor triggers new line In-Reply-To: <066.2fe574f41a0a824c470e1babc14e7e5b@lists.automattic.com> References: <066.2fe574f41a0a824c470e1babc14e7e5b@lists.automattic.com> Message-ID: <075.9f3803c8b7bf662092954a6fa85891c2@lists.automattic.com> #3312: Capital Z in HTML editor triggers new line -------------------------------------+-------------------------------------- Reporter: foolswisdom | Owner: andy Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: fixed Keywords: has-patch needs-testing | -------------------------------------+-------------------------------------- Changes (by ryan): * status: new => closed * resolution: => fixed Comment: [4501] -- Ticket URL: <http://trac.wordpress.org/ticket/3312#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 20 13:45:42 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 20 13:46:02 2006 Subject: [wp-trac] [WordPress Trac] #3374: img tags cant validates in w3c validator Message-ID: <066.5834ca4d599b467831225713c20bc68e@lists.automattic.com> #3374: img tags cant validates in w3c validator ----------------------------+----------------------------------------------- Reporter: tandilboy | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Keywords: ----------------------------+----------------------------------------------- the img tags generated by the wordpress image uploader is not w3c valid -- Ticket URL: <http://trac.wordpress.org/ticket/3374> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 20 13:49:56 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 20 13:50:23 2006 Subject: [wp-trac] [WordPress Trac] #3375: delay between ping Message-ID: <066.2129c617c51d65dbcd44298548abb07f@lists.automattic.com> #3375: delay between ping ----------------------------+----------------------------------------------- Reporter: tandilboy | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Keywords: ----------------------------+----------------------------------------------- i have a low capacity hosting. when i add more than 5 ping servers and post a new the server shows "500 Internal server Error" a good idea is a 1 or 2 seconds delay between server ping to avoid hosting overloads -- Ticket URL: <http://trac.wordpress.org/ticket/3375> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 20 14:02:34 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 20 14:02:51 2006 Subject: [wp-trac] [WordPress Trac] #3376: option to publish in RSS feeds or not Message-ID: <066.ab0f8a1330d6dfcb64ac7766a6cdf400@lists.automattic.com> #3376: option to publish in RSS feeds or not ----------------------------+----------------------------------------------- Reporter: tandilboy | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Keywords: ----------------------------+----------------------------------------------- a good new feature is add the option to publish the post in RSS feeds or not -- Ticket URL: <http://trac.wordpress.org/ticket/3376> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 20 19:16:37 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 20 19:16:47 2006 Subject: [wp-trac] Re: [WordPress Trac] #3354: PHP 5.2 & Fatal error in cache.php In-Reply-To: <066.5ee7e3cae8b01e9115acc642c7ec3c4d@lists.automattic.com> References: <066.5ee7e3cae8b01e9115acc642c7ec3c4d@lists.automattic.com> Message-ID: <075.c5d48f756584a55399bf8cf0b1888c7e@lists.automattic.com> #3354: PHP 5.2 & Fatal error in cache.php -----------------------+---------------------------------------------------- Reporter: pulponair | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: General | Version: 2.0.5 Severity: blocker | Resolution: Keywords: | -----------------------+---------------------------------------------------- Comment (by pulponair): Temporary fix : wp-includes/cache.php Line 28: {{{ if (!is_object($wp_object_cache)) { $wp_object_cache = new WP_Object_Cache(); } }}} wp-includes/cache.php Line 187: {{{ if (!is_object($wpdb)) { $wpdb = new wpdb(DB_USER, DB_PASSWORD, DB_NAME, DB_HOST); } }}} quick n dirty but working. -- Ticket URL: <http://trac.wordpress.org/ticket/3354#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 00:08:10 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 00:08:22 2006 Subject: [wp-trac] Re: [WordPress Trac] #2511: multi site support In-Reply-To: <066.7c801615b915ca803b560c74259c4b88@lists.automattic.com> References: <066.7c801615b915ca803b560c74259c4b88@lists.automattic.com> Message-ID: <075.73d32d5b6e6bfad8bd57e41ff97a6de2@lists.automattic.com> #2511: multi site support -------------------------+-------------------------------------------------- Reporter: pietrus | Owner: anonymous Type: enhancement | Status: closed Priority: lowest | Milestone: Component: General | Version: 2.0.1 Severity: normal | Resolution: wontfix Keywords: | -------------------------+-------------------------------------------------- Changes (by foolswisdom): * milestone: 2.5 => -- Ticket URL: <http://trac.wordpress.org/ticket/2511#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 00:10:23 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 00:10:33 2006 Subject: [wp-trac] Re: [WordPress Trac] #2948: validation error anchor "theme" already defined In-Reply-To: <066.0567ad61b037f1aef6ec2f9100022075@lists.automattic.com> References: <066.0567ad61b037f1aef6ec2f9100022075@lists.automattic.com> Message-ID: <075.9b6e2f7b65563ee3e741837d8bd80a54@lists.automattic.com> #2948: validation error anchor "theme" already defined ----------------------------+----------------------------------------------- Reporter: vizualbod | Owner: anonymous Type: defect | Status: closed Priority: lowest | Milestone: Component: Administration | Version: 2.0.3 Severity: normal | Resolution: worksforme Keywords: | ----------------------------+----------------------------------------------- Changes (by foolswisdom): * milestone: 2.2 => -- Ticket URL: <http://trac.wordpress.org/ticket/2948#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 00:10:48 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 00:10:55 2006 Subject: [wp-trac] Re: [WordPress Trac] #2462: Feed for pages feeds the content not the comments In-Reply-To: <066.510ba696d221e4f01c8147deadf4f05a@lists.automattic.com> References: <066.510ba696d221e4f01c8147deadf4f05a@lists.automattic.com> Message-ID: <075.0cb080e55948521d1bbfa8c5742e3593@lists.automattic.com> #2462: Feed for pages feeds the content not the comments ---------------------+------------------------------------------------------ Reporter: leflo | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: General | Version: 1.2 Severity: normal | Resolution: fixed Keywords: | ---------------------+------------------------------------------------------ Changes (by foolswisdom): * milestone: 2.2 => -- Ticket URL: <http://trac.wordpress.org/ticket/2462#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 00:11:05 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 00:11:16 2006 Subject: [wp-trac] Re: [WordPress Trac] #3280: Addition of an "Auto Line Breaks" toggle. In-Reply-To: <066.73852f0cf2e621ce86dcf72ee88f87bb@lists.automattic.com> References: <066.73852f0cf2e621ce86dcf72ee88f87bb@lists.automattic.com> Message-ID: <075.77f89d1520f4aad01422fb38033d0ae7@lists.automattic.com> #3280: Addition of an "Auto Line Breaks" toggle. -------------------------+-------------------------------------------------- Reporter: bryanveloso | Owner: markjaquith Type: enhancement | Status: closed Priority: normal | Milestone: Component: General | Version: Severity: normal | Resolution: wontfix Keywords: | -------------------------+-------------------------------------------------- Changes (by foolswisdom): * milestone: 2.2 => -- Ticket URL: <http://trac.wordpress.org/ticket/3280#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 00:11:16 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 00:11:25 2006 Subject: [wp-trac] Re: [WordPress Trac] #3313: "Under Maintenance" Page In-Reply-To: <066.e2bc9819eec5d749ce042c301cea25d3@lists.automattic.com> References: <066.e2bc9819eec5d749ce042c301cea25d3@lists.automattic.com> Message-ID: <075.d5a455e32ba8ad5fcbdf352949a86e6c@lists.automattic.com> #3313: "Under Maintenance" Page -------------------------+-------------------------------------------------- Reporter: bryanveloso | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: Component: General | Version: Severity: normal | Resolution: wontfix Keywords: | -------------------------+-------------------------------------------------- Changes (by foolswisdom): * milestone: 2.2 => -- Ticket URL: <http://trac.wordpress.org/ticket/3313#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 01:22:50 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 01:23:00 2006 Subject: [wp-trac] Re: [WordPress Trac] #3374: img tags cant validates in w3c validator In-Reply-To: <066.5834ca4d599b467831225713c20bc68e@lists.automattic.com> References: <066.5834ca4d599b467831225713c20bc68e@lists.automattic.com> Message-ID: <075.a151144de9bea77160aa8800820e5939@lists.automattic.com> #3374: img tags cant validates in w3c validator ----------------------------+----------------------------------------------- Reporter: tandilboy | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Resolution: worksforme Keywords: | ----------------------------+----------------------------------------------- Changes (by JeremyVisser): * status: new => closed * resolution: => worksforme Comment: It is completely valid on my end. Can you provide more information, and an example of a tag that it generated invalidly (!?) ? -- Ticket URL: <http://trac.wordpress.org/ticket/3374#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 08:33:45 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 08:33:53 2006 Subject: [wp-trac] Re: [WordPress Trac] #3376: option to publish in RSS feeds or not In-Reply-To: <066.ab0f8a1330d6dfcb64ac7766a6cdf400@lists.automattic.com> References: <066.ab0f8a1330d6dfcb64ac7766a6cdf400@lists.automattic.com> Message-ID: <075.32154017e144005d0231086ff90993fa@lists.automattic.com> #3376: option to publish in RSS feeds or not -------------------------+-------------------------------------------------- Reporter: tandilboy | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.1 Component: General | Version: 2.1 Severity: minor | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by Viper007Bond): * priority: normal => low * version: => 2.1 * component: Administration => General * severity: normal => minor * milestone: => 2.1 Comment: Probably best handled by a plugin since this would be used by few people. I'll leave it open though and let others weigh in. -- Ticket URL: <http://trac.wordpress.org/ticket/3376#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 10:13:08 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 10:13:17 2006 Subject: [wp-trac] Re: [WordPress Trac] #3376: option to publish in RSS feeds or not In-Reply-To: <066.ab0f8a1330d6dfcb64ac7766a6cdf400@lists.automattic.com> References: <066.ab0f8a1330d6dfcb64ac7766a6cdf400@lists.automattic.com> Message-ID: <075.0582e300f7728772e4442e6464e8adc5@lists.automattic.com> #3376: option to publish in RSS feeds or not -------------------------+-------------------------------------------------- Reporter: tandilboy | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.1 Component: General | Version: 2.1 Severity: minor | Resolution: Keywords: | -------------------------+-------------------------------------------------- Comment (by JeremyVisser): Generally, if you publish a post, you'll want it in your RSS. If you want to turn off feeds, go to WP Admin ? Options ? Reading, and in the Syndication Feeds section, make the "Show the most recent posts" value 0 (zero). -- Ticket URL: <http://trac.wordpress.org/ticket/3376#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 10:20:16 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 10:20:27 2006 Subject: [wp-trac] Re: [WordPress Trac] #3375: delay between ping In-Reply-To: <066.2129c617c51d65dbcd44298548abb07f@lists.automattic.com> References: <066.2129c617c51d65dbcd44298548abb07f@lists.automattic.com> Message-ID: <075.40dc0076dc92c4d171baa94f50dc4717@lists.automattic.com> #3375: delay between ping --------------------------+------------------------------------------------- Reporter: tandilboy | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.0.6 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: | --------------------------+------------------------------------------------- Changes (by JeremyVisser): * version: => 2.0.5 * component: Administration => Optimization * milestone: => 2.0.6 Comment: This might be caused from the WordPress 2.0.5 update. Try installing the [http://txfx.net/code/wordpress/wordpress-tuneup/wordpress-205-tuneup/ tuneup plugin] and see if that helps. -- Ticket URL: <http://trac.wordpress.org/ticket/3375#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 10:22:04 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 10:22:15 2006 Subject: [wp-trac] Re: [WordPress Trac] #3375: delay between ping In-Reply-To: <066.2129c617c51d65dbcd44298548abb07f@lists.automattic.com> References: <066.2129c617c51d65dbcd44298548abb07f@lists.automattic.com> Message-ID: <075.082a27eb255d012244ee4cb5a4dcfe24@lists.automattic.com> #3375: delay between ping --------------------------+------------------------------------------------- Reporter: tandilboy | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.0.6 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: | --------------------------+------------------------------------------------- Comment (by JeremyVisser): By the way, adding 1 or 2 seconds between pings will drastically slow down posting. That sort of thing will cause more complaints and timeouts than things that it would fix. Is this more of an issue for the [http://wordpress.org/support/ support forums]? -- Ticket URL: <http://trac.wordpress.org/ticket/3375#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 14:43:19 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 14:43:53 2006 Subject: [wp-trac] Re: [WordPress Trac] #3375: delay between ping In-Reply-To: <066.2129c617c51d65dbcd44298548abb07f@lists.automattic.com> References: <066.2129c617c51d65dbcd44298548abb07f@lists.automattic.com> Message-ID: <075.a758bb23730f93d2d3e901fca953da7d@lists.automattic.com> #3375: delay between ping --------------------------+------------------------------------------------- Reporter: tandilboy | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.0.6 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: | --------------------------+------------------------------------------------- Comment (by tandilboy): the idea is run the delay between ping "as background task" to eliminate the post slow down (the post shows "as published" but in background is pinging the servers) -- Ticket URL: <http://trac.wordpress.org/ticket/3375#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 15:44:34 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 15:45:00 2006 Subject: [wp-trac] Re: [WordPress Trac] #3375: delay between ping In-Reply-To: <066.2129c617c51d65dbcd44298548abb07f@lists.automattic.com> References: <066.2129c617c51d65dbcd44298548abb07f@lists.automattic.com> Message-ID: <075.ae6d1bba9d74d54ad81e113384c95b58@lists.automattic.com> #3375: delay between ping --------------------------+------------------------------------------------- Reporter: tandilboy | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: 2.0.6 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: worksforme Keywords: | --------------------------+------------------------------------------------- Changes (by westi): * status: new => closed * resolution: => worksforme Comment: Replying to [comment:3 tandilboy]: > the idea is run the delay between ping "as background task" to eliminate the post slow down (the post shows "as published" but in background is pinging the servers) I believe the cron features in 2.1 provide this functionality. Closing as WORKSFORME -- Ticket URL: <http://trac.wordpress.org/ticket/3375#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 17:27:29 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 17:31:02 2006 Subject: [wp-trac] [WordPress Trac] #3377: Atom feed contradicts itself Message-ID: <066.d79d5753398a3325a9464cd011a28c9f@lists.automattic.com> #3377: Atom feed contradicts itself ---------------------+------------------------------------------------------ Reporter: link92 | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: General | Version: Severity: normal | Keywords: ---------------------+------------------------------------------------------ {{{ <summary type="text/plain" mode="escaped"> }}} From a parser POV, what does this mean? Normally you only escape the content when you have HTML content, yet what we're given in the type attribute says it's text/plain. Since both are MAY [RFC2119] in Atom 0.3, many (if not all parsers) will just take one attribute and ignore the other. Fx 2.0 just treats it as unescaped plain text. -- Ticket URL: <http://trac.wordpress.org/ticket/3377> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 17:38:36 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 17:39:30 2006 Subject: [wp-trac] Re: [WordPress Trac] #3376: option to publish in RSS feeds or not In-Reply-To: <066.ab0f8a1330d6dfcb64ac7766a6cdf400@lists.automattic.com> References: <066.ab0f8a1330d6dfcb64ac7766a6cdf400@lists.automattic.com> Message-ID: <075.eb46b89cfa67cd8ca8ca8dd7a39ef894@lists.automattic.com> #3376: option to publish in RSS feeds or not -------------------------+-------------------------------------------------- Reporter: tandilboy | Owner: anonymous Type: enhancement | Status: closed Priority: low | Milestone: 2.1 Component: General | Version: 2.1 Severity: minor | Resolution: wontfix Keywords: | -------------------------+-------------------------------------------------- Changes (by foolswisdom): * status: new => closed * resolution: => wontfix Comment: Closing WONTFIX. Jeremy presents a good workaround, and I agree with Viper that this is plugin material. -- Ticket URL: <http://trac.wordpress.org/ticket/3376#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 19:24:10 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 19:24:31 2006 Subject: [wp-trac] [WordPress Trac] #3378: IE and translation fix for upload JS Message-ID: <066.30a81b7cfd0718d35eb8da91bda2497c@lists.automattic.com> #3378: IE and translation fix for upload JS ----------------------------+----------------------------------------------- Reporter: mdawaffe | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Keywords: JS has-patch needs-testing ----------------------------+----------------------------------------------- Attached Tested in FF2, IE7, IE6, Safari 2.0.4, Opera 9.02 -- Ticket URL: <http://trac.wordpress.org/ticket/3378> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 19:25:10 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 19:25:37 2006 Subject: [wp-trac] Re: [WordPress Trac] #3378: IE and translation fix for upload JS In-Reply-To: <066.30a81b7cfd0718d35eb8da91bda2497c@lists.automattic.com> References: <066.30a81b7cfd0718d35eb8da91bda2497c@lists.automattic.com> Message-ID: <075.a940333cf9f7600737557caab2e6e575@lists.automattic.com> #3378: IE and translation fix for upload JS ----------------------------------------+----------------------------------- Reporter: mdawaffe | Owner: mdawaffe Type: defect | Status: assigned Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: JS has-patch needs-testing | ----------------------------------------+----------------------------------- Changes (by mdawaffe): * status: new => assigned * owner: anonymous => mdawaffe Comment: Need to bump script version. -- Ticket URL: <http://trac.wordpress.org/ticket/3378#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 20:45:08 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 20:45:19 2006 Subject: [wp-trac] Re: [WordPress Trac] #3349: wp-config pickup consistency fixes In-Reply-To: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> References: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> Message-ID: <075.74dc92f6f80e30d0ecd0fac1f39233de@lists.automattic.com> #3349: wp-config pickup consistency fixes --------------------------+------------------------------------------------- Reporter: RuddO | Owner: markjaquith Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: 2nd-opinion | --------------------------+------------------------------------------------- Comment (by omry): RuddO, I never got your patch, please re-send. -- Ticket URL: <http://trac.wordpress.org/ticket/3349#comment:10> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 20:47:27 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 20:47:45 2006 Subject: [wp-trac] Re: [WordPress Trac] #3349: wp-config pickup consistency fixes In-Reply-To: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> References: <066.5b1ce5dbeba52bd1aa6229e3dda8bc9b@lists.automattic.com> Message-ID: <075.d6efba606cbe0b13c080d84b6941796a@lists.automattic.com> #3349: wp-config pickup consistency fixes --------------------------+------------------------------------------------- Reporter: RuddO | Owner: markjaquith Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: 2nd-opinion | --------------------------+------------------------------------------------- Comment (by omry): or better yet, open a ticket for it at firestats.cc, and attach the patch there. -- Ticket URL: <http://trac.wordpress.org/ticket/3349#comment:11> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 21:21:45 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 21:22:02 2006 Subject: [wp-trac] Re: [WordPress Trac] #1038: Limit access to php files In-Reply-To: <066.ea9d92b987b906b39582202d90d312d7@lists.automattic.com> References: <066.ea9d92b987b906b39582202d90d312d7@lists.automattic.com> Message-ID: <075.ffc53f4e406e188d4dc733079469008d@lists.automattic.com> #1038: Limit access to php files -----------------------------+---------------------------------------------- Reporter: anonymousbugger | Owner: matt Type: defect | Status: closed Priority: lowest | Milestone: Component: Security | Version: 2.0.2 Severity: trivial | Resolution: wontfix Keywords: needs-patch | -----------------------------+---------------------------------------------- Changes (by foolswisdom): * keywords: bg|needs-patch => needs-patch * status: assigned => closed * resolution: => wontfix * milestone: 2.1 => Comment: Closing ticket as WONTFIX. Ticket has not been updated in 7 months. It seems two issues are discussed in this bug:[[br]] 1. What if I web server problem resulted in served up php files being displayed in plain text, specifically wp-config.php [[br]] 2. Source php files in wp-include being directly called for malicious purposes The discussion has not resulted in any patches, though it sounds like ``` <?php defined('__WP__') || die(''); ``` would be accepted for the appropriate php files. Changing to enhancement b/c no real issue shown to be defective. As the priority of "lowest" reflects, and the lack of recent "progress", does not seem worth keeping this ticket open longer. -- Ticket URL: <http://trac.wordpress.org/ticket/1038#comment:16> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 22:00:04 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 22:00:13 2006 Subject: [wp-trac] Re: [WordPress Trac] #2980: Improvements to wptexturize In-Reply-To: <066.eadfc5956a95ef5fd98df2bad037e851@lists.automattic.com> References: <066.eadfc5956a95ef5fd98df2bad037e851@lists.automattic.com> Message-ID: <075.e2270f5a0459a8934a25343a0ac58d37@lists.automattic.com> #2980: Improvements to wptexturize ----------------------------------+----------------------------------------- Reporter: ecb29 | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.1 Component: Optimization | Version: 2.0.3 Severity: normal | Resolution: Keywords: wptexturize optimize | ----------------------------------+----------------------------------------- Changes (by ryan): * milestone: 2.2 => 2.1 -- Ticket URL: <http://trac.wordpress.org/ticket/2980#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 22:10:24 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 22:10:36 2006 Subject: [wp-trac] Re: [WordPress Trac] #3178: Import should not fail if file size larger than max php memory In-Reply-To: <066.af3d55a577764da3439c89b51c60bb83@lists.automattic.com> References: <066.af3d55a577764da3439c89b51c60bb83@lists.automattic.com> Message-ID: <075.714c79e234ba701c07722b85d08b91b3@lists.automattic.com> #3178: Import should not fail if file size larger than max php memory ---------------------------------------------+------------------------------ Reporter: technosailor | Owner: anonymous Type: defect | Status: reopened Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.0.4 Severity: normal | Resolution: Keywords: import MT filesize memory limit | ---------------------------------------------+------------------------------ Changes (by foolswisdom): * keywords: import MT => import MT filesize memory limit * summary: MT Importer Breaks if File Size takes too much memory => Import should not fail if file size larger than max php memory * milestone: 2.1 => 2.2 Old description: > I imagine my patch is ill-advisable so open to other recommendations. > This worked on a client platform where the memory_limit was set in > php.ini to be 12M, far smaller than was needed to do an MT import. This > patch temporarily adjusts the memory_limit to 50M which I'd think would > be big enough for just about anyone. > > A better solution might be to check file size against memory allocation > required and provide a more user-friendly error or prompt to split the MT > file into two. New description: MT Importer Breaks if File Size takes too much memory Proposed solution: [[br]] Read X MB of the file finding a convenient break point, import and continue where left off. Comment: r4388 is relevant Changing milestone to 2.2 Any implementations from other projects that can be copied/borrowed? Updated Description from:[[br]] I imagine my patch is ill-advisable so open to other recommendations. This worked on a client platform where the memory_limit was set in php.ini to be 12M, far smaller than was needed to do an MT import. This patch temporarily adjusts the memory_limit to 50M which I'd think would be big enough for just about anyone. A better solution might be to check file size against memory allocation required and provide a more user-friendly error or prompt to split the MT file into two. -- Ticket URL: <http://trac.wordpress.org/ticket/3178#comment:8> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 21 23:19:42 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 21 23:19:55 2006 Subject: [wp-trac] Re: [WordPress Trac] #2628: wordpress broken under apache mod_fastcgi with php ran as a cgi In-Reply-To: <066.25ab32bf3a773286dde86e5321b6e877@lists.automattic.com> References: <066.25ab32bf3a773286dde86e5321b6e877@lists.automattic.com> Message-ID: <075.cc4d0222f50b6922dc45e5f1585dc2ce@lists.automattic.com> #2628: wordpress broken under apache mod_fastcgi with php ran as a cgi --------------------------------------+------------------------------------- Reporter: scruby | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.0 Component: General | Version: 2.0 Severity: normal | Resolution: Keywords: has-patch, needs-testing | --------------------------------------+------------------------------------- Changes (by abecciu): * version: 2.0.2 => 2.0 * milestone: 2.2 => 2.0 Comment: This patch works like a charm for me. It was tested on Apache 2.2.3 PHP/FastCGI 5.1.6. -- Ticket URL: <http://trac.wordpress.org/ticket/2628#comment:8> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 22 00:16:51 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 22 00:17:06 2006 Subject: [wp-trac] Re: [WordPress Trac] #2628: wordpress broken under apache mod_fastcgi with php ran as a cgi In-Reply-To: <066.25ab32bf3a773286dde86e5321b6e877@lists.automattic.com> References: <066.25ab32bf3a773286dde86e5321b6e877@lists.automattic.com> Message-ID: <075.f5d70347560fb988b34a93418d793fed@lists.automattic.com> #2628: wordpress broken under apache mod_fastcgi with php ran as a cgi --------------------------------------+------------------------------------- Reporter: scruby | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.0.2 Severity: normal | Resolution: Keywords: has-patch, needs-testing | --------------------------------------+------------------------------------- Changes (by foolswisdom): * version: 2.0 => 2.0.2 * milestone: 2.0 => 2.1 Comment: abecciu what version of WordPress are you running ? Thank you. -- Ticket URL: <http://trac.wordpress.org/ticket/2628#comment:9> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 22 00:17:03 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 22 00:17:14 2006 Subject: [wp-trac] Re: [WordPress Trac] #2628: wordpress broken under apache mod_fastcgi with php ran as a cgi In-Reply-To: <066.25ab32bf3a773286dde86e5321b6e877@lists.automattic.com> References: <066.25ab32bf3a773286dde86e5321b6e877@lists.automattic.com> Message-ID: <075.f8154150845925a0c19a01e3032175d2@lists.automattic.com> #2628: wordpress broken under apache mod_fastcgi with php ran as a cgi --------------------------------------+------------------------------------- Reporter: scruby | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: General | Version: 2.0.2 Severity: normal | Resolution: Keywords: has-patch, needs-testing | --------------------------------------+------------------------------------- Changes (by foolswisdom): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2628#comment:10> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 22 01:03:15 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 22 01:49:29 2006 Subject: [wp-trac] [WordPress Trac] #3379: Autosave during Save or Publish click results in duplicate Message-ID: <048.6c584efce752b6cce924291961b883fe@lists.automattic.com> #3379: Autosave during Save or Publish click results in duplicate ----------------------------+----------------------------------------------- Reporter: foolswisdom | Owner: andy Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: critical | Keywords: autosave save draft saving ----------------------------+----------------------------------------------- Autosave during Save or Publish click results in duplicate ENV: WP trunk r4511 [[br]] Visual editor disabled b/c of unrelated testing The current very short autosave interval ```'autosave_interval', '16'``` makes it easy to demonstrate the bug creating multiple drafts or a draft and a published post by clicking either Save or Publish while "Saving ..." is shown left of those buttons. ACTUAL RESULT[[br]] Extra draft copy of the post EXPECTED RESULT[[br]] Obvious. -- Ticket URL: <http://trac.wordpress.org/ticket/3379> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 22 02:03:52 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 22 02:04:00 2006 Subject: [wp-trac] Re: [WordPress Trac] #3379: Autosave during Save or Publish click results in duplicate In-Reply-To: <048.6c584efce752b6cce924291961b883fe@lists.automattic.com> References: <048.6c584efce752b6cce924291961b883fe@lists.automattic.com> Message-ID: <057.199018ace36f762e8c107b144443bbb9@lists.automattic.com> #3379: Autosave during Save or Publish click results in duplicate ----------------------------------------+----------------------------------- Reporter: foolswisdom | Owner: andy Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: critical | Resolution: Keywords: autosave save draft saving | ----------------------------------------+----------------------------------- Comment (by Viper007Bond): If a solution can't be found behind the scenes, then a solution would be to disable the Save and Publish buttons while a save is in progress. -- Ticket URL: <http://trac.wordpress.org/ticket/3379#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 22 02:56:26 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 22 02:56:34 2006 Subject: [wp-trac] Re: [WordPress Trac] #3379: Autosave during Save or Publish click results in duplicate In-Reply-To: <048.6c584efce752b6cce924291961b883fe@lists.automattic.com> References: <048.6c584efce752b6cce924291961b883fe@lists.automattic.com> Message-ID: <057.300c5d5a8ab702d3e6e7f506a5a69463@lists.automattic.com> #3379: Autosave during Save or Publish click results in duplicate ----------------------------------------+----------------------------------- Reporter: foolswisdom | Owner: andy Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: critical | Resolution: Keywords: autosave save draft saving | ----------------------------------------+----------------------------------- Comment (by ryan): [4512] changes the interval to 2 minutes. This problem is usually seen when the server is experiencing a slowdown or having DB problems. Autosave send the save but we don't get a post ID back. So, we don't realize the save went through and we do another draft. -- Ticket URL: <http://trac.wordpress.org/ticket/3379#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 22 02:57:35 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 22 02:57:42 2006 Subject: [wp-trac] Re: [WordPress Trac] #3379: Autosave during Save or Publish click results in duplicate In-Reply-To: <048.6c584efce752b6cce924291961b883fe@lists.automattic.com> References: <048.6c584efce752b6cce924291961b883fe@lists.automattic.com> Message-ID: <057.d6a62bda4be285638d1f3883b9ce3268@lists.automattic.com> #3379: Autosave during Save or Publish click results in duplicate ----------------------------------------+----------------------------------- Reporter: foolswisdom | Owner: andy Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: critical | Resolution: Keywords: autosave save draft saving | ----------------------------------------+----------------------------------- Comment (by ryan): Also, [4507] should disable the buttons during autosave. That might be enough to close out this issue. -- Ticket URL: <http://trac.wordpress.org/ticket/3379#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 22 03:38:03 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 22 03:38:11 2006 Subject: [wp-trac] Re: [WordPress Trac] #3215: Login & Update functions everything is broken In-Reply-To: <049.6066b63c1044229dd67a636989ac05fd@lists.automattic.com> References: <049.6066b63c1044229dd67a636989ac05fd@lists.automattic.com> Message-ID: <058.38e91e26ffe34de1f7dcf3f7167a7611@lists.automattic.com> #3215: Login & Update functions everything is broken --------------------------------------------+------------------------------- Reporter: Xmion | Owner: markjaquith Type: defect | Status: assigned Priority: highest | Milestone: 2.0.6 Component: General | Version: 2.1 Severity: critical | Resolution: Keywords: Blank page 302 maint-candidate | --------------------------------------------+------------------------------- Comment (by ryan): MarkJaquith, the PHP dev responding to php bug #36705 suggests using HTTP/1.1 instead of Status: for cgi. PEAR's HTTP_header class does the same thing. This is contrary to what folks have been doing for awhile now. See #2628, for example. Maybe we should just skip status_header() for 'cgi-fcgi' SAPIs. For 2.1, we could consider bumping the PHP requirement to 4.3 so that we can use the extra args to header(). -- Ticket URL: <http://trac.wordpress.org/ticket/3215#comment:17> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 22 04:00:16 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 22 04:00:27 2006 Subject: [wp-trac] Re: [WordPress Trac] #3364: Metadata db improvements In-Reply-To: <066.71eed7cd9d54c39a681131d98fd3de53@lists.automattic.com> References: <066.71eed7cd9d54c39a681131d98fd3de53@lists.automattic.com> Message-ID: <075.d54b2a6ba10a270be166d5b645c09a48@lists.automattic.com> #3364: Metadata db improvements -----------------------------------------------------------------------------+ Reporter: dougal | Owner: dougal Type: enhancement | Status: new Priority: low | Milestone: 2.2 Component: Optimization | Version: 2.1 Severity: normal | Resolution: Keywords: meta, metadata, postmeta, usermeta, catmeta, postcustom, custom | -----------------------------------------------------------------------------+ Comment (by markjaquith): This would only break postmeta, I think. Usermeta userid + key combos are already unique, so that should be fine. There would need to be an API implemented (and preferably a full version ahead of these changes) for things like querying by value, mySQL LIKE queries, etc. -- Ticket URL: <http://trac.wordpress.org/ticket/3364#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 22 05:01:41 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 22 05:01:48 2006 Subject: [wp-trac] Re: [WordPress Trac] #3215: Login & Update functions everything is broken In-Reply-To: <049.6066b63c1044229dd67a636989ac05fd@lists.automattic.com> References: <049.6066b63c1044229dd67a636989ac05fd@lists.automattic.com> Message-ID: <058.5910f0fddf60fcd592ec53c7e8c03df6@lists.automattic.com> #3215: Login & Update functions everything is broken --------------------------------------------+------------------------------- Reporter: Xmion | Owner: markjaquith Type: defect | Status: assigned Priority: highest | Milestone: 2.0.6 Component: General | Version: 2.1 Severity: critical | Resolution: Keywords: Blank page 302 maint-candidate | --------------------------------------------+------------------------------- Comment (by markjaquith): [4513] and [4514] Doing HTTP/1.1 for CGI, and skipping status_header() for 'cgi-fcgi'. I have a contact with access to a number of affected hosts, and I'll have him test. -- Ticket URL: <http://trac.wordpress.org/ticket/3215#comment:18> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 22 05:13:27 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 22 05:13:33 2006 Subject: [wp-trac] Re: [WordPress Trac] #2628: wordpress broken under apache mod_fastcgi with php ran as a cgi In-Reply-To: <066.25ab32bf3a773286dde86e5321b6e877@lists.automattic.com> References: <066.25ab32bf3a773286dde86e5321b6e877@lists.automattic.com> Message-ID: <075.86b15c736604bb0657e4f5fd2bb33226@lists.automattic.com> #2628: wordpress broken under apache mod_fastcgi with php ran as a cgi --------------------------------------+------------------------------------- Reporter: scruby | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: General | Version: 2.0.2 Severity: normal | Resolution: Keywords: has-patch, needs-testing | --------------------------------------+------------------------------------- Comment (by markjaquith): [4513] and [4514] may affect this. Please test with this change applied. -- Ticket URL: <http://trac.wordpress.org/ticket/2628#comment:11> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 22 07:06:45 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 22 07:06:55 2006 Subject: [wp-trac] Re: [WordPress Trac] #3379: Autosave during Save or Publish click results in duplicate In-Reply-To: <048.6c584efce752b6cce924291961b883fe@lists.automattic.com> References: <048.6c584efce752b6cce924291961b883fe@lists.automattic.com> Message-ID: <057.577682d846820bb43c0ce421f733f642@lists.automattic.com> #3379: Autosave during Save or Publish click results in duplicate ----------------------------------------+----------------------------------- Reporter: foolswisdom | Owner: andy Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: critical | Resolution: Keywords: autosave save draft saving | ----------------------------------------+----------------------------------- Comment (by foolswisdom): [4507] does not seem to work as I was already at r4511 . I have tried again now and able to duplicate the previous buggy behavior. -- Ticket URL: <http://trac.wordpress.org/ticket/3379#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 22 14:54:52 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 22 14:55:00 2006 Subject: [wp-trac] [WordPress Trac] #3380: Make autosave interval configurable Message-ID: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> #3380: Make autosave interval configurable ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Keywords: ----------------------------+----------------------------------------------- It'd be nice IMO if you could set the autosave interval (or even enable/disable it) via the Options -> Writing screen (if you can't already -- I haven't looked lately). -- Ticket URL: <http://trac.wordpress.org/ticket/3380> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 22 19:04:16 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 22 19:04:35 2006 Subject: [wp-trac] Re: [WordPress Trac] #3380: Make autosave interval configurable In-Reply-To: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> References: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> Message-ID: <075.c533a1abfe9ef6164750fc3d0a834d67@lists.automattic.com> #3380: Make autosave interval configurable ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: wontfix Keywords: | ----------------------------+----------------------------------------------- Changes (by foolswisdom): * status: new => closed * resolution: => wontfix Comment: Please present your ticket in terms of functionality you are trying to achieve or problem this would address, particularly if it is based on experienced behavior with data. Closing as WONTFIX for now. -- Ticket URL: <http://trac.wordpress.org/ticket/3380#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 22 21:44:02 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 22 21:44:16 2006 Subject: [wp-trac] Re: [WordPress Trac] #3338: Blog Search: Ignore Soft Hyphens In-Reply-To: <066.1d365df65c10dae132b48a24338ba440@lists.automattic.com> References: <066.1d365df65c10dae132b48a24338ba440@lists.automattic.com> Message-ID: <075.4ed0c7cb9e5b51f6b6924f248e81e6e7@lists.automattic.com> #3338: Blog Search: Ignore Soft Hyphens ------------------------------------------------------------------+--------- Reporter: transalpin | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Optimization | Version: 2.0.5 Severity: normal | Resolution: Keywords: hyphenate, hyphenation, discretionary hyphen, search | ------------------------------------------------------------------+--------- Changes (by foolswisdom): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/3338#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 22 22:00:49 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 22 22:00:56 2006 Subject: [wp-trac] Re: [WordPress Trac] #3276: Ajax update of non-changed meta value results in "Something strange happened" error In-Reply-To: <066.3fe7c003e4b0edaf77914de802e7c534@lists.automattic.com> References: <066.3fe7c003e4b0edaf77914de802e7c534@lists.automattic.com> Message-ID: <075.4eb2585c99d1b32397998e203ff82307@lists.automattic.com> #3276: Ajax update of non-changed meta value results in "Something strange happened" error ----------------------------+----------------------------------------------- Reporter: markjaquith | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: Keywords: ajax postmeta | ----------------------------+----------------------------------------------- Comment (by Nazgul): Related to #3199. -- Ticket URL: <http://trac.wordpress.org/ticket/3276#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 23 00:36:02 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 23 00:36:10 2006 Subject: [wp-trac] Re: [WordPress Trac] #3343: Delete categories JavaScript error: Object doesn't support this property or method. In-Reply-To: <066.5314b9625f6b86ea30a04b93db2b365d@lists.automattic.com> References: <066.5314b9625f6b86ea30a04b93db2b365d@lists.automattic.com> Message-ID: <075.547037d22969c8eb3ffa96ba754dde25@lists.automattic.com> #3343: Delete categories JavaScript error: Object doesn't support this property or method. ----------------------------+----------------------------------------------- Reporter: dan-daemon | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by foolswisdom): * summary: Add/Delete categories bug in last trunks => Delete categories JavaScript error: Object doesn't support this property or method. Old description: > Hello guys, > > Can you give me solution for bugs I described here: > http://wordpress.org/support/topic/93417?replies=2 > > Thanks, > Dan New description: When I delete category, software initiates ajax request to the server, then delete item from the table by ajax response, correct? If so, after it I get JavaScript error: Object doesn't support this property or method. I use IE7 and thought that this bug in JavaScript with new IE release, then I checked it to Firefox and got this JavaScript error after deleting category (copied from JavaScript console): $(id) has no properties[[br]] http://my.domain.com/wp-includes/js/list-manipulation-js.php?ver=4187 Also, as I can see sometimes when I receive this error I also get this alert box (mostly Firefox): Are you sure you want to navigate away from this page?[[br]] Slow down, I'm still sending your data![[br]] Press OK to continue, or Cancel to stay on the current page. This bug presents in IE all time, but in firefox only for first deleted item. Then I do not see any errors, deleting goes well. Comment: Reproduced bug on delete of cat with IE 7 Hi Dan-daemon, thank you for reporting this problem. In the future please include the details right in the ticket. ENV: WP trunk r4515 WinXP / IE 7 * Could not reproduce on Linux / Firefox 2.0 - Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1) Gecko/20060601 Firefox/2.0 (Ubuntu-edgy) Description was:[[br]] Hello guys, Can you give me solution for bugs I described here: http://wordpress.org/support/topic/93417?replies=2 Thanks, Dan -- Ticket URL: <http://trac.wordpress.org/ticket/3343#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 23 00:36:48 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 23 00:36:55 2006 Subject: [wp-trac] Re: [WordPress Trac] #3372: Consolidated JavaScript/CSS Plugin API In-Reply-To: <066.3822605294f4b937960fe980ff535512@lists.automattic.com> References: <066.3822605294f4b937960fe980ff535512@lists.automattic.com> Message-ID: <075.20a95044f7dac174f0b2f17c01c7e995@lists.automattic.com> #3372: Consolidated JavaScript/CSS Plugin API -----------------------------+---------------------------------------------- Reporter: robertaccettura | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.2 Component: Optimization | Version: 2.1 Severity: minor | Resolution: Keywords: | -----------------------------+---------------------------------------------- Comment (by robertaccettura): Replying to [comment:2 RuddO]: > > Note that, due to the nature of the requests, it's impossible to make distinctions > based on which page the reader is visiting, because the custom CSS and JS is released > to the browser separately from the original request. Ah but you can. i.e. <script type="text/javascript" src="/wp- javascript.php?path=/archives/2006/11/22/monkey-love/"></script> <script type="text/javascript" src="/wp-javascript.php?path=/"></script> -- Ticket URL: <http://trac.wordpress.org/ticket/3372#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 23 01:44:47 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 23 01:44:54 2006 Subject: [wp-trac] Re: [WordPress Trac] #3380: Make autosave interval configurable In-Reply-To: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> References: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> Message-ID: <075.d7d633935d52be51b430b02e08fc22ab@lists.automattic.com> #3380: Make autosave interval configurable ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: wontfix Keywords: | ----------------------------+----------------------------------------------- Comment (by masquerade): I think its absolutely ridiculous this was closed as wontfix, I see no reason or rhyme to why it should be that way from what you said. Having said that, I can provide a real reason. It was previously requested and shot down to have autosave be a user configurable option, but shot down. A plugin can disable autosave easily via the script loader in 2.1, and the interval can be changed with filters via plugin as well. -- Ticket URL: <http://trac.wordpress.org/ticket/3380#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 23 03:58:53 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 23 03:59:01 2006 Subject: [wp-trac] [WordPress Trac] #3381: "Discard" button for autosaves Message-ID: <066.50f57507327172dd7de9adc751ad5207@lists.automattic.com> #3381: "Discard" button for autosaves ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Keywords: ----------------------------+----------------------------------------------- Write a post and let it get autosaved. Now what if you decide that you no longer want the draft? There's no way to discard the autosaved draft without browsing to the "edit" page for the draft. So, I propose a "Discard" button somewhere that shows up after an autosave is done. -- Ticket URL: <http://trac.wordpress.org/ticket/3381> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 23 03:59:27 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 23 03:59:35 2006 Subject: [wp-trac] Re: [WordPress Trac] #3380: Make autosave interval configurable In-Reply-To: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> References: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> Message-ID: <075.d2a0d9b4cb291bee0d4089514314f88d@lists.automattic.com> #3380: Make autosave interval configurable ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: wontfix Keywords: | ----------------------------+----------------------------------------------- Comment (by Viper007Bond): WTF @ foolswisdom. I'm not new to this you know... masquerade: valid points about the filters and now that I think of it, I can't really think of a widespread reason that one would want it off. This did occur to me though: #3381 -- Ticket URL: <http://trac.wordpress.org/ticket/3380#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 23 04:45:08 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 23 04:45:17 2006 Subject: [wp-trac] Re: [WordPress Trac] #3381: "Discard" button for autosaves In-Reply-To: <066.50f57507327172dd7de9adc751ad5207@lists.automattic.com> References: <066.50f57507327172dd7de9adc751ad5207@lists.automattic.com> Message-ID: <075.48e4791841c2ee0d21a8daa5333cc74b@lists.automattic.com> #3381: "Discard" button for autosaves ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by tedfox): Just curious, why would you not want the draft? Wouldn't managing the autosave draft be relevant to how you manage the rest of your draft as well. (i.e. if that's the case, wouldn't it nice to be able to easily discard other drafts as well) -- Ticket URL: <http://trac.wordpress.org/ticket/3381#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 23 10:30:20 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 23 10:30:28 2006 Subject: [wp-trac] Re: [WordPress Trac] #3381: "Discard" button for autosaves In-Reply-To: <066.50f57507327172dd7de9adc751ad5207@lists.automattic.com> References: <066.50f57507327172dd7de9adc751ad5207@lists.automattic.com> Message-ID: <075.5f241406a7c7edaf9eea6c5d3864d852@lists.automattic.com> #3381: "Discard" button for autosaves ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by Viper007Bond): Replying to [comment:1 tedfox]: > Just curious, why would you not want the draft? I often start writing a post and then a couple sentences into it I decide that it's not worth it or that I won't be able to make the point I wanted to make, so I close the tab. Maybe I'm just weird... -- Ticket URL: <http://trac.wordpress.org/ticket/3381#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 23 11:20:56 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 23 11:21:05 2006 Subject: [wp-trac] [WordPress Trac] #3382: formatting.php - sanitize_file() Message-ID: <066.dd15520aa8d2f6875960999724ce59da@lists.automattic.com> #3382: formatting.php - sanitize_file() ----------------------------+----------------------------------------------- Reporter: donncha | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Keywords: ----------------------------+----------------------------------------------- This patch adds a new function, sanitize_file() to formatting.php, via Matt -- Ticket URL: <http://trac.wordpress.org/ticket/3382> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 23 11:39:50 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 23 11:39:59 2006 Subject: [wp-trac] [WordPress Trac] #3383: Add post_deleted action Message-ID: <066.4f22f9ed607bec37416c3b27025c35bc@lists.automattic.com> #3383: Add post_deleted action ----------------------------+----------------------------------------------- Reporter: donncha | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Keywords: ----------------------------+----------------------------------------------- Please add post_deleted action to post.php See patch, via Andy -- Ticket URL: <http://trac.wordpress.org/ticket/3383> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 23 12:10:47 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 23 12:10:54 2006 Subject: [wp-trac] Re: [WordPress Trac] #2659: Comment meta In-Reply-To: <066.07478c85eb69faa27d72368493d72efa@lists.automattic.com> References: <066.07478c85eb69faa27d72368493d72efa@lists.automattic.com> Message-ID: <075.b2a79bd9046ca8b97d3744c49921795f@lists.automattic.com> #2659: Comment meta --------------------------------------------------+------------------------- Reporter: markjaquith | Owner: markjaquith Type: defect | Status: assigned Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: comment meta has-patch needs-testing | --------------------------------------------------+------------------------- Comment (by McShelby): The Favatar plugin also adds new columns to the comments table in lack of a commentsmeta table. I would appreciate to have commentsmeta table. -- Ticket URL: <http://trac.wordpress.org/ticket/2659#comment:10> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 23 16:49:27 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 23 16:49:40 2006 Subject: [wp-trac] Re: [WordPress Trac] #3382: formatting.php - sanitize_file() In-Reply-To: <066.dd15520aa8d2f6875960999724ce59da@lists.automattic.com> References: <066.dd15520aa8d2f6875960999724ce59da@lists.automattic.com> Message-ID: <075.c1bfd5e95bb311e712852e073a209f7f@lists.automattic.com> #3382: formatting.php - sanitize_file() ----------------------------+----------------------------------------------- Reporter: donncha | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by masquerade): Can we name it sanitize_file_name() or sanitize_filename(), sanitize_file() makes it sound like we are actually doing something to a file. -- Ticket URL: <http://trac.wordpress.org/ticket/3382#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 23 18:20:20 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 23 18:20:29 2006 Subject: [wp-trac] Re: [WordPress Trac] #3380: Make autosave interval configurable In-Reply-To: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> References: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> Message-ID: <075.419b64fd2e3e9eb415697c56d2afb49f@lists.automattic.com> #3380: Make autosave interval configurable ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: wontfix Keywords: | ----------------------------+----------------------------------------------- Comment (by foolswisdom): I stand by my comment. Present tickets in the problem or feature that they are to achieve, and then present possible solutions. -- Ticket URL: <http://trac.wordpress.org/ticket/3380#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 23 18:31:55 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 23 18:32:02 2006 Subject: [wp-trac] Re: [WordPress Trac] #3381: "Discard" button for autosaves In-Reply-To: <066.50f57507327172dd7de9adc751ad5207@lists.automattic.com> References: <066.50f57507327172dd7de9adc751ad5207@lists.automattic.com> Message-ID: <075.3d36548a36ef1dcaa8f6b58ca5dabc9b@lists.automattic.com> #3381: "Discard" button for autosaves ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by foolswisdom): Good points Viper! Autosave should result in a "Delete this Post" or better a "Discard Draft" or "Delete this Draft". With autosave "Save and Continue Editing" also becomes extraneous. -- Ticket URL: <http://trac.wordpress.org/ticket/3381#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 23 18:48:27 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 23 18:48:37 2006 Subject: [wp-trac] [WordPress Trac] #3384: get_the_category() is broken Message-ID: <056.3bcc9069bdc313fd0a41f7117df30547@lists.automattic.com> #3384: get_the_category() is broken ----------------------+----------------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: new Priority: high | Milestone: 2.1 Component: General | Version: 2.1 Severity: major | Keywords: category, posts ----------------------+----------------------------------------------------- The function get_the_category() in the loops, returns no categories. More, is broken also $cat->category_nicename, and "no category" appears also in the wp-admin/edit.php list. If I open posts, theire category is correctly set. More, in the sidebar's wp_list_cats() counts are ok. This, while I've updated to revision 4522. -- Ticket URL: <http://trac.wordpress.org/ticket/3384> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 24 04:07:32 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 24 04:08:21 2006 Subject: [wp-trac] Re: [WordPress Trac] #3382: formatting.php - sanitize_file() In-Reply-To: <066.dd15520aa8d2f6875960999724ce59da@lists.automattic.com> References: <066.dd15520aa8d2f6875960999724ce59da@lists.automattic.com> Message-ID: <075.1ff00a4d7bd7a453e2e3466d3a48eaed@lists.automattic.com> #3382: formatting.php - sanitize_file() ----------------------------+----------------------------------------------- Reporter: donncha | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by Viper007Bond): Replying to [comment:1 masquerade]: > Can we name it sanitize_file_name() or sanitize_filename(), sanitize_file() makes it sound like we are actually doing something to a file. Agreed. -- Ticket URL: <http://trac.wordpress.org/ticket/3382#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 24 04:13:33 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 24 04:13:40 2006 Subject: [wp-trac] [WordPress Trac] #3385: Whitespace Removal Message-ID: <066.7fe94e185a63e6565e6123a6c7fc9302@lists.automattic.com> #3385: Whitespace Removal --------------------------+------------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: new Priority: lowest | Milestone: 2.1 Component: Optimization | Version: 2.1 Severity: trivial | Keywords: --------------------------+------------------------------------------------- Just a little whitespace that was added recently. -- Ticket URL: <http://trac.wordpress.org/ticket/3385> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 24 11:06:07 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 24 11:06:18 2006 Subject: [wp-trac] [WordPress Trac] #3386: box-bg-right.gif isn't wide enough Message-ID: <066.41c48ef7938fa2c024051a83e65d68a2@lists.automattic.com> #3386: box-bg-right.gif isn't wide enough ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: defect | Status: new Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Keywords: has-patch ----------------------------+----------------------------------------------- On high resolutions, the background image on the bottom draggable boxes isn't wide enough: [[Image(http://img205.imageshack.us/img205/5170/boxesvk8.png)]] It needs to be wider and while we're at it, we might as well make it only 1px tall. I've taken the honors. -- Ticket URL: <http://trac.wordpress.org/ticket/3386> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 24 14:52:42 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 24 14:52:53 2006 Subject: [wp-trac] Re: [WordPress Trac] #3380: Make autosave interval configurable In-Reply-To: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> References: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> Message-ID: <075.ccc92add3b7e13e28c0bf9e34d69a153@lists.automattic.com> #3380: Make autosave interval configurable ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: wontfix Keywords: | ----------------------------+----------------------------------------------- Comment (by robmiller): Err... he did? Problem: Users cannot set autosave interval. Possible solution: Create option allowing users to set autosave interval. What the christ is wrong with that? -- Ticket URL: <http://trac.wordpress.org/ticket/3380#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 24 15:39:18 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 24 15:40:00 2006 Subject: [wp-trac] [WordPress Trac] #3387: Category is ancestor of Message-ID: <066.df6e3173d36655149b0cb9c687a4f755@lists.automattic.com> #3387: Category is ancestor of ----------------------------+----------------------------------------------- Reporter: donncha | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Keywords: ----------------------------+----------------------------------------------- Via Andy, this function checks that no parent of a category is the same category Patch includes using it in admin-db.php -- Ticket URL: <http://trac.wordpress.org/ticket/3387> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 24 15:53:56 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 24 15:54:18 2006 Subject: [wp-trac] [WordPress Trac] #3388: xmlrpc.php : add pre-upload handler, handle upload, use return of wp_new_comment() Message-ID: <066.080c8b359ed774e06ee09894723028fb@lists.automattic.com> #3388: xmlrpc.php : add pre-upload handler, handle upload, use return of wp_new_comment() ----------------------------+----------------------------------------------- Reporter: donncha | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Keywords: ----------------------------+----------------------------------------------- Patch to use the new uploader's wp_handle_upload when uploading files through xmlrpc Adds a pre_upload filter to check uploaded files Use return value of wp_new_comment() -- Ticket URL: <http://trac.wordpress.org/ticket/3388> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 24 16:00:07 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 24 16:00:20 2006 Subject: [wp-trac] [WordPress Trac] #3389: bookmark-template.php typo Message-ID: <066.8998d39ce32459d0d8d44c55fe87f498@lists.automattic.com> #3389: bookmark-template.php typo ----------------------------+----------------------------------------------- Reporter: donncha | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Keywords: ----------------------------+----------------------------------------------- This patch fixes a minor bug in bookmark-template.php -- Ticket URL: <http://trac.wordpress.org/ticket/3389> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 24 18:14:04 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 24 18:14:15 2006 Subject: [wp-trac] Re: [WordPress Trac] #3380: Make autosave interval configurable In-Reply-To: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> References: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> Message-ID: <075.4906c64d4ed634cbd23738bc18b2c639@lists.automattic.com> #3380: Make autosave interval configurable ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: wontfix Keywords: | ----------------------------+----------------------------------------------- Comment (by foolswisdom): Not being able to set something is not a problem in itself. Explaining the importance of why being able to set the interval is essential in this scenario. Language like "ridiculous, WTF, and christ" hurts my feels, and I don't think is helpful. -- Ticket URL: <http://trac.wordpress.org/ticket/3380#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 24 19:33:19 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 24 19:33:29 2006 Subject: [wp-trac] Re: [WordPress Trac] #3380: Make autosave interval configurable In-Reply-To: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> References: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> Message-ID: <075.85777b45217096a9eac12e9948d9a3e7@lists.automattic.com> #3380: Make autosave interval configurable ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: wontfix Keywords: | ----------------------------+----------------------------------------------- Comment (by masquerade): In the same manner, Viper may think that you needlessly and senselessly closing a ticket without any real rationalization is rude and unhelpful, and will therefore respond in the same manner. -- Ticket URL: <http://trac.wordpress.org/ticket/3380#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 24 21:59:44 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 24 22:00:36 2006 Subject: [wp-trac] [WordPress Trac] #3390: Better get_page_uri Message-ID: <066.9f9709c2765568d40377048621d5c575@lists.automattic.com> #3390: Better get_page_uri -----------------------------+---------------------------------------------- Reporter: ryanscheuermann | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.0.6 Component: Administration | Version: 2.0.5 Severity: normal | Keywords: -----------------------------+---------------------------------------------- I posted this ticket for trunk, but I figured I'd duplicate it here as well. This patch replaces get_page_uri with a version that only executes 1 general query instead of 1 for every single page in the tree. This is mainly an optimization for pages that display complete page heirarchies / navigation menus. The trunk ticket is here: #3373 -- Ticket URL: <http://trac.wordpress.org/ticket/3390> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 24 22:53:17 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 24 22:54:03 2006 Subject: [wp-trac] Re: [WordPress Trac] #3390: Better get_page_uri In-Reply-To: <066.9f9709c2765568d40377048621d5c575@lists.automattic.com> References: <066.9f9709c2765568d40377048621d5c575@lists.automattic.com> Message-ID: <075.016d400f2c6274f21f1109453738cf56@lists.automattic.com> #3390: Better get_page_uri -----------------------------+---------------------------------------------- Reporter: ryanscheuermann | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: 2.0.6 Component: Administration | Version: 2.0.5 Severity: normal | Resolution: duplicate Keywords: | -----------------------------+---------------------------------------------- Changes (by foolswisdom): * status: new => closed * resolution: => duplicate Comment: Marking as duplicate of 3373. Only one ticket for a problem regardless of the version or milestone. Thank you for contributing to WordPress! I am a layperson, but the nature of the problem and the fix looks great! -- Ticket URL: <http://trac.wordpress.org/ticket/3390#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Fri Nov 24 23:07:30 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Nov 24 23:09:09 2006 Subject: [wp-trac] Re: [WordPress Trac] #3386: box-bg-right.gif isn't wide enough In-Reply-To: <066.41c48ef7938fa2c024051a83e65d68a2@lists.automattic.com> References: <066.41c48ef7938fa2c024051a83e65d68a2@lists.automattic.com> Message-ID: <075.d7865f7d4619237b0ee1a4c2dbef25be@lists.automattic.com> #3386: box-bg-right.gif isn't wide enough ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: defect | Status: new Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: Keywords: has-patch | ----------------------------+----------------------------------------------- Comment (by markjaquith): At what resolution does this problem manifest itself? -- Ticket URL: <http://trac.wordpress.org/ticket/3386#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 25 00:16:37 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 25 00:17:18 2006 Subject: [wp-trac] Re: [WordPress Trac] #3386: box-bg-right.gif isn't wide enough In-Reply-To: <066.41c48ef7938fa2c024051a83e65d68a2@lists.automattic.com> References: <066.41c48ef7938fa2c024051a83e65d68a2@lists.automattic.com> Message-ID: <075.5a8a9e53024556270beea1d98b73b813@lists.automattic.com> #3386: box-bg-right.gif isn't wide enough ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: defect | Status: new Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: Keywords: has-patch | ----------------------------+----------------------------------------------- Comment (by Viper007Bond): All resolutions where the horizontal resolution is over 1100 or so. 1600x1200 for example (which is what I run). -- Ticket URL: <http://trac.wordpress.org/ticket/3386#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 25 01:35:53 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 25 01:37:05 2006 Subject: [wp-trac] Re: [WordPress Trac] #3388: xmlrpc.php : add pre-upload handler, handle upload, use return of wp_new_comment() In-Reply-To: <066.080c8b359ed774e06ee09894723028fb@lists.automattic.com> References: <066.080c8b359ed774e06ee09894723028fb@lists.automattic.com> Message-ID: <075.f9863a64b8a61faa48409448dfdacfc5@lists.automattic.com> #3388: xmlrpc.php : add pre-upload handler, handle upload, use return of wp_new_comment() ----------------------------+----------------------------------------------- Reporter: donncha | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: fixed Keywords: | ----------------------------+----------------------------------------------- Changes (by Viper007Bond): * version: => 2.1 * milestone: => 2.1 -- Ticket URL: <http://trac.wordpress.org/ticket/3388#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 25 01:35:44 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 25 02:06:22 2006 Subject: [wp-trac] Re: [WordPress Trac] #3388: xmlrpc.php : add pre-upload handler, handle upload, use return of wp_new_comment() In-Reply-To: <066.080c8b359ed774e06ee09894723028fb@lists.automattic.com> References: <066.080c8b359ed774e06ee09894723028fb@lists.automattic.com> Message-ID: <075.b623bb278c85e4670c734356b9380891@lists.automattic.com> #3388: xmlrpc.php : add pre-upload handler, handle upload, use return of wp_new_comment() ----------------------------+----------------------------------------------- Reporter: donncha | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Resolution: fixed Keywords: | ----------------------------+----------------------------------------------- Comment (by Viper007Bond): For future reference, single quotes should be used rather than double quotes. ;) -- Ticket URL: <http://trac.wordpress.org/ticket/3388#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 25 02:01:15 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 25 02:21:56 2006 Subject: [wp-trac] Re: [WordPress Trac] #3290: Importer strips img class and style In-Reply-To: <066.9ce1f29060f80c36ddb627f9d0cb035c@lists.automattic.com> References: <066.9ce1f29060f80c36ddb627f9d0cb035c@lists.automattic.com> Message-ID: <075.2d2a84d290af50b39597204f66323d2d@lists.automattic.com> #3290: Importer strips img class and style -----------------------------+---------------------------------------------- Reporter: foolswisdom | Owner: anonymous Type: defect | Status: new Priority: high | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: major | Resolution: Keywords: import importer | -----------------------------+---------------------------------------------- Comment (by foolswisdom): Slowly learning. The class and style are being removed during `$post_content = apply_filters('content_save_pre', $post_content);` in `wp_insert_post` -- Ticket URL: <http://trac.wordpress.org/ticket/3290#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 25 02:48:03 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 25 02:48:22 2006 Subject: [wp-trac] Re: [WordPress Trac] #3387: Category is ancestor of In-Reply-To: <066.df6e3173d36655149b0cb9c687a4f755@lists.automattic.com> References: <066.df6e3173d36655149b0cb9c687a4f755@lists.automattic.com> Message-ID: <075.bdb22f0b35073c3a01ba3f259d75da2d@lists.automattic.com> #3387: Category is ancestor of -------------------------+-------------------------------------------------- Reporter: donncha | Owner: anonymous Type: enhancement | Status: reopened Priority: normal | Milestone: Component: General | Version: Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by chuyskywalker): * status: closed => reopened * component: Administration => General * resolution: fixed => Comment: This is broken -- the function is called with an underscore ( _ ) suffixed, but defined without it. -- Ticket URL: <http://trac.wordpress.org/ticket/3387#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 25 02:55:53 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 25 02:56:01 2006 Subject: [wp-trac] [WordPress Trac] #3391: Can't click Labels for Radio Buttons in Moderation Queue Message-ID: <066.9a690ceca65d298990d422bbc01acc28@lists.automattic.com> #3391: Can't click Labels for Radio Buttons in Moderation Queue ----------------------------+----------------------------------------------- Reporter: JeremyVisser | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.0.6 Component: Administration | Version: 2.0.5 Severity: minor | Keywords: ----------------------------+----------------------------------------------- In WordPress 2.0.5, with a comment in the moderation queue, go to WordPress Admin ? Manage ? Awaiting Moderation (''x''). Try clicking the labels for the radio buttons "Approve", "Spam", "Delete", "Defer until later". That does not work because the IDs and corresponding {{{label}}} elements do not match. This problem has been fixed for {{{/trunk/}}}, but the 2.0 branch still has the problem. Attached is a patch to fix the problem. -- Ticket URL: <http://trac.wordpress.org/ticket/3391> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 25 03:33:29 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 25 03:33:41 2006 Subject: [wp-trac] Re: [WordPress Trac] #3391: Can't click Labels for Radio Buttons in Moderation Queue In-Reply-To: <066.9a690ceca65d298990d422bbc01acc28@lists.automattic.com> References: <066.9a690ceca65d298990d422bbc01acc28@lists.automattic.com> Message-ID: <075.a438f5349bc2ab478efe2249fc9b6037@lists.automattic.com> #3391: Can't click Labels for Radio Buttons in Moderation Queue ----------------------------+----------------------------------------------- Reporter: JeremyVisser | Owner: shorty114 Type: enhancement | Status: assigned Priority: low | Milestone: 2.0.6 Component: Administration | Version: 2.0.5 Severity: trivial | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by shorty114): * priority: normal => low * status: new => assigned * type: defect => enhancement * severity: minor => trivial * owner: anonymous => shorty114 Comment: I don't this is *absolutely necessary* for 2.0... 2.1 is coming out in ~2 months, can people live without it until then? ;) Also, I would put the <label> wrapped *around* the input. Can't remember why though. -- Ticket URL: <http://trac.wordpress.org/ticket/3391#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 25 03:39:26 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 25 03:39:39 2006 Subject: [wp-trac] Re: [WordPress Trac] #3391: Can't click Labels for Radio Buttons in Moderation Queue In-Reply-To: <066.9a690ceca65d298990d422bbc01acc28@lists.automattic.com> References: <066.9a690ceca65d298990d422bbc01acc28@lists.automattic.com> Message-ID: <075.08525b9ca3d32f6017dd4a5a5fe05a52@lists.automattic.com> #3391: Can't click Labels for Radio Buttons in Moderation Queue ----------------------------+----------------------------------------------- Reporter: JeremyVisser | Owner: shorty114 Type: enhancement | Status: assigned Priority: low | Milestone: 2.0.6 Component: Administration | Version: 2.0.5 Severity: trivial | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by shorty114): Replying to [comment:1 shorty114]: > I don't this is *absolutely necessary* for 2.0... 2.1 is coming out in ~2 months, can people live without it until then? ;) > > Also, I would put the <label> wrapped *around* the input. Can't remember why though. Never mind, this is a good patch. -- Ticket URL: <http://trac.wordpress.org/ticket/3391#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 25 04:01:37 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 25 04:01:45 2006 Subject: [wp-trac] Re: [WordPress Trac] #3391: Can't click Labels for Radio Buttons in Moderation Queue In-Reply-To: <066.9a690ceca65d298990d422bbc01acc28@lists.automattic.com> References: <066.9a690ceca65d298990d422bbc01acc28@lists.automattic.com> Message-ID: <075.adecee2931908aa4c43af28bd0683f9e@lists.automattic.com> #3391: Can't click Labels for Radio Buttons in Moderation Queue ----------------------------+----------------------------------------------- Reporter: JeremyVisser | Owner: shorty114 Type: defect | Status: assigned Priority: low | Milestone: 2.0.6 Component: Administration | Version: 2.0.5 Severity: trivial | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by JeremyVisser): * type: enhancement => defect Comment: Replying to [comment:1 shorty114]: > Also, I would put the <label> wrapped *around* the input. Can't remember why though. The reason I didn't do that is because I'm fixing it the same way Matt fixed it for 2.1. -- Ticket URL: <http://trac.wordpress.org/ticket/3391#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 25 04:20:52 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 25 04:20:57 2006 Subject: [wp-trac] Re: [WordPress Trac] #2700: Reverse-pingbacks for comments In-Reply-To: <066.247dce4954d151acfcfe16fc25909505@lists.automattic.com> References: <066.247dce4954d151acfcfe16fc25909505@lists.automattic.com> Message-ID: <075.f63ca7dfb0d69ee67241f77e5f984d5d@lists.automattic.com> #2700: Reverse-pingbacks for comments -------------------------+-------------------------------------------------- Reporter: geekdreams | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.1 Component: XML-RPC | Version: 2.1 Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Comment (by technosailor): Sounds like a good way to leverage spam/XSS attacks, to be quite frank. Though conceptually, good idea. -- Ticket URL: <http://trac.wordpress.org/ticket/2700#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 25 04:24:41 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 25 04:24:50 2006 Subject: [wp-trac] Re: [WordPress Trac] #2724: Import and export UI tweaks In-Reply-To: <066.12afc14db8a2a609b13852127d28a52c@lists.automattic.com> References: <066.12afc14db8a2a609b13852127d28a52c@lists.automattic.com> Message-ID: <075.a6a5c54189881969ec2f1e9a9765ea39@lists.automattic.com> #2724: Import and export UI tweaks ----------------------------+----------------------------------------------- Reporter: MichaelH | Owner: anonymous Type: defect | Status: reopened Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: needs-patch | ----------------------------+----------------------------------------------- Comment (by technosailor): I laugh because no one is changing my usage of the term "Howdy" and carrying the term into other importers. -- Ticket URL: <http://trac.wordpress.org/ticket/2724#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 25 06:30:00 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 25 06:30:08 2006 Subject: [wp-trac] Re: [WordPress Trac] #3112: Upload bugs In-Reply-To: <066.14e809726ce4b2faf15395e2a4d6167d@lists.automattic.com> References: <066.14e809726ce4b2faf15395e2a4d6167d@lists.automattic.com> Message-ID: <075.8ad73af39cf8a983e6cbdd9ac8cdc452@lists.automattic.com> #3112: Upload bugs ----------------------------+----------------------------------------------- Reporter: kakingho | Owner: anonymous Type: defect | Status: reopened Priority: normal | Milestone: 2.0.6 Component: Administration | Version: 2.0.4 Severity: normal | Resolution: Keywords: needs-patch | ----------------------------+----------------------------------------------- Changes (by ryan): * version: => 2.0.4 * milestone: => 2.0.6 -- Ticket URL: <http://trac.wordpress.org/ticket/3112#comment:8> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 25 06:37:08 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 25 06:37:24 2006 Subject: [wp-trac] Re: [WordPress Trac] #3391: Can't click Labels for Radio Buttons in Moderation Queue In-Reply-To: <066.9a690ceca65d298990d422bbc01acc28@lists.automattic.com> References: <066.9a690ceca65d298990d422bbc01acc28@lists.automattic.com> Message-ID: <075.a18eb837858bcfdb477afe9b2d37a11f@lists.automattic.com> #3391: Can't click Labels for Radio Buttons in Moderation Queue ----------------------------+----------------------------------------------- Reporter: JeremyVisser | Owner: shorty114 Type: defect | Status: assigned Priority: low | Milestone: 2.0.6 Component: Administration | Version: 2.0.5 Severity: trivial | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by markjaquith): Remember, just because 2.1 is coming out, that doesn't mean 2.0 development is dying! Appreciate that you patched it to sync with 2.1 -- Ticket URL: <http://trac.wordpress.org/ticket/3391#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 25 09:04:40 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 25 09:04:46 2006 Subject: [wp-trac] Re: [WordPress Trac] #3384: get_the_category() is broken In-Reply-To: <056.3bcc9069bdc313fd0a41f7117df30547@lists.automattic.com> References: <056.3bcc9069bdc313fd0a41f7117df30547@lists.automattic.com> Message-ID: <065.a8a3957072b03160db2df92d5bd0e679@lists.automattic.com> #3384: get_the_category() is broken -----------------------------+---------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: closed Priority: high | Milestone: 2.1 Component: General | Version: 2.1 Severity: major | Resolution: fixed Keywords: category, posts | -----------------------------+---------------------------------------------- Changes (by tassoman): * status: new => closed * resolution: => fixed Comment: Solved in revision 4532. -- Ticket URL: <http://trac.wordpress.org/ticket/3384#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 25 12:56:17 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 25 12:56:25 2006 Subject: [wp-trac] Re: [WordPress Trac] #3290: Importer strips img class and style In-Reply-To: <066.9ce1f29060f80c36ddb627f9d0cb035c@lists.automattic.com> References: <066.9ce1f29060f80c36ddb627f9d0cb035c@lists.automattic.com> Message-ID: <075.d6411c69627eb470c2500bda6637ea52@lists.automattic.com> #3290: Importer strips img class and style -----------------------------+---------------------------------------------- Reporter: foolswisdom | Owner: anonymous Type: defect | Status: new Priority: high | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: major | Resolution: Keywords: import importer | -----------------------------+---------------------------------------------- Comment (by filosofo): I think the real problem is that wp-admin/admin.php calls kses_init_filters() for *every* import, even for those with admin permissions, and there's no easy way--that I've yet found--for a plugin to disable it. -- Ticket URL: <http://trac.wordpress.org/ticket/3290#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 25 20:34:23 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 25 20:34:30 2006 Subject: [wp-trac] Re: [WordPress Trac] #3384: get_the_category() is broken In-Reply-To: <056.3bcc9069bdc313fd0a41f7117df30547@lists.automattic.com> References: <056.3bcc9069bdc313fd0a41f7117df30547@lists.automattic.com> Message-ID: <065.d44507899fd22d69cd8b1ed5456801b0@lists.automattic.com> #3384: get_the_category() is broken -----------------------------+---------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: closed Priority: high | Milestone: 2.1 Component: General | Version: 2.1 Severity: major | Resolution: fixed Keywords: category, posts | -----------------------------+---------------------------------------------- Comment (by Viper007Bond): [4532] -- Ticket URL: <http://trac.wordpress.org/ticket/3384#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 25 20:36:50 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 25 20:36:57 2006 Subject: [wp-trac] Re: [WordPress Trac] #3384: get_the_category() is broken In-Reply-To: <056.3bcc9069bdc313fd0a41f7117df30547@lists.automattic.com> References: <056.3bcc9069bdc313fd0a41f7117df30547@lists.automattic.com> Message-ID: <065.645afb25372de4f33ba7a8801e466ed6@lists.automattic.com> #3384: get_the_category() is broken -----------------------------+---------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: reopened Priority: high | Milestone: 2.1 Component: General | Version: 2.1 Severity: major | Resolution: Keywords: category, posts | -----------------------------+---------------------------------------------- Changes (by Viper007Bond): * status: closed => reopened * resolution: fixed => Comment: Er, whoops, hit submit without meaning to. Anyway, gonna reopen until it's actually confirmed it's fixed. [4532] is just a version bump. -- Ticket URL: <http://trac.wordpress.org/ticket/3384#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sat Nov 25 22:05:33 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sat Nov 25 22:06:20 2006 Subject: [wp-trac] Re: [WordPress Trac] #3384: get_the_category() is broken In-Reply-To: <056.3bcc9069bdc313fd0a41f7117df30547@lists.automattic.com> References: <056.3bcc9069bdc313fd0a41f7117df30547@lists.automattic.com> Message-ID: <065.bea0bc5b4d12dc8eee6c8abd0a98e1fb@lists.automattic.com> #3384: get_the_category() is broken -----------------------------+---------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: closed Priority: high | Milestone: 2.1 Component: General | Version: 2.1 Severity: major | Resolution: fixed Keywords: category, posts | -----------------------------+---------------------------------------------- Changes (by foolswisdom): * status: reopened => closed * resolution: => fixed Comment: Re-marking as CLOSED fixed as original submitter marked it closed and no one else has said here they are still experiencing this issue. Please reopen with additional details if anyone is still experiencing this problem. Hi Tassoman, Are you saying that you upgraded to r4532 and are no longer seeing the issue? As Viper points out that is different than saying it is resolved *in* that revision. And thank you for the great contribution to WordPress! -- Ticket URL: <http://trac.wordpress.org/ticket/3384#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 26 00:03:33 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 26 00:03:39 2006 Subject: [wp-trac] Re: [WordPress Trac] #1070: 404 error because of common server setting In-Reply-To: <066.ffb7f08ed0cdba2b673d687dc1ec13f3@lists.automattic.com> References: <066.ffb7f08ed0cdba2b673d687dc1ec13f3@lists.automattic.com> Message-ID: <075.a1a33116eeef78eeee44b57373f00295@lists.automattic.com> #1070: 404 error because of common server setting -----------------------------+---------------------------------------------- Reporter: anonymousbugger | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: General | Version: 1.5.1 Severity: major | Resolution: Keywords: dev-feedback | -----------------------------+---------------------------------------------- Comment (by shorty114): Why oh why would you do Index.php instead of index.php... I don't think this is worth fixing. -- Ticket URL: <http://trac.wordpress.org/ticket/1070#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 26 00:20:42 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 26 00:20:54 2006 Subject: [wp-trac] Re: [WordPress Trac] #1070: 404 error because of common server setting In-Reply-To: <066.ffb7f08ed0cdba2b673d687dc1ec13f3@lists.automattic.com> References: <066.ffb7f08ed0cdba2b673d687dc1ec13f3@lists.automattic.com> Message-ID: <075.1eb36e367a8c085ca775773a30942858@lists.automattic.com> #1070: 404 error because of common server setting -----------------------------+---------------------------------------------- Reporter: anonymousbugger | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: General | Version: 1.5.1 Severity: major | Resolution: wontfix Keywords: dev-feedback | -----------------------------+---------------------------------------------- Changes (by foolswisdom): * status: new => closed * resolution: => wontfix Comment: Closing WONTFIX based on nazgul's recommendation and no compelling argument since. -- Ticket URL: <http://trac.wordpress.org/ticket/1070#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 26 05:25:13 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 26 05:25:21 2006 Subject: [wp-trac] Re: [WordPress Trac] #3384: get_the_category() is broken In-Reply-To: <056.3bcc9069bdc313fd0a41f7117df30547@lists.automattic.com> References: <056.3bcc9069bdc313fd0a41f7117df30547@lists.automattic.com> Message-ID: <065.bd1f1a4e94ddc039c6ace00214bf340b@lists.automattic.com> #3384: get_the_category() is broken -----------------------------+---------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: closed Priority: high | Milestone: 2.1 Component: General | Version: 2.1 Severity: major | Resolution: fixed Keywords: category, posts | -----------------------------+---------------------------------------------- Comment (by Viper007Bond): Oh crap, I didn't notice that the person who closed it was the one that opened it. My bad. -- Ticket URL: <http://trac.wordpress.org/ticket/3384#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 26 06:08:46 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 26 06:08:54 2006 Subject: [wp-trac] [WordPress Trac] #3392: TinyMCE version number is off in help Message-ID: <066.44115f9771fdfd97531eb404d384cc7b@lists.automattic.com> #3392: TinyMCE version number is off in help ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: defect | Status: new Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Keywords: has-patch ----------------------------+----------------------------------------------- The TinyMCE version is off in the help window. -- Ticket URL: <http://trac.wordpress.org/ticket/3392> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 26 08:37:29 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 26 09:13:24 2006 Subject: [wp-trac] Re: [WordPress Trac] #3384: get_the_category() is broken In-Reply-To: <056.3bcc9069bdc313fd0a41f7117df30547@lists.automattic.com> References: <056.3bcc9069bdc313fd0a41f7117df30547@lists.automattic.com> Message-ID: <065.8fc466791e52bc889a837864ee372857@lists.automattic.com> #3384: get_the_category() is broken -----------------------------+---------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: closed Priority: high | Milestone: 2.1 Component: General | Version: 2.1 Severity: major | Resolution: fixed Keywords: category, posts | -----------------------------+---------------------------------------------- Comment (by tassoman): Sorry guys I was in a hurry. I wanted to say, one day after, when I upgraded at [http://trac.wordpress.org/changeset/4532 4532] the problem vanished. I hope it's solved. -- Ticket URL: <http://trac.wordpress.org/ticket/3384#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 26 09:53:31 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 26 09:54:18 2006 Subject: [wp-trac] [WordPress Trac] #3393: Akismet plugin missing from menus Message-ID: <056.4081b99544248d4522b2ab9bb5d3cac5@lists.automattic.com> #3393: Akismet plugin missing from menus ----------------------------+----------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: new Priority: high | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Keywords: admin, akismet ----------------------------+----------------------------------------------- I can't get into the admin page of Akismet plugin. While clicking into the dashboard panel (wp-admin/edit.php?page=akismet-admin) displaying "you have XXX spams caught", it returns an error page with the wordpress logo and the following text: '''impossible to load akismet-admin''' -- Ticket URL: <http://trac.wordpress.org/ticket/3393> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 26 20:54:05 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 26 20:54:44 2006 Subject: [wp-trac] [WordPress Trac] #3394: Possible bug in update_option() Message-ID: <066.20738f1c8c7f224f63e0b10b8006c99a@lists.automattic.com> #3394: Possible bug in update_option() -----------------------+---------------------------------------------------- Reporter: roscohead | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: General | Version: Severity: normal | Keywords: -----------------------+---------------------------------------------------- I posted this on the forum, and someone kindly pointed me here :) I think I've hit a bug in the update_option() function. The problem occurs when the $newvalue is an array containing arrays - it checks {{{ // If the new and old values are the same, no need to update. $oldvalue = get_option($option_name); if ( $newvalue == $oldvalue ) { return false; } }}} to see if the value has changed. However this behaves incorrectly when the only change is in the order of elements of the sub-array, the comparison returns true, so the setting is never updated. My workaround is to do a comparison on the serialized versions instead: {{{ // If the new and old values are the same, no need to update. $oldvalue = get_option($option_name); if ( maybe_serialize($newvalue) == maybe_serialize($oldvalue) ) { return false; } }}} This seems to work, and doesn't seem to break anything, but it has only been minimally tested. If there's a better way to fix the problem, feel free to ignore my suggested fix :) ROSCO -- Ticket URL: <http://trac.wordpress.org/ticket/3394> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Sun Nov 26 20:55:56 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Sun Nov 26 20:56:04 2006 Subject: [wp-trac] Re: [WordPress Trac] #3394: Possible bug in update_option() In-Reply-To: <066.20738f1c8c7f224f63e0b10b8006c99a@lists.automattic.com> References: <066.20738f1c8c7f224f63e0b10b8006c99a@lists.automattic.com> Message-ID: <075.31b828087a98be6b5e26785292ffb163@lists.automattic.com> #3394: Possible bug in update_option() -----------------------+---------------------------------------------------- Reporter: roscohead | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: General | Version: 2.0.5 Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Changes (by roscohead): * version: => 2.0.5 -- Ticket URL: <http://trac.wordpress.org/ticket/3394#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 27 07:05:18 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 27 07:05:28 2006 Subject: [wp-trac] Re: [WordPress Trac] #3394: Possible bug in update_option() In-Reply-To: <066.20738f1c8c7f224f63e0b10b8006c99a@lists.automattic.com> References: <066.20738f1c8c7f224f63e0b10b8006c99a@lists.automattic.com> Message-ID: <075.f58a9ad26a80950d9e1628e21c1d867e@lists.automattic.com> #3394: Possible bug in update_option() -----------------------+---------------------------------------------------- Reporter: roscohead | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.0.5 Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Changes (by Viper007Bond): * milestone: => 2.1 Comment: What about a triple equal sign (`===`) instead. Wouldn't that work? -- Ticket URL: <http://trac.wordpress.org/ticket/3394#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 27 08:50:19 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 27 08:50:29 2006 Subject: [wp-trac] Re: [WordPress Trac] #3380: Make autosave interval configurable In-Reply-To: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> References: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> Message-ID: <075.b2e063171813a3626e53471abc9a23d8@lists.automattic.com> #3380: Make autosave interval configurable ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: wontfix Keywords: | ----------------------------+----------------------------------------------- Comment (by Viper007Bond): Replying to [comment:4 foolswisdom]: > I stand by my comment. Present tickets in the problem or feature that they are to achieve, and then present possible solutions. Well I'm glad you're the king of Trac. :rolleyes: >and I don't think is helpful. Nor is closing tickets just because you think they are formatted improperly. Next time I'll write an essay for you. -- Ticket URL: <http://trac.wordpress.org/ticket/3380#comment:8> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 27 17:00:16 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 27 17:26:01 2006 Subject: [wp-trac] [WordPress Trac] #3395: xmlrpc - get the name right Message-ID: <066.473b84893ef9ecf76a5139bbcd4496ac@lists.automattic.com> #3395: xmlrpc - get the name right ----------------------------+----------------------------------------------- Reporter: donncha | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Keywords: ----------------------------+----------------------------------------------- This patch does two things: 1. sanitize the filename 2. passes it to the wp_handle_upload() filter with the correct filename. -- Ticket URL: <http://trac.wordpress.org/ticket/3395> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 27 21:09:58 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 27 21:10:59 2006 Subject: [wp-trac] Re: [WordPress Trac] #3394: Possible bug in update_option() In-Reply-To: <066.20738f1c8c7f224f63e0b10b8006c99a@lists.automattic.com> References: <066.20738f1c8c7f224f63e0b10b8006c99a@lists.automattic.com> Message-ID: <075.7ce8e6a2d4b9b7ddac5f06aa52c9cebb@lists.automattic.com> #3394: Possible bug in update_option() -----------------------+---------------------------------------------------- Reporter: roscohead | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.0.5 Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Comment (by roscohead): D'oh! Of course it would! Thanks for that. -- Ticket URL: <http://trac.wordpress.org/ticket/3394#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 27 21:09:58 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 27 21:11:00 2006 Subject: [wp-trac] Re: [WordPress Trac] #3394: Possible bug in update_option() In-Reply-To: <066.20738f1c8c7f224f63e0b10b8006c99a@lists.automattic.com> References: <066.20738f1c8c7f224f63e0b10b8006c99a@lists.automattic.com> Message-ID: <075.7ce8e6a2d4b9b7ddac5f06aa52c9cebb@lists.automattic.com> #3394: Possible bug in update_option() -----------------------+---------------------------------------------------- Reporter: roscohead | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.0.5 Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Comment (by roscohead): D'oh! Of course it would! Thanks for that. -- Ticket URL: <http://trac.wordpress.org/ticket/3394#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 27 20:02:22 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 27 22:09:39 2006 Subject: [wp-trac] Re: [WordPress Trac] #3380: Make autosave interval configurable In-Reply-To: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> References: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> Message-ID: <075.ea6159ec5d131727c8e611f264561db0@lists.automattic.com> #3380: Make autosave interval configurable ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: wontfix Keywords: | ----------------------------+----------------------------------------------- Comment (by foolswisdom): Viper, The issue is not one of formatting, but one of content. The reasoning of why an enhancement is important often reveals additional solutions. I am sorry that the way I closed the ticket offended you, of course that was not my intention. I have deep respect for your fantastic contribution to WordPress. -- Ticket URL: <http://trac.wordpress.org/ticket/3380#comment:9> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 27 23:09:39 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 27 23:09:51 2006 Subject: [wp-trac] Re: [WordPress Trac] #2984: 404 response header on js.php file In-Reply-To: <066.49582eebe2be1608bd22ece77e0dc1de@lists.automattic.com> References: <066.49582eebe2be1608bd22ece77e0dc1de@lists.automattic.com> Message-ID: <075.235ac355dab1126567d888be556671ca@lists.automattic.com> #2984: 404 response header on js.php file ---------------------+------------------------------------------------------ Reporter: ttscoff | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: General | Version: 2.0.4 Severity: normal | Resolution: Keywords: 404 bug | ---------------------+------------------------------------------------------ Comment (by xurizaemon): Bump. This code shouldn't generate a 404 header in an external file that wants to access WP things, but rather only if WordPress can't find the content. My js.php file parses fine, but WP(2.0) returns a 404 header as a special bonus. So (as a crude workaround) I just rewrote the headers I didn't like, once wp-blog-header.php had done its filth. Alternatively, some other non-404ing method should be available to use WP's functions without it owning the headers. (Perhaps I missed that in the docs.) <? define('WP_USE_THEMES', false) ; require('../../../wp-blog-header.php'); header("HTTP/1.1 200 OK"); header("Status: 200 All rosy") ; ?> 404 should only get set IF wordpress really is dealing with the request, IMO. -- Ticket URL: <http://trac.wordpress.org/ticket/2984#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Mon Nov 27 23:10:48 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Mon Nov 27 23:11:52 2006 Subject: [wp-trac] Re: [WordPress Trac] #2984: 404 response header on js.php file In-Reply-To: <066.49582eebe2be1608bd22ece77e0dc1de@lists.automattic.com> References: <066.49582eebe2be1608bd22ece77e0dc1de@lists.automattic.com> Message-ID: <075.3d81a9fbce69e20cbd19b3bc97006734@lists.automattic.com> #2984: 404 response header on js.php file ---------------------+------------------------------------------------------ Reporter: ttscoff | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: General | Version: 2.0.4 Severity: normal | Resolution: Keywords: 404 bug | ---------------------+------------------------------------------------------ Comment (by xurizaemon): {{{ <? define('WP_USE_THEMES', false) ; require('../../../wp-blog-header.php'); // i'm in wp- content/themes/js.php header("HTTP/1.1 200 OK"); // else we get 404 header("Status: 200 All rosy") ; // what should this really say? ?> }}} -- Ticket URL: <http://trac.wordpress.org/ticket/2984#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 28 00:21:52 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 28 00:22:04 2006 Subject: [wp-trac] [WordPress Trac] #3396: Plugin version, etc. not sanitized like description is Message-ID: <066.5ea4f172713a35c5685b20825b9dfb37@lists.automattic.com> #3396: Plugin version, etc. not sanitized like description is ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: defect | Status: new Priority: lowest | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Keywords: ----------------------------+----------------------------------------------- We sanitize plugin descriptions with kses, so why not the version and such? Try this in a plugin for example: {{{ Version: 1.0 <script type="text/javascript">alert('I haxz0red your PC!');</script> }}} Now of course plugin authors could just put bad JS into the plugin itself, so this isn't really a security ticket, more a "let's-do-the-same-thing- to-all-fields" ticket (either sanitize them all or none). -- Ticket URL: <http://trac.wordpress.org/ticket/3396> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 28 01:08:36 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 28 01:08:44 2006 Subject: [wp-trac] Re: [WordPress Trac] #3290: Importer strips img class and style In-Reply-To: <066.9ce1f29060f80c36ddb627f9d0cb035c@lists.automattic.com> References: <066.9ce1f29060f80c36ddb627f9d0cb035c@lists.automattic.com> Message-ID: <075.f827809004288e5a5c87cc709ce1b8a3@lists.automattic.com> #3290: Importer strips img class and style -----------------------------+---------------------------------------------- Reporter: foolswisdom | Owner: anonymous Type: defect | Status: new Priority: high | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: major | Resolution: Keywords: import importer | -----------------------------+---------------------------------------------- Comment (by foolswisdom): filosofo, my generous teacher! All imports are done with "author" privileges. Thank you for describing the design limitation. ENV: WP trunk r6949 I duplicated that as an "author" posting those img tags are stripped I now see that those tags for img are not allowed because they are not included in in $allowedposttags . I found an old wp-testers thread that says this is for security reasons: http://comox.textdrive.com/pipermail/wp-testers/2005-September/000461.html I found at least one popular theme is very heavy on its use of img class tags, http://cutline.tubetorial.com/image-handling-with-cutline/#comment- 481 PREVIOUS WORKAROUND my-hacks.php file, CUSTOM_TAGS[[br]] [resolved] Can Wordpress Support Pictures Inside Comments? [[br]] http://wordpress.org/support/topic/43139?replies=17 QUESTIONS I am left with the following questions: 1. I would like to better understand the security issues with the class tag, and so far have not found anything on the web. ? 2. How about style, is it safe? Can it be added to $allowedposttags? POSSIBLE SOLUTIONS It seem this bug has exposed two independent issues: * Possibly additional $allowedposttags values * Import with filtering appropriate to the user (if exists) or establish if new [[br]] Code changes for r3430 (Make the xmlrpc user the current user) seems possibly useful -- Ticket URL: <http://trac.wordpress.org/ticket/3290#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 28 01:51:47 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 28 01:51:57 2006 Subject: [wp-trac] [WordPress Trac] #3397: Occasional dbx.js cookie-related JS error Message-ID: <066.bf2ccb2370cebbdc21e22f611072a3d9@lists.automattic.com> #3397: Occasional dbx.js cookie-related JS error ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: defect | Status: new Priority: high | Milestone: 2.0.6 Component: Administration | Version: 2.0.5 Severity: blocker | Keywords: ----------------------------+----------------------------------------------- From time to time, I get a Javascript error from `dbx.js` and the only way to fix it delete the cookie. No idea what causes it, but it seems to happen randomly and has been happening for quite some time. I'm using Firefox and it happened on both 1.5.x and 2.0. Here's the Javascript error that occurs: {{{ Error: this.cookie[i][1] has no properties Source File: http://localhost/wordpress-2.0.x/wp-includes/js/dbx.js Line: 6 }}} -- Ticket URL: <http://trac.wordpress.org/ticket/3397> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 28 01:52:55 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 28 01:53:03 2006 Subject: [wp-trac] Re: [WordPress Trac] #3397: Occasional dbx.js cookie-related JS error In-Reply-To: <066.bf2ccb2370cebbdc21e22f611072a3d9@lists.automattic.com> References: <066.bf2ccb2370cebbdc21e22f611072a3d9@lists.automattic.com> Message-ID: <075.1d542f37b74f3f7bde0436a78059185d@lists.automattic.com> #3397: Occasional dbx.js cookie-related JS error ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: defect | Status: new Priority: high | Milestone: 2.0.6 Component: Administration | Version: 2.0.5 Severity: blocker | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by Viper007Bond): The cookie is `dbx-postmeta` and it happens on both my local server and my blog (I think, hard to remember). -- Ticket URL: <http://trac.wordpress.org/ticket/3397#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 28 02:07:01 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 28 02:07:10 2006 Subject: [wp-trac] Re: [WordPress Trac] #3397: Occasional dbx.js cookie-related JS error In-Reply-To: <066.bf2ccb2370cebbdc21e22f611072a3d9@lists.automattic.com> References: <066.bf2ccb2370cebbdc21e22f611072a3d9@lists.automattic.com> Message-ID: <075.a9dcf8bbfeb7c70957216df47c875308@lists.automattic.com> #3397: Occasional dbx.js cookie-related JS error ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: defect | Status: new Priority: high | Milestone: 2.0.6 Component: Administration | Version: 2.0.5 Severity: blocker | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by foolswisdom): When you say for some time, do you recall if you saw it prior to 2.0.5 ? -- Ticket URL: <http://trac.wordpress.org/ticket/3397#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 28 05:15:05 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 28 05:15:13 2006 Subject: [wp-trac] Re: [WordPress Trac] #3397: Occasional dbx.js cookie-related JS error In-Reply-To: <066.bf2ccb2370cebbdc21e22f611072a3d9@lists.automattic.com> References: <066.bf2ccb2370cebbdc21e22f611072a3d9@lists.automattic.com> Message-ID: <075.18f2cb534113acdd2430d07ea55da708@lists.automattic.com> #3397: Occasional dbx.js cookie-related JS error ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: defect | Status: new Priority: high | Milestone: 2.0.6 Component: Administration | Version: 2.0.5 Severity: blocker | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by Viper007Bond): Yes, it's been happening for a couple versions now. -- Ticket URL: <http://trac.wordpress.org/ticket/3397#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 28 05:19:12 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 28 05:19:20 2006 Subject: [wp-trac] [WordPress Trac] #3398: import data from Geeklog Message-ID: <066.433d19ab30ee19ccf1f1a4efc0af4d4b@lists.automattic.com> #3398: import data from Geeklog ----------------------------+----------------------------------------------- Reporter: justdave | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Keywords: ----------------------------+----------------------------------------------- I recently converted my blog from geeklog to wordpress, and wound up converting the existing TextPattern importer to be able to pull data directly from a Geeklog database and import it to Wordpress. The importer is incomplete, but usable, and currently imports categories, users, posts, and comments. It pretty much does what I needed it to do, and I'm sure someone else can make use of it, and possibly clean it up better. -- Ticket URL: <http://trac.wordpress.org/ticket/3398> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 28 05:37:21 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 28 05:37:28 2006 Subject: [wp-trac] Re: [WordPress Trac] #3398: import data from Geeklog In-Reply-To: <066.433d19ab30ee19ccf1f1a4efc0af4d4b@lists.automattic.com> References: <066.433d19ab30ee19ccf1f1a4efc0af4d4b@lists.automattic.com> Message-ID: <075.912583c22e96f7511e7628ff04e291d5@lists.automattic.com> #3398: import data from Geeklog ----------------------------+----------------------------------------------- Reporter: justdave | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by justdave): also worthy of note: I had to add these to my <VirtualHost> block in my apache config to make it work right: php_value max_execution_time 300 php_value memory_limit 16M -- Ticket URL: <http://trac.wordpress.org/ticket/3398#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 28 09:29:13 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 28 09:29:21 2006 Subject: [wp-trac] Re: [WordPress Trac] #3398: import data from Geeklog In-Reply-To: <066.433d19ab30ee19ccf1f1a4efc0af4d4b@lists.automattic.com> References: <066.433d19ab30ee19ccf1f1a4efc0af4d4b@lists.automattic.com> Message-ID: <075.f2ec88994ddc084e6d4608e1eabb7e68@lists.automattic.com> #3398: import data from Geeklog ----------------------------+----------------------------------------------- Reporter: justdave | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by Viper007Bond): Just add this to the script: {{{ set_time_limit(300); ini_set('memory_limit', '16M'); }}} -- Ticket URL: <http://trac.wordpress.org/ticket/3398#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 28 13:27:00 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 28 13:27:09 2006 Subject: [wp-trac] [WordPress Trac] #3399: i18n issues Message-ID: <050.d1d24a309b8c8eca72345a5c3129f839@lists.automattic.com> #3399: i18n issues ------------------------+--------------------------------------------------- Reporter: nbachiyski | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: minor | Keywords: ------------------------+--------------------------------------------------- Most notably: * wider use of the js_escape function * dbx on-hover messages And numerous little fixes. Expect some more in near future :-) -- Ticket URL: <http://trac.wordpress.org/ticket/3399> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 28 17:10:59 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 28 17:11:20 2006 Subject: [wp-trac] [WordPress Trac] #3400: xmlrpc uploaded files need attachments Message-ID: <066.bb4152eb8480ad4b7d906a491916bde3@lists.automattic.com> #3400: xmlrpc uploaded files need attachments ----------------------------+----------------------------------------------- Reporter: donncha | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Keywords: ----------------------------+----------------------------------------------- Files uploaded through the xmlrpc interface aren't attached to any post. This patch adds them to the post being made. -- Ticket URL: <http://trac.wordpress.org/ticket/3400> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 28 19:12:25 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 28 19:16:42 2006 Subject: [wp-trac] Re: [WordPress Trac] #3400: xmlrpc uploaded files need attachments In-Reply-To: <066.bb4152eb8480ad4b7d906a491916bde3@lists.automattic.com> References: <066.bb4152eb8480ad4b7d906a491916bde3@lists.automattic.com> Message-ID: <075.d65ad9075c5c0cf1066877208bd80da1@lists.automattic.com> #3400: xmlrpc uploaded files need attachments ----------------------------+----------------------------------------------- Reporter: donncha | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by foolswisdom): * version: => 2.1 * milestone: => 2.1 -- Ticket URL: <http://trac.wordpress.org/ticket/3400#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 28 20:52:58 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 28 20:53:20 2006 Subject: [wp-trac] [WordPress Trac] #3401: raquo should receive gettext treatment Message-ID: <066.309ff0d00f3db6bcfee907176d4de18d@lists.automattic.com> #3401: raquo should receive gettext treatment ----------------------------+----------------------------------------------- Reporter: ryan | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Keywords: ----------------------------+----------------------------------------------- This: {{{ __('Do it »'); }}} not this: {{{ __('Do it') . '»' -- Ticket URL: <http://trac.wordpress.org/ticket/3401> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 28 20:54:42 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 28 20:54:52 2006 Subject: [wp-trac] Re: [WordPress Trac] #3399: i18n issues In-Reply-To: <050.d1d24a309b8c8eca72345a5c3129f839@lists.automattic.com> References: <050.d1d24a309b8c8eca72345a5c3129f839@lists.automattic.com> Message-ID: <059.2c24c2c506c2b062aff289c7eb152182@lists.automattic.com> #3399: i18n issues ------------------------+--------------------------------------------------- Reporter: nbachiyski | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: minor | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by ryan): Looks good except raquo should remain within the gettext string. Some locales, especially RTL ones, like to use something else. I opened #3401 for raquo cleanup. -- Ticket URL: <http://trac.wordpress.org/ticket/3399#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 28 21:57:34 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 28 21:57:55 2006 Subject: [wp-trac] Re: [WordPress Trac] #3188: Shouldn't use deprecated functions start_wp In-Reply-To: <044.eaf5fdb38ad397846321cda10f551945@lists.automattic.com> References: <044.eaf5fdb38ad397846321cda10f551945@lists.automattic.com> Message-ID: <053.09ed094bace979e5effbfcd0237df4a0@lists.automattic.com> #3188: Shouldn't use deprecated functions start_wp -------------------------+-------------------------------------------------- Reporter: foolswisdom | Owner: westi Type: defect | Status: reopened Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch | -------------------------+-------------------------------------------------- Changes (by westi): * keywords: => has-patch Comment: Attached patch fixes the exporter to use the API and kills off start_wp for good -- Ticket URL: <http://trac.wordpress.org/ticket/3188#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 28 21:59:00 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 28 21:59:18 2006 Subject: [wp-trac] Re: [WordPress Trac] #3393: Akismet plugin missing from menus In-Reply-To: <056.4081b99544248d4522b2ab9bb5d3cac5@lists.automattic.com> References: <056.4081b99544248d4522b2ab9bb5d3cac5@lists.automattic.com> Message-ID: <065.f8ba38cb290fb1fda064d26f293f68aa@lists.automattic.com> #3393: Akismet plugin missing from menus ----------------------------+----------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: closed Priority: high | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: fixed Keywords: admin, akismet | ----------------------------+----------------------------------------------- Changes (by ryan): * status: new => closed * resolution: => fixed Comment: http://dev.wp-plugins.org/changeset/6957 -- Ticket URL: <http://trac.wordpress.org/ticket/3393#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 28 23:50:19 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 28 23:50:28 2006 Subject: [wp-trac] Re: [WordPress Trac] #3394: Possible bug in update_option() In-Reply-To: <066.20738f1c8c7f224f63e0b10b8006c99a@lists.automattic.com> References: <066.20738f1c8c7f224f63e0b10b8006c99a@lists.automattic.com> Message-ID: <075.ed45fa98629d91a090734a3a507cff62@lists.automattic.com> #3394: Possible bug in update_option() -----------------------+---------------------------------------------------- Reporter: roscohead | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.0.5 Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Comment (by markjaquith): Patch it up! -- Ticket URL: <http://trac.wordpress.org/ticket/3394#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Tue Nov 28 23:55:06 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Tue Nov 28 23:55:14 2006 Subject: [wp-trac] Re: [WordPress Trac] #3290: Importer strips img class and style In-Reply-To: <066.9ce1f29060f80c36ddb627f9d0cb035c@lists.automattic.com> References: <066.9ce1f29060f80c36ddb627f9d0cb035c@lists.automattic.com> Message-ID: <075.67ecbca341b26cf7d68e3cb85231a6a4@lists.automattic.com> #3290: Importer strips img class and style -----------------------------+---------------------------------------------- Reporter: foolswisdom | Owner: anonymous Type: defect | Status: new Priority: high | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: major | Resolution: Keywords: import importer | -----------------------------+---------------------------------------------- Comment (by foolswisdom): 1. 2. Yeah neither class nor style are safe. A friend 'anotherjesse' explained to me how how class could be used to make ~ login prompt, and style can have javascript within it. It seems that the possible solution is limited to allowing importing as filtering appropriate to the user. -- Ticket URL: <http://trac.wordpress.org/ticket/3290#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 00:00:08 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 00:00:15 2006 Subject: [wp-trac] Re: [WordPress Trac] #3380: Make autosave interval configurable In-Reply-To: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> References: <066.6c950a092cead0f7cd945eac74460aa1@lists.automattic.com> Message-ID: <075.f6d95ec57b9c2fda9eba671fb965c03e@lists.automattic.com> #3380: Make autosave interval configurable ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: wontfix Keywords: | ----------------------------+----------------------------------------------- Comment (by markjaquith): Gmail functions well without this being configurable. Do you use Gmail, Viper007Bond? Is there a difference between Gmail's autosave and WP's autosave that makes you desire the interval to be configurable? Is it something we could fix? -- Ticket URL: <http://trac.wordpress.org/ticket/3380#comment:10> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 00:03:43 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 00:03:50 2006 Subject: [wp-trac] Re: [WordPress Trac] #3396: Plugin version, etc. not sanitized like description is In-Reply-To: <066.5ea4f172713a35c5685b20825b9dfb37@lists.automattic.com> References: <066.5ea4f172713a35c5685b20825b9dfb37@lists.automattic.com> Message-ID: <075.2ca496318b55baa741f0713ca07333a3@lists.automattic.com> #3396: Plugin version, etc. not sanitized like description is ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: markjaquith Type: defect | Status: assigned Priority: lowest | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: Keywords: needs-patch | ----------------------------+----------------------------------------------- Changes (by markjaquith): * keywords: => needs-patch * status: new => assigned * owner: anonymous => markjaquith Comment: Agreed re: "all or nothing" I'd go with "all," if only to stave off the inevitable "WordPress Security Bulletin: plugins can p0wn your WordPress!" Patch it up! -- Ticket URL: <http://trac.wordpress.org/ticket/3396#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 00:06:42 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 00:06:54 2006 Subject: [wp-trac] Re: [WordPress Trac] #3397: Occasional dbx.js cookie-related JS error In-Reply-To: <066.bf2ccb2370cebbdc21e22f611072a3d9@lists.automattic.com> References: <066.bf2ccb2370cebbdc21e22f611072a3d9@lists.automattic.com> Message-ID: <075.0682f10faf4fc5bd22c91f6c10becdc8@lists.automattic.com> #3397: Occasional dbx.js cookie-related JS error ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: markjaquith Type: defect | Status: assigned Priority: high | Milestone: 2.0.6 Component: Administration | Version: 2.0.5 Severity: blocker | Resolution: Keywords: needs-patch | ----------------------------+----------------------------------------------- Changes (by markjaquith): * keywords: => needs-patch * status: new => assigned * owner: anonymous => markjaquith Comment: Clarification: 1.5.x and 2.0 are WP version numbers, not FF numbers, right? Attn: Andy Skelton, Robert Deaton I'm no JS guru, but I think this happens when you try to access the cookie's values when the cookie isn't set, so you might be able to fix it by checking <<<this.cookie>>> first. -- Ticket URL: <http://trac.wordpress.org/ticket/3397#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 00:19:34 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 00:19:45 2006 Subject: [wp-trac] [WordPress Trac] #3402: Add global filter for wp_list_pages excludes Message-ID: <066.11257137b884678b178c5c9cffbd8edf@lists.automattic.com> #3402: Add global filter for wp_list_pages excludes -------------------------+-------------------------------------------------- Reporter: markjaquith | Owner: markjaquith Type: enhancement | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Keywords: -------------------------+-------------------------------------------------- Currently, the only way to reliably exclude pages from {{{wp_list_pages()}}} is to use the {{{exclude}}} query param in each instance of the function. Not user-friendly, as it requires template editing. There should be a global filter for this. I'll write the patch in a bit. The filter should probably pass an array of pages already excluded via the {{{exclude=}}} method, and then plugins can just {{{$excludes[] = 34; return $excludes;}}} and we'll {{{implode()}}} -- Ticket URL: <http://trac.wordpress.org/ticket/3402> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 05:13:57 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 05:14:03 2006 Subject: [wp-trac] Re: [WordPress Trac] #3402: Add global filter for wp_list_pages excludes In-Reply-To: <066.11257137b884678b178c5c9cffbd8edf@lists.automattic.com> References: <066.11257137b884678b178c5c9cffbd8edf@lists.automattic.com> Message-ID: <075.dd192baaf6747d4c2f7150926efd6242@lists.automattic.com> #3402: Add global filter for wp_list_pages excludes -----------------------------------+---------------------------------------- Reporter: markjaquith | Owner: markjaquith Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch 2nd-opinion | -----------------------------------+---------------------------------------- Changes (by markjaquith): * keywords: => has-patch 2nd-opinion * status: new => assigned Comment: Patch is up. Will let it sit for a bit, so speak now. -- Ticket URL: <http://trac.wordpress.org/ticket/3402#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 07:58:28 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 07:58:35 2006 Subject: [wp-trac] Re: [WordPress Trac] #3396: Plugin version, etc. not sanitized like description is In-Reply-To: <066.5ea4f172713a35c5685b20825b9dfb37@lists.automattic.com> References: <066.5ea4f172713a35c5685b20825b9dfb37@lists.automattic.com> Message-ID: <075.f1b04d62acb821947797ce76c275bd68@lists.automattic.com> #3396: Plugin version, etc. not sanitized like description is ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: markjaquith Type: defect | Status: assigned Priority: lowest | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: Keywords: needs-patch | ----------------------------+----------------------------------------------- Comment (by Viper007Bond): Roger, captain! -- Ticket URL: <http://trac.wordpress.org/ticket/3396#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 07:59:08 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 07:59:14 2006 Subject: [wp-trac] [WordPress Trac] #3403: XML export lacks category data Message-ID: <066.59c20113d193e1771638f57dadae624c@lists.automattic.com> #3403: XML export lacks category data ----------------------------+----------------------------------------------- Reporter: andy | Owner: andy Type: enhancement | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.5 Severity: normal | Keywords: ----------------------------+----------------------------------------------- Export/import does not maintain category name, description, parent, privacy. -- Ticket URL: <http://trac.wordpress.org/ticket/3403> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 07:59:23 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 07:59:30 2006 Subject: [wp-trac] Re: [WordPress Trac] #3397: Occasional dbx.js cookie-related JS error In-Reply-To: <066.bf2ccb2370cebbdc21e22f611072a3d9@lists.automattic.com> References: <066.bf2ccb2370cebbdc21e22f611072a3d9@lists.automattic.com> Message-ID: <075.d6fe0fd1eccdf13f1fe75686bf59422a@lists.automattic.com> #3397: Occasional dbx.js cookie-related JS error ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: markjaquith Type: defect | Status: assigned Priority: high | Milestone: 2.0.6 Component: Administration | Version: 2.0.5 Severity: blocker | Resolution: Keywords: needs-patch | ----------------------------+----------------------------------------------- Comment (by Viper007Bond): I mean FF versions. This JS didn't exist in WP v1.5.x. ;) -- Ticket URL: <http://trac.wordpress.org/ticket/3397#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 08:03:38 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 08:03:48 2006 Subject: [wp-trac] Re: [WordPress Trac] #3394: Possible bug in update_option() In-Reply-To: <066.20738f1c8c7f224f63e0b10b8006c99a@lists.automattic.com> References: <066.20738f1c8c7f224f63e0b10b8006c99a@lists.automattic.com> Message-ID: <075.9b182349bac09380912626d24460824a@lists.automattic.com> #3394: Possible bug in update_option() ------------------------------+--------------------------------------------- Reporter: roscohead | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.0.5 Severity: normal | Resolution: Keywords: has-patch commit | ------------------------------+--------------------------------------------- Changes (by Viper007Bond): * keywords: has-patch => has-patch commit -- Ticket URL: <http://trac.wordpress.org/ticket/3394#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 08:03:26 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 08:05:30 2006 Subject: [wp-trac] Re: [WordPress Trac] #3394: Possible bug in update_option() In-Reply-To: <066.20738f1c8c7f224f63e0b10b8006c99a@lists.automattic.com> References: <066.20738f1c8c7f224f63e0b10b8006c99a@lists.automattic.com> Message-ID: <075.d008c35560900cf6bb19154db2bbb54d@lists.automattic.com> #3394: Possible bug in update_option() -----------------------+---------------------------------------------------- Reporter: roscohead | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: General | Version: 2.0.5 Severity: normal | Resolution: Keywords: has-patch | -----------------------+---------------------------------------------------- Changes (by Viper007Bond): * keywords: => has-patch -- Ticket URL: <http://trac.wordpress.org/ticket/3394#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 08:09:00 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 08:09:07 2006 Subject: [wp-trac] Re: [WordPress Trac] #3396: Plugin version, etc. not sanitized like description is In-Reply-To: <066.5ea4f172713a35c5685b20825b9dfb37@lists.automattic.com> References: <066.5ea4f172713a35c5685b20825b9dfb37@lists.automattic.com> Message-ID: <075.c309553ebaee1a9305c40672c7cb47f8@lists.automattic.com> #3396: Plugin version, etc. not sanitized like description is ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: markjaquith Type: defect | Status: assigned Priority: lowest | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: Keywords: has-patch | ----------------------------+----------------------------------------------- Changes (by Viper007Bond): * keywords: needs-patch => has-patch -- Ticket URL: <http://trac.wordpress.org/ticket/3396#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 08:31:36 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 08:31:57 2006 Subject: [wp-trac] Re: [WordPress Trac] #3397: Occasional dbx.js cookie-related JS error In-Reply-To: <066.bf2ccb2370cebbdc21e22f611072a3d9@lists.automattic.com> References: <066.bf2ccb2370cebbdc21e22f611072a3d9@lists.automattic.com> Message-ID: <075.3e86485323ca9ed76bc98e5b8cd0c63f@lists.automattic.com> #3397: Occasional dbx.js cookie-related JS error ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: markjaquith Type: defect | Status: assigned Priority: high | Milestone: 2.0.6 Component: Administration | Version: 2.0.5 Severity: blocker | Resolution: Keywords: needs-patch | ----------------------------+----------------------------------------------- Comment (by markjaquith): Doh! Also note that in that comment I forgot the code syntax for Trac. It was late. It appears that we're using DBX 2.01 but 2.05 is the current version. Maybe upgrading will fix that error. Patch coming. -- Ticket URL: <http://trac.wordpress.org/ticket/3397#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 09:10:36 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 09:10:44 2006 Subject: [wp-trac] Re: [WordPress Trac] #3397: Occasional dbx.js cookie-related JS error In-Reply-To: <066.bf2ccb2370cebbdc21e22f611072a3d9@lists.automattic.com> References: <066.bf2ccb2370cebbdc21e22f611072a3d9@lists.automattic.com> Message-ID: <075.1a49b9e8d1295abea9976566421d1b2b@lists.automattic.com> #3397: Occasional dbx.js cookie-related JS error ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: markjaquith Type: defect | Status: assigned Priority: high | Milestone: 2.0.6 Component: Administration | Version: 2.0.5 Severity: blocker | Resolution: Keywords: has-patch | ----------------------------+----------------------------------------------- Changes (by markjaquith): * keywords: needs-patch => has-patch Comment: There's a patch for /branches/2.0/ Trunk is already using DBX 2.05 Viper007Bond: have you experienced this problem while using 2.1 or WP.com? -- Ticket URL: <http://trac.wordpress.org/ticket/3397#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 09:25:57 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 09:26:04 2006 Subject: [wp-trac] Re: [WordPress Trac] #3396: Plugin version, etc. not sanitized like description is In-Reply-To: <066.5ea4f172713a35c5685b20825b9dfb37@lists.automattic.com> References: <066.5ea4f172713a35c5685b20825b9dfb37@lists.automattic.com> Message-ID: <075.5b3dcae1c6b85ffcc111f63a260b7781@lists.automattic.com> #3396: Plugin version, etc. not sanitized like description is ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: markjaquith Type: defect | Status: closed Priority: lowest | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: fixed Keywords: has-patch | ----------------------------+----------------------------------------------- Comment (by markjaquith): Minor nitpicky note: In the future, when using whitespace to align blocks of similar assignments (like the row of KSES calls), use spaces instead of tabs to make them line up. Many text editors can set tabs to be varying sizes, so they won't line up unless someone is using the same size tabs as you. -- Ticket URL: <http://trac.wordpress.org/ticket/3396#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 09:45:17 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 09:45:27 2006 Subject: [wp-trac] Re: [WordPress Trac] #3396: Plugin version, etc. not sanitized like description is In-Reply-To: <066.5ea4f172713a35c5685b20825b9dfb37@lists.automattic.com> References: <066.5ea4f172713a35c5685b20825b9dfb37@lists.automattic.com> Message-ID: <075.e356aa7e631514736d7a771c4eedf843@lists.automattic.com> #3396: Plugin version, etc. not sanitized like description is ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: markjaquith Type: defect | Status: closed Priority: lowest | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: fixed Keywords: has-patch | ----------------------------+----------------------------------------------- Comment (by Viper007Bond): Well there is a quasi-standard, but good point. :) -- Ticket URL: <http://trac.wordpress.org/ticket/3396#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 10:41:10 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 10:41:19 2006 Subject: [wp-trac] [WordPress Trac] #3404: "ID" column title isn't centered on Manage -> Posts Message-ID: <066.aa26b0f3a082589a1fa6bbd537f14ee6@lists.automattic.com> #3404: "ID" column title isn't centered on Manage -> Posts ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: defect | Status: new Priority: lowest | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: trivial | Keywords: has-patch ----------------------------+----------------------------------------------- Trivial, but it looks better and matches the other pages. -- Ticket URL: <http://trac.wordpress.org/ticket/3404> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 11:14:40 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 11:14:51 2006 Subject: [wp-trac] Re: [WordPress Trac] #3402: Add global filter for wp_list_pages excludes In-Reply-To: <066.11257137b884678b178c5c9cffbd8edf@lists.automattic.com> References: <066.11257137b884678b178c5c9cffbd8edf@lists.automattic.com> Message-ID: <075.50ca98a31ebe23102b1916bfa4f4b69b@lists.automattic.com> #3402: Add global filter for wp_list_pages excludes -----------------------------------+---------------------------------------- Reporter: markjaquith | Owner: markjaquith Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch 2nd-opinion | -----------------------------------+---------------------------------------- Comment (by ryan): Kool with a K, which is kooler than cool. -- Ticket URL: <http://trac.wordpress.org/ticket/3402#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 11:33:31 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 11:33:43 2006 Subject: [wp-trac] [WordPress Trac] #3405: Support Post Enclosures Via XML-RPC MetaWeblog API Function Message-ID: <066.df52417a7c56d1c73fb98a76b3f73c6f@lists.automattic.com> #3405: Support Post Enclosures Via XML-RPC MetaWeblog API Function -------------------------+-------------------------------------------------- Reporter: swinton | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.0.6 Component: XML-RPC | Version: 2.0.5 Severity: normal | Keywords: enclosure meta mw_newPost MetaWeblog API XMLRPC -------------------------+-------------------------------------------------- I have attached a patchfile for xmlrpc.php (xmlrpc.php.diff) which adds enclosure support to the mw_newPost function. The change supports enclosures as specified by the metaWeblog API spec (http://www.xmlrpc.com/metaWeblogApi), i.e. enclosures can be specified as part of the content struct. -- Ticket URL: <http://trac.wordpress.org/ticket/3405> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 14:35:40 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 14:36:06 2006 Subject: [wp-trac] Re: [WordPress Trac] #3403: XML export lacks category data In-Reply-To: <066.59c20113d193e1771638f57dadae624c@lists.automattic.com> References: <066.59c20113d193e1771638f57dadae624c@lists.automattic.com> Message-ID: <075.0881ac036be431179c433af46dc6fd1b@lists.automattic.com> #3403: XML export lacks category data -------------------------------------+-------------------------------------- Reporter: andy | Owner: andy Type: enhancement | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.5 Severity: normal | Resolution: Keywords: has-patch needs-testing | -------------------------------------+-------------------------------------- Changes (by andy): * keywords: => has-patch needs-testing Comment: Attached patch exports and imports categories with hierarchy. -- Ticket URL: <http://trac.wordpress.org/ticket/3403#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 17:16:33 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 17:33:30 2006 Subject: [wp-trac] [WordPress Trac] #3406: Use HTML4 instead of XHTML1 Message-ID: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> #3406: Use HTML4 instead of XHTML1 -----------------------+---------------------------------------------------- Reporter: TedNelson | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Template | Version: Severity: normal | Keywords: -----------------------+---------------------------------------------------- Please use HTML4 instead of XHTML1 in the output from WordPress blogs. The browser used by the majority of my readers doesn't support XHTML1, and is having to rely on error handling to handle your output. -- Ticket URL: <http://trac.wordpress.org/ticket/3406> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 17:36:53 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 17:37:22 2006 Subject: [wp-trac] Re: [WordPress Trac] #3406: Use HTML4 instead of XHTML1 In-Reply-To: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> References: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> Message-ID: <075.fd0556d2a506dd93373676d30176dc4e@lists.automattic.com> #3406: Use HTML4 instead of XHTML1 -----------------------+---------------------------------------------------- Reporter: TedNelson | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Template | Version: Severity: normal | Resolution: wontfix Keywords: | -----------------------+---------------------------------------------------- Changes (by technosailor): * status: new => closed * resolution: => wontfix Comment: The problem is is that most modern browsers (and thus most WP users) can parse xhtml1 and in fact, xhtml1 is the defacto standard on the internet. Code is Poetry. I think I speak for all WP devs when I say this won't be changed. -- Ticket URL: <http://trac.wordpress.org/ticket/3406#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 18:15:29 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 18:15:48 2006 Subject: [wp-trac] Re: [WordPress Trac] #3406: Use HTML4 instead of XHTML1 In-Reply-To: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> References: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> Message-ID: <075.5ee5243e3ac42bcc127af782b14bdb0c@lists.automattic.com> #3406: Use HTML4 instead of XHTML1 -----------------------+---------------------------------------------------- Reporter: TedNelson | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Template | Version: Severity: normal | Resolution: wontfix Keywords: | -----------------------+---------------------------------------------------- Comment (by link92): The whole issue is that it _isn't_ parsed as XHTML 1. It's parsed as HTML. -- Ticket URL: <http://trac.wordpress.org/ticket/3406#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 18:17:54 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 18:18:17 2006 Subject: [wp-trac] Re: [WordPress Trac] #3406: Use HTML4 instead of XHTML1 In-Reply-To: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> References: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> Message-ID: <075.f5a8a3d018ddd0fc761d488e2fe61227@lists.automattic.com> #3406: Use HTML4 instead of XHTML1 -----------------------+---------------------------------------------------- Reporter: TedNelson | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Template | Version: Severity: normal | Resolution: wontfix Keywords: | -----------------------+---------------------------------------------------- Comment (by technosailor): Let's take the argument out of the arena of speculation and talk facts. What browser are your users using? -- Ticket URL: <http://trac.wordpress.org/ticket/3406#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 18:25:45 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 18:26:15 2006 Subject: [wp-trac] Re: [WordPress Trac] #3406: Use HTML4 instead of XHTML1 In-Reply-To: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> References: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> Message-ID: <075.405a1658132eacaaffae9bc733673d56@lists.automattic.com> #3406: Use HTML4 instead of XHTML1 -----------------------+---------------------------------------------------- Reporter: TedNelson | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Template | Version: Severity: normal | Resolution: wontfix Keywords: | -----------------------+---------------------------------------------------- Comment (by link92): It's irrelevant - any UA which follows the HTTP specification will parse it as a text/html document, an HTML document. For a UA to parse it as XHTML is MUST be sent as application/xhtml+xml. -- Ticket URL: <http://trac.wordpress.org/ticket/3406#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 18:30:01 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 18:30:25 2006 Subject: [wp-trac] Re: [WordPress Trac] #3406: Use HTML4 instead of XHTML1 In-Reply-To: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> References: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> Message-ID: <075.9e3c9aa359e0e62bb6cd520beccff318@lists.automattic.com> #3406: Use HTML4 instead of XHTML1 -----------------------+---------------------------------------------------- Reporter: TedNelson | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Template | Version: Severity: normal | Resolution: wontfix Keywords: | -----------------------+---------------------------------------------------- Comment (by Nazgul): Some background info on XHTML browser support: http://en.wikipedia.org/wiki/XHTML#Adoption -- Ticket URL: <http://trac.wordpress.org/ticket/3406#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 18:54:47 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 18:55:06 2006 Subject: [wp-trac] Re: [WordPress Trac] #3406: Use HTML4 instead of XHTML1 In-Reply-To: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> References: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> Message-ID: <075.acaa461d4ca6740a373a30df6b862185@lists.automattic.com> #3406: Use HTML4 instead of XHTML1 -----------------------+---------------------------------------------------- Reporter: TedNelson | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Template | Version: Severity: normal | Resolution: wontfix Keywords: | -----------------------+---------------------------------------------------- Comment (by Viper007Bond): Themes are independent of WordPress. You can make/use a HTML 4.01 theme without any problems. ;) -- Ticket URL: <http://trac.wordpress.org/ticket/3406#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 19:02:18 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 19:02:41 2006 Subject: [wp-trac] Re: [WordPress Trac] #3406: Use HTML4 instead of XHTML1 In-Reply-To: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> References: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> Message-ID: <075.965fb8749d88909aeddc13273974a54a@lists.automattic.com> #3406: Use HTML4 instead of XHTML1 -----------------------+---------------------------------------------------- Reporter: TedNelson | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Template | Version: Severity: normal | Resolution: wontfix Keywords: | -----------------------+---------------------------------------------------- Comment (by link92): Viper007Bond, you can't. There are places where " />" is hardcoded (a simple output buffer won't help, because then you can't use valid attributes such as title="bleh />"). -- Ticket URL: <http://trac.wordpress.org/ticket/3406#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 19:50:40 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 19:50:55 2006 Subject: [wp-trac] Re: [WordPress Trac] #3406: Use HTML4 instead of XHTML1 In-Reply-To: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> References: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> Message-ID: <075.750983914cdb65c392fd66505667d297@lists.automattic.com> #3406: Use HTML4 instead of XHTML1 -----------------------+---------------------------------------------------- Reporter: TedNelson | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Template | Version: Severity: normal | Resolution: wontfix Keywords: | -----------------------+---------------------------------------------------- Comment (by Viper007Bond): Oh, right, right, generated content. Forgot about that. D'oh! Well anyway, this is 2006. Time for people to stop using Netscape or whatever as their browser. -- Ticket URL: <http://trac.wordpress.org/ticket/3406#comment:8> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 20:12:25 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 20:12:47 2006 Subject: [wp-trac] [WordPress Trac] #3407: TinyMCE bugs Message-ID: <066.e671f089aa478fb419e58f6a06064718@lists.automattic.com> #3407: TinyMCE bugs -------------------------------+-------------------------------------------- Reporter: Denis-de-Bernardy | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Keywords: -------------------------------+-------------------------------------------- - It sometimes chokes when you type too fast. In particular, the Return key. - It or WordPress sometimes produces junk like <div /> which breaks css- based layouts in IE. - It's a huge mess when users paste from FrontPage and include the html, head and body tags. - It's an even bigger mess when users paste from Word. Enjoy. D. -- Ticket URL: <http://trac.wordpress.org/ticket/3407> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 20:20:02 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 20:20:23 2006 Subject: [wp-trac] Re: [WordPress Trac] #3399: i18n issues In-Reply-To: <050.d1d24a309b8c8eca72345a5c3129f839@lists.automattic.com> References: <050.d1d24a309b8c8eca72345a5c3129f839@lists.automattic.com> Message-ID: <059.0da13adb2020b2b815218c493e6f39c6@lists.automattic.com> #3399: i18n issues ------------------------+--------------------------------------------------- Reporter: nbachiyski | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: minor | Resolution: fixed Keywords: | ------------------------+--------------------------------------------------- Comment (by foolswisdom): This fix seems to have caused a bug that was resolved in r4539. -- Ticket URL: <http://trac.wordpress.org/ticket/3399#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 20:48:05 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 20:48:26 2006 Subject: [wp-trac] Re: [WordPress Trac] #1371: Allowing HTML in post titles In-Reply-To: <066.a2feb6e5c7418566463847737f16c1c4@lists.automattic.com> References: <066.a2feb6e5c7418566463847737f16c1c4@lists.automattic.com> Message-ID: <075.73ae0a8076eb74054f531bde16644498@lists.automattic.com> #1371: Allowing HTML in post titles ----------------------------------------------------------------------------------------------+ Reporter: MaThIbUs | Owner: MathiasBynens Type: enhancement | Status: new Priority: lowest | Milestone: 2.2 Component: Template | Version: 1.5.2 Severity: normal | Resolution: Keywords: kubrick title attribute html validation bg|dev-feedback bg|2nd-opinion has-patch | ----------------------------------------------------------------------------------------------+ Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1371#comment:14> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 20:49:30 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 20:50:01 2006 Subject: [wp-trac] Re: [WordPress Trac] #1829: Assign categories to images In-Reply-To: <066.28b03246b85f70b1ff747399ddae9248@lists.automattic.com> References: <066.28b03246b85f70b1ff747399ddae9248@lists.automattic.com> Message-ID: <075.ec7656a0f32d7694dff73495f925d230@lists.automattic.com> #1829: Assign categories to images -----------------------------+---------------------------------------------- Reporter: IoZ | Owner: anonymous Type: enhancement | Status: new Priority: lowest | Milestone: 2.2 Component: Administration | Version: 1.6 Severity: normal | Resolution: Keywords: image uploading | -----------------------------+---------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1829#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 20:49:52 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 20:50:19 2006 Subject: [wp-trac] Re: [WordPress Trac] #1971: Trackback "response" not used consistently In-Reply-To: <066.366ff7faf6fa1a4f3c38f0371ebb5e2d@lists.automattic.com> References: <066.366ff7faf6fa1a4f3c38f0371ebb5e2d@lists.automattic.com> Message-ID: <075.abcb3575736e19a37819cfc23135fa96@lists.automattic.com> #1971: Trackback "response" not used consistently ------------------------+--------------------------------------------------- Reporter: NathanWong | Owner: anonymous Type: defect | Status: new Priority: lowest | Milestone: 2.2 Component: General | Version: 1.6 Severity: trivial | Resolution: Keywords: | ------------------------+--------------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1971#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 20:51:26 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 20:51:43 2006 Subject: [wp-trac] Re: [WordPress Trac] #2121: Edit / Preview links on edit screens appear unstyled In-Reply-To: <066.21aefebf5ab5a66c1b883c177b3f99c3@lists.automattic.com> References: <066.21aefebf5ab5a66c1b883c177b3f99c3@lists.automattic.com> Message-ID: <075.68bbb867506f6860bcf0d9d5ce7ccc36@lists.automattic.com> #2121: Edit / Preview links on edit screens appear unstyled -------------------------------+-------------------------------------------- Reporter: ryanduff | Owner: anonymous Type: defect | Status: closed Priority: lowest | Milestone: 2.1 Component: Administration | Version: 2.0 Severity: normal | Resolution: invalid Keywords: edit preview link | -------------------------------+-------------------------------------------- Changes (by matt): * status: new => closed * resolution: => invalid Comment: These links are gone. -- Ticket URL: <http://trac.wordpress.org/ticket/2121#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 20:52:48 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 20:53:17 2006 Subject: [wp-trac] Re: [WordPress Trac] #2280: Opera Uploads iFrame Issue In-Reply-To: <066.e800c075d902ced9589d92b1200b1e38@lists.automattic.com> References: <066.e800c075d902ced9589d92b1200b1e38@lists.automattic.com> Message-ID: <075.1ee92a50482806a4a2a1cd486ef25801@lists.automattic.com> #2280: Opera Uploads iFrame Issue ----------------------------+----------------------------------------------- Reporter: schestowitz | Owner: anonymous Type: defect | Status: closed Priority: lowest | Milestone: 2.1 Component: Administration | Version: 2.0 Severity: trivial | Resolution: worksforme Keywords: | ----------------------------+----------------------------------------------- Changes (by matt): * status: new => closed * resolution: => worksforme Comment: No feedback, closing. -- Ticket URL: <http://trac.wordpress.org/ticket/2280#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 20:53:23 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 20:53:42 2006 Subject: [wp-trac] Re: [WordPress Trac] #2421: Create advanded option to allow posts to have same slug? In-Reply-To: <066.0451f184eee6acb86d17fb72215f4312@lists.automattic.com> References: <066.0451f184eee6acb86d17fb72215f4312@lists.automattic.com> Message-ID: <075.824c7737d2f94fd3324dbddd8db77292@lists.automattic.com> #2421: Create advanded option to allow posts to have same slug? --------------------------+------------------------------------------------- Reporter: Viper007Bond | Owner: markjaquith Type: enhancement | Status: closed Priority: lowest | Milestone: 2.1 Component: General | Version: 2.0.1 Severity: normal | Resolution: wontfix Keywords: bg|has-patch | --------------------------+------------------------------------------------- Changes (by matt): * status: assigned => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/2421#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 20:54:12 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 20:54:42 2006 Subject: [wp-trac] Re: [WordPress Trac] #3024: "Store uploads in this folder" default In-Reply-To: <066.f41ead8a814803a96d2b171b97056c59@lists.automattic.com> References: <066.f41ead8a814803a96d2b171b97056c59@lists.automattic.com> Message-ID: <075.76933449d3582ac3cef8d7af690ad7ae@lists.automattic.com> #3024: "Store uploads in this folder" default ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: defect | Status: closed Priority: lowest | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: trivial | Resolution: worksforme Keywords: | ----------------------------+----------------------------------------------- Changes (by matt): * status: new => closed * resolution: => worksforme -- Ticket URL: <http://trac.wordpress.org/ticket/3024#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 20:54:34 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 20:55:05 2006 Subject: [wp-trac] Re: [WordPress Trac] #3307: Add i18n support to function get_archives() In-Reply-To: <066.3d8d033666ec8824e0395d60fc092589@lists.automattic.com> References: <066.3d8d033666ec8824e0395d60fc092589@lists.automattic.com> Message-ID: <075.26589c0255f828fa5f70b89e8899ea67@lists.automattic.com> #3307: Add i18n support to function get_archives() ----------------------------+----------------------------------------------- Reporter: yskins | Owner: anonymous Type: defect | Status: closed Priority: lowest | Milestone: 2.1 Component: Administration | Version: 2.0.4 Severity: normal | Resolution: duplicate Keywords: i18n | ----------------------------+----------------------------------------------- Changes (by matt): * status: new => closed * resolution: => duplicate -- Ticket URL: <http://trac.wordpress.org/ticket/3307#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 20:55:14 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 20:55:34 2006 Subject: [wp-trac] Re: [WordPress Trac] #3321: Empty list item in default theme's sidebar In-Reply-To: <066.11bcbeeb1070458348ddc8a0d5ed6fe2@lists.automattic.com> References: <066.11bcbeeb1070458348ddc8a0d5ed6fe2@lists.automattic.com> Message-ID: <075.eb41ced8e91826a329302880f191727d@lists.automattic.com> #3321: Empty list item in default theme's sidebar -------------------------+-------------------------------------------------- Reporter: idle | Owner: anonymous Type: enhancement | Status: closed Priority: lowest | Milestone: 2.1 Component: Template | Version: 2.0.5 Severity: trivial | Resolution: wontfix Keywords: | -------------------------+-------------------------------------------------- Changes (by matt): * status: new => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/3321#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:00:06 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:00:23 2006 Subject: [wp-trac] Re: [WordPress Trac] #787: bad PRIMARY key for the table wp_post2cat In-Reply-To: <066.65bb704158a15dba2a4c279790c4e06c@lists.automattic.com> References: <066.65bb704158a15dba2a4c279790c4e06c@lists.automattic.com> Message-ID: <075.5eb289f77759a5fdcec02b1c850e0323@lists.automattic.com> #787: bad PRIMARY key for the table wp_post2cat --------------------------+------------------------------------------------- Reporter: michel v | Owner: ketsugi Type: defect | Status: new Priority: low | Milestone: 2.2 Component: Optimization | Version: 2.0.4 Severity: minor | Resolution: Keywords: | --------------------------+------------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/787#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:00:48 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:01:11 2006 Subject: [wp-trac] Re: [WordPress Trac] #1485: Don't use trailingslashed IRIs if the user doesn't prefer them In-Reply-To: <066.0ce3909f436a92abe4d6b66115ebacd3@lists.automattic.com> References: <066.0ce3909f436a92abe4d6b66115ebacd3@lists.automattic.com> Message-ID: <075.90b5c1c0cee73083a97a8c33e5f17759@lists.automattic.com> #1485: Don't use trailingslashed IRIs if the user doesn't prefer them -------------------------------------------------------------------------------------+ Reporter: MathiasBynens | Owner: markjaquith Type: enhancement | Status: assigned Priority: low | Milestone: 2.2 Component: Template | Version: 1.6 Severity: normal | Resolution: Keywords: permalink permalinks iridesign bg|dev-feedback bg|2nd-opinion has-patch | -------------------------------------------------------------------------------------+ Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1485#comment:18> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:02:22 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:02:51 2006 Subject: [wp-trac] Re: [WordPress Trac] #3407: TinyMCE bugs In-Reply-To: <066.e671f089aa478fb419e58f6a06064718@lists.automattic.com> References: <066.e671f089aa478fb419e58f6a06064718@lists.automattic.com> Message-ID: <075.0026ec969ed5b78afdae903137e80915@lists.automattic.com> #3407: TinyMCE bugs -------------------------------+-------------------------------------------- Reporter: Denis-de-Bernardy | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Resolution: Keywords: | -------------------------------+-------------------------------------------- Comment (by ryan): Regarding pasting from Word, tinyMCE does have a special filter for that accessible from the advanced toolbar (Alt+Shift+V). -- Ticket URL: <http://trac.wordpress.org/ticket/3407#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:03:32 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:03:57 2006 Subject: [wp-trac] Re: [WordPress Trac] #1754: Feature request: pass reason for moderation/spam flag In-Reply-To: <066.beba34a54a7aae0fe6786dd73fa346ee@lists.automattic.com> References: <066.beba34a54a7aae0fe6786dd73fa346ee@lists.automattic.com> Message-ID: <075.1e0b3b01fae533faf2b990ca7c419c36@lists.automattic.com> #1754: Feature request: pass reason for moderation/spam flag ---------------------------------------------------+------------------------ Reporter: dougal | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.2 Component: General | Version: 1.6 Severity: normal | Resolution: Keywords: featurerequest spam plugins api hooks | ---------------------------------------------------+------------------------ Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1754#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:03:48 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:04:23 2006 Subject: [wp-trac] Re: [WordPress Trac] #1998: "Size of the post box" input box too small In-Reply-To: <066.c34765d00409a83b40ebdb26faaa3d12@lists.automattic.com> References: <066.c34765d00409a83b40ebdb26faaa3d12@lists.automattic.com> Message-ID: <075.2b233219180e911f58aec0cbefebee1c@lists.automattic.com> #1998: "Size of the post box" input box too small -----------------------------------------------------------+---------------- Reporter: tysontate | Owner: masquerade Type: defect | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.0 Severity: trivial | Resolution: wontfix Keywords: inputbox sizeofpostbox bg|has-patch bg|commit | -----------------------------------------------------------+---------------- Changes (by matt): * status: new => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/1998#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:04:02 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:04:29 2006 Subject: [wp-trac] Re: [WordPress Trac] #2031: Ability to go directly so subpage in admin panel In-Reply-To: <066.644c2f891db09ee01809b1d514f305ff@lists.automattic.com> References: <066.644c2f891db09ee01809b1d514f305ff@lists.automattic.com> Message-ID: <075.03490d0c3096389e9d44be0731b7f124@lists.automattic.com> #2031: Ability to go directly so subpage in admin panel ------------------------------------+--------------------------------------- Reporter: smachet | Owner: anonymous Type: enhancement | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.0 Severity: normal | Resolution: wontfix Keywords: navigation, simplicity | ------------------------------------+--------------------------------------- Changes (by matt): * status: new => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/2031#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:04:23 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:04:38 2006 Subject: [wp-trac] Re: [WordPress Trac] #2156: Unbalanced quotes break RTE structure In-Reply-To: <066.76097952384fa25dbe737255de7c3034@lists.automattic.com> References: <066.76097952384fa25dbe737255de7c3034@lists.automattic.com> Message-ID: <075.97043ca90951dd1b604280d6de99b666@lists.automattic.com> #2156: Unbalanced quotes break RTE structure ----------------------------+----------------------------------------------- Reporter: schestowitz | Owner: anonymous Type: defect | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.0 Severity: minor | Resolution: wontfix Keywords: | ----------------------------+----------------------------------------------- Changes (by matt): * status: new => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/2156#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:04:40 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:05:05 2006 Subject: [wp-trac] Re: [WordPress Trac] #2200: Ability to hide preview In-Reply-To: <066.66030d68d5b53480594bf4443ca2dfa4@lists.automattic.com> References: <066.66030d68d5b53480594bf4443ca2dfa4@lists.automattic.com> Message-ID: <075.32968a8e250f5ba834473af7357a27f8@lists.automattic.com> #2200: Ability to hide preview -----------------------------------+---------------------------------------- Reporter: hypercubed | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.2 Component: Administration | Version: 2.0 Severity: normal | Resolution: Keywords: 2nd-opinion has-patch | -----------------------------------+---------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2200#comment:9> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:05:44 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:06:05 2006 Subject: [wp-trac] Re: [WordPress Trac] #1577: New Hook: future_post In-Reply-To: <066.83848ae048c49f07b79b4b12df4d5fd1@lists.automattic.com> References: <066.83848ae048c49f07b79b4b12df4d5fd1@lists.automattic.com> Message-ID: <075.95d60ea564277720c2ee562556e9cec9@lists.automattic.com> #1577: New Hook: future_post ---------------------------------------------------------+------------------ Reporter: skippy | Owner: markjaquith Type: defect | Status: closed Priority: low | Milestone: 2.1 Component: General | Version: 1.5.2 Severity: normal | Resolution: fixed Keywords: bg|has-patch bg|dev-feedback bg|2nd-opinion | ---------------------------------------------------------+------------------ Changes (by ryan): * status: assigned => closed * resolution: => fixed -- Ticket URL: <http://trac.wordpress.org/ticket/1577#comment:9> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:05:51 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:06:15 2006 Subject: [wp-trac] Re: [WordPress Trac] #2252: Write page : timestamp checkbox is useless In-Reply-To: <066.45be0d8771a5787870985de33ce8dce4@lists.automattic.com> References: <066.45be0d8771a5787870985de33ce8dce4@lists.automattic.com> Message-ID: <075.a81a2527f7771525e26db0a9092b87e6@lists.automattic.com> #2252: Write page : timestamp checkbox is useless ------------------------------------------+--------------------------------- Reporter: xibe | Owner: anonymous Type: enhancement | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.0 Severity: normal | Resolution: worksforme Keywords: timestamp checkbox usability | ------------------------------------------+--------------------------------- Changes (by matt): * status: new => closed * resolution: => worksforme -- Ticket URL: <http://trac.wordpress.org/ticket/2252#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:09:34 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:10:32 2006 Subject: [wp-trac] Re: [WordPress Trac] #2259: autop creates unclosed paras inside list items In-Reply-To: <066.90e66525c2255a57844f2d40d3babe14@lists.automattic.com> References: <066.90e66525c2255a57844f2d40d3babe14@lists.automattic.com> Message-ID: <075.06c6fb425243bdfe48abf0c180daea77@lists.automattic.com> #2259: autop creates unclosed paras inside list items --------------------------+------------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: defect | Status: reopened Priority: low | Milestone: 2.2 Component: General | Version: 2.0 Severity: minor | Resolution: Keywords: | --------------------------+------------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2259#comment:9> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:10:05 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:10:42 2006 Subject: [wp-trac] Re: [WordPress Trac] #2275: Check "From:" on post-by-email In-Reply-To: <066.74f35f913d0e747c80e3d86228fca6f1@lists.automattic.com> References: <066.74f35f913d0e747c80e3d86228fca6f1@lists.automattic.com> Message-ID: <075.59e4e44f8c9cd096e9a3c316079f4cc5@lists.automattic.com> #2275: Check "From:" on post-by-email -------------------------+-------------------------------------------------- Reporter: skeltoac | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.2 Component: General | Version: 2.0 Severity: normal | Resolution: Keywords: needs-patch | -------------------------+-------------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2275#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:10:25 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:10:45 2006 Subject: [wp-trac] Re: [WordPress Trac] #2391: User defined thumbnail size In-Reply-To: <066.e12b4d85f2875cc46b65bedf75f0b19a@lists.automattic.com> References: <066.e12b4d85f2875cc46b65bedf75f0b19a@lists.automattic.com> Message-ID: <075.5afcb89cedcff60666b259db7eb19819@lists.automattic.com> #2391: User defined thumbnail size ----------------------------+----------------------------------------------- Reporter: hypercubed | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.2 Component: Administration | Version: 2.0 Severity: normal | Resolution: Keywords: bg|2nd-opinion | ----------------------------+----------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2391#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:10:45 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:11:16 2006 Subject: [wp-trac] Re: [WordPress Trac] #2470: <strike> sucks, <del> does not In-Reply-To: <066.391364284bd5537648406174bd2be505@lists.automattic.com> References: <066.391364284bd5537648406174bd2be505@lists.automattic.com> Message-ID: <075.9a5b5bd9f570968519df194182da0e75@lists.automattic.com> #2470: <strike> sucks, <del> does not ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: markjaquith Type: defect | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.0.1 Severity: minor | Resolution: wontfix Keywords: has-patch | ----------------------------+----------------------------------------------- Changes (by matt): * status: assigned => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/2470#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:11:10 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:11:40 2006 Subject: [wp-trac] Re: [WordPress Trac] #2539: Better maintainability of client-server administration code. In-Reply-To: <066.f9f6c5fac995352cc77c6dd12d8531a3@lists.automattic.com> References: <066.f9f6c5fac995352cc77c6dd12d8531a3@lists.automattic.com> Message-ID: <075.e0e8c4742af34392cde2e1480440af1e@lists.automattic.com> #2539: Better maintainability of client-server administration code. ----------------------+----------------------------------------------------- Reporter: mdawaffe | Owner: anonymous Type: defect | Status: new Priority: low | Milestone: 2.2 Component: General | Version: 2.0.1 Severity: normal | Resolution: Keywords: AJAX | ----------------------+----------------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2539#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:11:50 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:12:17 2006 Subject: [wp-trac] Re: [WordPress Trac] #2566: moderation may fail due to memory constraints In-Reply-To: <054.21e92a936508ca0c5b7daee4940dcf8d@lists.automattic.com> References: <054.21e92a936508ca0c5b7daee4940dcf8d@lists.automattic.com> Message-ID: <063.9798c2b49f59d4ccc28910082ff57a6c@lists.automattic.com> #2566: moderation may fail due to memory constraints --------------------------+------------------------------------------------- Reporter: fimion | Owner: markjaquith Type: defect | Status: closed Priority: low | Milestone: 2.1 Component: Optimization | Version: 2.0 Severity: minor | Resolution: wontfix Keywords: | --------------------------+------------------------------------------------- Changes (by matt): * status: assigned => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/2566#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:12:18 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:12:57 2006 Subject: [wp-trac] Re: [WordPress Trac] #2640: dos line endings confuse xgettext In-Reply-To: <066.2d785dc3a9a3776657a0e4119deabc76@lists.automattic.com> References: <066.2d785dc3a9a3776657a0e4119deabc76@lists.automattic.com> Message-ID: <075.cb30c73ec0a08408bb2ae19ccbdbb4a5@lists.automattic.com> #2640: dos line endings confuse xgettext ------------------------+--------------------------------------------------- Reporter: nbachiyski | Owner: anonymous Type: defect | Status: closed Priority: low | Milestone: 2.1 Component: General | Version: 2.1 Severity: minor | Resolution: worksforme Keywords: has-patch | ------------------------+--------------------------------------------------- Changes (by matt): * status: new => closed * resolution: => worksforme -- Ticket URL: <http://trac.wordpress.org/ticket/2640#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:12:32 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:12:59 2006 Subject: [wp-trac] Re: [WordPress Trac] #2702: Easier way to change page order (AJAX?) In-Reply-To: <066.16049b713296e4233392f4110a99b901@lists.automattic.com> References: <066.16049b713296e4233392f4110a99b901@lists.automattic.com> Message-ID: <075.a34f4af04cec778384f3f0071f7f6300@lists.automattic.com> #2702: Easier way to change page order (AJAX?) ----------------------------------------+----------------------------------- Reporter: FireMotion | Owner: anonymous Type: defect | Status: new Priority: low | Milestone: 2.2 Component: Administration | Version: 2.0 Severity: normal | Resolution: Keywords: ajax js list-manipulation? | ----------------------------------------+----------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2702#comment:10> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:12:36 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:13:04 2006 Subject: [wp-trac] Re: [WordPress Trac] #209: Subject line of sent e-mails is not UTF-8 In-Reply-To: <043.9ee9eb0dd13ea4643c3c53cb430e2ff5@lists.automattic.com> References: <043.9ee9eb0dd13ea4643c3c53cb430e2ff5@lists.automattic.com> Message-ID: <052.184094d964b89e899cb0bfc6b925f23c@lists.automattic.com> #209: Subject line of sent e-mails is not UTF-8 ---------------------------------------------------------+------------------ Reporter: crculver | Owner: ryan Type: defect | Status: assigned Priority: normal | Milestone: Component: Administration | Version: 2.0.4 Severity: normal | Resolution: Keywords: bg|2nd-opinion bg|dev-feedback bg|has-patch | ---------------------------------------------------------+------------------ Changes (by shorty114): * keywords: bg|2nd-opinion bg|dev-feedback bg|needs-patch => bg|2nd- opinion bg|dev-feedback bg|has-patch -- Ticket URL: <http://trac.wordpress.org/ticket/209#comment:17> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:13:18 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:13:48 2006 Subject: [wp-trac] Re: [WordPress Trac] #2716: Some messages for the export file In-Reply-To: <066.af83919faaf40be68f73c89a52584244@lists.automattic.com> References: <066.af83919faaf40be68f73c89a52584244@lists.automattic.com> Message-ID: <075.8e50d0a1a8ed4cc83b06ff0136a45e9e@lists.automattic.com> #2716: Some messages for the export file ----------------------------+----------------------------------------------- Reporter: Potter_System | Owner: anonymous Type: defect | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: trivial | Resolution: wontfix Keywords: has-patch | ----------------------------+----------------------------------------------- Changes (by matt): * status: new => closed * resolution: => wontfix Comment: Not crazy about this language. -- Ticket URL: <http://trac.wordpress.org/ticket/2716#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:14:10 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:14:44 2006 Subject: [wp-trac] Re: [WordPress Trac] #2965: Permalinks with category may give a 404 error if /category/ is not in the URL In-Reply-To: <066.d2d643981c21256ab2c310bf81c31e4e@lists.automattic.com> References: <066.d2d643981c21256ab2c310bf81c31e4e@lists.automattic.com> Message-ID: <075.052e78ecf95114348683e057da549d3e@lists.automattic.com> #2965: Permalinks with category may give a 404 error if /category/ is not in the URL -------------------------------------+-------------------------------------- Reporter: PozHonks | Owner: anonymous Type: defect | Status: new Priority: low | Milestone: 2.2 Component: General | Version: 2.0.3 Severity: minor | Resolution: Keywords: permalinks category 404 | -------------------------------------+-------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2965#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:14:43 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:15:15 2006 Subject: [wp-trac] Re: [WordPress Trac] #3032: Snow number of comments for each member in Authors & Users tab in admin cp . In-Reply-To: <060.88eb91acef795d64215a9587574bf791@lists.automattic.com> References: <060.88eb91acef795d64215a9587574bf791@lists.automattic.com> Message-ID: <069.61b2a085985506eab6050b188ac76043@lists.automattic.com> #3032: Snow number of comments for each member in Authors & Users tab in admin cp . ----------------------------+----------------------------------------------- Reporter: war59312 | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.2 Component: Administration | Version: 2.1 Severity: trivial | Resolution: Keywords: bg|has-patch | ----------------------------+----------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/3032#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:15:48 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:16:18 2006 Subject: [wp-trac] Re: [WordPress Trac] #3406: Use HTML4 instead of XHTML1 In-Reply-To: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> References: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> Message-ID: <075.57517a1bbed08c6a84aba2ca5e7f48ef@lists.automattic.com> #3406: Use HTML4 instead of XHTML1 -----------------------+---------------------------------------------------- Reporter: TedNelson | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Template | Version: Severity: normal | Resolution: wontfix Keywords: | -----------------------+---------------------------------------------------- Comment (by lachlanhunt): The problem is that WordPress does not use a proper XML pipeline to ensure that the content is well-formed. It uses string-based processing to concatenate strings of markup together, regexes to find and replace all sorts of things, and other nasty little hacks all over the place. So much so, that even claiming that WordPress supports XHTML is absolutely bogus - it doesn't and it shouldn't pretend to. The reality is, even if all browsers started supporting application/xhtml+xml tomorrow and didn't have any major issues with it (like they currently do), it would be impractical to change the MIME type of WordPress from text/html because it only takes one small error for the result to be fatal. I know there are many authors out there that are diligent enough to ensure their own markup is well formed, but for the average user, the tool must do that for them. It's such a [http://hsivonen.iki.fi/producing-xml/ fundamental flaw with the way WordPress has been built], the only sane choice is to give up the myth that WordPress is even capable of producing XHTML; it's a tag-soup CMS only. However, I don't expect this bug to be fixed, I knew it would never be before it was even filed. -- Ticket URL: <http://trac.wordpress.org/ticket/3406#comment:9> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:16:29 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:16:54 2006 Subject: [wp-trac] Re: [WordPress Trac] #3377: Atom feed contradicts itself In-Reply-To: <066.d79d5753398a3325a9464cd011a28c9f@lists.automattic.com> References: <066.d79d5753398a3325a9464cd011a28c9f@lists.automattic.com> Message-ID: <075.92691fb2deda08964de0bf482eb57ae0@lists.automattic.com> #3377: Atom feed contradicts itself -----------------------------------------------------------+---------------- Reporter: link92 | Owner: anonymous Type: defect | Status: new Priority: low | Milestone: 2.0.6 Component: General | Version: 2.0.5 Severity: normal | Resolution: Keywords: bg|dev-feedback bg|2nd-opinion bg|needs-patch | -----------------------------------------------------------+---------------- Changes (by shorty114): * priority: normal => low * keywords: => bg|dev-feedback bg|2nd-opinion bg|needs-patch * version: => 2.0.5 * milestone: => 2.0.6 Comment: It would make sense that once it's escaped, it can be used as text/plain. But maybe do type="text/html" instead? -- Ticket URL: <http://trac.wordpress.org/ticket/3377#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:16:53 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:17:19 2006 Subject: [wp-trac] Re: [WordPress Trac] #3105: Post screen category checklist borked in internet explorer In-Reply-To: <066.5393efcf83091ac6fc8de71e847e6e41@lists.automattic.com> References: <066.5393efcf83091ac6fc8de71e847e6e41@lists.automattic.com> Message-ID: <075.0dc56c58ee3fbbe5b54b9089f576b256@lists.automattic.com> #3105: Post screen category checklist borked in internet explorer ----------------------------+----------------------------------------------- Reporter: matt | Owner: anonymous Type: defect | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: fixed Keywords: | ----------------------------+----------------------------------------------- Changes (by matt): * status: new => closed * resolution: => fixed Comment: This has been fixed in [4515]. -- Ticket URL: <http://trac.wordpress.org/ticket/3105#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:17:17 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:17:37 2006 Subject: [wp-trac] Re: [WordPress Trac] #3377: Atom feed contradicts itself In-Reply-To: <066.d79d5753398a3325a9464cd011a28c9f@lists.automattic.com> References: <066.d79d5753398a3325a9464cd011a28c9f@lists.automattic.com> Message-ID: <075.b015e187ac0ffa3df0178e3b33e7593d@lists.automattic.com> #3377: Atom feed contradicts itself --------------------------------------------+------------------------------- Reporter: link92 | Owner: anonymous Type: defect | Status: new Priority: low | Milestone: 2.0.6 Component: General | Version: 2.0.5 Severity: normal | Resolution: Keywords: bg|dev-feedback bg|2nd-opinion | --------------------------------------------+------------------------------- Changes (by shorty114): * keywords: bg|dev-feedback bg|2nd-opinion bg|needs-patch => bg|dev- feedback bg|2nd-opinion -- Ticket URL: <http://trac.wordpress.org/ticket/3377#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:17:12 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:17:40 2006 Subject: [wp-trac] Re: [WordPress Trac] #3161: DBX Cookies Not Cross Version Compatible In-Reply-To: <066.560ec6d7c7d1465f4d8f8aed3214d085@lists.automattic.com> References: <066.560ec6d7c7d1465f4d8f8aed3214d085@lists.automattic.com> Message-ID: <075.1cd7dd4f2aabc661425577b676da842b@lists.automattic.com> #3161: DBX Cookies Not Cross Version Compatible ----------------------------+----------------------------------------------- Reporter: intoxination | Owner: anonymous Type: defect | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: trivial | Resolution: wontfix Keywords: dbx cookies | ----------------------------+----------------------------------------------- Changes (by matt): * status: new => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/3161#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:17:38 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:18:12 2006 Subject: [wp-trac] Re: [WordPress Trac] #3377: Atom feed contradicts itself In-Reply-To: <066.d79d5753398a3325a9464cd011a28c9f@lists.automattic.com> References: <066.d79d5753398a3325a9464cd011a28c9f@lists.automattic.com> Message-ID: <075.e6eaa5f8bce429688d5521e00049415c@lists.automattic.com> #3377: Atom feed contradicts itself --------------------------------------------+------------------------------- Reporter: link92 | Owner: shorty114 Type: defect | Status: assigned Priority: low | Milestone: 2.0.6 Component: General | Version: 2.0.5 Severity: normal | Resolution: Keywords: bg|dev-feedback bg|2nd-opinion | --------------------------------------------+------------------------------- Changes (by shorty114): * status: new => assigned * owner: anonymous => shorty114 Comment: I would be glad to do a patch but any devs have an opinion? -- Ticket URL: <http://trac.wordpress.org/ticket/3377#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:16:02 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:19:55 2006 Subject: [wp-trac] Re: [WordPress Trac] #3095: Can't escape characters for date format in Options > General In-Reply-To: <066.1caee79ab923b47088d8885397fda827@lists.automattic.com> References: <066.1caee79ab923b47088d8885397fda827@lists.automattic.com> Message-ID: <075.4f89c52a2034f69d9d3e185b82b4b1de@lists.automattic.com> #3095: Can't escape characters for date format in Options > General ----------------------------+----------------------------------------------- Reporter: pandem | Owner: mdawaffe Type: defect | Status: assigned Priority: low | Milestone: 2.2 Component: Administration | Version: 2.1 Severity: minor | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/3095#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:22:11 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:22:50 2006 Subject: [wp-trac] Re: [WordPress Trac] #3377: Atom feed contradicts itself In-Reply-To: <066.d79d5753398a3325a9464cd011a28c9f@lists.automattic.com> References: <066.d79d5753398a3325a9464cd011a28c9f@lists.automattic.com> Message-ID: <075.dc6ff95193de1915538bff720948dc89@lists.automattic.com> #3377: Atom feed contradicts itself --------------------------------------------+------------------------------- Reporter: link92 | Owner: shorty114 Type: defect | Status: closed Priority: low | Milestone: 2.0.6 Component: General | Version: 2.0.5 Severity: normal | Resolution: wontfix Keywords: bg|dev-feedback bg|2nd-opinion | --------------------------------------------+------------------------------- Changes (by matt): * status: assigned => closed * resolution: => wontfix Comment: Since our feeds currently work everywhere, I'm not inclined to change this. -- Ticket URL: <http://trac.wordpress.org/ticket/3377#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:22:33 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:23:27 2006 Subject: [wp-trac] Re: [WordPress Trac] #3249: Nothing in wp-db.php is translatable In-Reply-To: <066.ce84a9cb70d9476e4e6f9d5e55238739@lists.automattic.com> References: <066.ce84a9cb70d9476e4e6f9d5e55238739@lists.automattic.com> Message-ID: <075.e494d57bae177d66d6768645f771acad@lists.automattic.com> #3249: Nothing in wp-db.php is translatable ---------------------------------+------------------------------------------ Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: closed Priority: low | Milestone: 2.1 Component: General | Version: 2.1 Severity: minor | Resolution: wontfix Keywords: DB i18n needs-patch | ---------------------------------+------------------------------------------ Changes (by matt): * status: new => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/3249#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 20:59:51 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:23:53 2006 Subject: [wp-trac] Re: [WordPress Trac] #148: view paginated pages as single entry for printing In-Reply-To: <042.def7d39c887da0a8ff3311b0d4ebe71c@lists.automattic.com> References: <042.def7d39c887da0a8ff3311b0d4ebe71c@lists.automattic.com> Message-ID: <051.c18fb87f210623e932f2d8d5dc327606@lists.automattic.com> #148: view paginated pages as single entry for printing --------------------------------------+------------------------------------- Reporter: Grod | Owner: mdawaffe Type: enhancement | Status: closed Priority: low | Milestone: 2.1 Component: General | Version: Severity: normal | Resolution: wontfix Keywords: bg|2nd-opinion has-patch | --------------------------------------+------------------------------------- Changes (by matt): * status: assigned => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/148#comment:11> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 20:52:14 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:24:11 2006 Subject: [wp-trac] Re: [WordPress Trac] #2129: left align the code tag In-Reply-To: <066.833f5637af6bd009513842c0f53e8bd3@lists.automattic.com> References: <066.833f5637af6bd009513842c0f53e8bd3@lists.automattic.com> Message-ID: <075.85b7fb8825eb93c4e6c09a3c3133d700@lists.automattic.com> #2129: left align the code tag ------------------------------------------------------+--------------------- Reporter: johnjosephbachir | Owner: robmiller Type: enhancement | Status: closed Priority: lowest | Milestone: 2.1 Component: Template | Version: 2.0 Severity: trivial | Resolution: wontfix Keywords: code-tag style bg|dev-feedback has-patch | ------------------------------------------------------+--------------------- Changes (by matt): * status: assigned => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/2129#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:24:38 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:25:10 2006 Subject: [wp-trac] Re: [WordPress Trac] #3285: add_menu_page + add_submenu_page bug In-Reply-To: <066.26d7b62be24a3cfe15e6d6fb671db424@lists.automattic.com> References: <066.26d7b62be24a3cfe15e6d6fb671db424@lists.automattic.com> Message-ID: <075.36e52d464a359b4490e443580a78dd35@lists.automattic.com> #3285: add_menu_page + add_submenu_page bug ----------------------------+----------------------------------------------- Reporter: arena | Owner: anonymous Type: enhancement | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.0.4 Severity: minor | Resolution: worksforme Keywords: | ----------------------------+----------------------------------------------- Changes (by matt): * status: new => closed * resolution: => worksforme -- Ticket URL: <http://trac.wordpress.org/ticket/3285#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:25:21 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:25:38 2006 Subject: [wp-trac] Re: [WordPress Trac] #3382: formatting.php - sanitize_file() In-Reply-To: <066.dd15520aa8d2f6875960999724ce59da@lists.automattic.com> References: <066.dd15520aa8d2f6875960999724ce59da@lists.automattic.com> Message-ID: <075.5f22352a2cf5a1cfa1a6c89edc8d70d7@lists.automattic.com> #3382: formatting.php - sanitize_file() ------------------------------------------+--------------------------------- Reporter: donncha | Owner: shorty114 Type: enhancement | Status: assigned Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Resolution: Keywords: bg|has-patch bg|dev-feedback | ------------------------------------------+--------------------------------- Changes (by shorty114): * keywords: => bg|has-patch bg|dev-feedback * status: new => assigned * owner: anonymous => shorty114 -- Ticket URL: <http://trac.wordpress.org/ticket/3382#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:25:18 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:25:49 2006 Subject: [wp-trac] Re: [WordPress Trac] #3311: Visual rich editor doesn't handle HTML correctly (linebreaks,   , <, > , & , IFRAME) In-Reply-To: <066.e0aeea32d7f624204682e023ea9e010f@lists.automattic.com> References: <066.e0aeea32d7f624204682e023ea9e010f@lists.automattic.com> Message-ID: <075.c81a347fe155663f255da4655dcec585@lists.automattic.com> #3311: Visual rich editor doesn't handle HTML correctly (linebreaks,  , <, >, &, IFRAME) ----------------------------+----------------------------------------------- Reporter: ceefour | Owner: anonymous Type: defect | Status: new Priority: low | Milestone: 2.2 Component: Administration | Version: 2.0.4 Severity: minor | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/3311#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:25:36 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:26:01 2006 Subject: [wp-trac] Re: [WordPress Trac] #3355: e-mail "mark as spam" link shows yes/no dialog even when comment is already spam In-Reply-To: <066.a6b68d805b0561fa7c64aa97ebbb0ab7@lists.automattic.com> References: <066.a6b68d805b0561fa7c64aa97ebbb0ab7@lists.automattic.com> Message-ID: <075.bf0c29a5fa78338de316213293d78536@lists.automattic.com> #3355: e-mail "mark as spam" link shows yes/no dialog even when comment is already spam ----------------------------+----------------------------------------------- Reporter: markjaquith | Owner: anonymous Type: defect | Status: closed Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: trivial | Resolution: wontfix Keywords: comment spam | ----------------------------+----------------------------------------------- Changes (by matt): * status: new => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/3355#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:34:36 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:34:55 2006 Subject: [wp-trac] Re: [WordPress Trac] #1540: Date format returned by wp_get_archives is not localizable In-Reply-To: <066.f159754cdee0b432fa5e4f9ec2e8ede9@lists.automattic.com> References: <066.f159754cdee0b432fa5e4f9ec2e8ede9@lists.automattic.com> Message-ID: <075.3b59c40227e9f7170277fb6c5f2e28bd@lists.automattic.com> #1540: Date format returned by wp_get_archives is not localizable -----------------------------------------------------+---------------------- Reporter: stephenju | Owner: skippy Type: defect | Status: assigned Priority: lowest | Milestone: 2.0.6 Component: Template | Version: 1.5.1.2 Severity: normal | Resolution: Keywords: bg|needs-patch bg|2nd-opinion has-patch | -----------------------------------------------------+---------------------- Changes (by ryan): * milestone: 2.1 => 2.0.6 -- Ticket URL: <http://trac.wordpress.org/ticket/1540#comment:8> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:36:31 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:36:50 2006 Subject: [wp-trac] Re: [WordPress Trac] #3370: Do not have permission to add category. In-Reply-To: <066.70d47b11909d090da6f4f0afcfd8da92@lists.automattic.com> References: <066.70d47b11909d090da6f4f0afcfd8da92@lists.automattic.com> Message-ID: <075.7d9841a724dea7cdd1638acaf6dee47b@lists.automattic.com> #3370: Do not have permission to add category. ----------------------------------------+----------------------------------- Reporter: computerwolf | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: 2.0.5 Severity: normal | Resolution: Keywords: category permission adding | ----------------------------------------+----------------------------------- Comment (by foolswisdom): Hi computerwolf, Still at a loss as to what is causing this. As this has not been reported more generally, it is likely something specific to your environment. Any other clues? How are you connected to the Internet? Is it over proxy? -- Ticket URL: <http://trac.wordpress.org/ticket/3370#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:43:37 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:43:51 2006 Subject: [wp-trac] Re: [WordPress Trac] #935: client/admin code separation In-Reply-To: <066.9e255594cdc843e12139936ed2252e26@lists.automattic.com> References: <066.9e255594cdc843e12139936ed2252e26@lists.automattic.com> Message-ID: <075.4ede60511cbc76c6dc2b8f83a317e000@lists.automattic.com> #935: client/admin code separation -----------------------------+---------------------------------------------- Reporter: michel v | Owner: skippy Type: defect | Status: closed Priority: normal | Milestone: Component: General | Version: Severity: minor | Resolution: wontfix Keywords: bg|dev-feedback | -----------------------------+---------------------------------------------- Changes (by shorty114): * keywords: bg|dev-feedback bg|needs-patch => bg|dev-feedback * status: assigned => closed * resolution: => wontfix * cc: mikelittle (removed) Comment: Too much work for only maybe a completely fractional increase in performance, if any. -- Ticket URL: <http://trac.wordpress.org/ticket/935#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:45:03 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:45:26 2006 Subject: [wp-trac] Re: [WordPress Trac] #1225: cat_name and category_nicename inconsistency In-Reply-To: <066.eef96f8f0e8b5946fafe8c2233cd355a@lists.automattic.com> References: <066.eef96f8f0e8b5946fafe8c2233cd355a@lists.automattic.com> Message-ID: <075.16a97fb108509c04916ad7ae1363ddb8@lists.automattic.com> #1225: cat_name and category_nicename inconsistency -------------------------------+-------------------------------------------- Reporter: Denis de Bernardy | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: General | Version: Severity: trivial | Resolution: wontfix Keywords: | -------------------------------+-------------------------------------------- Changes (by shorty114): * status: new => closed * resolution: => wontfix Comment: It works, this is 2 years old... WONTFIX. Patch welcome, but it would probably pretty complicated due to legacy issues. -- Ticket URL: <http://trac.wordpress.org/ticket/1225#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:51:19 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:51:46 2006 Subject: [wp-trac] Re: [WordPress Trac] #1081: Implement language tagging In-Reply-To: <066.e3c45ceb913b1bb5ae9bb14e573ddb8e@lists.automattic.com> References: <066.e3c45ceb913b1bb5ae9bb14e573ddb8e@lists.automattic.com> Message-ID: <075.2820a4610bf0b1d8927a02b430d0fa03@lists.automattic.com> #1081: Implement language tagging --------------------------------------------+------------------------------- Reporter: kim | Owner: shorty114 Type: enhancement | Status: assigned Priority: low | Milestone: Component: General | Version: 1.5.1 Severity: normal | Resolution: Keywords: bg|dev-feedback bg|2nd-opinion | --------------------------------------------+------------------------------- Changes (by shorty114): * priority: normal => low * keywords: => bg|dev-feedback bg|2nd-opinion * status: new => assigned * owner: anonymous => shorty114 * cc: idanso (removed) Comment: The header() part would be easy, and why not just include the meta tag in wp_head hook? -- Ticket URL: <http://trac.wordpress.org/ticket/1081#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:54:31 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:54:53 2006 Subject: [wp-trac] Re: [WordPress Trac] #952: cruftfree URLs based on ErrorDocument don't work right on some servers In-Reply-To: <066.ac76b52c9ff430b4807d597686febce6@lists.automattic.com> References: <066.ac76b52c9ff430b4807d597686febce6@lists.automattic.com> Message-ID: <075.4068d81fca389e126ad9b1b03f3e69f6@lists.automattic.com> #952: cruftfree URLs based on ErrorDocument don't work right on some servers ----------------------------+----------------------------------------------- Reporter: gbhugo | Owner: matt Type: defect | Status: closed Priority: normal | Milestone: Component: Administration | Version: 1.5 Severity: minor | Resolution: wontfix Keywords: | ----------------------------+----------------------------------------------- Changes (by shorty114): * status: assigned => closed * resolution: => wontfix Comment: 2 years old, wontfix. If someone wants to do a patch, feel free and submit it. -- Ticket URL: <http://trac.wordpress.org/ticket/952#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:55:01 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:55:33 2006 Subject: [wp-trac] Re: [WordPress Trac] #952: cruftfree URLs based on ErrorDocument don't work right on some servers In-Reply-To: <066.ac76b52c9ff430b4807d597686febce6@lists.automattic.com> References: <066.ac76b52c9ff430b4807d597686febce6@lists.automattic.com> Message-ID: <075.58d2311b3b99272baff4a91a2e3ae186@lists.automattic.com> #952: cruftfree URLs based on ErrorDocument don't work right on some servers ----------------------------+----------------------------------------------- Reporter: gbhugo | Owner: matt Type: defect | Status: closed Priority: normal | Milestone: Component: Administration | Version: 1.5 Severity: minor | Resolution: wontfix Keywords: | ----------------------------+----------------------------------------------- Comment (by shorty114): Discussed in IRC: We've done lots of fixes to that ErrorCode stuff in the last two years. Let's assume fixed. I know it works for Litespeed and other non-Apache servers. -- Ryan -- Ticket URL: <http://trac.wordpress.org/ticket/952#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 21:58:47 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 21:59:11 2006 Subject: [wp-trac] Re: [WordPress Trac] #1118: [i18n] Ship WP w/ lang packs, auto detect language, provide switch in admin centre In-Reply-To: <066.eec7b2ea7546cf906dc456d87108bce4@lists.automattic.com> References: <066.eec7b2ea7546cf906dc456d87108bce4@lists.automattic.com> Message-ID: <075.e10b702e639b431502da3063d75dd740@lists.automattic.com> #1118: [i18n] Ship WP w/ lang packs, auto detect language, provide switch in admin centre -------------------------+-------------------------------------------------- Reporter: TigerDE2 | Owner: anonymous Type: enhancement | Status: closed Priority: low | Milestone: Component: General | Version: 1.5.1 Severity: normal | Resolution: wontfix Keywords: | -------------------------+-------------------------------------------------- Changes (by shorty114): * priority: normal => low * status: new => closed * resolution: => wontfix Comment: The switch is in wp-config.php, it's a basic variable so it has to be there before we load anything else. If you want other language packs, look at http://codex.wordpress.org/WordPress_in_Your_Language -- Ticket URL: <http://trac.wordpress.org/ticket/1118#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:00:55 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:01:21 2006 Subject: [wp-trac] Re: [WordPress Trac] #3401: raquo should receive gettext treatment In-Reply-To: <066.309ff0d00f3db6bcfee907176d4de18d@lists.automattic.com> References: <066.309ff0d00f3db6bcfee907176d4de18d@lists.automattic.com> Message-ID: <075.570bfbf9af245789489eec24faac4751@lists.automattic.com> #3401: raquo should receive gettext treatment ----------------------------+----------------------------------------------- Reporter: ryan | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by shorty114): I think some langauges actually use this to switch it to «, such as Arabic, since it's right-to-left, so it reverses the ». -- Ticket URL: <http://trac.wordpress.org/ticket/3401#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:13:34 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:13:50 2006 Subject: [wp-trac] Re: [WordPress Trac] #1081: Implement language tagging In-Reply-To: <066.e3c45ceb913b1bb5ae9bb14e573ddb8e@lists.automattic.com> References: <066.e3c45ceb913b1bb5ae9bb14e573ddb8e@lists.automattic.com> Message-ID: <075.7dcf0951e7c0283a69559cb2e678b1b9@lists.automattic.com> #1081: Implement language tagging --------------------------------------------+------------------------------- Reporter: kim | Owner: shorty114 Type: enhancement | Status: closed Priority: low | Milestone: Component: General | Version: 1.5.1 Severity: normal | Resolution: fixed Keywords: bg|dev-feedback bg|2nd-opinion | --------------------------------------------+------------------------------- Changes (by shorty114): * status: assigned => closed * resolution: => fixed Comment: Fixed by [http://trac.wordpress.org/ticket/3136 3136], according to Ryan. Closed. -- Ticket URL: <http://trac.wordpress.org/ticket/1081#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:13:58 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:14:12 2006 Subject: [wp-trac] Re: [WordPress Trac] #1081: Implement language tagging In-Reply-To: <066.e3c45ceb913b1bb5ae9bb14e573ddb8e@lists.automattic.com> References: <066.e3c45ceb913b1bb5ae9bb14e573ddb8e@lists.automattic.com> Message-ID: <075.931c09f6d65739659f5fe8ce8e2ce235@lists.automattic.com> #1081: Implement language tagging --------------------------------------------+------------------------------- Reporter: kim | Owner: shorty114 Type: enhancement | Status: reopened Priority: low | Milestone: 2.1 Component: General | Version: 1.5.1 Severity: normal | Resolution: Keywords: bg|dev-feedback bg|2nd-opinion | --------------------------------------------+------------------------------- Changes (by shorty114): * status: closed => reopened * resolution: fixed => * milestone: => 2.1 -- Ticket URL: <http://trac.wordpress.org/ticket/1081#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:14:07 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:14:21 2006 Subject: [wp-trac] Re: [WordPress Trac] #1081: Implement language tagging In-Reply-To: <066.e3c45ceb913b1bb5ae9bb14e573ddb8e@lists.automattic.com> References: <066.e3c45ceb913b1bb5ae9bb14e573ddb8e@lists.automattic.com> Message-ID: <075.820c7a9dd4c8003a0f19bcc884a5859f@lists.automattic.com> #1081: Implement language tagging --------------------------------------------+------------------------------- Reporter: kim | Owner: shorty114 Type: enhancement | Status: closed Priority: low | Milestone: 2.1 Component: General | Version: 1.5.1 Severity: normal | Resolution: fixed Keywords: bg|dev-feedback bg|2nd-opinion | --------------------------------------------+------------------------------- Changes (by shorty114): * status: reopened => closed * resolution: => fixed -- Ticket URL: <http://trac.wordpress.org/ticket/1081#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:15:20 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:15:31 2006 Subject: [wp-trac] Re: [WordPress Trac] #3405: Support Post Enclosures Via XML-RPC MetaWeblog API Function In-Reply-To: <066.df52417a7c56d1c73fb98a76b3f73c6f@lists.automattic.com> References: <066.df52417a7c56d1c73fb98a76b3f73c6f@lists.automattic.com> Message-ID: <075.e246fc1561b742627a6127c388d57f3a@lists.automattic.com> #3405: Support Post Enclosures Via XML-RPC MetaWeblog API Function ------------------------------------------+--------------------------------- Reporter: swinton | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.0.6 Component: XML-RPC | Version: 2.0.5 Severity: normal | Resolution: Keywords: bg|has-patch bg|dev-feedback | ------------------------------------------+--------------------------------- Changes (by shorty114): * keywords: enclosure meta mw_newPost MetaWeblog API XMLRPC => bg|has- patch bg|dev-feedback -- Ticket URL: <http://trac.wordpress.org/ticket/3405#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:17:45 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:17:58 2006 Subject: [wp-trac] Re: [WordPress Trac] #3215: Login & Update functions everything is broken In-Reply-To: <049.6066b63c1044229dd67a636989ac05fd@lists.automattic.com> References: <049.6066b63c1044229dd67a636989ac05fd@lists.automattic.com> Message-ID: <058.2771b3f4623edc01ee39e8bc9ceaf6b7@lists.automattic.com> #3215: Login & Update functions everything is broken --------------------------------------------+------------------------------- Reporter: Xmion | Owner: markjaquith Type: defect | Status: assigned Priority: highest | Milestone: 2.0.6 Component: General | Version: 2.1 Severity: critical | Resolution: Keywords: Blank page 302 maint-candidate | --------------------------------------------+------------------------------- Comment (by shorty114): Wouldn't this be a blocker? -- Ticket URL: <http://trac.wordpress.org/ticket/3215#comment:19> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:28:26 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:28:39 2006 Subject: [wp-trac] Re: [WordPress Trac] #3276: Ajax update of non-changed meta value results in "Something strange happened" error In-Reply-To: <066.3fe7c003e4b0edaf77914de802e7c534@lists.automattic.com> References: <066.3fe7c003e4b0edaf77914de802e7c534@lists.automattic.com> Message-ID: <075.9f4fe7585c9e48b2879c0c22ba1697d8@lists.automattic.com> #3276: Ajax update of non-changed meta value results in "Something strange happened" error --------------------------------------------+------------------------------- Reporter: markjaquith | Owner: mdawaffe Type: enhancement | Status: assigned Priority: low | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: Keywords: ajax postmeta has-patch commit | --------------------------------------------+------------------------------- Changes (by mdawaffe): * keywords: ajax postmeta => ajax postmeta has-patch commit * status: new => assigned * owner: anonymous => mdawaffe -- Ticket URL: <http://trac.wordpress.org/ticket/3276#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:33:26 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:33:45 2006 Subject: [wp-trac] Re: [WordPress Trac] #3386: box-bg-right.gif isn't wide enough In-Reply-To: <066.41c48ef7938fa2c024051a83e65d68a2@lists.automattic.com> References: <066.41c48ef7938fa2c024051a83e65d68a2@lists.automattic.com> Message-ID: <075.de08f65f9a7251e04b7ad231924c5355@lists.automattic.com> #3386: box-bg-right.gif isn't wide enough ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: defect | Status: new Priority: low | Milestone: 2.2 Component: Administration | Version: 2.1 Severity: minor | Resolution: Keywords: has-patch | ----------------------------+----------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/3386#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:33:59 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:34:15 2006 Subject: [wp-trac] Re: [WordPress Trac] #3371: Request for additional $before and $after parameters to wp_list_cats() In-Reply-To: <066.4a62aad0beb4ab519051a72b8f07e378@lists.automattic.com> References: <066.4a62aad0beb4ab519051a72b8f07e378@lists.automattic.com> Message-ID: <075.d7478db7950a1b43dafd70ae433660e7@lists.automattic.com> #3371: Request for additional $before and $after parameters to wp_list_cats() -------------------------+-------------------------------------------------- Reporter: vdzhuvinov | Owner: westi Type: enhancement | Status: assigned Priority: low | Milestone: 2.2 Component: Template | Version: 2.0.5 Severity: trivial | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/3371#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:35:01 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:35:11 2006 Subject: [wp-trac] Re: [WordPress Trac] #3406: Use HTML4 instead of XHTML1 In-Reply-To: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> References: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> Message-ID: <075.e0cbb9ee50da2022c73297ef93a24a38@lists.automattic.com> #3406: Use HTML4 instead of XHTML1 -----------------------+---------------------------------------------------- Reporter: TedNelson | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Template | Version: Severity: normal | Resolution: wontfix Keywords: | -----------------------+---------------------------------------------------- Comment (by Viper007Bond): Replying to [comment:9 lachlanhunt]: > even claiming that WordPress supports XHTML is absolutely bogus That's funny seeing as how all my WordPress powered sites are 100% XHTML valid... And it's not a horrible idea to switch to XML powered themes, although that's definitely WordPress 3.0 material... -- Ticket URL: <http://trac.wordpress.org/ticket/3406#comment:10> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:35:43 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:36:06 2006 Subject: [wp-trac] Re: [WordPress Trac] #881: Lengthen password field for protected posts In-Reply-To: <050.c5731c496d939d738656dcfcc3dbd041@lists.automattic.com> References: <050.c5731c496d939d738656dcfcc3dbd041@lists.automattic.com> Message-ID: <059.5eec0dd5af8016b27721100813de5720@lists.automattic.com> #881: Lengthen password field for protected posts ------------------------------+--------------------------------------------- Reporter: ScytheBlade1 | Owner: Nazgul Type: enhancement | Status: closed Priority: normal | Milestone: 2.1 Component: Optimization | Version: Severity: normal | Resolution: wontfix Keywords: has-patch commit | ------------------------------+--------------------------------------------- Changes (by matt): * status: new => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/881#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:36:00 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:36:16 2006 Subject: [wp-trac] Re: [WordPress Trac] #890: support relative paths for enclosures In-Reply-To: <066.9967a58c87655afdb329e77bf96ff87d@lists.automattic.com> References: <066.9967a58c87655afdb329e77bf96ff87d@lists.automattic.com> Message-ID: <075.50c4187515ef6741b435d0e56bafac6a@lists.automattic.com> #890: support relative paths for enclosures -----------------------------------+---------------------------------------- Reporter: anonymousbugger | Owner: markjaquith Type: enhancement | Status: assigned Priority: normal | Milestone: 2.2 Component: Administration | Version: 1.5 Severity: normal | Resolution: Keywords: has-patch 2nd-opinion | -----------------------------------+---------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/890#comment:9> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:36:54 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:37:06 2006 Subject: [wp-trac] Re: [WordPress Trac] #3097: #2390 and [4117] break ajax post meta and sometimes draft saving In-Reply-To: <066.578690c927a9265391254e0640eb8c98@lists.automattic.com> References: <066.578690c927a9265391254e0640eb8c98@lists.automattic.com> Message-ID: <075.c93253ba349015a5c32bd87cde7dadb1@lists.automattic.com> #3097: #2390 and [4117] break ajax post meta and sometimes draft saving -----------------------------------+---------------------------------------- Reporter: mdawaffe | Owner: mdawaffe Type: defect | Status: assigned Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch 2nd-opinion | -----------------------------------+---------------------------------------- Changes (by mdawaffe): * keywords: => has-patch 2nd-opinion * status: new => assigned * owner: anonymous => mdawaffe -- Ticket URL: <http://trac.wordpress.org/ticket/3097#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:37:26 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:37:52 2006 Subject: [wp-trac] Re: [WordPress Trac] #1065: Detect Whether a User is Logged in for Popup Comments as well In-Reply-To: <066.95626526db0e6e87ee0ff09a8cec1dbb@lists.automattic.com> References: <066.95626526db0e6e87ee0ff09a8cec1dbb@lists.automattic.com> Message-ID: <075.af1447434d939bea02734af427147294@lists.automattic.com> #1065: Detect Whether a User is Logged in for Popup Comments as well -------------------------+-------------------------------------------------- Reporter: tin | Owner: Type: enhancement | Status: new Priority: normal | Milestone: 2.2 Component: Template | Version: 1.6 Severity: normal | Resolution: Keywords: has-patch | -------------------------+-------------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1065#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:37:53 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:38:09 2006 Subject: [wp-trac] Re: [WordPress Trac] #1072: list_cats() ignores 'optionall=1' option In-Reply-To: <047.9083569b64e152f1a06a3cfa93dec8a4@lists.automattic.com> References: <047.9083569b64e152f1a06a3cfa93dec8a4@lists.automattic.com> Message-ID: <056.1203d92d5d82cf1a76bf7aa4d7242bac@lists.automattic.com> #1072: list_cats() ignores 'optionall=1' option -------------------------+-------------------------------------------------- Reporter: dpbeatley | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: 2.1 Component: General | Version: 1.5.2 Severity: normal | Resolution: wontfix Keywords: has-patch | -------------------------+-------------------------------------------------- Changes (by matt): * status: reopened => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/1072#comment:8> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:40:03 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:40:25 2006 Subject: [wp-trac] Re: [WordPress Trac] #1155: Add wp-login.php to theme/template system In-Reply-To: <047.42a609146cbec5e75ebedf824ba77376@lists.automattic.com> References: <047.42a609146cbec5e75ebedf824ba77376@lists.automattic.com> Message-ID: <056.278b17bc0e8c4e150c2454c4ca80bb89@lists.automattic.com> #1155: Add wp-login.php to theme/template system --------------------------------------+------------------------------------- Reporter: TechGnome | Owner: markjaquith Type: enhancement | Status: assigned Priority: normal | Milestone: 2.2 Component: Template | Version: 2.0.1 Severity: normal | Resolution: Keywords: bg|needs-patch has-patch | --------------------------------------+------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1155#comment:10> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:40:28 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:40:48 2006 Subject: [wp-trac] Re: [WordPress Trac] #1144: REQUEST_URI may be encoded but PATH_INFO, get_option('home') are not In-Reply-To: <066.d4a0bbb48b69a513fe77116e93fc7dbd@lists.automattic.com> References: <066.d4a0bbb48b69a513fe77116e93fc7dbd@lists.automattic.com> Message-ID: <075.b7d214acec943347de16dd7016f447c5@lists.automattic.com> #1144: REQUEST_URI may be encoded but PATH_INFO, get_option('home') are not -----------------------+---------------------------------------------------- Reporter: lev | Owner: ryan Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: General | Version: 1.5 Severity: major | Resolution: Keywords: has-patch | -----------------------+---------------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1144#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:40:50 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:41:11 2006 Subject: [wp-trac] Re: [WordPress Trac] #1103: Move RSS feed update for dashboard to pseudo cron In-Reply-To: <066.b86e631dd7cacc7565be648c4d01f254@lists.automattic.com> References: <066.b86e631dd7cacc7565be648c4d01f254@lists.automattic.com> Message-ID: <075.cecacb3ab25516a87d1d2174584121c4@lists.automattic.com> #1103: Move RSS feed update for dashboard to pseudo cron -----------------------------+---------------------------------------------- Reporter: anonymousbugger | Owner: matt Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: General | Version: 2.0.1 Severity: trivial | Resolution: fixed Keywords: has-patch | -----------------------------+---------------------------------------------- Changes (by matt): * status: assigned => closed * resolution: => fixed Comment: This should be addressed by the new AJAX loading. -- Ticket URL: <http://trac.wordpress.org/ticket/1103#comment:14> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:41:25 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:41:38 2006 Subject: [wp-trac] Re: [WordPress Trac] #1170: Nested blockquotes unallowed? In-Reply-To: <066.47ab8fde9a3adfdcff6f025423e8585d@lists.automattic.com> References: <066.47ab8fde9a3adfdcff6f025423e8585d@lists.automattic.com> Message-ID: <075.a3f4d816a320d77025209942a116c068@lists.automattic.com> #1170: Nested blockquotes unallowed? -----------------------------------+---------------------------------------- Reporter: anonymousbugger | Owner: ryan Type: defect | Status: assigned Priority: normal | Milestone: 2.2 Component: General | Version: 1.5 Severity: minor | Resolution: Keywords: has-patch 2nd-opinion | -----------------------------------+---------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1170#comment:11> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:41:57 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:42:13 2006 Subject: [wp-trac] Re: [WordPress Trac] #1199: Permalink /%category%/%postname%/ fails to generate In-Reply-To: <066.f33ea7ecb99d87871ff2ea41b94f68c2@lists.automattic.com> References: <066.f33ea7ecb99d87871ff2ea41b94f68c2@lists.automattic.com> Message-ID: <075.9b5a307374d3362d9ab73521746258ef@lists.automattic.com> #1199: Permalink /%category%/%postname%/ fails to generate -----------------------------+---------------------------------------------- Reporter: anonymousbugger | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: General | Version: 2.0 Severity: major | Resolution: Keywords: permalinks | -----------------------------+---------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1199#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:42:55 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:43:15 2006 Subject: [wp-trac] Re: [WordPress Trac] #1277: Extend is_page() to support child_of and decendent_of In-Reply-To: <066.87acc3dbbbf70515cb394629b17c4933@lists.automattic.com> References: <066.87acc3dbbbf70515cb394629b17c4933@lists.automattic.com> Message-ID: <075.ee442c56fb19e506ac2dfdb51fb99677@lists.automattic.com> #1277: Extend is_page() to support child_of and decendent_of -------------------------+-------------------------------------------------- Reporter: astorm | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.2 Component: General | Version: 1.5.1 Severity: normal | Resolution: Keywords: has-patch | -------------------------+-------------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1277#comment:10> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:43:23 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:43:38 2006 Subject: [wp-trac] Re: [WordPress Trac] #1280: Visually Disambiguate Future-Dated Posts In-Reply-To: <066.bde37f2d78091fd9bf0c19de37139a84@lists.automattic.com> References: <066.bde37f2d78091fd9bf0c19de37139a84@lists.automattic.com> Message-ID: <075.8c77236e347a9227570e57a290e298af@lists.automattic.com> #1280: Visually Disambiguate Future-Dated Posts ----------------------------+----------------------------------------------- Reporter: skippy | Owner: morydd Type: enhancement | Status: assigned Priority: normal | Milestone: 2.2 Component: Administration | Version: 1.5 Severity: trivial | Resolution: Keywords: bg|has-patch | ----------------------------+----------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1280#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:43:43 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:44:02 2006 Subject: [wp-trac] Re: [WordPress Trac] #1303: new script for importing posts from Blosxom (import-blosxom.php) In-Reply-To: <044.eed26506f05bdb53e95132da33ce8c81@lists.automattic.com> References: <044.eed26506f05bdb53e95132da33ce8c81@lists.automattic.com> Message-ID: <053.60a8c71c7b338ae0801c2c54fa63ab96@lists.automattic.com> #1303: new script for importing posts from Blosxom (import-blosxom.php) -----------------------------+---------------------------------------------- Reporter: anonymousbugger | Owner: markjaquith Type: enhancement | Status: assigned Priority: normal | Milestone: 2.2 Component: Administration | Version: Severity: normal | Resolution: Keywords: has-patch | -----------------------------+---------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1303#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:44:16 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:44:29 2006 Subject: [wp-trac] Re: [WordPress Trac] #1352: wp_email() From: header doesn't include name In-Reply-To: <066.b135274b0319baa3ee1ede214794880a@lists.automattic.com> References: <066.b135274b0319baa3ee1ede214794880a@lists.automattic.com> Message-ID: <075.c0913da854beb2a10934d25c94b855ce@lists.automattic.com> #1352: wp_email() From: header doesn't include name -------------------------+-------------------------------------------------- Reporter: doey | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: 2.1 Component: General | Version: 1.5.1 Severity: normal | Resolution: wontfix Keywords: has-patch | -------------------------+-------------------------------------------------- Changes (by matt): * status: reopened => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/1352#comment:10> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:44:39 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:44:50 2006 Subject: [wp-trac] Re: [WordPress Trac] #1376: Comment HTML cleaner mangles PHP open tag In-Reply-To: <066.2ce78db3cf4a8511c7475f2b7b1ad6c9@lists.automattic.com> References: <066.2ce78db3cf4a8511c7475f2b7b1ad6c9@lists.automattic.com> Message-ID: <075.eae6a235554a3e42a17f37d78c1194b5@lists.automattic.com> #1376: Comment HTML cleaner mangles PHP open tag -----------------------------+---------------------------------------------- Reporter: anonymousbugger | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: General | Version: 1.5.1 Severity: trivial | Resolution: Keywords: needs-patch | -----------------------------+---------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1376#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:45:41 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:46:00 2006 Subject: [wp-trac] Re: [WordPress Trac] #1412: Object unserialization using get_option fails In-Reply-To: <066.d4789f46e03e9aeb1eaaccade9a0712f@lists.automattic.com> References: <066.d4789f46e03e9aeb1eaaccade9a0712f@lists.automattic.com> Message-ID: <075.510fc2524025ddbe09d0e3b99276f959@lists.automattic.com> #1412: Object unserialization using get_option fails -----------------------------------+---------------------------------------- Reporter: EricAnderson | Owner: westi Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: General | Version: 1.5.1.1 Severity: normal | Resolution: wontfix Keywords: has-patch 2nd-opinion | -----------------------------------+---------------------------------------- Changes (by matt): * status: assigned => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/1412#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:46:41 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:46:53 2006 Subject: [wp-trac] Re: [WordPress Trac] #1418: wptexturize doesn't correctly translate doublequote in brackets In-Reply-To: <066.bf457ed6effb236ee2f7cd252a145e66@lists.automattic.com> References: <066.bf457ed6effb236ee2f7cd252a145e66@lists.automattic.com> Message-ID: <075.142fa50e63c1f36f1b2abbb000bbe98d@lists.automattic.com> #1418: wptexturize doesn't correctly translate doublequote in brackets -----------------------------------------------------------------------------+ Reporter: Kafkaesqui | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 1.5.1.1 Severity: normal | Resolution: Keywords: bg|has-patch bg|dev-feedback formatting wptexturize curl quotes | -----------------------------------------------------------------------------+ Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1418#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:46:51 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:47:01 2006 Subject: [wp-trac] Re: [WordPress Trac] #1421: <!--more--> logic should be a filter In-Reply-To: <066.c32d19728d2c653bf5b5dda40147ff9a@lists.automattic.com> References: <066.c32d19728d2c653bf5b5dda40147ff9a@lists.automattic.com> Message-ID: <075.da43c7d52a25730da709ead075add96a@lists.automattic.com> #1421: <!--more--> logic should be a filter -------------------------+-------------------------------------------------- Reporter: markjaquith | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.2 Component: General | Version: 1.5.1.1 Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1421#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:48:12 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:50:17 2006 Subject: [wp-trac] Re: [WordPress Trac] #1452: Trackback not working with XML-RPC In-Reply-To: <066.b3709bcf9da6961917be75f385531882@lists.automattic.com> References: <066.b3709bcf9da6961917be75f385531882@lists.automattic.com> Message-ID: <075.8b5b30703d949931710340a4f792bbce@lists.automattic.com> #1452: Trackback not working with XML-RPC ----------------------------------------+----------------------------------- Reporter: pombsd | Owner: ryan Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: XML-RPC | Version: 1.5.1.2 Severity: normal | Resolution: worksforme Keywords: trackback xmlrpc has-patch | ----------------------------------------+----------------------------------- Changes (by matt): * status: new => closed * resolution: => worksforme -- Ticket URL: <http://trac.wordpress.org/ticket/1452#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:48:24 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:53:12 2006 Subject: [wp-trac] Re: [WordPress Trac] #1024: wp filters turn < hr /> into < hr /> < br /> In-Reply-To: <066.dd662e99ce9c934f089267d82dfd9859@lists.automattic.com> References: <066.dd662e99ce9c934f089267d82dfd9859@lists.automattic.com> Message-ID: <075.8ad5e07351b73199575c2b9baac59a59@lists.automattic.com> #1024: wp filters turn <hr /> into <hr /><br /> -----------------------------+---------------------------------------------- Reporter: anonymousbugger | Owner: shorty114 Type: defect | Status: assigned Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: minor | Resolution: Keywords: bg|has-patch | -----------------------------+---------------------------------------------- Changes (by shorty114): * status: new => assigned * owner: filosofo => shorty114 Comment: Added patch which uses Dreamseer's patch. -- Ticket URL: <http://trac.wordpress.org/ticket/1024#comment:8> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:48:49 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:54:52 2006 Subject: [wp-trac] Re: [WordPress Trac] #1476: WordPress Update Notification In-Reply-To: <066.493f8d88c7a4cc248c5a7a19c780998c@lists.automattic.com> References: <066.493f8d88c7a4cc248c5a7a19c780998c@lists.automattic.com> Message-ID: <075.05a297594e4b19bb315242a209674519@lists.automattic.com> #1476: WordPress Update Notification --------------------------------------------------+------------------------- Reporter: mdawaffe | Owner: westi Type: defect | Status: assigned Priority: normal | Milestone: 2.2 Component: Administration | Version: 1.6 Severity: minor | Resolution: Keywords: update upgrade has-patch 2nd-opinion | --------------------------------------------------+------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1476#comment:8> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:49:06 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:54:58 2006 Subject: [wp-trac] Re: [WordPress Trac] #1526: have wp-atom.php generate Atom 1.0 (fix attached) In-Reply-To: <066.a6bc17396db25c52fd13e311c2a84cc1@lists.automattic.com> References: <066.a6bc17396db25c52fd13e311c2a84cc1@lists.automattic.com> Message-ID: <075.91b1ceb06783b21178a64c9d57f60461@lists.automattic.com> #1526: have wp-atom.php generate Atom 1.0 (fix attached) ------------------------------------------+--------------------------------- Reporter: comatoast | Owner: markjaquith Type: enhancement | Status: assigned Priority: normal | Milestone: 2.2 Component: General | Version: 2.0.2 Severity: normal | Resolution: Keywords: bg|has-patch bg|dev-feedback | ------------------------------------------+--------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1526#comment:26> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:49:28 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:55:27 2006 Subject: [wp-trac] Re: [WordPress Trac] #1585: Added `summary' field to table generated by get_calendar() to comply with WAI checkpoint 5.5 In-Reply-To: <066.7eaa7c7f44b4765a27a4095e052eb016@lists.automattic.com> References: <066.7eaa7c7f44b4765a27a4095e052eb016@lists.automattic.com> Message-ID: <075.f5fab404bd98703326dd4d56ffc99e8b@lists.automattic.com> #1585: Added `summary' field to table generated by get_calendar() to comply with WAI checkpoint 5.5 ------------------------------------------+--------------------------------- Reporter: littleram | Owner: markjaquith Type: defect | Status: assigned Priority: normal | Milestone: 2.2 Component: General | Version: 1.5.2 Severity: trivial | Resolution: Keywords: bg|has-patch bg|dev-feedback | ------------------------------------------+--------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1585#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:49:55 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:58:33 2006 Subject: [wp-trac] Re: [WordPress Trac] #1595: Post Content Prerendering In-Reply-To: <066.14d38a23cbac84ebd7bf7f8ce14f8274@lists.automattic.com> References: <066.14d38a23cbac84ebd7bf7f8ce14f8274@lists.automattic.com> Message-ID: <075.6dfe0ccac59c0773ce83672e5331e8f2@lists.automattic.com> #1595: Post Content Prerendering -----------------------------------------+---------------------------------- Reporter: markjaquith | Owner: markjaquith Type: enhancement | Status: new Priority: normal | Milestone: 2.2 Component: Optimization | Version: 1.6 Severity: normal | Resolution: Keywords: bg|2nd-opinion bg|has-patch | -----------------------------------------+---------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1595#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:50:16 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:58:39 2006 Subject: [wp-trac] Re: [WordPress Trac] #1597: balanceTags() doesn't filter self-closing tags which shouldn't be self-closed In-Reply-To: <066.d2f182f8db64b6379c27192f23c9026d@lists.automattic.com> References: <066.d2f182f8db64b6379c27192f23c9026d@lists.automattic.com> Message-ID: <075.dad79752846e9a3dafdd1b6d5c8c2b09@lists.automattic.com> #1597: balanceTags() doesn't filter self-closing tags which shouldn't be self- closed -------------------------------------------------+-------------------------- Reporter: frenzie | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: General | Version: 1.5.2 Severity: minor | Resolution: Keywords: balance tags formatting needs-patch | -------------------------------------------------+-------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1597#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:50:29 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:59:13 2006 Subject: [wp-trac] Re: [WordPress Trac] #1609: User and author listing needs to page In-Reply-To: <066.f238da438c052bc0b4f31259e7beefa5@lists.automattic.com> References: <066.f238da438c052bc0b4f31259e7beefa5@lists.automattic.com> Message-ID: <075.1600593dc0fd2cfa010f4a901cdff9d5@lists.automattic.com> #1609: User and author listing needs to page ----------------------------+----------------------------------------------- Reporter: matt | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 1.6 Severity: normal | Resolution: fixed Keywords: bg|needs-patch | ----------------------------+----------------------------------------------- Changes (by matt): * status: new => closed * resolution: => fixed -- Ticket URL: <http://trac.wordpress.org/ticket/1609#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:50:57 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:59:21 2006 Subject: [wp-trac] Re: [WordPress Trac] #1625: Multiple category support and category negation for get_posts() In-Reply-To: <066.28df26b381ea73cab6c828315b2228e4@lists.automattic.com> References: <066.28df26b381ea73cab6c828315b2228e4@lists.automattic.com> Message-ID: <075.2fed3a4f1f1d81ee1330f2805a285395@lists.automattic.com> #1625: Multiple category support and category negation for get_posts() ---------------------------------------------------+------------------------ Reporter: markjaquith | Owner: drac Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 1.6 Severity: normal | Resolution: Keywords: bg|has-patch bg|review bg|2nd opinion | ---------------------------------------------------+------------------------ Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1625#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:51:09 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:59:31 2006 Subject: [wp-trac] Re: [WordPress Trac] #1658: "Submitting draft for review" model In-Reply-To: <066.2a76ee5bc8e764948d21683a1849a68e@lists.automattic.com> References: <066.2a76ee5bc8e764948d21683a1849a68e@lists.automattic.com> Message-ID: <075.3943c30248ba62f116f10d127f3527d4@lists.automattic.com> #1658: "Submitting draft for review" model -------------------------------------------------------------+-------------- Reporter: kidaz | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 1.5.2 Severity: normal | Resolution: Keywords: submit model review admin author bg|needs-patch | -------------------------------------------------------------+-------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1658#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:51:23 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:59:39 2006 Subject: [wp-trac] Re: [WordPress Trac] #1691: Missing Hooks for Widget Filters In-Reply-To: <066.42eeff79df4a0c625eb3eebe8c6e877e@lists.automattic.com> References: <066.42eeff79df4a0c625eb3eebe8c6e877e@lists.automattic.com> Message-ID: <075.cb1136314c71d2b83be16250933944da@lists.automattic.com> #1691: Missing Hooks for Widget Filters -------------------------+-------------------------------------------------- Reporter: GreyGore | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.2 Component: Template | Version: 1.5.2 Severity: normal | Resolution: Keywords: has-patch | -------------------------+-------------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1691#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:33:46 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 22:59:46 2006 Subject: [wp-trac] Re: [WordPress Trac] #3381: "Discard" button for autosaves In-Reply-To: <066.50f57507327172dd7de9adc751ad5207@lists.automattic.com> References: <066.50f57507327172dd7de9adc751ad5207@lists.automattic.com> Message-ID: <075.a8d46901441eb4217cc6e859afce956d@lists.automattic.com> #3381: "Discard" button for autosaves ----------------------------+----------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.2 Component: Administration | Version: 2.1 Severity: minor | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/3381#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:51:47 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:00:07 2006 Subject: [wp-trac] Re: [WordPress Trac] #1720: dropdown_cats() should be deprecated in favor of a modified list_cats()/get_category_link() In-Reply-To: <066.5b33b55ee807981d7fcb99e0b2f9d93f@lists.automattic.com> References: <066.5b33b55ee807981d7fcb99e0b2f9d93f@lists.automattic.com> Message-ID: <075.875896cf1b6851783d73246bbd4fe997@lists.automattic.com> #1720: dropdown_cats() should be deprecated in favor of a modified list_cats()/get_category_link() ----------------------------+----------------------------------------------- Reporter: mark | Owner: ryan Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 1.6 Severity: normal | Resolution: wontfix Keywords: | ----------------------------+----------------------------------------------- Changes (by matt): * status: new => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/1720#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:52:14 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:00:43 2006 Subject: [wp-trac] Re: [WordPress Trac] #1762: permalinks structure not i18n friendly In-Reply-To: <066.2b47804476bff102ec51a7c070c19872@lists.automattic.com> References: <066.2b47804476bff102ec51a7c070c19872@lists.automattic.com> Message-ID: <075.fc7c48358e827ecee278621aed6f2ecc@lists.automattic.com> #1762: permalinks structure not i18n friendly -------------------------------------------+-------------------------------- Reporter: anatman | Owner: davidhouse Type: defect | Status: assigned Priority: normal | Milestone: 2.2 Component: Administration | Version: 1.5.2 Severity: normal | Resolution: Keywords: i18n bg|has-patch bg|squashed | -------------------------------------------+-------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1762#comment:13> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:55:25 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:02:07 2006 Subject: [wp-trac] Re: [WordPress Trac] #2372: <a href= changes to <a xhref= ! In-Reply-To: <066.159f13dd046b2ff1d776a0c474e33a9d@lists.automattic.com> References: <066.159f13dd046b2ff1d776a0c474e33a9d@lists.automattic.com> Message-ID: <075.a84608c4a53921ca9d026fbd0d6c9ec8@lists.automattic.com> #2372: <a href= changes to <a xhref= ! ------------------------+--------------------------------------------------- Reporter: carnaticwm | Owner: skeltoac Type: defect | Status: reopened Priority: normal | Milestone: 2.1 Component: General | Version: 2.0.4 Severity: minor | Resolution: Keywords: | ------------------------+--------------------------------------------------- Changes (by bertilow): * status: closed => reopened * resolution: worksforme => Comment: I was just bit by this bug in WP 2.0.5 (at "http://lingvakritiko.com"). I was flabbergasted. I will now try to turn off the Rich Editor for all users. This bug most definitely has life in it. -- Ticket URL: <http://trac.wordpress.org/ticket/2372#comment:18> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:56:20 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:03:01 2006 Subject: [wp-trac] Re: [WordPress Trac] #1872: xml-rpc does not rethrow errors generated by plugins In-Reply-To: <062.65088c63a0f590716e2abd9aa61221f8@lists.automattic.com> References: <062.65088c63a0f590716e2abd9aa61221f8@lists.automattic.com> Message-ID: <071.4dd7edf81720a425527ce23fb8fff8d4@lists.automattic.com> #1872: xml-rpc does not rethrow errors generated by plugins ---------------------------------------------------+------------------------ Reporter: pidge | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: XML-RPC | Version: 1.5.2 Severity: major | Resolution: Keywords: xml-rpc, exteded live archive, plugin | ---------------------------------------------------+------------------------ Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1872#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:56:35 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:03:11 2006 Subject: [wp-trac] Re: [WordPress Trac] #1872: xml-rpc does not rethrow errors generated by plugins In-Reply-To: <062.65088c63a0f590716e2abd9aa61221f8@lists.automattic.com> References: <062.65088c63a0f590716e2abd9aa61221f8@lists.automattic.com> Message-ID: <071.acf6baa766174b4cce3dc64b653783ab@lists.automattic.com> #1872: xml-rpc does not rethrow errors generated by plugins ---------------------------------------------------+------------------------ Reporter: pidge | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.2 Component: XML-RPC | Version: 1.5.2 Severity: major | Resolution: wontfix Keywords: xml-rpc, exteded live archive, plugin | ---------------------------------------------------+------------------------ Changes (by matt): * status: new => closed * resolution: => wontfix Comment: Actually I don't know if we can trivially fix this, closing. -- Ticket URL: <http://trac.wordpress.org/ticket/1872#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:56:51 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:03:19 2006 Subject: [wp-trac] Re: [WordPress Trac] #1835: no link to get back to post from subpost if post title is blank In-Reply-To: <066.ff589f0bf3729a41db6ff4551ae0fefc@lists.automattic.com> References: <066.ff589f0bf3729a41db6ff4551ae0fefc@lists.automattic.com> Message-ID: <075.57e8faab57a0a8318d2bac321e7c3ac2@lists.automattic.com> #1835: no link to get back to post from subpost if post title is blank ----------------------------+----------------------------------------------- Reporter: stevecooley | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 1.6 Severity: minor | Resolution: Keywords: needs-patch | ----------------------------+----------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1835#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:58:28 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:03:38 2006 Subject: [wp-trac] Re: [WordPress Trac] #1785: Atom-based comment feed In-Reply-To: <066.c33db763e114919264e491bebda4200f@lists.automattic.com> References: <066.c33db763e114919264e491bebda4200f@lists.automattic.com> Message-ID: <075.fd005fbf1ae32ede649fe4424c88af6e@lists.automattic.com> #1785: Atom-based comment feed ---------------------------------------------+------------------------------ Reporter: kurtmckee | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.2 Component: General | Version: 1.6 Severity: normal | Resolution: Keywords: atom comments feed bg|has-patch | ---------------------------------------------+------------------------------ Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1785#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:59:05 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:03:44 2006 Subject: [wp-trac] Re: [WordPress Trac] #1767: Admin form submissions with errors should re-populate form data In-Reply-To: <066.56b5dc61d8c5aefe97fd88197aa205bc@lists.automattic.com> References: <066.56b5dc61d8c5aefe97fd88197aa205bc@lists.automattic.com> Message-ID: <075.f853708e7f5f2680163c138eccab435b@lists.automattic.com> #1767: Admin form submissions with errors should re-populate form data ----------------------------+----------------------------------------------- Reporter: h3h | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 1.6 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1767#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 22:56:03 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:03:53 2006 Subject: [wp-trac] Re: [WordPress Trac] #1955: Outgoing trackback ping could include 'charset' attribute for international trackbacks In-Reply-To: <066.988ed82f9f9ab88b067d6ca1a3a682b1@lists.automattic.com> References: <066.988ed82f9f9ab88b067d6ca1a3a682b1@lists.automattic.com> Message-ID: <075.84056512bc2454210760afe2c5e26c51@lists.automattic.com> #1955: Outgoing trackback ping could include 'charset' attribute for international trackbacks --------------------------------------------+------------------------------- Reporter: matopc | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Optimization | Version: 2.0 Severity: normal | Resolution: Keywords: trackback charset bg|has-patch | --------------------------------------------+------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1955#comment:17> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:08:25 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:08:49 2006 Subject: [wp-trac] Re: [WordPress Trac] #1969: Check for category and author page existence In-Reply-To: <066.de275aaa5f45706e98beecc7fa3e17d0@lists.automattic.com> References: <066.de275aaa5f45706e98beecc7fa3e17d0@lists.automattic.com> Message-ID: <075.2fa6a56717887ec760f3ddaf59cae93f@lists.automattic.com> #1969: Check for category and author page existence ---------------------------+------------------------------------------------ Reporter: chuyskywalker | Owner: anonymous Type: defect | Status: reopened Priority: normal | Milestone: 2.2 Component: General | Version: 2.0.1 Severity: normal | Resolution: Keywords: bg|has-patch | ---------------------------+------------------------------------------------ Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1969#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:11:33 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:11:46 2006 Subject: [wp-trac] Re: [WordPress Trac] #2059: Slashes stripped in <pre> (caused by #1793) In-Reply-To: <066.32715e04d232e6eb86a11ad7d3fd2a1c@lists.automattic.com> References: <066.32715e04d232e6eb86a11ad7d3fd2a1c@lists.automattic.com> Message-ID: <075.d0af4035283c177bf3e417756141bf31@lists.automattic.com> #2059: Slashes stripped in <pre> (caused by #1793) ------------------------------------------+--------------------------------- Reporter: allan | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: General | Version: 1.5.2 Severity: normal | Resolution: Keywords: bg|has-patch bg|dev-feedback | ------------------------------------------+--------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2059#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:11:45 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:12:00 2006 Subject: [wp-trac] Re: [WordPress Trac] #2055: No way to "sign out" from password-protected posts/pages In-Reply-To: <066.fa5a5615179975e32f392ac1543d51e8@lists.automattic.com> References: <066.fa5a5615179975e32f392ac1543d51e8@lists.automattic.com> Message-ID: <075.3d14768d1368b628594accfcb4856bf5@lists.automattic.com> #2055: No way to "sign out" from password-protected posts/pages -----------------------------+---------------------------------------------- Reporter: skeltoac | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Security | Version: 2.0 Severity: minor | Resolution: Keywords: password cookie | -----------------------------+---------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2055#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:12:02 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:12:14 2006 Subject: [wp-trac] Re: [WordPress Trac] #2054: Add $post_title to comments in moderation queue In-Reply-To: <066.6301e7552183accc0a1b2c6cad90f12a@lists.automattic.com> References: <066.6301e7552183accc0a1b2c6cad90f12a@lists.automattic.com> Message-ID: <075.603289492d36afa77d66b7759b3db6be@lists.automattic.com> #2054: Add $post_title to comments in moderation queue ------------------------------+--------------------------------------------- Reporter: nmeans | Owner: nmeans Type: enhancement | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: wontfix Keywords: moderation queue | ------------------------------+--------------------------------------------- Changes (by matt): * status: reopened => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/2054#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:12:23 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:12:33 2006 Subject: [wp-trac] Re: [WordPress Trac] #2043: Dirty cache queries In-Reply-To: <066.7bd1f618f9e4d0f4c33bcb2fa78ef343@lists.automattic.com> References: <066.7bd1f618f9e4d0f4c33bcb2fa78ef343@lists.automattic.com> Message-ID: <075.03857d671b65931e8bd53f0698d97cd1@lists.automattic.com> #2043: Dirty cache queries ----------------------------+----------------------------------------------- Reporter: matt | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.0 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2043#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:12:37 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:12:50 2006 Subject: [wp-trac] Re: [WordPress Trac] #2039: Wordpress fails silently when cookies are disabled In-Reply-To: <047.ecf37bcf4f013c8931876b85ab7518b5@lists.automattic.com> References: <047.ecf37bcf4f013c8931876b85ab7518b5@lists.automattic.com> Message-ID: <056.3935e3cc3044afe24d6730084d7bac9b@lists.automattic.com> #2039: Wordpress fails silently when cookies are disabled --------------------------+------------------------------------------------- Reporter: sjmurdoch | Owner: Nazgul Type: defect | Status: assigned Priority: normal | Milestone: 2.2 Component: General | Version: 2.0 Severity: major | Resolution: Keywords: dev-feedback | --------------------------+------------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2039#comment:11> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:13:54 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:14:12 2006 Subject: [wp-trac] Re: [WordPress Trac] #2014: Filters not applied to bloginfo_rss() In-Reply-To: <066.c7106913875bbfb4863247f8bb318bb0@lists.automattic.com> References: <066.c7106913875bbfb4863247f8bb318bb0@lists.automattic.com> Message-ID: <075.c0835fe52cba6e16b96df8cc13343d18@lists.automattic.com> #2014: Filters not applied to bloginfo_rss() -----------------------------------------------+---------------------------- Reporter: Kafkaesqui | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.0 Severity: normal | Resolution: Keywords: bloginfo_rss filters bg|has-patch | -----------------------------------------------+---------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2014#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:14:07 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:14:16 2006 Subject: [wp-trac] Re: [WordPress Trac] #2004: Pages page should page In-Reply-To: <066.71d38ac920090645d89544b34dcfdaa3@lists.automattic.com> References: <066.71d38ac920090645d89544b34dcfdaa3@lists.automattic.com> Message-ID: <075.8fb2202e6f0636b696a3495f247fda6c@lists.automattic.com> #2004: Pages page should page ----------------------------+----------------------------------------------- Reporter: matt | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.0 Severity: normal | Resolution: Keywords: bg|needs-patch | ----------------------------+----------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2004#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:14:46 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:14:59 2006 Subject: [wp-trac] Re: [WordPress Trac] #2001: Permalink options page lacks syntax or formatting instructions In-Reply-To: <066.de3849c782ec11e0e451edd6c9839f82@lists.automattic.com> References: <066.de3849c782ec11e0e451edd6c9839f82@lists.automattic.com> Message-ID: <075.349f3a7291b283e02e4ed3c09329f56a@lists.automattic.com> #2001: Permalink options page lacks syntax or formatting instructions -----------------------------------+---------------------------------------- Reporter: h3h | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0 Severity: major | Resolution: wontfix Keywords: has-patch 2nd-opinion | -----------------------------------+---------------------------------------- Changes (by matt): * status: reopened => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/2001#comment:10> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:19:13 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:19:25 2006 Subject: [wp-trac] Re: [WordPress Trac] #1721: vars.php calls get_settings() on 'siteurl' and 'home' before filters applied In-Reply-To: <066.cfe67cc3615f048a848840d526469053@lists.automattic.com> References: <066.cfe67cc3615f048a848840d526469053@lists.automattic.com> Message-ID: <075.eabb6c4ee261011764d48c9ec8b3c12f@lists.automattic.com> #1721: vars.php calls get_settings() on 'siteurl' and 'home' before filters applied ------------------------------------------------+--------------------------- Reporter: asknight | Owner: anonymous Type: defect | Status: new Priority: high | Milestone: 2.2 Component: Administration | Version: 1.2 Severity: major | Resolution: Keywords: vars.php cookies filters has-patch | ------------------------------------------------+--------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/1721#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:20:10 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:20:22 2006 Subject: [wp-trac] Re: [WordPress Trac] #1928: Reference to NULL in "query" function of "wp-db.php" file In-Reply-To: <066.92a8645ec505b92b52bf42ddb91adf16@lists.automattic.com> References: <066.92a8645ec505b92b52bf42ddb91adf16@lists.automattic.com> Message-ID: <075.77408bed5b7e6e5120f25478d2fedcfb@lists.automattic.com> #1928: Reference to NULL in "query" function of "wp-db.php" file ---------------------------------------------------------------------+------ Reporter: nima_dezhkam | Owner: mdawaffe Type: defect | Status: closed Priority: high | Milestone: 2.1 Component: Administration | Version: 1.5.2 Severity: major | Resolution: worksforme Keywords: Incomplete Installation, Reference to Null bg|has-patch | ---------------------------------------------------------------------+------ Changes (by matt): * status: assigned => closed * resolution: => worksforme -- Ticket URL: <http://trac.wordpress.org/ticket/1928#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:21:20 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:21:38 2006 Subject: [wp-trac] Re: [WordPress Trac] #2397: URL Rewriting Interferes with HTTP Authentication In-Reply-To: <066.97a773b3417a0205a012ea180e4cad61@lists.automattic.com> References: <066.97a773b3417a0205a012ea180e4cad61@lists.automattic.com> Message-ID: <075.9c5e537a7b73c5a99b2f59115662e8ec@lists.automattic.com> #2397: URL Rewriting Interferes with HTTP Authentication -----------------------------------------+---------------------------------- Reporter: thenerdsangle | Owner: anonymous Type: defect | Status: new Priority: high | Milestone: 2.2 Component: Administration | Version: 2.0 Severity: major | Resolution: Keywords: rewrite http authentication | -----------------------------------------+---------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2397#comment:10> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:21:31 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:22:00 2006 Subject: [wp-trac] Re: [WordPress Trac] #3370: Do not have permission to add category. In-Reply-To: <066.70d47b11909d090da6f4f0afcfd8da92@lists.automattic.com> References: <066.70d47b11909d090da6f4f0afcfd8da92@lists.automattic.com> Message-ID: <075.f6a38b9bd6905bf02809d2a8ec011043@lists.automattic.com> #3370: Do not have permission to add category. ----------------------------------------+----------------------------------- Reporter: computerwolf | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: 2.0.5 Severity: normal | Resolution: Keywords: category permission adding | ----------------------------------------+----------------------------------- Comment (by computerwolf): I am connected to the internet on a LAN by cable modem, and have had the problem on multiple computers. The problem only appeared after the upgrade so I figured it was code related. I have no javascript errors on any other pages that I know of. -- Ticket URL: <http://trac.wordpress.org/ticket/3370#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:23:21 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:23:28 2006 Subject: [wp-trac] Re: [WordPress Trac] #3406: Use HTML4 instead of XHTML1 In-Reply-To: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> References: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> Message-ID: <075.551116561fe55578ab5ead0631b069b2@lists.automattic.com> #3406: Use HTML4 instead of XHTML1 -----------------------+---------------------------------------------------- Reporter: TedNelson | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Template | Version: Severity: normal | Resolution: wontfix Keywords: | -----------------------+---------------------------------------------------- Comment (by JeremyVisser): Replying to [ticket:3406 TedNelson]: > Please use HTML4 instead of XHTML1 in the output from WordPress blogs. The browser used by the majority of my readers doesn't support XHTML1, and is having to rely on error handling to handle your output. Ted, it's not WordPress' fault if it is causing problems for your viewers. Are the devs going to completely change the default behaviour of the WP core (and thus break most themes) just to stop some issues with your viewers' browsers? Probably not. I hate to be like this, but this sort of stuff has seemed to work with other WP users for years now. It's not WordPress' fault if they're using crappy non-standards-compliant browsers that don't support XHTML. Why fix it for their sake, when there are ''already'' existent browsers that ''fully support'' XML parsing. Why not put a Get Firefox or Get Opera link on your blog? -- Ticket URL: <http://trac.wordpress.org/ticket/3406#comment:11> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:27:02 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:27:11 2006 Subject: [wp-trac] [WordPress Trac] #3408: Additional category admin hooks to allow alternate category admin interface Message-ID: <066.072415560b7455ce020d1efe4e65a792@lists.automattic.com> #3408: Additional category admin hooks to allow alternate category admin interface ----------------------------+----------------------------------------------- Reporter: alexkingorg | Owner: ryan Type: enhancement | Status: new Priority: high | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Keywords: categories has-patch ----------------------------+----------------------------------------------- Per conversation with Ryan, the following hooks allow me to implement an alternate category admin interface for managing categories - one that works better when there is a *large* volume of categories. Fewer changes were needed than I expected - only 3 new hooks. -- Ticket URL: <http://trac.wordpress.org/ticket/3408> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:45:56 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:46:08 2006 Subject: [wp-trac] Re: [WordPress Trac] #3407: TinyMCE bugs In-Reply-To: <066.e671f089aa478fb419e58f6a06064718@lists.automattic.com> References: <066.e671f089aa478fb419e58f6a06064718@lists.automattic.com> Message-ID: <075.c40f293eb6a84a3d2d51ca2c1d7e5f18@lists.automattic.com> #3407: TinyMCE bugs -------------------------------+-------------------------------------------- Reporter: Denis-de-Bernardy | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Administration | Version: Severity: normal | Resolution: invalid Keywords: | -------------------------------+-------------------------------------------- Changes (by matt): * status: new => closed * resolution: => invalid Comment: It would really help for this bug to have steps to reproduce, and to be split into individual issues rather than a bunch in one. Closing. -- Ticket URL: <http://trac.wordpress.org/ticket/3407#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:46:11 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:46:28 2006 Subject: [wp-trac] Re: [WordPress Trac] #2828: Ease MySQL4.1 character set configuration In-Reply-To: <057.145bee3a1c7d3fa9baee844a23207d56@lists.automattic.com> References: <057.145bee3a1c7d3fa9baee844a23207d56@lists.automattic.com> Message-ID: <066.44e7280bc6281532575fc6f1b580a8de@lists.automattic.com> #2828: Ease MySQL4.1 character set configuration ---------------------------+------------------------------------------------ Reporter: tenpura | Owner: tenpura Type: enhancement | Status: assigned Priority: high | Milestone: 2.2 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: needs-testing | ---------------------------+------------------------------------------------ Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2828#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:50:45 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:50:54 2006 Subject: [wp-trac] Re: [WordPress Trac] #2875: https enclosures fail on post. In-Reply-To: <066.a596dcd93750d620544186cd3dd8519b@lists.automattic.com> References: <066.a596dcd93750d620544186cd3dd8519b@lists.automattic.com> Message-ID: <075.43971f452b0c57044062336ab65ee27e@lists.automattic.com> #2875: https enclosures fail on post. -------------------------+-------------------------------------------------- Reporter: nigelkane | Owner: anonymous Type: defect | Status: new Priority: high | Milestone: 2.2 Component: General | Version: 2.0.2 Severity: major | Resolution: Keywords: needs-patch | -------------------------+-------------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2875#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:51:52 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:52:00 2006 Subject: [wp-trac] Re: [WordPress Trac] #2992: HTML editor deletes rows (that have properties) from tables In-Reply-To: <066.e77633c60447f814cfffd49c2039b73b@lists.automattic.com> References: <066.e77633c60447f814cfffd49c2039b73b@lists.automattic.com> Message-ID: <075.b9b1573e074adba480ba238f0a37cae1@lists.automattic.com> #2992: HTML editor deletes rows (that have properties) from tables ----------------------------+----------------------------------------------- Reporter: FireMotion | Owner: anonymous Type: defect | Status: new Priority: high | Milestone: 2.2 Component: Administration | Version: 2.0 Severity: major | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2992#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:53:33 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:53:43 2006 Subject: [wp-trac] Re: [WordPress Trac] #3070: use of php's "strip_tags" gives improper/incomplete results In-Reply-To: <066.1049386fd82c760e0529aff78a5b61f8@lists.automattic.com> References: <066.1049386fd82c760e0529aff78a5b61f8@lists.automattic.com> Message-ID: <075.0ce3ca77bcb5d267a8db0c6c2acbebc9@lists.automattic.com> #3070: use of php's "strip_tags" gives improper/incomplete results ----------------------------+----------------------------------------------- Reporter: _ck_ | Owner: anonymous Type: defect | Status: closed Priority: high | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: major | Resolution: wontfix Keywords: | ----------------------------+----------------------------------------------- Changes (by matt): * status: new => closed * resolution: => wontfix Comment: I don't see what this provides that KSES doesn't. Showing what's in between the tags when the strip things is okay. -- Ticket URL: <http://trac.wordpress.org/ticket/3070#comment:10> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Wed Nov 29 23:54:07 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Wed Nov 29 23:54:15 2006 Subject: [wp-trac] Re: [WordPress Trac] #3290: Importer strips img class and style In-Reply-To: <066.9ce1f29060f80c36ddb627f9d0cb035c@lists.automattic.com> References: <066.9ce1f29060f80c36ddb627f9d0cb035c@lists.automattic.com> Message-ID: <075.71547bd878d03680e92fe39f6ae1077f@lists.automattic.com> #3290: Importer strips img class and style -----------------------------+---------------------------------------------- Reporter: foolswisdom | Owner: anonymous Type: defect | Status: new Priority: highest | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: major | Resolution: Keywords: import importer | -----------------------------+---------------------------------------------- Changes (by matt): * priority: high => highest Comment: We shouldn't be doing any stripping for admins. -- Ticket URL: <http://trac.wordpress.org/ticket/3290#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:04:01 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:04:07 2006 Subject: [wp-trac] Re: [WordPress Trac] #3202: "Redirect Old Slugs" should be in core. In-Reply-To: <066.bcd5a297b816b6ea10b92c72283437d1@lists.automattic.com> References: <066.bcd5a297b816b6ea10b92c72283437d1@lists.automattic.com> Message-ID: <075.b6ed0960735ef28065b887fc5d35e721@lists.automattic.com> #3202: "Redirect Old Slugs" should be in core. -----------------------------------+---------------------------------------- Reporter: bryanveloso | Owner: markjaquith Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch 2nd-opinion | -----------------------------------+---------------------------------------- Comment (by matt): +1, go for it. -- Ticket URL: <http://trac.wordpress.org/ticket/3202#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:07:22 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:07:35 2006 Subject: [wp-trac] Re: [WordPress Trac] #3225: Export file does not download in FF In-Reply-To: <066.c6ba1a3b130cbdb1bf3f267ce7680516@lists.automattic.com> References: <066.c6ba1a3b130cbdb1bf3f267ce7680516@lists.automattic.com> Message-ID: <075.245da48bd918d198710e1ca0a3d9cda2@lists.automattic.com> #3225: Export file does not download in FF --------------------------------+------------------------------------------- Reporter: Viper007Bond | Owner: markjaquith Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: fixed Keywords: 2nd-opinion export | --------------------------------+------------------------------------------- Changes (by matt): * status: reopened => closed * resolution: => fixed -- Ticket URL: <http://trac.wordpress.org/ticket/3225#comment:13> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:10:20 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:10:31 2006 Subject: [wp-trac] Re: [WordPress Trac] #3406: Use HTML4 instead of XHTML1 In-Reply-To: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> References: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> Message-ID: <075.119e2beed5c4b32782f831888b926749@lists.automattic.com> #3406: Use HTML4 instead of XHTML1 -----------------------+---------------------------------------------------- Reporter: TedNelson | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Template | Version: Severity: normal | Resolution: wontfix Keywords: | -----------------------+---------------------------------------------------- Comment (by benjaminhawkeslewis): Viper007Bond: A couple points about this. First, XHTML conformance is not a matter of mere validity and, second, I suspect Lachlan regards XHTML 1.0 served as text/html as tag soup since it has no specified handling beyond browsers copying each others? error recovery (see RFC 2854). I?m going to go out on a limb here and guess that [http://www.viper007bond.com www.viper007bond.com] is one of your WordPress sites? One of the things I?ve learned when dealing with tag soup systems is to never judging a site?s validity by its homepage. And sure enough, if we visit your [http://www.viper007bond.com/archives/2006/11/19/casino-royale/" penultimate post] we find it fails validation with two errors. If you were serving that page as application/xhtml+xml, so that Firefox used its XHTML parser rather than its tag soup parser, you?d see a yellow screen of death instead of your page because your tags are mismatched. It doesn?t reflect especially poorly on you that this happens (and I don?t claim to be any paragon of marking up myself). It?s a natural consequence of the fact that WordPress is not designed from the ground-up to emit valid XHTML, but instead to belt out broken markup that mostly renders okay thanks to browsers? forgiving error handling. JeremyVisser: Most (if not all) WordPress blogs would break very visibly, just like Viper007Bond?s, if they were served as application/xhtml+xml, forcing browsers to use XML parsing rather than tag soup parsing. Indeed our ability to serve XHTML as text/html at all depends on browsers being ?crappy? and ?non-standards-compliant?, since if they had complied with the HTML specification they would interpret minimized XHTML tags ending /> as really ending at the / and print the > as part of the text content, due the SGML declaration for HTML 4. -- Ticket URL: <http://trac.wordpress.org/ticket/3406#comment:12> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:12:19 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:12:27 2006 Subject: [wp-trac] Re: [WordPress Trac] #3188: Shouldn't use deprecated functions start_wp In-Reply-To: <044.eaf5fdb38ad397846321cda10f551945@lists.automattic.com> References: <044.eaf5fdb38ad397846321cda10f551945@lists.automattic.com> Message-ID: <053.a7db7a2f8fa96ffc02bb4259da7fbad5@lists.automattic.com> #3188: Shouldn't use deprecated functions start_wp -------------------------+-------------------------------------------------- Reporter: foolswisdom | Owner: westi Type: defect | Status: reopened Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch | -------------------------+-------------------------------------------------- Comment (by matt): Wouldn't this allow someone to put export in the query string on someone's blog or RSS feed and grab the whole thing? -- Ticket URL: <http://trac.wordpress.org/ticket/3188#comment:8> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:12:55 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:13:02 2006 Subject: [wp-trac] Re: [WordPress Trac] #3130: Proposal for category improvements In-Reply-To: <066.c4fbde74d3dc82689100c4a4f6ed44bc@lists.automattic.com> References: <066.c4fbde74d3dc82689100c4a4f6ed44bc@lists.automattic.com> Message-ID: <075.289d1f008b485784a83001959a15293d@lists.automattic.com> #3130: Proposal for category improvements ----------------------------+----------------------------------------------- Reporter: markjaquith | Owner: markjaquith Type: enhancement | Status: assigned Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/3130#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:22:50 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:23:04 2006 Subject: [wp-trac] Re: [WordPress Trac] #3122: Edit post page should have a link to the post In-Reply-To: <066.dd70fa436b539d3ab25f0f45d8fcfe1e@lists.automattic.com> References: <066.dd70fa436b539d3ab25f0f45d8fcfe1e@lists.automattic.com> Message-ID: <075.d0aac6379833bd6155af46d96f01bcda@lists.automattic.com> #3122: Edit post page should have a link to the post ----------------------------+----------------------------------------------- Reporter: matt | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/3122#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:23:03 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:23:15 2006 Subject: [wp-trac] Re: [WordPress Trac] #3102: When sending an image to the editor, it scrolls everything to the top In-Reply-To: <066.1dfcd0caf256fe1417c0e2fcde170796@lists.automattic.com> References: <066.1dfcd0caf256fe1417c0e2fcde170796@lists.automattic.com> Message-ID: <075.1f2c61ed0b10891bbe139454e3cba886@lists.automattic.com> #3102: When sending an image to the editor, it scrolls everything to the top ----------------------------+----------------------------------------------- Reporter: matt | Owner: skeltoac Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/3102#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:23:48 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:23:59 2006 Subject: [wp-trac] Re: [WordPress Trac] #2919: Option to insert image css class or id in tinyMCE In-Reply-To: <066.077823148a18c9c2e29a7ebc84b08a99@lists.automattic.com> References: <066.077823148a18c9c2e29a7ebc84b08a99@lists.automattic.com> Message-ID: <075.697109afeaf1b6dab4357e0ce2be6dee@lists.automattic.com> #2919: Option to insert image css class or id in tinyMCE --------------------------------+------------------------------------------- Reporter: pcdinh | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.2 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: images css tinyMCE | --------------------------------+------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2919#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:24:17 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:24:27 2006 Subject: [wp-trac] Re: [WordPress Trac] #2967: Grabbing IP Address on registration In-Reply-To: <066.7c80b47e351c8295250a853893d094cd@lists.automattic.com> References: <066.7c80b47e351c8295250a853893d094cd@lists.automattic.com> Message-ID: <075.9873fb27466457fb5cc99cbe9fd2ecac@lists.automattic.com> #2967: Grabbing IP Address on registration ----------------------------+----------------------------------------------- Reporter: darkfate | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.4 Severity: normal | Resolution: invalid Keywords: needs-patch | ----------------------------+----------------------------------------------- Changes (by matt): * status: new => closed * resolution: => invalid Comment: I don't think it's a good idea. -- Ticket URL: <http://trac.wordpress.org/ticket/2967#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:25:48 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:26:03 2006 Subject: [wp-trac] Re: [WordPress Trac] #2406: add_query_arg() does not return Strict XHTML links. In-Reply-To: <066.3d0517a98945720478f62101861834df@lists.automattic.com> References: <066.3d0517a98945720478f62101861834df@lists.automattic.com> Message-ID: <075.dd95cd6081583437267e07a054cb0883@lists.automattic.com> #2406: add_query_arg() does not return Strict XHTML links. ---------------------------------------------------------------+------------ Reporter: majelbstoat | Owner: markjaquith Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.1 Severity: normal | Resolution: invalid Keywords: add_query_arg ampersand xhtml strict bg|has-patch | ---------------------------------------------------------------+------------ Changes (by matt): * status: assigned => closed * resolution: => invalid Comment: Yes we should do this on a different level, so we don't break redirects. -- Ticket URL: <http://trac.wordpress.org/ticket/2406#comment:9> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:26:04 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:26:13 2006 Subject: [wp-trac] Re: [WordPress Trac] #2407: "Ready for Publication" button needed for contributing authors In-Reply-To: <066.02c2926445346b0ce388929b6394b89a@lists.automattic.com> References: <066.02c2926445346b0ce388929b6394b89a@lists.automattic.com> Message-ID: <075.78fead9fd18fcc87518afdd7e97db4cc@lists.automattic.com> #2407: "Ready for Publication" button needed for contributing authors ----------------------------+----------------------------------------------- Reporter: skippy | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.1 Severity: major | Resolution: duplicate Keywords: bg|needs-patch | ----------------------------+----------------------------------------------- Changes (by matt): * status: new => closed * resolution: => duplicate -- Ticket URL: <http://trac.wordpress.org/ticket/2407#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:27:30 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:27:37 2006 Subject: [wp-trac] Re: [WordPress Trac] #2409: wordpress errors return status 200 In-Reply-To: <066.972c91c7c13ec1759614199db66f35b7@lists.automattic.com> References: <066.972c91c7c13ec1759614199db66f35b7@lists.automattic.com> Message-ID: <075.46a6199ffc4c46688c3b89dcde5d72a5@lists.automattic.com> #2409: wordpress errors return status 200 -----------------------------------+---------------------------------------- Reporter: glub | Owner: markjaquith Type: defect | Status: assigned Priority: normal | Milestone: 2.2 Component: General | Version: 2.0.1 Severity: normal | Resolution: Keywords: has-patch 2nd-opinion | -----------------------------------+---------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2409#comment:12> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:27:52 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:28:01 2006 Subject: [wp-trac] Re: [WordPress Trac] #2415: New hooks for previous and next post In-Reply-To: <066.b1243405ee04c18526a2b0ca2bc100a4@lists.automattic.com> References: <066.b1243405ee04c18526a2b0ca2bc100a4@lists.automattic.com> Message-ID: <075.454f3033a781231b8d3e370e2e70c001@lists.automattic.com> #2415: New hooks for previous and next post ---------------------------------------------------+------------------------ Reporter: majelbstoat | Owner: majelbstoat Type: enhancement | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.0.1 Severity: normal | Resolution: Keywords: hook previous next posts bg|has-patch | ---------------------------------------------------+------------------------ Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2415#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:28:12 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:28:22 2006 Subject: [wp-trac] Re: [WordPress Trac] #3202: "Redirect Old Slugs" should be in core. In-Reply-To: <066.bcd5a297b816b6ea10b92c72283437d1@lists.automattic.com> References: <066.bcd5a297b816b6ea10b92c72283437d1@lists.automattic.com> Message-ID: <075.a07942b8ea249cba797192f0a63ae15d@lists.automattic.com> #3202: "Redirect Old Slugs" should be in core. -----------------------------------+---------------------------------------- Reporter: bryanveloso | Owner: markjaquith Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch 2nd-opinion | -----------------------------------+---------------------------------------- Comment (by JeremyVisser): If you're going to commit this, can you also make the slug automatically update to reflect the post title when the post title is changed? I believe the reason the slug wasn't updated to reflect an updated post title was to not break links, but if this is committed, that won't be an issue. -- Ticket URL: <http://trac.wordpress.org/ticket/3202#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:34:08 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:34:21 2006 Subject: [wp-trac] Re: [WordPress Trac] #2460: wp-mail.php: quoted printable encoding not decoding In-Reply-To: <066.afb2805f6b22d6bed1725473b44f0567@lists.automattic.com> References: <066.afb2805f6b22d6bed1725473b44f0567@lists.automattic.com> Message-ID: <075.7d4b44879d28fc55d08a2a9aec71e327@lists.automattic.com> #2460: wp-mail.php: quoted printable encoding not decoding ----------------------------------------------------+----------------------- Reporter: Staro | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: General | Version: 2.0.1 Severity: normal | Resolution: Keywords: wp-mail.php quoted printable has-patch | ----------------------------------------------------+----------------------- Changes (by matt): * milestone: 2.1 => 2.2 Comment: +1 -- Ticket URL: <http://trac.wordpress.org/ticket/2460#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:34:42 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:34:52 2006 Subject: [wp-trac] Re: [WordPress Trac] #2461: Categories and Posts, Parents and Children not separated in list_cats() In-Reply-To: <066.edcdbc60fa7d07f3af3ce7cfaf99bca8@lists.automattic.com> References: <066.edcdbc60fa7d07f3af3ce7cfaf99bca8@lists.automattic.com> Message-ID: <075.4f656b9c2e9027eb379e005b209294c7@lists.automattic.com> #2461: Categories and Posts, Parents and Children not separated in list_cats() ------------------------+--------------------------------------------------- Reporter: researcher | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Template | Version: 2.0.1 Severity: normal | Resolution: invalid Keywords: list_cats | ------------------------+--------------------------------------------------- Changes (by matt): * status: new => closed * resolution: => invalid Comment: Sorry, I don't understand this. -- Ticket URL: <http://trac.wordpress.org/ticket/2461#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:33:30 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:36:39 2006 Subject: [wp-trac] Re: [WordPress Trac] #2458: postmeta data not escaped In-Reply-To: <066.ca755916a8b62b84b282ec43cf63e639@lists.automattic.com> References: <066.ca755916a8b62b84b282ec43cf63e639@lists.automattic.com> Message-ID: <075.0acd1f1fad72d316438539186d0edeb8@lists.automattic.com> #2458: postmeta data not escaped -----------------------------------------+---------------------------------- Reporter: bungeman | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.1 Severity: normal | Resolution: invalid Keywords: escape, slash, bg|has-patch | -----------------------------------------+---------------------------------- Changes (by matt): * status: new => closed * resolution: => invalid -- Ticket URL: <http://trac.wordpress.org/ticket/2458#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:47:42 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:47:53 2006 Subject: [wp-trac] Re: [WordPress Trac] #2437: Add CSS classes to parents of the current item in the output of wp_list_cats and wp_list_pages [patch] In-Reply-To: <066.13b12d802db72cf6030ad63c6ec731ac@lists.automattic.com> References: <066.13b12d802db72cf6030ad63c6ec731ac@lists.automattic.com> Message-ID: <075.8981704bbdcebe9680be1b60e73bdb44@lists.automattic.com> #2437: Add CSS classes to parents of the current item in the output of wp_list_cats and wp_list_pages [patch] --------------------------+------------------------------------------------- Reporter: janX | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.2 Component: General | Version: 2.0.1 Severity: normal | Resolution: Keywords: bg|has-patch | --------------------------+------------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2437#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:47:53 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:48:03 2006 Subject: [wp-trac] Re: [WordPress Trac] #2433: Provide some API for WP_Rewrite In-Reply-To: <066.4294b26dc3a137f58aedbe59103e9789@lists.automattic.com> References: <066.4294b26dc3a137f58aedbe59103e9789@lists.automattic.com> Message-ID: <075.81c2996ba02192214081a17d0c65c5b4@lists.automattic.com> #2433: Provide some API for WP_Rewrite ---------------------------------------------------------+------------------ Reporter: davidhouse | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.0.1 Severity: normal | Resolution: Keywords: bg|has-patch bg|2nd-opinion bg|dev-feedback | ---------------------------------------------------------+------------------ Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2433#comment:26> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:48:26 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:48:36 2006 Subject: [wp-trac] Re: [WordPress Trac] #2682: Remove db store of absolute path for uploads In-Reply-To: <066.c49ff6ef44fded9522229645606a1738@lists.automattic.com> References: <066.c49ff6ef44fded9522229645606a1738@lists.automattic.com> Message-ID: <075.7fe877dfe00f1b0ac7b79ae8f327d8fd@lists.automattic.com> #2682: Remove db store of absolute path for uploads ---------------------------------------------------------------+------------ Reporter: ryanscheuermann | Owner: ryanscheuermann Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: upload, migration, bg|has-patch, bg|needs-testing | ---------------------------------------------------------------+------------ Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2682#comment:20> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:51:00 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:51:12 2006 Subject: [wp-trac] Re: [WordPress Trac] #2687: The comments_number function's fourth parameter is overwritten in the function body. In-Reply-To: <066.deefbaafe4ab34234fca244094b71016@lists.automattic.com> References: <066.deefbaafe4ab34234fca244094b71016@lists.automattic.com> Message-ID: <075.eaa63c7bb98d52ffd01ea1671e01d194@lists.automattic.com> #2687: The comments_number function's fourth parameter is overwritten in the function body. -------------------------------------------------------+-------------------- Reporter: Pyrmont | Owner: westi Type: defect | Status: assigned Priority: normal | Milestone: 2.2 Component: General | Version: 2.0.2 Severity: normal | Resolution: Keywords: bg|dev-feedback comments, comments_number | -------------------------------------------------------+-------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2687#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:51:16 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:51:28 2006 Subject: [wp-trac] Re: [WordPress Trac] #2710: list_cats / wp_list_cats: hide_empty does not hide cats with non-empty sub-cats In-Reply-To: <066.5c3b0ebcd67a0a75291af284749c29c3@lists.automattic.com> References: <066.5c3b0ebcd67a0a75291af284749c29c3@lists.automattic.com> Message-ID: <075.23f1011f6708fdf258befb58a630ba60@lists.automattic.com> #2710: list_cats / wp_list_cats: hide_empty does not hide cats with non-empty sub- cats -----------------------------------------------+---------------------------- Reporter: janX | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Template | Version: 2.0.2 Severity: normal | Resolution: Keywords: list_cats wp_list_cats hide_empty | -----------------------------------------------+---------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2710#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:56:33 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 00:56:40 2006 Subject: [wp-trac] Re: [WordPress Trac] #2763: get_post_status should use post_status = inherit instead of post_type = attachment In-Reply-To: <066.8aefb32599ace4851348b1798243a4e0@lists.automattic.com> References: <066.8aefb32599ace4851348b1798243a4e0@lists.automattic.com> Message-ID: <075.85f329f13a003b40874d5e0e0c1885ee@lists.automattic.com> #2763: get_post_status should use post_status = inherit instead of post_type = attachment ----------------------------------------------------------+----------------- Reporter: ryanscheuermann | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: post_status attachment has-patch 2nd-opinion | ----------------------------------------------------------+----------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2763#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 01:11:25 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 01:11:32 2006 Subject: [wp-trac] Re: [WordPress Trac] #2926: Theme files are not ordered alphabetically In-Reply-To: <066.2b9634044b516a16294ccac0562782c3@lists.automattic.com> References: <066.2b9634044b516a16294ccac0562782c3@lists.automattic.com> Message-ID: <075.76e5befbe7479739af563ea46e06dcb3@lists.automattic.com> #2926: Theme files are not ordered alphabetically -------------------------------------------------------------+-------------- Reporter: Arrrr | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.0.3 Severity: normal | Resolution: Keywords: theme theme-editor order alphabetical has-patch | -------------------------------------------------------------+-------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2926#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 01:12:56 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 01:13:04 2006 Subject: [wp-trac] Re: [WordPress Trac] #2874: comment mails should include a link directly to #respond In-Reply-To: <066.ea6ab6ea0cedd385c135d5328dbc8d26@lists.automattic.com> References: <066.ea6ab6ea0cedd385c135d5328dbc8d26@lists.automattic.com> Message-ID: <075.107178bb4d9bfdc653c47f416ddf87f2@lists.automattic.com> #2874: comment mails should include a link directly to #respond ----------------------------+----------------------------------------------- Reporter: RuddO | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: Severity: normal | Resolution: wontfix Keywords: has-patch | ----------------------------+----------------------------------------------- Changes (by matt): * status: new => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/2874#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 01:13:06 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 01:13:15 2006 Subject: [wp-trac] Re: [WordPress Trac] #2864: Magpie falling behind feed developments In-Reply-To: <066.897fbefe09c7ae61f53e55b1085c67ed@lists.automattic.com> References: <066.897fbefe09c7ae61f53e55b1085c67ed@lists.automattic.com> Message-ID: <075.0747d5b15df67af6463551d82c115ad1@lists.automattic.com> #2864: Magpie falling behind feed developments -------------------------------------------------------------------+-------- Reporter: skeltoac | Owner: link92 Type: enhancement | Status: reopened Priority: normal | Milestone: 2.2 Component: Optimization | Version: 2.0.3 Severity: normal | Resolution: Keywords: magpie rss atom rdf xml bg|has-patch bg|needs-testing | -------------------------------------------------------------------+-------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2864#comment:10> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 01:13:19 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 01:13:29 2006 Subject: [wp-trac] Re: [WordPress Trac] #2864: Magpie falling behind feed developments In-Reply-To: <066.897fbefe09c7ae61f53e55b1085c67ed@lists.automattic.com> References: <066.897fbefe09c7ae61f53e55b1085c67ed@lists.automattic.com> Message-ID: <075.134ad4bbf76c6c74a3b040b19b697af9@lists.automattic.com> #2864: Magpie falling behind feed developments -------------------------------------------------------------------+-------- Reporter: skeltoac | Owner: link92 Type: enhancement | Status: closed Priority: normal | Milestone: 2.2 Component: Optimization | Version: 2.0.3 Severity: normal | Resolution: invalid Keywords: magpie rss atom rdf xml bg|has-patch bg|needs-testing | -------------------------------------------------------------------+-------- Changes (by matt): * status: reopened => closed * resolution: => invalid Comment: Closing awaiting new patches. -- Ticket URL: <http://trac.wordpress.org/ticket/2864#comment:11> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 01:14:07 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 01:14:18 2006 Subject: [wp-trac] Re: [WordPress Trac] #2818: "Admin" not a "Post Author" option In-Reply-To: <066.e7280131a48143e26bc17b75ed8f4f7c@lists.automattic.com> References: <066.e7280131a48143e26bc17b75ed8f4f7c@lists.automattic.com> Message-ID: <075.5470b5142702c85baee4346bb6e86315@lists.automattic.com> #2818: "Admin" not a "Post Author" option ----------------------------+----------------------------------------------- Reporter: markjaquith | Owner: markjaquith Type: defect | Status: assigned Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2818#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 01:16:07 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 01:16:13 2006 Subject: [wp-trac] Re: [WordPress Trac] #2797: Drag and Drop uploaded file URL breaks in Firefox 1.5.0.4 In-Reply-To: <066.c433c5e3a21728b3ac9c3cf0bbde5994@lists.automattic.com> References: <066.c433c5e3a21728b3ac9c3cf0bbde5994@lists.automattic.com> Message-ID: <075.1c918c17a6ac3c05c3177c3e371fc358@lists.automattic.com> #2797: Drag and Drop uploaded file URL breaks in Firefox 1.5.0.4 ----------------------------+----------------------------------------------- Reporter: buddyellis | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.0.2 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2797#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 01:16:44 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 01:16:51 2006 Subject: [wp-trac] Re: [WordPress Trac] #2784: Make all foreach() loops cast to array In-Reply-To: <066.8e19d6f44e448c02efdf2d54a0585438@lists.automattic.com> References: <066.8e19d6f44e448c02efdf2d54a0585438@lists.automattic.com> Message-ID: <075.0b41714ca3040aa306815590d2f471b5@lists.automattic.com> #2784: Make all foreach() loops cast to array --------------------------+------------------------------------------------- Reporter: markjaquith | Owner: markjaquith Type: defect | Status: assigned Priority: normal | Milestone: 2.2 Component: Optimization | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch | --------------------------+------------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/2784#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 01:30:19 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 01:30:26 2006 Subject: [wp-trac] Re: [WordPress Trac] #2967: Grabbing IP Address on registration In-Reply-To: <066.7c80b47e351c8295250a853893d094cd@lists.automattic.com> References: <066.7c80b47e351c8295250a853893d094cd@lists.automattic.com> Message-ID: <075.aa3949be699f6ae78d2996ff8662b6a8@lists.automattic.com> #2967: Grabbing IP Address on registration ----------------------------+----------------------------------------------- Reporter: darkfate | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.4 Severity: normal | Resolution: invalid Keywords: needs-patch | ----------------------------+----------------------------------------------- Comment (by Viper007Bond): Agreed. Best left to a plugin. -- Ticket URL: <http://trac.wordpress.org/ticket/2967#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 00:12:36 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 01:33:35 2006 Subject: [wp-trac] Re: [WordPress Trac] #3146: Private posts on Manage \ Posts are twice designated as private In-Reply-To: <066.2594c4508c0d98b4ded2acc3a844ee40@lists.automattic.com> References: <066.2594c4508c0d98b4ded2acc3a844ee40@lists.automattic.com> Message-ID: <075.40aff77c2893568da61dfc5f03c9ebb7@lists.automattic.com> #3146: Private posts on Manage \ Posts are twice designated as private ----------------------------+----------------------------------------------- Reporter: markjaquith | Owner: markjaquith Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: fixed Keywords: | ----------------------------+----------------------------------------------- Changes (by matt): * status: new => closed * resolution: => fixed -- Ticket URL: <http://trac.wordpress.org/ticket/3146#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 01:45:36 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 01:45:45 2006 Subject: [wp-trac] Re: [WordPress Trac] #2474: Inline documentation for wpdb In-Reply-To: <066.c08e4ee3cb5bcd5c6da5ca2e3b81d20f@lists.automattic.com> References: <066.c08e4ee3cb5bcd5c6da5ca2e3b81d20f@lists.automattic.com> Message-ID: <075.4c935c1c4a154f3bf9101d29944afe93@lists.automattic.com> #2474: Inline documentation for wpdb --------------------------------+------------------------------------------- Reporter: masquerade | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.1 Severity: normal | Resolution: Keywords: inline-docs commit | --------------------------------+------------------------------------------- Comment (by ryan): [4549] gets most of this in but some bits of the patch didn't apply. Anyone care to provide and updated patch? -- Ticket URL: <http://trac.wordpress.org/ticket/2474#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 02:24:13 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 02:24:26 2006 Subject: [wp-trac] Re: [WordPress Trac] #2200: Ability to hide preview In-Reply-To: <066.66030d68d5b53480594bf4443ca2dfa4@lists.automattic.com> References: <066.66030d68d5b53480594bf4443ca2dfa4@lists.automattic.com> Message-ID: <075.634625fc30a0e937c86ed8d38694d8ff@lists.automattic.com> #2200: Ability to hide preview -----------------------------------+---------------------------------------- Reporter: hypercubed | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.2 Component: Administration | Version: 2.0 Severity: normal | Resolution: Keywords: 2nd-opinion has-patch | -----------------------------------+---------------------------------------- Comment (by markjaquith): Not the same fix, but people who want it off altogether can use this: http://txfx.net/code/wordpress/clutter-free/ -- Ticket URL: <http://trac.wordpress.org/ticket/2200#comment:10> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 02:38:13 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 02:38:21 2006 Subject: [wp-trac] Re: [WordPress Trac] #3215: Login & Update functions everything is broken In-Reply-To: <049.6066b63c1044229dd67a636989ac05fd@lists.automattic.com> References: <049.6066b63c1044229dd67a636989ac05fd@lists.automattic.com> Message-ID: <058.8dda7eb898785c1308406a8703c8c978@lists.automattic.com> #3215: Login & Update functions everything is broken --------------------------------------------+------------------------------- Reporter: Xmion | Owner: markjaquith Type: defect | Status: assigned Priority: highest | Milestone: 2.0.6 Component: General | Version: 2.1 Severity: blocker | Resolution: Keywords: Blank page 302 maint-candidate | --------------------------------------------+------------------------------- Changes (by markjaquith): * severity: critical => blocker Comment: Yes... blocker. I haven't heard anything since 11/22's commits, so I'm going to ping wp-testers -- Ticket URL: <http://trac.wordpress.org/ticket/3215#comment:20> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 02:40:40 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 02:40:49 2006 Subject: [wp-trac] Re: [WordPress Trac] #2415: New hooks for previous and next post In-Reply-To: <066.b1243405ee04c18526a2b0ca2bc100a4@lists.automattic.com> References: <066.b1243405ee04c18526a2b0ca2bc100a4@lists.automattic.com> Message-ID: <075.dafd8ec988e2b69f0e08c7b287633646@lists.automattic.com> #2415: New hooks for previous and next post ---------------------------------------------------+------------------------ Reporter: majelbstoat | Owner: majelbstoat Type: enhancement | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.0.1 Severity: normal | Resolution: Keywords: hook previous next posts bg|has-patch | ---------------------------------------------------+------------------------ Comment (by majelbstoat): Can I ask why such a minor but useful modification will not be present in the next major release? -- Ticket URL: <http://trac.wordpress.org/ticket/2415#comment:8> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 07:44:15 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 07:44:23 2006 Subject: [wp-trac] [WordPress Trac] #3409: Make save_mod_rewrite_rules() return something Message-ID: <066.7864125767ab778c25d79557521b1896@lists.automattic.com> #3409: Make save_mod_rewrite_rules() return something --------------------------+------------------------------------------------- Reporter: Viper007Bond | Owner: anonymous Type: enhancement | Status: new Priority: low | Milestone: 2.1 Component: General | Version: 2.1 Severity: minor | Keywords: has-patch --------------------------+------------------------------------------------- I have a plugin that forces a write of the `.htaccess` file. It'd be nice to know if it was successful or not. :) -- Ticket URL: <http://trac.wordpress.org/ticket/3409> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 08:27:43 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 08:27:51 2006 Subject: [wp-trac] Re: [WordPress Trac] #3370: Do not have permission to add category. In-Reply-To: <066.70d47b11909d090da6f4f0afcfd8da92@lists.automattic.com> References: <066.70d47b11909d090da6f4f0afcfd8da92@lists.automattic.com> Message-ID: <075.2f172380110fc97c742f8c2d0066b51b@lists.automattic.com> #3370: Do not have permission to add category. ----------------------------------------+----------------------------------- Reporter: computerwolf | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.0.5 Component: Administration | Version: 2.0.5 Severity: normal | Resolution: Keywords: category permission adding | ----------------------------------------+----------------------------------- Changes (by computerwolf): * milestone: => 2.0.5 -- Ticket URL: <http://trac.wordpress.org/ticket/3370#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 08:31:52 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 08:32:01 2006 Subject: [wp-trac] Re: [WordPress Trac] #3202: "Redirect Old Slugs" should be in core. In-Reply-To: <066.bcd5a297b816b6ea10b92c72283437d1@lists.automattic.com> References: <066.bcd5a297b816b6ea10b92c72283437d1@lists.automattic.com> Message-ID: <075.fc5d91f957212d4d0af085e54f3a2aca@lists.automattic.com> #3202: "Redirect Old Slugs" should be in core. -----------------------------------+---------------------------------------- Reporter: bryanveloso | Owner: markjaquith Type: enhancement | Status: assigned Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch 2nd-opinion | -----------------------------------+---------------------------------------- Comment (by markjaquith): JeremyVisser, Hm, probably not a great idea. It'd cause a lot of unnecessary redirects. Take for instance the rather common practice of updating "Post Title" to "Post Title (UPDATED!)" ... that shouldn't cause a slug change, because, well, it doesn't make sense to have "updated" in the slug, it'll break caching, and it could cause the link to lose a bit of Google juice. -- Ticket URL: <http://trac.wordpress.org/ticket/3202#comment:7> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 09:08:42 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 09:08:52 2006 Subject: [wp-trac] Re: [WordPress Trac] #3188: Shouldn't use deprecated functions start_wp In-Reply-To: <044.eaf5fdb38ad397846321cda10f551945@lists.automattic.com> References: <044.eaf5fdb38ad397846321cda10f551945@lists.automattic.com> Message-ID: <053.be17d246c77281d945d0e687a4212c96@lists.automattic.com> #3188: Shouldn't use deprecated functions start_wp -------------------------+-------------------------------------------------- Reporter: foolswisdom | Owner: westi Type: defect | Status: reopened Priority: normal | Milestone: 2.1 Component: General | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch | -------------------------+-------------------------------------------------- Comment (by westi): Replying to [comment:8 matt]: > Wouldn't this allow someone to put export in the query string on someone's blog or RSS feed and grab the whole thing? Well post_type is a private query var (http://trac.wordpress.org/browser/trunk/wp-includes/classes.php#L6). I'm not entirely sure how that affects where or not it is allowed in the url without spending more time reading the code. However it probably should. -- Ticket URL: <http://trac.wordpress.org/ticket/3188#comment:9> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 09:11:22 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 09:11:29 2006 Subject: [wp-trac] Re: [WordPress Trac] #3406: Use HTML4 instead of XHTML1 In-Reply-To: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> References: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> Message-ID: <075.3a61befc91c1f6a4b7ee93ac23292cfc@lists.automattic.com> #3406: Use HTML4 instead of XHTML1 -----------------------+---------------------------------------------------- Reporter: TedNelson | Owner: anonymous Type: defect | Status: reopened Priority: normal | Milestone: Component: Template | Version: Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Changes (by benjaminhawkeslewis): * status: closed => reopened * resolution: wontfix => Comment: Given the understandable concerns about breaking existing templates, how about just giving authors the option of either emitting pseudo-XHTML tag soup or the option of switching to HTML 4 by introducing an HTML 4 mode into WordPress? What exactly would be the downside of that? Better yet, if you want to step boldly into the XHTML future, you could do it properly by serializing to HTML 4 or XHTML served as application/xhtml+xml depending on the Accept header. I suggest a reasonable method of content negotiation using the Accept header at: http://lists.w3.org/Archives/Public/www-html/2006Nov/0044.html At the very least, you should start serving XHTML with the correct MIME type of application/xhtml+xml to supporting user agents. This is what the authors of Appendix C intended, not that you should continue to inflict tag soup on all comers. You'll lose incremental rendering in Firefox, but that's a small price to pay for progress isn't it? If it forces you to impose better checks on validity and conformance, so much the better. -- Ticket URL: <http://trac.wordpress.org/ticket/3406#comment:13> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 09:43:29 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 09:43:45 2006 Subject: [wp-trac] Re: [WordPress Trac] #3406: Use HTML4 instead of XHTML1 In-Reply-To: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> References: <066.ad6e65442a6edb4a0958a56989891e07@lists.automattic.com> Message-ID: <075.d6dc637ba667d49be87844d8074eb399@lists.automattic.com> #3406: Use HTML4 instead of XHTML1 -----------------------+---------------------------------------------------- Reporter: TedNelson | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: Component: Template | Version: Severity: normal | Resolution: wontfix Keywords: | -----------------------+---------------------------------------------------- Changes (by Viper007Bond): * status: reopened => closed * resolution: => wontfix Comment: Something as large as this shouldn't be discussed via Trac. Take it up on [http://codex.wordpress.org/Mailing_Lists#Hackers wp-hackers]. Replying to [comment:12 benjaminhawkeslewis]: And sure enough, if we visit your [http://www.viper007bond.com/archives/2006/11/19/casino-royale/" penultimate post] we find it fails validation with two errors. If you were serving that page as application/xhtml+xml, so that Firefox used its XHTML parser rather than its tag soup parser, you?d see a yellow screen of death instead of your page because your tags are mismatched. A result of my stupidity / a plugin. -- Ticket URL: <http://trac.wordpress.org/ticket/3406#comment:14> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 10:29:48 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 10:30:04 2006 Subject: [wp-trac] [WordPress Trac] #3410: Security : wp-admin/users.php No role user can list all wp users Message-ID: <066.b2ee6bb47daabf6d32bbc1313852710e@lists.automattic.com> #3410: Security : wp-admin/users.php No role user can list all wp users -----------------------+---------------------------------------------------- Reporter: devil1591 | Owner: anonymous Type: defect | Status: new Priority: highest | Milestone: 2.1 Component: Security | Version: Severity: critical | Keywords: security users.php -----------------------+---------------------------------------------------- A simple user, even without role can list every WP users. - Just login to WP with a basic account - Type /wp-admin/users.php at the end of the URL Then it lists every users, with email and others... -- Ticket URL: <http://trac.wordpress.org/ticket/3410> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 10:47:02 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 10:47:11 2006 Subject: [wp-trac] Re: [WordPress Trac] #3410: Security : wp-admin/users.php No role user can list all wp users In-Reply-To: <066.b2ee6bb47daabf6d32bbc1313852710e@lists.automattic.com> References: <066.b2ee6bb47daabf6d32bbc1313852710e@lists.automattic.com> Message-ID: <075.32fe67b0245b916c274532b1c463a384@lists.automattic.com> #3410: Security : wp-admin/users.php No role user can list all wp users ------------------------------------------+--------------------------------- Reporter: devil1591 | Owner: westi Type: defect | Status: assigned Priority: highest | Milestone: 2.1 Component: Security | Version: 2.1 Severity: critical | Resolution: Keywords: security users.php has-patch | ------------------------------------------+--------------------------------- Changes (by westi): * keywords: security users.php => security users.php has-patch * status: new => assigned * version: => 2.1 * owner: anonymous => westi Comment: Confirm this works on trunk. Attaching simple patch which just blocks you accessing users.php as I can't see a need for someone without edit_users accessing it. -- Ticket URL: <http://trac.wordpress.org/ticket/3410#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 10:53:48 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 10:54:03 2006 Subject: [wp-trac] Re: [WordPress Trac] #3410: Security : wp-admin/users.php No role user can list all wp users In-Reply-To: <066.b2ee6bb47daabf6d32bbc1313852710e@lists.automattic.com> References: <066.b2ee6bb47daabf6d32bbc1313852710e@lists.automattic.com> Message-ID: <075.dbbce6e1efa102ea6af210a528c8f1d2@lists.automattic.com> #3410: Security : wp-admin/users.php No role user can list all wp users ------------------------------------------+--------------------------------- Reporter: devil1591 | Owner: westi Type: defect | Status: assigned Priority: highest | Milestone: 2.1 Component: Security | Version: 2.1 Severity: critical | Resolution: Keywords: security users.php has-patch | ------------------------------------------+--------------------------------- Comment (by westi): 2.0.5 / branches/2.0 is safe from this issue already: "You do not have sufficient permissions to access this page." - protected by the menu.php capabilities checks. -- Ticket URL: <http://trac.wordpress.org/ticket/3410#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 12:19:13 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 12:19:37 2006 Subject: [wp-trac] [WordPress Trac] #3411: If file uploaded aren't images, dont' link them with an image Message-ID: <056.b9860923b4a488a71dbcf95bcd350b9e@lists.automattic.com> #3411: If file uploaded aren't images, dont' link them with an image ----------------------------+----------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Keywords: admin, upload ----------------------------+----------------------------------------------- There is one issue with upload of not images files: If i select to link the not image file, this is the result i get in editor: {{{ <a href='!http://www.domain.tld/wp-content/uploads/modem.mp3' title='Modem'> <img src='!http://www.domain.tld/wp-content/uploads/modem.mp3' alt='Modem' /> </a> }}} Tag IMG shouldn't be there. More, Links shouldn't done by absolute path for portability. If i'll change the domain in the future, or the domain, the links still unchanged. Would be better some kind of placeholder to filter with the site url global variable? -- Ticket URL: <http://trac.wordpress.org/ticket/3411> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 12:54:24 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 12:54:33 2006 Subject: [wp-trac] [WordPress Trac] #3412: Images in upload page and pane are missing Message-ID: <056.63f2faa2c649c3a745f5b7144c5f5290@lists.automattic.com> #3412: Images in upload page and pane are missing ----------------------------+----------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Keywords: ----------------------------+----------------------------------------------- I can't see the images but only the blue squares with theire respective ALT text hovering. Could be the src= path broken? -- Ticket URL: <http://trac.wordpress.org/ticket/3412> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 12:59:45 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 12:59:58 2006 Subject: [wp-trac] Re: [WordPress Trac] #3412: Images in upload page and pane are missing In-Reply-To: <056.63f2faa2c649c3a745f5b7144c5f5290@lists.automattic.com> References: <056.63f2faa2c649c3a745f5b7144c5f5290@lists.automattic.com> Message-ID: <065.02ae8b8416ac454faeaa497e46745e09@lists.automattic.com> #3412: Images in upload page and pane are missing ----------------------------+----------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: invalid Keywords: | ----------------------------+----------------------------------------------- Changes (by Viper007Bond): * status: new => closed * resolution: => invalid Comment: I don't see an `<img>` tag in the source, do you? ;) -- Ticket URL: <http://trac.wordpress.org/ticket/3412#comment:1> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 18:38:03 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 18:38:23 2006 Subject: [wp-trac] Re: [WordPress Trac] #3410: Security : wp-admin/users.php No role user can list all wp users In-Reply-To: <066.b2ee6bb47daabf6d32bbc1313852710e@lists.automattic.com> References: <066.b2ee6bb47daabf6d32bbc1313852710e@lists.automattic.com> Message-ID: <075.46df85e20d1acfe776ad2f504c377d1c@lists.automattic.com> #3410: Security : wp-admin/users.php No role user can list all wp users ------------------------------------------+--------------------------------- Reporter: devil1591 | Owner: westi Type: defect | Status: assigned Priority: highest | Milestone: 2.1 Component: Security | Version: 2.1 Severity: critical | Resolution: Keywords: security users.php has-patch | ------------------------------------------+--------------------------------- Comment (by ryan): This is because of the way the User and Profile menus are conditionally populated in 2.1. westi's fix looks good. -- Ticket URL: <http://trac.wordpress.org/ticket/3410#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 18:58:08 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 18:58:31 2006 Subject: [wp-trac] Re: [WordPress Trac] #3412: Images in upload page and pane are missing In-Reply-To: <056.63f2faa2c649c3a745f5b7144c5f5290@lists.automattic.com> References: <056.63f2faa2c649c3a745f5b7144c5f5290@lists.automattic.com> Message-ID: <065.64812b0b88314018b1a6b76c1db42e29@lists.automattic.com> #3412: Images in upload page and pane are missing ----------------------------+----------------------------------------------- Reporter: tassoman | Owner: anonymous Type: defect | Status: reopened Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by tassoman): * status: closed => reopened * resolution: invalid => Comment: Do you prefer the attacnment? -- Ticket URL: <http://trac.wordpress.org/ticket/3412#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 19:51:43 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 19:52:05 2006 Subject: [wp-trac] Re: [WordPress Trac] #3370: Do not have permission to add category. In-Reply-To: <066.70d47b11909d090da6f4f0afcfd8da92@lists.automattic.com> References: <066.70d47b11909d090da6f4f0afcfd8da92@lists.automattic.com> Message-ID: <075.e749743eeae650a0c1c3b0babce3a887@lists.automattic.com> #3370: Do not have permission to add category. ----------------------------------------+----------------------------------- Reporter: computerwolf | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: Component: Administration | Version: 2.0.5 Severity: normal | Resolution: Keywords: category permission adding | ----------------------------------------+----------------------------------- Comment (by foolswisdom): This will probably require direct debugging on your server. I would volunteer, but I do not yet have the expertise. -- Ticket URL: <http://trac.wordpress.org/ticket/3370#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 20:23:58 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 20:24:38 2006 Subject: [wp-trac] Re: [WordPress Trac] #3202: "Redirect Old Slugs" should be in core. In-Reply-To: <066.bcd5a297b816b6ea10b92c72283437d1@lists.automattic.com> References: <066.bcd5a297b816b6ea10b92c72283437d1@lists.automattic.com> Message-ID: <075.f7ca3e2137016cabe323e61a85ce0ed8@lists.automattic.com> #3202: "Redirect Old Slugs" should be in core. -----------------------------------+---------------------------------------- Reporter: bryanveloso | Owner: markjaquith Type: enhancement | Status: reopened Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: has-patch 2nd-opinion | -----------------------------------+---------------------------------------- Changes (by ryan): * status: closed => reopened * resolution: fixed => Comment: I see this when updating the slug on a published post. Warning: in_array() [function.in-array]: Wrong datatype for second argument in /var/www/weblog/wp-admin/admin-functions.php on line 2094 -- Ticket URL: <http://trac.wordpress.org/ticket/3202#comment:9> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 22:19:25 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 22:19:43 2006 Subject: [wp-trac] Re: [WordPress Trac] #3002: On Windows machines register_activation_hook() does not work if plugin is in a subfolder of the plugins dir In-Reply-To: <066.bbe89dea56ace1da24ca9accf904913a@lists.automattic.com> References: <066.bbe89dea56ace1da24ca9accf904913a@lists.automattic.com> Message-ID: <075.30d74e603164280dbd9fe4dce4c5cdd1@lists.automattic.com> #3002: On Windows machines register_activation_hook() does not work if plugin is in a subfolder of the plugins dir ----------------------------+----------------------------------------------- Reporter: McShelby | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.0.4 Severity: major | Resolution: Keywords: | ----------------------------+----------------------------------------------- -- Ticket URL: <http://trac.wordpress.org/ticket/3002> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 22:19:35 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 22:19:44 2006 Subject: [wp-trac] Re: [WordPress Trac] #3002: On Windows machines register_activation_hook() does not work if plugin is in a subfolder of the plugins dir In-Reply-To: <066.bbe89dea56ace1da24ca9accf904913a@lists.automattic.com> References: <066.bbe89dea56ace1da24ca9accf904913a@lists.automattic.com> Message-ID: <075.7a42b13e5cfd263e12e8ffe1773a6dfe@lists.automattic.com> #3002: On Windows machines register_activation_hook() does not work if plugin is in a subfolder of the plugins dir ----------------------------+----------------------------------------------- Reporter: McShelby | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.0.4 Severity: major | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/3002#comment:5> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 22:19:49 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 22:20:02 2006 Subject: [wp-trac] Re: [WordPress Trac] #3007: wpautop error when div tags lack space before or after other text In-Reply-To: <066.e72f1810404bc00390b48ece76ea43a9@lists.automattic.com> References: <066.e72f1810404bc00390b48ece76ea43a9@lists.automattic.com> Message-ID: <075.05e0672b90ffb9ee81ece00353ffc58b@lists.automattic.com> #3007: wpautop error when div tags lack space before or after other text ---------------------+------------------------------------------------------ Reporter: erik | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: General | Version: 2.0.4 Severity: normal | Resolution: Keywords: wpautop | ---------------------+------------------------------------------------------ Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/3007#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 22:21:30 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 22:21:48 2006 Subject: [wp-trac] Re: [WordPress Trac] #3014: why use the @? In-Reply-To: <066.1af9387b01e6d0254b3bded3e01b01b9@lists.automattic.com> References: <066.1af9387b01e6d0254b3bded3e01b01b9@lists.automattic.com> Message-ID: <075.a04edc817425e18a8cee71892f1c7230@lists.automattic.com> #3014: why use the @? --------------------------------------+------------------------------------- Reporter: Denis-de-Bernardy | Owner: markjaquith Type: defect | Status: assigned Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.0.4 Severity: normal | Resolution: Keywords: needs-patch dev-feedback | --------------------------------------+------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/3014#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 22:44:17 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 22:44:24 2006 Subject: [wp-trac] Re: [WordPress Trac] #3083: Add alphabetizing to users' page In-Reply-To: <066.784b9c2f4370ff7a4d1810c20fec0795@lists.automattic.com> References: <066.784b9c2f4370ff7a4d1810c20fec0795@lists.automattic.com> Message-ID: <075.d78fc792f6e87767e70a776853eab578@lists.automattic.com> #3083: Add alphabetizing to users' page --------------------------------------------+------------------------------- Reporter: filosofo | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Optimization | Version: 2.1 Severity: normal | Resolution: wontfix Keywords: bg|has-patch users alphabetize | --------------------------------------------+------------------------------- Changes (by matt): * status: new => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/3083#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 22:59:08 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 22:59:21 2006 Subject: [wp-trac] Re: [WordPress Trac] #3080: wp_list_pages() is not closing the </li> in some circumstances In-Reply-To: <066.da674fc106c619c1ecdc93c39b317953@lists.automattic.com> References: <066.da674fc106c619c1ecdc93c39b317953@lists.automattic.com> Message-ID: <075.9062ac97def8b4597e42650ad0453150@lists.automattic.com> #3080: wp_list_pages() is not closing the </li> in some circumstances --------------------------+------------------------------------------------- Reporter: JeremyVisser | Owner: ryan Type: defect | Status: new Priority: high | Milestone: 2.1 Component: Template | Version: 2.1 Severity: normal | Resolution: Keywords: bughunt | --------------------------+------------------------------------------------- Changes (by matt): * priority: normal => high -- Ticket URL: <http://trac.wordpress.org/ticket/3080#comment:2> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 22:59:54 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 23:00:04 2006 Subject: [wp-trac] Re: [WordPress Trac] #3065: Ampersand in URL patch (needed as rss validation failed in a syndicated blog) In-Reply-To: <066.4a8363d6de54789f194ddeaa8397901d@lists.automattic.com> References: <066.4a8363d6de54789f194ddeaa8397901d@lists.automattic.com> Message-ID: <075.ee1b66e392ded21ff12e631824deacd8@lists.automattic.com> #3065: Ampersand in URL patch (needed as rss validation failed in a syndicated blog) ----------------------------+----------------------------------------------- Reporter: murky | Owner: anonymous Type: defect | Status: reopened Priority: normal | Milestone: 2.2 Component: Administration | Version: Severity: normal | Resolution: Keywords: has-patch | ----------------------------+----------------------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/3065#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 23:01:05 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 23:01:14 2006 Subject: [wp-trac] Re: [WordPress Trac] #3057: No load wp-settings.php from wp-config.php In-Reply-To: <066.f80b0e9ee52666d79510fb476694a2ee@lists.automattic.com> References: <066.f80b0e9ee52666d79510fb476694a2ee@lists.automattic.com> Message-ID: <075.bf1069257ef6e4f5b7ff0707d465ac96@lists.automattic.com> #3057: No load wp-settings.php from wp-config.php ----------------------------------------+----------------------------------- Reporter: forceagainstsomething | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.1 Severity: normal | Resolution: Keywords: settings, config has-patch | ----------------------------------------+----------------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/3057#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 23:01:50 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Thu Nov 30 23:02:04 2006 Subject: [wp-trac] Re: [WordPress Trac] #3052: pingback_ping() function displays wrong content in pingback-display in some occurances In-Reply-To: <066.2423427cdd66f111c851102decbc3436@lists.automattic.com> References: <066.2423427cdd66f111c851102decbc3436@lists.automattic.com> Message-ID: <075.f23d8b8a4ee7fbc48f0e9c6a5aac2615@lists.automattic.com> #3052: pingback_ping() function displays wrong content in pingback-display in some occurances -------------------------------------------------------+-------------------- Reporter: webrocker | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 2.2 Component: XML-RPC | Version: 2.0.4 Severity: normal | Resolution: Keywords: pingback|xmlrpc.php|has patch|2nd opinion | -------------------------------------------------------+-------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/3052#comment:9> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 23:03:21 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Dec 1 00:02:37 2006 Subject: [wp-trac] Re: [WordPress Trac] #3050: Quicktag - IMG - add title attribute In-Reply-To: <066.aa5de76da77824f42fc92bd34eef296c@lists.automattic.com> References: <066.aa5de76da77824f42fc92bd34eef296c@lists.automattic.com> Message-ID: <075.478c204b449cc06b59a7c90339530899@lists.automattic.com> #3050: Quicktag - IMG - add title attribute ------------------------------------------------+--------------------------- Reporter: nuclearmoose | Owner: anonymous Type: enhancement | Status: closed Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.1 Severity: trivial | Resolution: wontfix Keywords: quicktag attribute title has-patch | ------------------------------------------------+--------------------------- Changes (by matt): * status: new => closed * resolution: => wontfix Comment: Actually I don't think this is needed in the quicktags. -- Ticket URL: <http://trac.wordpress.org/ticket/3050#comment:4> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 23:03:44 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Dec 1 00:02:40 2006 Subject: [wp-trac] Re: [WordPress Trac] #3037: Styles & Code ( Make it beauty ) In-Reply-To: <066.143b2ef30f6447b16cc2cea0c3eb33c7@lists.automattic.com> References: <066.143b2ef30f6447b16cc2cea0c3eb33c7@lists.automattic.com> Message-ID: <075.4e949939c33bc10edddf23e8a3d80634@lists.automattic.com> #3037: Styles & Code ( Make it beauty ) ----------------------------+----------------------------------------------- Reporter: Xmion | Owner: bryanveloso Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: Administration | Version: 2.1 Severity: normal | Resolution: wontfix Keywords: Styles & Code | ----------------------------+----------------------------------------------- Changes (by matt): * status: new => closed * resolution: => wontfix -- Ticket URL: <http://trac.wordpress.org/ticket/3037#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 23:28:14 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Dec 1 00:18:57 2006 Subject: [wp-trac] Re: [WordPress Trac] #3035: wpautop breaks object tags In-Reply-To: <066.c6bdd1e638e7b0c86be10f5cb5812d0a@lists.automattic.com> References: <066.c6bdd1e638e7b0c86be10f5cb5812d0a@lists.automattic.com> Message-ID: <075.133aaf2ee471e1ae38dc572b1ab97d41@lists.automattic.com> #3035: wpautop breaks object tags ---------------------------------------------------+------------------------ Reporter: bwooster47 | Owner: anonymous Type: defect | Status: closed Priority: normal | Milestone: 2.1 Component: General | Version: 2.0.4 Severity: normal | Resolution: fixed Keywords: wpautop breaks object embed has-patch | ---------------------------------------------------+------------------------ Changes (by matt): * status: new => closed * resolution: => fixed Comment: This seems to work fine in trunk. -- Ticket URL: <http://trac.wordpress.org/ticket/3035#comment:6> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software From wp-trac at lists.automattic.com Thu Nov 30 23:02:54 2006 From: wp-trac at lists.automattic.com (WordPress Trac) Date: Fri Dec 1 00:31:36 2006 Subject: [wp-trac] Re: [WordPress Trac] #3050: Quicktag - IMG - add title attribute In-Reply-To: <066.aa5de76da77824f42fc92bd34eef296c@lists.automattic.com> References: <066.aa5de76da77824f42fc92bd34eef296c@lists.automattic.com> Message-ID: <075.f28ef70866cca4a294ca8508bb801502@lists.automattic.com> #3050: Quicktag - IMG - add title attribute ------------------------------------------------+--------------------------- Reporter: nuclearmoose | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 2.2 Component: Administration | Version: 2.1 Severity: trivial | Resolution: Keywords: quicktag attribute title has-patch | ------------------------------------------------+--------------------------- Changes (by matt): * milestone: 2.1 => 2.2 -- Ticket URL: <http://trac.wordpress.org/ticket/3050#comment:3> WordPress Trac <http://trac.wordpress.org/> WordPress blogging software