[wp-hackers] Proposal: StackOverflow for WordPress
Pixel Insert
studio at pixert.com
Fri May 14 03:04:47 UTC 2010
bbPress 1.1 is to be released soon. Also, for those who missed it,
bbPress website looks better now http://bbpress.org/
>> I like the new bbPress website. I can't wait for new bbPress updates. I'm
hoping for more integration between WordPress and bbPress in the future
>> Can anyone explain differences between Stack Overflow and WP Questions?
It looks similar to me.
On Thu, May 13, 2010 at 3:00 PM, <wp-hackers-request at lists.automattic.com>wrote:
> Send wp-hackers mailing list submissions to
> wp-hackers at lists.automattic.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.automattic.com/mailman/listinfo/wp-hackers
> or, via email, send a message with subject or body 'help' to
> wp-hackers-request at lists.automattic.com
>
> You can reach the person managing the list at
> wp-hackers-owner at lists.automattic.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of wp-hackers digest..."
>
>
> Today's Topics:
>
> 1. Re: ordering by a custom field (Brian Fidler)
> 2. Important changes to post type and taxonomy registration
> (Andrew Nacin)
> 3. Shortcodes getting wrapped with a "p" tag by rich editor
> (Ezwan Aizat Bin Abdullah Faiz)
> 4. Re: Shortcodes getting wrapped with a "p" tag by rich editor
> (Thomas Belknap)
> 5. Re: Proposal: StackOverflow for WordPress (Calvin Freitas)
> 6. Re: Proposal: StackOverflow for WordPress (Stas Su?cov)
> 7. Re: Proposal: StackOverflow for WordPress (Doug Stewart)
> 8. Bugs caused by adding a second rich editor to the add/edit
> posts screen (Matthew Gerring)
> 9. Re: Proposal: StackOverflow for WordPress (Michael E. Hancock)
> 10. Re: Bugs caused by adding a second rich editor to the
> add/edit posts screen (scribu)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 13 May 2010 07:06:44 -0700
> From: Brian Fidler <fidler.brian at gmail.com>
> Subject: Re: [wp-hackers] ordering by a custom field
> To: wp-hackers at lists.automattic.com
> Message-ID:
> <AANLkTinURxf4r_Wn-MClqJl0uUYCkqCQ-6vZ5URukhyp at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Thanks Mike, I may have some questions on how to implement it.
>
> On Wed, May 12, 2010 at 10:39 PM, Mike Schinkel <
> mikeschinkel at newclarity.net
> > wrote:
>
> > On May 13, 2010, at 12:22 AM, Brian Fidler wrote:
> > >
> > > - I have a second custom field in my posts that allows me to set
> > > display_order. Instead of ending my query with ORDER BY
> > > wp_posts.post_title ASC, I'd like to order by the custom field
> > > "display_order"
> >
> > What will your custom field's value be? The name of a field in the posts
> > table, or something else? If the former, I assume there's a finite set
> of
> > options which you would test against (otherwise you might end up having a
> > SQL injection vulnerability?)
> >
> > > and secondly, is there a simpler way to run this query using wpdb
> class?
> >
> > What about it do you want to be simpler? AFAICT NextGen doesn't give
> you
> > hooks into their queries so you'll have to do it with SQL.
> >
> > Anyway, here's a standalone file you can put in your root and I think it
> > should give you want you want, minus the display order I haven't
> implemented
> > yet. Let me know if this is what you are looking for?
> >
> > http://wordpress.pastebin.com/79QDM7Ng
> >
> > HTH.
> >
> > -Mike
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 13 May 2010 11:53:57 -0400
> From: Andrew Nacin <wp at andrewnacin.com>
> Subject: [wp-hackers] Important changes to post type and taxonomy
> registration
> To: wp-testers <wp-testers at lists.automattic.com>,
> wp-hackers at lists.automattic.com
> Message-ID:
> <AANLkTil6M8NOmcId4h_B2phRVYp1CB0gc2T9ku3OmDJp at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Testers and hackers,
>
> We've made two important changes to how you register post types and
> taxonomies. We've introduced two new arrays into the arguments you would
> normally pass during registration: 'labels', and 'capabilities'.
>
> More or less, label and singular_label is not enough for i18n purposes, so
> we now generate a dozen or so labels based off the post type that can be
> used throughout core, and any plugin can choose to register their own
> translations for their own custom post types. (This also will apply to
> taxonomies.) It isn't fully implemented yet, but it's close. We may
> eliminate singular_label entirely, since that was introduced earlier in the
> 3.0 cycle.
>
> Second, we've moved the fine-grained capabilities controls for custom post
> types and taxonomies into a capabilities array. Thus, if you were using
> manage_cap, assign_cap, edit_type_cap, etc -- all of those are gone, moved
> under a cap object. ($post_type_object->cap->edit_posts.) Please take note.
>
> I've also chronicled this in more detail (and arguably more confusing
> fashion) at http://wpdevel.wordpress.com/?p=814. That post also references
> the tickets where this was implemented, so you can look at the code if you
> have any questions, or ping any of the committers etc.
>
> Thanks,
> Nacin
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 14 May 2010 00:05:07 +0800
> From: Ezwan Aizat Bin Abdullah Faiz <aizat.faiz at gmail.com>
> Subject: [wp-hackers] Shortcodes getting wrapped with a "p" tag by
> rich editor
> To: wp-hackers at lists.automattic.com
> Message-ID:
> <AANLkTiku3pFWcgWLlkFECFvlF17Z1LS2Qt0ZPjHEq7DG at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Holas,
>
> I've written up a trac ticket #13288 (
> http://core.trac.wordpress.org/ticket/13288 ), and have yet to a see a
> response of any kind.
>
> Was wondering what is the procedure to get this looked at.
>
> Trac ticket description, reproduced here:
>
> This bug appeared when trying to hunt down a bug with the TinyMCE Advanced
> (
> > http://wordpress.org/extend/plugins/tinymce-advanced/ ) plugin where
> > extra spaces were being added (
> http://wordpress.org/support/topic/350867), and was related to the
> WordPress code.
>
>
> > It appears that shortcodes are wrapped with a "p" tag, before being sent
> to
> > the rich editor.
>
>
> > This patch removes the "p" tag, by calling shortcode_unautop.
>
>
> Regards,
> Aizat
>
> --
> http://aizatto.com
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 13 May 2010 12:17:05 -0400
> From: Thomas Belknap <dragonfly at dragonflyeye.net>
> Subject: Re: [wp-hackers] Shortcodes getting wrapped with a "p" tag by
> rich editor
> To: wp-hackers at lists.automattic.com
> Message-ID:
> <AANLkTikdRPyqCmzSrsz9Awsco1-nbe36iDRz2K_USfAb at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I think I've always used the HTML editor. Thought that was the way it was
> supposed to work?
>
> On May 13, 2010 12:05 PM, "Ezwan Aizat Bin Abdullah Faiz" <
> aizat.faiz at gmail.com> wrote:
>
> Holas,
>
> I've written up a trac ticket #13288 (
> http://core.trac.wordpress.org/ticket/13288 ), and have yet to a see a
> response of any kind.
>
> Was wondering what is the procedure to get this looked at.
>
> Trac ticket description, reproduced here:
>
> This bug appeared when trying to hunt down a bug with the TinyMCE Advanced
> (
> > http://wordpress.org/extend/plugins/tinymce-advanced/ ) plugin where
> > extra spaces were being added (
> http://wordpress.org/support/topic/350867),
> and was related to the WordPress code.
>
>
> > It appears that shortcodes are wrapped with a "p" tag, before being sent
> to
> > the rich editor.
>
>
> > This patch removes the "p" tag, by calling shortcode_unautop.
>
>
> Regards,
> Aizat
>
> --
> http://aizatto.com
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 13 May 2010 10:05:37 -0700
> From: Calvin Freitas <cal at calvinf.com>
> Subject: Re: [wp-hackers] Proposal: StackOverflow for WordPress
> To: wp-hackers at lists.automattic.com
> Message-ID:
> <AANLkTil-ILGstowUjMNQcp0QdchEsFBQAuHEROR2yuAO at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> It'd be great to have all the same tools and features available to run on a
> site powered by bbPress, but from what I've seen those tools aren't there.
> When was the last time bbPress had any kind of update?
>
> - Cal
>
>
> On Wed, May 12, 2010 at 4:52 PM, Christopher O'Connell <
> jwriteclub at gmail.com
> > wrote:
>
> > I'm going to add +1 to this whole concept.
> >
> > ~ Christopher
> >
>
>
> ------------------------------
>
> Message: 6
> Date: Thu, 13 May 2010 20:22:52 +0300
> From: Stas Su?cov <stas at nerd.ro>
> Subject: Re: [wp-hackers] Proposal: StackOverflow for WordPress
> To: wp-hackers at lists.automattic.com
> Message-ID: <1273771372.14542.17.camel at rivalry>
> Content-Type: text/plain; charset="UTF-8"
>
> ?n data de Jo, 13-05-2010 la 10:05 -0700, Calvin Freitas a scris:
> > It'd be great to have all the same tools and features available to run on
> a
> > site powered by bbPress, but from what I've seen those tools aren't
> there.
> > When was the last time bbPress had any kind of update?
>
> bbPress 1.1 is to be released soon. Also, for those who missed it,
> bbPress website looks better now http://bbpress.org/
>
> There are also plans to rewrite it as a new WordPress 3.0 plugin using
> exclusively the api for custom post types and taxonomy. This was
> discussed recently on #bbpress and #wordpress-gsoc.
>
> For those who missed the wcsf keynote, there are also plans to move the
> whole *press.org stuff to BuddyPress so I believe bbPress still has the
> chance to get better (much better).
>
> Jane is right, there's no reason to move all the data to somebody's else
> yard, at least without trying to fix something by ourselves.
>
> --
> () Campania Panglicii ?n ASCII
> /\ http://www.asciiribbon.org/
>
>
>
> ------------------------------
>
> Message: 7
> Date: Thu, 13 May 2010 14:45:38 -0400
> From: Doug Stewart <zamoose at gmail.com>
> Subject: Re: [wp-hackers] Proposal: StackOverflow for WordPress
> To: wp-hackers at lists.automattic.com
> Message-ID:
> <AANLkTin2NgiNt_rQ_8DZthWmA9N-0mPHUz43Mctl3yQn at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On 5/13/10, Stas Su?cov <stas at nerd.ro> wrote:
> > Jane is right, there's no reason to move all the data to somebody's else
> > yard, at least without trying to fix something by ourselves.
>
> I would cede your point if it were simply data we were talking about.
> What SO, et al., offer is /curation/ of that data.
>
> At this point, I think the distinction is roughly this: The DotOrg
> forums are fields of wildflowers, weeds and prairie grass, with little
> semblance of "here's where you go to find an answer to Question X" and
> harried "gardeners" (mods) scurrying about frantically stamping out
> "contributions" from folks intent on re-growing a patch of daisies
> while a perfectly fine bit is growing over the next rise.
> StackOverflow is a local topiary.
>
> Both may very well contain the same "plants", it's just an order of
> magnitude easier to find the bushes shaped like a Shared Host
> Recommendation in the topiary.
>
> --
> -Doug
> @zamoose
> http://literalbarrage.org/blog/
>
>
> ------------------------------
>
> Message: 8
> Date: Thu, 13 May 2010 12:21:40 -0700
> From: Matthew Gerring <mgerring at emrl.com>
> Subject: [wp-hackers] Bugs caused by adding a second rich editor to
> the add/edit posts screen
> To: wp-hackers at lists.automattic.com
> Message-ID: <429CE6F8-49E0-4EF0-A872-EC32C3FB02BC at emrl.com>
> Content-Type: text/plain; charset=us-ascii
>
> Hello all.
>
> I wrote a simple addition to a theme that adds a meta box in the add/edit
> posts screen. It allows you to use the rich editor to edit content that
> shows up in the sidebar.
>
> The problem is that the dialogs for some buttons now appear inside the text
> area for this second rich editor. For instance, clicking the "add link"
> button on the regular rich editor causes the Add Link dialog to appear in
> the second rich editor, underneath the grey overlay.
>
> Does anyone know why this is happening, or a way around it?
>
> -Matthew
>
> ------------------------------
>
> Message: 9
> Date: Thu, 13 May 2010 16:53:42 -0400
> From: "Michael E. Hancock" <justmichaelh at gmail.com>
> Subject: Re: [wp-hackers] Proposal: StackOverflow for WordPress
> To: <wp-hackers at lists.automattic.com>
> Message-ID: <025d01caf2de$60b72fc0$6401a8c0 at dell8600>
> Content-Type: text/plain; format=flowed; charset="UTF-8";
> reply-type=original
>
>
> ----- Original Message -----
> From: "Doug Stewart"
> > StackOverflow is a local topiary.
>
> I'd say it's planting season. Seems there's enough +1's from this list to
> get that growing. If you don't want to use the Forums, then ignore it. If
> you want your own, then start plowing.
>
> May your harvest be plentiful.
>
> MichaelH
>
>
>
>
>
>
> ------------------------------
>
> Message: 10
> Date: Fri, 14 May 2010 01:00:45 +0300
> From: scribu <scribu at gmail.com>
> Subject: Re: [wp-hackers] Bugs caused by adding a second rich editor
> to the add/edit posts screen
> To: wp-hackers at lists.automattic.com
> Message-ID:
> <AANLkTiluFrb-SdH2L-6SDWGT45W22SUa02xLG0Zlx1X6 at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> See this trac ticket:
>
> http://core.trac.wordpress.org/ticket/11862
>
>
> On Thu, May 13, 2010 at 10:21 PM, Matthew Gerring <mgerring at emrl.com>
> wrote:
>
> > Hello all.
> >
> > I wrote a simple addition to a theme that adds a meta box in the add/edit
> > posts screen. It allows you to use the rich editor to edit content that
> > shows up in the sidebar.
> >
> > The problem is that the dialogs for some buttons now appear inside the
> text
> > area for this second rich editor. For instance, clicking the "add link"
> > button on the regular rich editor causes the Add Link dialog to appear in
> > the second rich editor, underneath the grey overlay.
> >
> > Does anyone know why this is happening, or a way around it?
> >
>
>
> --
> http://scribu.net
>
>
> ------------------------------
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>
>
> End of wp-hackers Digest, Vol 64, Issue 33
> ******************************************
>
More information about the wp-hackers
mailing list