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, [email protected] wrote: > Send wp-testers mailing list submissions to > [email protected] > > 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 > [email protected] > > You can reach the person managing the list at > [email protected] > > 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 <[email protected]> > Subject: Re: [wp-testers] wp-testers Digest, Vol 68, Issue 5 > To: [email protected] > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > l tried that and it worked. Thants Jenni Jenni Jenni Jenni. > > Mark Beihoffer > Dragonfly Networks > [email protected] > [email protected] > (612)508-5128 > > > On Thu, Oct 21, 2010 at 7:00 AM, > <[email protected]>wrote: > >> Send wp-testers mailing list submissions to >> [email protected] >> >> 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 >> [email protected] >> >> You can reach the person managing the list at >> [email protected] >> >> 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" <[email protected]> >> Subject: [wp-testers] php and word press problems >> To: <[email protected]> >> Message-ID: <2f2863d6f386428c92a68c12cfea4...@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 <[email protected]<johnbillion%[email protected]> >>> >> Subject: Re: [wp-testers] php and word press problems >> To: [email protected] >> Message-ID: >> <[email protected]> >> 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 <[email protected]> >> 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 >>> [email protected] >>> http://lists.automattic.com/mailman/listinfo/wp-testers >>> >> >> >> ------------------------------ >> >> Message: 3 >> Date: Thu, 21 Oct 2010 12:08:46 +0100 >> From: Andrew Macaulay-Brook <[email protected]> >> Subject: [wp-testers] Custom post type capabilities not fully set up >> on registration >> To: [email protected] >> Message-ID: <[email protected]> >> 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:[email protected] ? http://www.theburo.net/ >> >> >> >> ------------------------------ >> >> Message: 4 >> Date: Thu, 21 Oct 2010 07:29:13 -0400 >> From: Andrew Nacin <[email protected]> >> Subject: Re: [wp-testers] Custom post type capabilities not fully set >> up on registration >> To: [email protected] >> Message-ID: >> >> <[email protected]<aanlktincxxjucdok-pw%[email protected]> >>> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> On Thu, Oct 21, 2010 at 7:08 AM, Andrew Macaulay-Brook <[email protected] >>> 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 <[email protected]> >> Subject: Re: [wp-testers] Custom post type capabilities not fully set >> up on registration >> To: [email protected] >> Message-ID: <[email protected]> >> 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 <[email protected] >>> 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 >>> [email protected] >>> http://lists.automattic.com/mailman/listinfo/wp-testers >> >> Andrew Macaulay-Brook, BEng MBCS CITP, trading as theburo.net >> mailto:[email protected] ? http://www.theburo.net/ >> >> >> >> ------------------------------ >> >> _______________________________________________ >> wp-testers mailing list >> [email protected] >> 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 <[email protected]> > Subject: [wp-testers] Mark Beihoffer has invited you to open a Google > mail account > To: [email protected] > Message-ID: > <[email protected]> > 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 <[email protected]> > Subject: Re: [wp-testers] Mark Beihoffer has invited you to open a > Google mail account > To: [email protected] > Message-ID: <[email protected]> > 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 <[email protected]> > Subject: Re: [wp-testers] Custom post type capabilities not fully set > up on registration > To: [email protected] > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=windows-1252 > > On Thu, Oct 21, 2010 at 7:44 AM, Andrew Macaulay-Brook > <[email protected]>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 > [email protected] > http://lists.automattic.com/mailman/listinfo/wp-testers > > > End of wp-testers Digest, Vol 68, Issue 6 > ***************************************** _______________________________________________ wp-testers mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-testers
