[wp-testers] wp-testers Digest, Vol 68, Issue 6
Administrator
rontekadmin at hawaiisportsrap.com
Sun Oct 24 22:30:59 UTC 2010
First this has been submitted when 3.0.1 was still a beta. It was ignored.
Second, you should understand that when a beta is constructed, you still
using most the core code that exists in the release version. By reporting
that a bug exists in the release, you alert the developers that they are
carrying a bug into the beta which may reproduce the same undesirable
results or worse. When it comes to the core editting functions of the word
processor, one would think that a developer would at least take the time to
acknowledge the problem so that it CAN be corrected in the upcoming
beta-later to be the update. I'm not a developer per se so I don't write
code. I do understand the code and can recommend how it should be fixed.
I'm already seeing development that doesn't understand the differences
necessary in PHP version usage as related to Apache server software
versions. Earlier versions of Apache like 1.333 won't react proply with
PHP5 and cause errors. I also know sloppy code when I see it.
I have worked for one of the top developers of broadcast software for radio
and television. The only time a developer seems to reply on a given bug is
when they get insulted. So go back and take a look at yourselves. Idiot
may be a bit harsh but it got your attention didn't it? I'm aware that
you'll probably ignore the problem because you're insulted but that's
childish. If you really develop for the love and not the money then, take
pride in your work and produce functions that actually work as described.
----- Original Message -----
From: "Bill Nickerson" <bill at wcnickerson.ca>
To: <wp-testers at lists.automattic.com>
Sent: Sunday, October 24, 2010 11:47 AM
Subject: Re: [wp-testers] wp-testers Digest, Vol 68, Issue 6
> If you were a real R&D tester then you'd understand the difference
> between beta and release. You're reporting an error in the release
> version of the code to the beta tester's mailing list. Why not submit a
> trouble ticket in the appropriate place and turn down the name calling.
> WP is open source, so maybe you could fix it and submit the fix instead
> of trashing all of those who are working to provide this code for us to
> use at no cost.
>
> On 24/10/2010 3:29 PM, Administrator wrote:
>> You code junkies are always claiming this isn't for support. You can
>> call it anything you want but you don't really use it for that. You
>> use these for supporting each others sloppy code and any little pet
>> addition that meets your fancy. Those who actually TEST the software
>> and report problems and are ingnored. Si I've got a really good
>> idea. Why don't you guys make a wp-developers mailing list. Maybe
>> those that picked up on the WordPress software will actually put
>> together a group for REAL testing of your software. I have been a
>> real R&D tester with a 6 figure salary, so I know what I'm talking about.
>> Quickly about the Internal Server Error. It most probably has to do
>> with using fast graphics on a server. Older version of Apache like
>> 1.333 are still in use with major hosting sites. Using fast graphics
>> with this slopped together code from wordpress will quite often cause
>> 500 errors by causing the server to time out on you. Also you may
>> want to read the install instructions regarding 3.01 if upgrading from
>> as opposed to installing fresh.
>> Hope that helps. The rest of you idiots that are responsible for the
>> code for the core editor have really screwed it up. You put an
>> automatic save in the software that is NOT configurable. That
>> shouldn't be uncontrollable because it interferes with other
>> processes. The proportional redisplay of media has been totally
>> broken and been reported and ignored. Fix that stuff why don't cha.
>>
>> ---- Original Message ----- From: "Matthew Mascioni"
>> <kingmattm at gmail.com>
>> To: <wp-testers at lists.automattic.com>
>> Cc: <wp-testers at lists.automattic.com>
>> Sent: Saturday, October 23, 2010 10:28 AM
>> Subject: Re: [wp-testers] wp-testers Digest, Vol 68, Issue 6
>>
>>
>>> 500 Internal Server error when installing WordPress 3.0.1 on my
>>> server, suggest look into it.
>>>
>>> Best Regards,
>>> Matthew Mascioni
>>> Founder/CEO of App Inquirer
>>> http://appinquirer.com
>>>
>>>
>>> On 2010-10-23, at 8:00 AM, wp-testers-request at lists.automattic.com
>>> wrote:
>>>
>>>> Send wp-testers mailing list submissions to
>>>> wp-testers at lists.automattic.com
>>>>
>>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>> http://lists.automattic.com/mailman/listinfo/wp-testers
>>>> or, via email, send a message with subject or body 'help' to
>>>> wp-testers-request at lists.automattic.com
>>>>
>>>> You can reach the person managing the list at
>>>> wp-testers-owner at lists.automattic.com
>>>>
>>>> When replying, please edit your Subject line so it is more specific
>>>> than "Re: Contents of wp-testers digest..."
>>>>
>>>>
>>>> Today's Topics:
>>>>
>>>> 1. Re: wp-testers Digest, Vol 68, Issue 5 (Mark Beihoffer)
>>>> 2. Mark Beihoffer has invited you to open a Google mail account
>>>> (Mark Beihoffer)
>>>> 3. Re: Mark Beihoffer has invited you to open a Google mail
>>>> account (Rich Pedley)
>>>> 4. Re: Custom post type capabilities not fully set up on
>>>> registration (Andrew Nacin)
>>>>
>>>>
>>>> ----------------------------------------------------------------------
>>>>
>>>> Message: 1
>>>> Date: Fri, 22 Oct 2010 07:12:49 -0500
>>>> From: Mark Beihoffer <mbeihoffer at gmail.com>
>>>> Subject: Re: [wp-testers] wp-testers Digest, Vol 68, Issue 5
>>>> To: wp-testers at lists.automattic.com
>>>> Message-ID:
>>>> <AANLkTinH_eD2io6kT7W=f8Yd7t1zSJTBgvuBaB637m6T at mail.gmail.com>
>>>> Content-Type: text/plain; charset=UTF-8
>>>>
>>>> l tried that and it worked. Thants Jenni Jenni Jenni Jenni.
>>>>
>>>> Mark Beihoffer
>>>> Dragonfly Networks
>>>> mbeihoffer at gmail.com
>>>> mark at dragonfly-networks.com
>>>> (612)508-5128
>>>>
>>>>
>>>> On Thu, Oct 21, 2010 at 7:00 AM,
>>>> <wp-testers-request at lists.automattic.com>wrote:
>>>>
>>>>> Send wp-testers mailing list submissions to
>>>>> wp-testers at lists.automattic.com
>>>>>
>>>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>>> http://lists.automattic.com/mailman/listinfo/wp-testers
>>>>> or, via email, send a message with subject or body 'help' to
>>>>> wp-testers-request at lists.automattic.com
>>>>>
>>>>> You can reach the person managing the list at
>>>>> wp-testers-owner at lists.automattic.com
>>>>>
>>>>> When replying, please edit your Subject line so it is more specific
>>>>> than "Re: Contents of wp-testers digest..."
>>>>>
>>>>>
>>>>> Today's Topics:
>>>>>
>>>>> 1. php and word press problems (Marvin Hunkin)
>>>>> 2. Re: php and word press problems (John Blackbourn)
>>>>> 3. Custom post type capabilities not fully set up on
>>>>> registration (Andrew Macaulay-Brook)
>>>>> 4. Re: Custom post type capabilities not fully set up on
>>>>> registration (Andrew Nacin)
>>>>> 5. Re: Custom post type capabilities not fully set up on
>>>>> registration (Andrew Macaulay-Brook)
>>>>>
>>>>>
>>>>> ----------------------------------------------------------------------
>>>>>
>>>>> Message: 1
>>>>> Date: Thu, 21 Oct 2010 10:45:50 +1100
>>>>> From: "Marvin Hunkin" <startrekcafe at gmail.com>
>>>>> Subject: [wp-testers] php and word press problems
>>>>> To: <wp-testers at lists.automattic.com>
>>>>> Message-ID: <2F2863D6F386428C92A68C12CFEA4592 at marvinPC>
>>>>> Content-Type: text/plain; charset="iso-8859-1"
>>>>>
>>>>> ?hi.
>>>>> the person who sent me the code to turn on php.
>>>>> cold they resend the code to me and the process to get it to
>>>>> work.as lost
>>>>> it
>>>>> .
>>>>> thank you.
>>>>> marvin from australia.
>>>>>
>>>>> ------------------------------
>>>>>
>>>>> Message: 2
>>>>> Date: Thu, 21 Oct 2010 04:19:09 +0100
>>>>> From: John Blackbourn
>>>>> <johnbillion+wp at gmail.com<johnbillion%2Bwp at gmail.com>
>>>>>>
>>>>> Subject: Re: [wp-testers] php and word press problems
>>>>> To: wp-testers at lists.automattic.com
>>>>> Message-ID:
>>>>> <AANLkTim3BrunjP91K_nUxKR-A1vsxO55FEaiaBpbas9M at mail.gmail.com>
>>>>> Content-Type: text/plain; charset=ISO-8859-1
>>>>>
>>>>> Marvin, the wp-hackers mailing list isn't for support; it's for
>>>>> discussion on WordPress hacking and core development of the platform.
>>>>>
>>>>> The information you want is freely available on the web. Try Googling
>>>>> for any phrase like "how to turn on php" and you'll get hundreds of
>>>>> thousands of results.
>>>>>
>>>>> Also, if you're struggling with setting up PHP you might be better off
>>>>> going with a cheap shared host. There are some recommendations here:
>>>>> http://wordpress.org/hosting/ .
>>>>>
>>>>> John
>>>>>
>>>>> On Thu, Oct 21, 2010 at 12:45 AM, Marvin Hunkin
>>>>> <startrekcafe at gmail.com>
>>>>> wrote:
>>>>>> ?hi.
>>>>>> the person who sent me the code to turn on php.
>>>>>> cold they resend the code to me and the process to get it to
>>>>>> work.aslost it
>>>>>> ?.
>>>>>> thank you.
>>>>>> marvin from australia.
>>>>>> _______________________________________________
>>>>>> wp-testers mailing list
>>>>>> wp-testers at lists.automattic.com
>>>>>> http://lists.automattic.com/mailman/listinfo/wp-testers
>>>>>>
>>>>>
>>>>>
>>>>> ------------------------------
>>>>>
>>>>> Message: 3
>>>>> Date: Thu, 21 Oct 2010 12:08:46 +0100
>>>>> From: Andrew Macaulay-Brook <am at theburo.net>
>>>>> Subject: [wp-testers] Custom post type capabilities not fully set up
>>>>> on registration
>>>>> To: wp-testers at lists.automattic.com
>>>>> Message-ID: <9EF30455-B202-40AE-9C19-8AC80DDF0DD5 at theburo.net>
>>>>> Content-Type: text/plain; charset=windows-1252
>>>>>
>>>>> I can't work out whether this is covered by
>>>>> http://core.trac.wordpress.org/ticket/14122 or not.
>>>>>
>>>>> I'm using a custom post type called property, assigning
>>>>> capabilities using
>>>>> 'capability_type' => 'property' and then giving my Editors
>>>>> *_property and
>>>>> *_propertys capabilities wherever I can see they already have
>>>>> *_post or
>>>>> *_posts.
>>>>>
>>>>> The rationale for all this is that it lets me turn off all the
>>>>> capabilities
>>>>> for blog Posts, hiding the Posts menu for Editors, as this site
>>>>> doesn't use
>>>>> the blog. I then give my client an Editor level login.
>>>>>
>>>>> I'm mapping meta-capabilities using Justin Tadlock's code at
>>>>> http://justintadlock.com/archives/2010/07/10/meta-capabilities-for-custom-post-types
>>>>>
>>>>>
>>>>> Problem: Neither my clients, nor the Admin login can Trash custom
>>>>> posts.
>>>>>
>>>>> It seems that using the argument 'capability_type' => 'property'
>>>>> only sets
>>>>> up the following mappings in the post type object:
>>>>>
>>>>> <!-- Capability mapping: stdClass Object
>>>>> (
>>>>> [edit_post] => edit_property
>>>>> [edit_posts] => edit_propertys
>>>>> [edit_others_posts] => edit_others_propertys
>>>>> [publish_posts] => publish_propertys
>>>>> [read_post] => read_property
>>>>> [read_private_posts] => read_private_propertys
>>>>> [delete_post] => delete_property
>>>>> )
>>>>> -->
>>>>>
>>>>> ... which I generated using $post_type = get_post_type_object(
>>>>> $post->post_type ); print_r($post_type->cap);
>>>>>
>>>>> It looks like the mappings for $post_type->cap->delete_posts and
>>>>> $post_type->cap->delete_others_posts aren't being set up.
>>>>>
>>>>> I've got an issue with taxonomy capabilities too, but that's my
>>>>> next job.
>>>>>
>>>>> Andrew Macaulay-Brook, BEng MBCS CITP, trading as theburo.net
>>>>> mailto:am at theburo.net ? http://www.theburo.net/
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------
>>>>>
>>>>> Message: 4
>>>>> Date: Thu, 21 Oct 2010 07:29:13 -0400
>>>>> From: Andrew Nacin <wp at andrewnacin.com>
>>>>> Subject: Re: [wp-testers] Custom post type capabilities not fully set
>>>>> up on registration
>>>>> To: wp-testers at lists.automattic.com
>>>>> Message-ID:
>>>>>
>>>>> <AANLkTincxXJuCdoK-Pw+vENv7pD_9wr4we-KXr42T7VE at mail.gmail.com<AANLkTincxXJuCdoK-Pw%2BvENv7pD_9wr4we-KXr42T7VE at mail.gmail.com>
>>>>>
>>>>>>
>>>>> Content-Type: text/plain; charset=ISO-8859-1
>>>>>
>>>>> On Thu, Oct 21, 2010 at 7:08 AM, Andrew Macaulay-Brook <am at theburo.net
>>>>>> wrote:
>>>>>
>>>>>> I can't work out whether this is covered by
>>>>>> http://core.trac.wordpress.org/ticket/14122 or not.
>>>>>>
>>>>>> I'm using a custom post type called property, assigning capabilities
>>>>> using
>>>>>> 'capability_type' => 'property' and then giving my Editors
>>>>>> *_property and
>>>>>> *_propertys capabilities wherever I can see they already have
>>>>>> *_post or
>>>>>> *_posts.
>>>>>>
>>>>>> The rationale for all this is that it lets me turn off all the
>>>>> capabilities
>>>>>> for blog Posts, hiding the Posts menu for Editors, as this site
>>>>>> doesn't
>>>>> use
>>>>>> the blog. I then give my client an Editor level login.
>>>>>>
>>>>>> I'm mapping meta-capabilities using Justin Tadlock's code at
>>>>>>
>>>>> http://justintadlock.com/archives/2010/07/10/meta-capabilities-for-custom-post-types
>>>>>
>>>>>>
>>>>>> Problem: Neither my clients, nor the Admin login can Trash custom
>>>>>> posts.
>>>>>>
>>>>>> It seems that using the argument 'capability_type' => 'property' only
>>>>> sets
>>>>>> up the following mappings in the post type object:
>>>>>>
>>>>>> <!-- Capability mapping: stdClass Object
>>>>>> (
>>>>>> [edit_post] => edit_property
>>>>>> [edit_posts] => edit_propertys
>>>>>> [edit_others_posts] => edit_others_propertys
>>>>>> [publish_posts] => publish_propertys
>>>>>> [read_post] => read_property
>>>>>> [read_private_posts] => read_private_propertys
>>>>>> [delete_post] => delete_property
>>>>>> )
>>>>>> -->
>>>>>>
>>>>>> ... which I generated using $post_type = get_post_type_object(
>>>>>> $post->post_type ); print_r($post_type->cap);
>>>>>>
>>>>>> It looks like the mappings for $post_type->cap->delete_posts and
>>>>>> $post_type->cap->delete_others_posts aren't being set up.
>>>>>>
>>>>>
>>>>> This is indeed the same ticket at issue.
>>>>>
>>>>> If you read Justin's post again, you'll see that he deliberately
>>>>> sets up
>>>>> those additional capabilities by overloading what gets passed to the
>>>>> capabilities array.
>>>>>
>>>>> I haven't yet got around to committing my meta capabilities patch
>>>>> for 3.1
>>>>> yet, basically because after a few attempts I don't think I've
>>>>> quite nailed
>>>>> it yet.
>>>>>
>>>>> But what you'll see is when map_meta_cap is true (a new flag for
>>>>> register_post_type), then these additional capabilities will need
>>>>> to be set
>>>>> up, or WordPress will do it for you, based on capability_type.
>>>>>
>>>>> Hope that makes sense.
>>>>>
>>>>> Nacin
>>>>>
>>>>>
>>>>> ------------------------------
>>>>>
>>>>> Message: 5
>>>>> Date: Thu, 21 Oct 2010 12:44:49 +0100
>>>>> From: Andrew Macaulay-Brook <am at theburo.net>
>>>>> Subject: Re: [wp-testers] Custom post type capabilities not fully set
>>>>> up on registration
>>>>> To: wp-testers at lists.automattic.com
>>>>> Message-ID: <E6B61DE2-70AC-4FC7-AA3A-319F8A7E11D3 at theburo.net>
>>>>> Content-Type: text/plain; charset=windows-1252
>>>>>
>>>>> Thanks Andrew - depends on how literally you read Justin's post I
>>>>> guess. I
>>>>> read "I?ve also added in a couple of extra capabilities that were
>>>>> not shown
>>>>> in my previous tutorial on post types: delete_posts and
>>>>> delete_others_posts." and didn't mentally add "because WordPress
>>>>> doesn't do
>>>>> it." :-)
>>>>>
>>>>> I'll use the overloading instead of being lazy and look out for the
>>>>> patch -
>>>>> is it looking definite for 3.1?
>>>>>
>>>>> A.
>>>>>
>>>>> On 21 Oct 2010, at 12:29, Andrew Nacin wrote:
>>>>>
>>>>>> On Thu, Oct 21, 2010 at 7:08 AM, Andrew Macaulay-Brook
>>>>>> <am at theburo.net
>>>>>> wrote:
>>>>>>
>>>>>>> I can't work out whether this is covered by
>>>>>>> http://core.trac.wordpress.org/ticket/14122 or not.
>>>>>>>
>>>>>>> I'm using a custom post type called property, assigning capabilities
>>>>> using
>>>>>>> 'capability_type' => 'property' and then giving my Editors
>>>>>>> *_property
>>>>> and
>>>>>>> *_propertys capabilities wherever I can see they already have
>>>>>>> *_post or
>>>>>>> *_posts.
>>>>>>>
>>>>>>> The rationale for all this is that it lets me turn off all the
>>>>> capabilities
>>>>>>> for blog Posts, hiding the Posts menu for Editors, as this site
>>>>>>> doesn't
>>>>> use
>>>>>>> the blog. I then give my client an Editor level login.
>>>>>>>
>>>>>>> I'm mapping meta-capabilities using Justin Tadlock's code at
>>>>>>>
>>>>> http://justintadlock.com/archives/2010/07/10/meta-capabilities-for-custom-post-types
>>>>>
>>>>>>>
>>>>>>> Problem: Neither my clients, nor the Admin login can Trash custom
>>>>>>> posts.
>>>>>>>
>>>>>>> It seems that using the argument 'capability_type' => 'property'
>>>>>>> only
>>>>> sets
>>>>>>> up the following mappings in the post type object:
>>>>>>>
>>>>>>> <!-- Capability mapping: stdClass Object
>>>>>>> (
>>>>>>> [edit_post] => edit_property
>>>>>>> [edit_posts] => edit_propertys
>>>>>>> [edit_others_posts] => edit_others_propertys
>>>>>>> [publish_posts] => publish_propertys
>>>>>>> [read_post] => read_property
>>>>>>> [read_private_posts] => read_private_propertys
>>>>>>> [delete_post] => delete_property
>>>>>>> )
>>>>>>> -->
>>>>>>>
>>>>>>> ... which I generated using $post_type = get_post_type_object(
>>>>>>> $post->post_type ); print_r($post_type->cap);
>>>>>>>
>>>>>>> It looks like the mappings for $post_type->cap->delete_posts and
>>>>>>> $post_type->cap->delete_others_posts aren't being set up.
>>>>>>>
>>>>>>
>>>>>> This is indeed the same ticket at issue.
>>>>>>
>>>>>> If you read Justin's post again, you'll see that he deliberately
>>>>>> sets up
>>>>>> those additional capabilities by overloading what gets passed to the
>>>>>> capabilities array.
>>>>>>
>>>>>> I haven't yet got around to committing my meta capabilities patch
>>>>>> for 3.1
>>>>>> yet, basically because after a few attempts I don't think I've quite
>>>>> nailed
>>>>>> it yet.
>>>>>>
>>>>>> But what you'll see is when map_meta_cap is true (a new flag for
>>>>>> register_post_type), then these additional capabilities will need
>>>>>> to be
>>>>> set
>>>>>> up, or WordPress will do it for you, based on capability_type.
>>>>>>
>>>>>> Hope that makes sense.
>>>>>>
>>>>>> Nacin
>>>>>> _______________________________________________
>>>>>> wp-testers mailing list
>>>>>> wp-testers at lists.automattic.com
>>>>>> http://lists.automattic.com/mailman/listinfo/wp-testers
>>>>>
>>>>> Andrew Macaulay-Brook, BEng MBCS CITP, trading as theburo.net
>>>>> mailto:am at theburo.net ? http://www.theburo.net/
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------
>>>>>
>>>>> _______________________________________________
>>>>> wp-testers mailing list
>>>>> wp-testers at lists.automattic.com
>>>>> http://lists.automattic.com/mailman/listinfo/wp-testers
>>>>>
>>>>>
>>>>> End of wp-testers Digest, Vol 68, Issue 5
>>>>> *****************************************
>>>>>
>>>>
>>>>
>>>> ------------------------------
>>>>
>>>> Message: 2
>>>> Date: Fri, 22 Oct 2010 07:57:58 -0500
>>>> From: Mark Beihoffer <mbeihoffer at gmail.com>
>>>> Subject: [wp-testers] Mark Beihoffer has invited you to open a Google
>>>> mail account
>>>> To: wp-testers at lists.automattic.com
>>>> Message-ID:
>>>> <AANLkTi=9X-NU9tmRObBz0APdubPJOAVC=m-Ok=ZtC4CS at mail.gmail.com>
>>>> Content-Type: text/plain; charset=UTF-8
>>>>
>>>> I've been using Gmail and thought you might like to try it out.
>>>> Here's an
>>>> invitation to create an account.
>>>>
>>>>
>>>> You're Invited to Gmail!
>>>>
>>>> Mark Beihoffer has invited you to open a Gmail account.
>>>>
>>>> Gmail is Google's free email service, built on the idea that email
>>>> can be
>>>> intuitive, efficient, and fun. Gmail has:
>>>>
>>>> *Less spam*
>>>> Keep unwanted messages out of your inbox with Google's innovative
>>>> technology.
>>>>
>>>> *Lots of space*
>>>> Enough storage so that you'll never have to delete another message.
>>>>
>>>> *Built-in chat*
>>>> Text or video chat with Mark Beihoffer and other friends in real time.
>>>>
>>>> *Mobile access*
>>>> Get your email anywhere with Gmail on your mobile phone.
>>>>
>>>> You can even import your contacts and email from Yahoo!, Hotmail,
>>>> AOL, or
>>>> any other web mail or POP accounts.
>>>>
>>>> Once you create your account, Mark Beihoffer will be notified of
>>>> your new
>>>> Gmail address so you can stay in touch. Learn
>>>> more<http://mail.google.com/mail/help/intl/en/about.html>or get
>>>> started<http://mail.google.com/mail/a-273fae0330-d2c0d5bcec-wZxYlk-EFZypE67MHnxHLWmT-mY>
>>>>
>>>> !
>>>> Sign
>>>> up<http://mail.google.com/mail/a-273fae0330-d2c0d5bcec-wZxYlk-EFZypE67MHnxHLWmT-mY>
>>>>
>>>> Google Inc. | 1600 Ampitheatre Parkway | Mountain View, California
>>>> 94043
>>>>
>>>>
>>>> ------------------------------
>>>>
>>>> Message: 3
>>>> Date: Fri, 22 Oct 2010 15:19:55 +0100
>>>> From: Rich Pedley <elfin at elfden.co.uk>
>>>> Subject: Re: [wp-testers] Mark Beihoffer has invited you to open a
>>>> Google mail account
>>>> To: wp-testers at lists.automattic.com
>>>> Message-ID: <4CC19D8B.4000208 at elfden.co.uk>
>>>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>>>
>>>> On 22/10/2010 13:57, Mark Beihoffer wrote:
>>>>> I've been using Gmail and thought you might like to try it out.
>>>>> Here's an
>>>>> invitation to create an account.
>>>>>
>>>>>
>>>>> You're Invited to Gmail!
>>>>>
>>>>> Mark Beihoffer has invited you to open a Gmail account.
>>>>>
>>>>> Gmail is Google's free email service, built on the idea that email
>>>>> can be
>>>>> intuitive, efficient, and fun. Gmail has:
>>>>>
>>>>> *Less spam*
>>>>> Keep unwanted messages out of your inbox with Google's innovative
>>>>> technology.
>>>>
>>>> oh the irony.
>>>>
>>>> Rich
>>>>
>>>>
>>>> ------------------------------
>>>>
>>>> Message: 4
>>>> Date: Fri, 22 Oct 2010 15:50:21 -0400
>>>> From: Andrew Nacin <wp at andrewnacin.com>
>>>> Subject: Re: [wp-testers] Custom post type capabilities not fully set
>>>> up on registration
>>>> To: wp-testers at lists.automattic.com
>>>> Message-ID:
>>>> <AANLkTimNG8J4swrFnhZ4rwmRg7kbJBjXHSQB=mwCZ5ji at mail.gmail.com>
>>>> Content-Type: text/plain; charset=windows-1252
>>>>
>>>> On Thu, Oct 21, 2010 at 7:44 AM, Andrew Macaulay-Brook
>>>> <am at theburo.net>wrote:
>>>>
>>>>> Thanks Andrew - depends on how literally you read Justin's post I
>>>>> guess. I
>>>>> read "I?ve also added in a couple of extra capabilities that were
>>>>> not shown
>>>>> in my previous tutorial on post types: delete_posts and
>>>>> delete_others_posts." and didn't mentally add "because WordPress
>>>>> doesn't do
>>>>> it." :-)
>>>>>
>>>>> I'll use the overloading instead of being lazy and look out for the
>>>>> patch -
>>>>> is it looking definite for 3.1?
>>>>
>>>>
>>>> Yes. This conversation got me looking at things again. Here's the
>>>> ticket:
>>>> http://core.trac.wordpress.org/ticket/14122. The first pass was
>>>> committed
>>>> yesterday, so you'll see this in 3.1. Please test it if you can to
>>>> find any
>>>> bugs or limitations.
>>>>
>>>>
>>>> ------------------------------
>>>>
>>>> _______________________________________________
>>>> wp-testers mailing list
>>>> wp-testers at lists.automattic.com
>>>> http://lists.automattic.com/mailman/listinfo/wp-testers
>>>>
>>>>
>>>> End of wp-testers Digest, Vol 68, Issue 6
>>>> *****************************************
>>> _______________________________________________
>>> wp-testers mailing list
>>> wp-testers at lists.automattic.com
>>> http://lists.automattic.com/mailman/listinfo/wp-testers
>>>
>>
>> _______________________________________________
>> wp-testers mailing list
>> wp-testers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-testers
>>
> _______________________________________________
> wp-testers mailing list
> wp-testers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-testers
>
More information about the wp-testers
mailing list