<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.web.wordpress.devel">
    <title>gmane.comp.web.wordpress.devel</title>
    <link>http://blog.gmane.org/gmane.comp.web.wordpress.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47166"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47152"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47147"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47143"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47136"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47135"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47133"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47132"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47129"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47127"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47122"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47118"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47115"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47113"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47103"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47099"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47098"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47083"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47080"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47077"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47166">
    <title>Incorrect "last updated" date on plugin page</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47166</link>
    <description>&lt;pre&gt;The "last updated" date for one of my plugins is three months out:
http://wordpress.org/plugins/intercom-for-wordpress/

It should be 14th April when I uploaded v0.4, but it's showing the date
from the previous version.

Did I do something wrong when I made that last commit?

Can it be corrected somehow?

Thanks
Simon
&lt;/pre&gt;</description>
    <dc:creator>Simon Blackbourn</dc:creator>
    <dc:date>2013-05-23T22:33:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47152">
    <title>Escaping post meta values</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47152</link>
    <description>&lt;pre&gt;Hi wp-hackers,

What's the deal with post meta value escaping? I didn't see any mention of it in the documentation, but it seems important if you're ever going to store JSON data in the postmeta table (i.e., {"key":"value with \"quotes\" in the content."})

Reduced example:

$str1 = '\\"';
 
update_post_meta($post-&amp;gt;ID, "test", $str1);
$str2 = get_post_meta($post-&amp;gt;ID, "test", true);

echo "$str1&amp;lt;br&amp;gt;$str2";

/*
 
Result:
\"
"
 
*/

Thanks,
Dan
&lt;/pre&gt;</description>
    <dc:creator>Dan Phiffer</dc:creator>
    <dc:date>2013-05-22T15:46:46</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47147">
    <title>Custom Post Types Clean-Up</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47147</link>
    <description>&lt;pre&gt;Hey,

I might be missing something but I've been doing a lot of custom post_types recently and clean up seems to be a huge pain. Here's the deal:

I have a plugin that uses register_post_type in an init hook to do the initial setup of a post type (call it "custom").
Let's say for argument's sake I wanna focus on a page - http://mysite.com/custom/potato/.
I type that in before ever enabling the plugin and it's a 404.
I enable the plugin, play around with it, create a potato page.
Now http://mysite.com/custom/potato/ links to that page and all is good.
Now I disable the plugin.
I try http://mysite.com/custom/potato and now instead of a 404, I get the home page displayed while the url stays the same.
In fact, http://mysite.com/custom/[anything]/ will also result in the homepage being displayed without modifying the url.

Question: Is it just my setup and I should start disabling stuff or is that normal behavior? If it is, shouldn't we do something about it?

Thanks!
~Dobri
&lt;/pre&gt;</description>
    <dc:creator>Dobri</dc:creator>
    <dc:date>2013-05-20T20:55:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47143">
    <title>hyphens to differentiate database names for WP in mysql</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47143</link>
    <description>&lt;pre&gt;Folks,

I like to create my wordpress databases with hyphens such as wp-exetermusic
 and wp-mysite.  I have to escape them with backticks when creating them.

Is this a bad practice?
Might some plugins choke on this?
Are underscores or some other thing, better?

Thanks
&lt;/pre&gt;</description>
    <dc:creator>Bearcat Şándor</dc:creator>
    <dc:date>2013-05-20T18:34:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47136">
    <title>GSoC - Is it obvious?</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47136</link>
    <description>&lt;pre&gt;Hello hackers

I wanted to ask a question about GSoC 2013.
Is it obvious for selected students to receive mail or IRC or comment on
their proposal(on melange) ?? Asking about more information related to
their ideas.
Is there any way i can know if my proposal has been viewed or not ? [1]

Thank you
Happy selecting. !!

[1] Link to my proposal&amp;lt;https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/hardyy/1&amp;gt;

Best
Hard Patel
&lt;/pre&gt;</description>
    <dc:creator>Hard Patel</dc:creator>
    <dc:date>2013-05-19T13:28:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47135">
    <title>Enhanced Emails - GSoC '13</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47135</link>
    <description>&lt;pre&gt;Hi,

I have updated my Wordpress blog regarding GSoC (
http://gsoc13.wordpress.com/) . Update is regarding a plugin, which I have
added to the wordpress repository. My plugin is now public.

Its been quite some time since someone has commented on my proposal(on
melange). I have replied to the comments put, and have also regularly
updated my proposal on melange through my comments.

I hope that the developers community has been through my proposal on
melange and also though my blog. What should I be doing now?

Regards,
Pranjal Prabhash
&lt;/pre&gt;</description>
    <dc:creator>Pranjal Prabhash</dc:creator>
    <dc:date>2013-05-18T21:44:07</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47133">
    <title>Missing safety check in WP3.6</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47133</link>
    <description>&lt;pre&gt;Greetings,

I have been testing WP3.6 and have run into a problem. It seems a
safety check has been removed since wp3.5. In
wp-includes/js/media-editor.js, the add function used to simply return
the wp.media object of the object, if it existed already:

WP3.5:
add: function( id, options ) {
var workflow = this.get( id );

if ( workflow )
return workflow;

workflow = workflows[ id ] = wp.media( _.defaults( options || {}, {
frame:    'post',
state:    'insert',
title:    wp.media.view.l10n.addMedia,
multiple: true
} ) );

workflow.on( 'insert', function( selection ) { ...

WP3.6:
add: function( id, options ) {
var workflow = this.get( id );

workflow = workflows[ id ] = wp.media( _.defaults( options || {}, {
frame:    'post',
state:    'insert',
title:    wp.media.view.l10n.addMedia,
multiple: true
} ) );

workflow.on( 'insert', function( selection ) { ...

You used to be able to create the editor's add-media window and make
modifications to it, using
var dialog = wp.media.editor.add('content');
dialog.on('open', dosomething...
dialog.on(event, dosomethingelse...

This would work in 3.5, since all code calling "add" would get the
same object, creating it if it did not yet exist.
In 3.6, the same method seems to cause double-creation of the object,
which makes plupload fail when user tries to upload a file.
When that happens, it causes exception where $index is undefined, in
this section of media-views.js:
info: function() {
var queue = this.queue,
index = 0, active;

if ( ! queue.length )
return;

active = this.queue.find( function( attachment, i ) {
index = i;
return attachment.get('uploading');
});

this.$index.text( index + 1 );

Is this a bug in 3.6, or does code that interacts with the uploader
need to be rewritten, to check existence with get() before calling
add(), and wait for the initial add() call on admin pages, somehow? I
couldn't find any documentation on this issue.

Other than that, wp3.6 seems pretty stable, looking forward to release
day Monday.

Best regards,
Luke
&lt;/pre&gt;</description>
    <dc:creator>Luke Bryan</dc:creator>
    <dc:date>2013-05-17T18:56:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47132">
    <title>WordPress.org Stats API</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47132</link>
    <description>&lt;pre&gt;Is there a way to get a filter on http://api.wordpress.org/stats/php/1.0/ (like
`?wp=3.5`) to reduce the result to a particular version of WordPress? If
not, can that be added please?
(I'm requesting the API handle this; It'd also be nice, but not necessary,
to add it to http://wordpress.org/about/stats/ )

I think it'd be useful for plugin authors to see the PHP version breakdown
for a particular version (mainly, the latest WP version) rather then having
older versions (3.0-3.4) mixed in.
(Just for fun, it'd also be interesting to see which PHP versions beta
testers are using to test!)

Example Case: I'm making a plugin that will require at least WP 3.6 (It'll
be in the plugin header, and have a check), and would like to use PHP 5.4
(or at least 5.3). Since the plugin won't run on lower versions, the PHP
versions reported for those lower WP versions aren't useful for my inquiry.

Currently http://wordpress.org/about/stats/ shows 62.5% on PHP 5.2. I would
assume a correlation of older WP to older PHP. Only 33% of WP up to date on
3.5. I'd further assume that the percent of PHP 5.2 for WP 3.5 would be
lower then 62.5%. I just don't have the access to that data yet to confirm.
Please liberate the data for the sake of us poor curious developers! :-)

P.S I originally sent this yesterday, but evidently was having
email/internet issues. I've seen on twitter that Nacin talked about this
yesterday (coincidence). He said that the data isn't yet broken down that
way even internally, but also that the difference in PHP version by WP
version is negligible. Still, it'd be nice to see the data anyway (removing
doubt would help). Also note, this isn't an argument to get WP to abandon
5.2, it's to get more info to plugin/theme devs.
&lt;/pre&gt;</description>
    <dc:creator>Ken (WraithKenny</dc:creator>
    <dc:date>2013-05-17T17:18:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47129">
    <title>Admin Login Brute Force Attacks (Revisited)</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47129</link>
    <description>&lt;pre&gt;For performance[*], I would like to be able to reject any login attempt
where _POST['log'} begins with 'admin', and to do it at the earliest possible
moment, to minimize the load on my server.

Is login_form_login a reasonable place for this kind of check?  Or is there
an earlier hook that would cause less load on the server?

And what is the best way to "die" in this case - exit? die? redirect?


Thanks,
Bryan

[*] This is NOT intended as a security measure.  I have taken all necessary and
reasonable precautions to prevent someone from breaking in to any of the sites
I host.  I'm looking to mitigate the resource usage caused by bots trying to
log in as admin, or adminadmin, or administrator which is what I'm seeing and
have been seeing for the past few months.


&lt;/pre&gt;</description>
    <dc:creator>Bryan Spahr</dc:creator>
    <dc:date>2013-05-17T15:08:53</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47127">
    <title>Two wordpress sites but one wordpress DB</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47127</link>
    <description>&lt;pre&gt;I would like to explore the possibilities of a installing a new wordpress
installation which will be tapping into the same database as the first one.

The new site will obviously be identical in terms of content but I may
choose to install different plugins, use different themes on the second
one.

Of course, wp_options table will be my deal breaker here. but I'm sure
there are work arounds this matter.

So I searched the matter and found this post, but before I explore the
suggested route I wanted to check with you guys to see if this is the way
to go or not?

Thank you

Here is the suggestion.

&amp;lt;quote&amp;gt;

I've done this before, having 6 websites shoot out content from the same
database.

It's easy enough to do. Upload WP into both directories. Make sure they
have the identical wp-config.php file.

In the second sites directory do the following:
In the wp-settings.php file change the options database value to something
like this:

// Table names
$wpdb-&amp;gt;posts = $table_prefix . 'posts';
$wpdb-&amp;gt;users = $table_prefix . 'users';
$wpdb-&amp;gt;categories = $table_prefix . 'categories';
$wpdb-&amp;gt;post2cat = $table_prefix . 'post2cat';
$wpdb-&amp;gt;comments = $table_prefix . 'comments';
$wpdb-&amp;gt;links = $table_prefix . 'links';
$wpdb-&amp;gt;linkcategories = $table_prefix . 'linkcategories';
$wpdb-&amp;gt;options = 'YOURNEWPREFIX_options';
$wpdb-&amp;gt;postmeta = $table_prefix . 'postmeta';
$wpdb-&amp;gt;usermeta = $table_prefix . 'usermeta';

$wpdb-&amp;gt;prefix = $table_prefix;

See how I've removed $table_prefix . in the options line?
Instead of YOURNEWPREFIX put something like 'site2' or whatever you want.

Then, in PHPmyAdmin duplicate the wp_options table, and rename one of the
them to be YOURNEWPREFIX_options, so if you chose 'site2', it would be
'site2_options'.

Bingo. Edit the information in the 'site2_options' table to refelct the
correct information for your second site and you will be on your way.
&amp;lt;quote&amp;gt;
&lt;/pre&gt;</description>
    <dc:creator>Haluk Karamete</dc:creator>
    <dc:date>2013-05-16T20:31:33</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47122">
    <title>Regenerating re-writes upon migration</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47122</link>
    <description>&lt;pre&gt;Hi,

To answer my own question from yesterday...

If you're doing an online replacement (i.e. from within WordPress 
itself) of your own database from another webserver, and want to do a 
best-effort job of regenerating your (possibly non-existent) .htaccess 
file to take account of the possibly different permalink structure in 
the database being imported, then...

This is sufficient:
         global $wp_rewrite;
         $wp_rewrite-&amp;gt;init();
         flush_rewrite_rules(true);

Only other thing is that you'll need to hook the the pre_option_ filter 
for the options permalink_structure, rewrite_rules and page_on_front 
options in order to make sure that WordPress gets the data from your 
newly-migrated database instead of from cached settings.

David

&lt;/pre&gt;</description>
    <dc:creator>David Anderson</dc:creator>
    <dc:date>2013-05-15T12:13:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47118">
    <title>Quick rewrite question</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47118</link>
    <description>&lt;pre&gt;Another question about migrating data from one WordPress install into 
another. (Thanks for the previous answers about changing table prefixes).

Other than WordPress itself, plugins, themes, uploads and other things 
in WP_CONTENT_DIR, wp-config.php, and the database, the other major 
place where site configuration can live is in the webserver's configuration.

For the vast majority (but not always) of cases, it's in a .htaccess 
file (or a web.config file on IIS).

Looking into this, it looks rather like, after importing the files + 
database, a simple call to flush_rewrite_rules(true) (found in 
wp-includes/rewrite.php) is both a) harmless in general and b) all that 
needs doing in many (most?) cases - it will write out a working file for 
you, if it judges it needed + possible.

Is that right? Anything else I should think of? I realise that .htaccess 
files can be infinitely and arbitrarily complex, and that there is no 
programmatic way of transferring one from one site to another. My aim is 
1) to do the best job possible for as many users as possible 2) to not 
do anything destructive to any users at all.

Many thanks,
David

&lt;/pre&gt;</description>
    <dc:creator>David Anderson</dc:creator>
    <dc:date>2013-05-14T22:42:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47115">
    <title>Must Use plugin example?</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47115</link>
    <description>&lt;pre&gt;Howdy,

I'd like to learn how to write a solid Must Use plugin.

Just curious if anyone knows of an existing, simple, Must Use plugin
that I could use to learn from?

I'd like to see an example of a MU plugin that uses PHP5+ OOP/Class.
The simpler the example the better ... I'm mostly wanting to figure
out the template/pattern that I need to use.

Thanks!
M
&lt;/pre&gt;</description>
    <dc:creator>Micky Hulse</dc:creator>
    <dc:date>2013-05-14T20:49:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47113">
    <title>Can PHPdoc recognize custom filters?</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47113</link>
    <description>&lt;pre&gt;Is it possible to get PHPDoc to recognize WP filters declarations? I think
that one thing like

/**
 * &amp;lt; at &amp;gt;filter_name my_filter
 * &amp;lt; at &amp;gt;filter_param string $my_param
 * &amp;lt; at &amp;gt;filter_args int 2
 *
**/
$filtered = apply_filters("my_filter", $arg1, $arg2); // this is the first
time my filter appears in code

would make sense.
I don't know if it is possible (I've always used PHPDoc for standard code)
and I'd like to know if
anyone has an alternative.




Filippo Pisano
cel: 3291821355 / skype: filippopisano
&lt;/pre&gt;</description>
    <dc:creator>Filippo Pisano</dc:creator>
    <dc:date>2013-05-13T12:31:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47103">
    <title>WordPress Polyglots</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47103</link>
    <description>&lt;pre&gt;Is WP Polyglots being moderated?  Can someone point me in the direction 
of who I can talk to to take over one of the translation groups that 
seems has been dormant for quite a while and not responding to enquiries?

Should this go to regular forum?
&lt;/pre&gt;</description>
    <dc:creator>Melanie Dunford</dc:creator>
    <dc:date>2013-05-12T01:25:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47099">
    <title>Why do some user meta entries use the table prefix inthe meta key?</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47099</link>
    <description>&lt;pre&gt;
I've developed some code that imports a WordPress database, and allows a 
change of $table_prefix whilst you do so. i.e. If the site you're 
importing had a different table prefix, then you can change it as you 
import.

The running of the SQL import itself works fine - that's just some 
regexes before executing the SQL.

However, testing it out has revealed something I did not know before - 
that various entries in the usermeta table have meta_key entries that 
depend upon the table prefix. Essential example: if your prefix is wp_, 
then your user will have an entry wp_capabilities, which contains your 
capabilities.

So, those also need renaming - otherwise you can't even log in (because 
the entries being looked for aren't there).

Whilst researching, I came across this plugin: 
http://wordpress.org/extend/plugins/change-table-prefix/

It appears to know about this phenomena. It makes two adjustments:

i. (prefix)_user_roles in the options table
ii. Then all those beginning with (prefix) in the user meta table.

Questions:

1. Why does WordPress do this? On the face of it, it seems like a gross 
layering violation - table keys depend on the names of tables. But the 
WP core coders are smart guys, so there must be a reason.

2. Are there any others that anyone knows about? Any other hidden 
hazards to changing your table prefix?

Thank you!

David

&lt;/pre&gt;</description>
    <dc:creator>David Anderson</dc:creator>
    <dc:date>2013-05-11T20:51:30</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47098">
    <title>Custom Taxonomy and "Filter by Term" URL parameters</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47098</link>
    <description>&lt;pre&gt;Hi list,

I just started working on an issue that I encounter each time I use Custom
Taxonomies.

If you use Custom Taxonomies, it would be great if you could perform that
quick test, and tell me if you can replicate the bug, or if I'm
hallucinating...

Here are the steps:

In the admin interface, if we go into Posts &amp;gt; Categories, or Posts &amp;gt; Tags,
we see a table showing all our Categories/Tags. The right column of that
table shows the number of Posts for each Category/Tag. That number is
hyperlinked - when we follow it, we see a listing of all the Posts that
have that Category/Tag.

For Categories, the link is built like this:
wp-admin/edit.php?category_name=my_category_term

For Tags, it looks like this:
wp-admin/edit.php?tag=my_tag_term

Now, let's say you have a Custom Taxonomy, called "foo". Go to the page
that shows the overview of that taxonomy, which should be
/edit-tags.php?taxonomy=foo

Now, the critical part:
Let's say you have a taxonomy term named "bar". Let's imagine that the term
has been applied to 3 Posts. If you click that number/link, you will arrive
at /edit.php?foo=bar

Expected result:
You would expect to see a filtered list, showing only the Posts that have
the "bar" term assigned (in our example, 3 Posts).

Actual result (at least in my case):
The ?foo=bar parameter has no visible effect: it doesn't isolate the 3
Posts with the "bar" term. I see the complete list of Posts, without any
filtering - the same as visiting /edit.php

What works:
If I manually change the URL parameter to make it look like
this:wp-admin/edit.php?taxonomy=foo&amp;amp;term=bar then I get the expected
result: I see the list of 3 Posts.

I started investigating this and created a patch, but before I continue, I
want to make sure this *is* a bug, and not some wrong custom taxonomy
configuration on my side.

Trac user Knut Sparhell tells me that he cannot replicate the problem.

If you want to comment on Trac or add improved patches, it's here:
http://core.trac.wordpress.org/ticket/24317
&lt;/pre&gt;</description>
    <dc:creator>Manuel Schmalstieg</dc:creator>
    <dc:date>2013-05-11T19:30:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47083">
    <title>Reinvoke wordpress</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47083</link>
    <description>&lt;pre&gt;Hey guys,

I know this might be a weird question but I've got a weird client:

I have a multi-site installation. When a non-existing site slug is encountered, I reach the 404.php page and just before saying "nope, doesn't exist", I do some checks. If they work out, I would like to display some content from another site the same way it would have been displayed by wordpress if requested properly, going through all the templates and post_types and all of that fun stuff. So far, I have managed to detect if everything checks out and use switch_to_blog() to switch to the appropriate blog. Is it possible to reach my end goal with this? In essence, when I reach the 404 and I check and everything is in order, I want to reinvoke WordPress, just with a different request on a different site. Redirecting doesn't work since there is a mix of static files and wordpress sites and redirecting would link to the static files (precisely the reason I'm doing this). So… ideas?

~Dobri
&lt;/pre&gt;</description>
    <dc:creator>Dobri</dc:creator>
    <dc:date>2013-05-08T16:18:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47080">
    <title>WordPress plugin support forum oddity</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47080</link>
    <description>&lt;pre&gt;Not sure where to post this, so have opted for here in the hope that I can be pointed somewhere more relevant.

I've been trying to post a bug report to the support forum for:
http://wordpress.org/support/plugin/yahoo-weather-forecasts

However, the thread is being marked as "closed" before it's even been opened and seemingly cannot be seen by anyone but me:
http://wordpress.org/support/topic/reposting-bug-report-credit-not-defined?replies=0

On my profile page, the topic appears in my "Recent Replies" list, but not in my "Threads Started" list. And if I try and edit the topic, I get redirected to:
http://wordpress.org/support/

Most curious. Any help appreciated.

Cheers,

Christian
&lt;/pre&gt;</description>
    <dc:creator>Christian Wach</dc:creator>
    <dc:date>2013-05-08T11:02:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47077">
    <title>Version control (git) and uploads/blogs.dir folders?</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47077</link>
    <description>&lt;pre&gt;Quick question, but just curious if folks ignore the uploads/blogs.dir
folders when pushing/pulling to/from local/test/production
environments?

Specifically, as a WP developer, what bits (specific to WP) do you
include in your .gitignore?

I'm thinking I want to add something like:

uploads/*
blogs.dir/*

Thanks!
M
&lt;/pre&gt;</description>
    <dc:creator>Micky Hulse</dc:creator>
    <dc:date>2013-05-07T18:10:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.wordpress.devel/47075">
    <title>Review GSoC import/export plugin to JSON proposal</title>
    <link>http://comments.gmane.org/gmane.comp.web.wordpress.devel/47075</link>
    <description>&lt;pre&gt;Hello everyone,

I have updated my application, included link to few more bugs for which I
submitted patch today.
Please review it once again: http://panks.me/gsoc/

I would be modifying my implementation of export.php a little, in a day or
two, would update the proposal at my blog when that's done.

Thank you.

&lt;/pre&gt;</description>
    <dc:creator>Panks</dc:creator>
    <dc:date>2013-05-07T02:00:55</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.web.wordpress.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.web.wordpress.devel</link>
  </textinput>
</rdf:RDF>
