[wp-hackers] Structured Blogging - getting extra plugin hooks inserted in the WP code

[Phillip Pearson]

Steve,

The aforementioned Structured Blogging plugin is perhaps all you need to 
achieve what you're planning... it's relatively easy to define new 
microcontent types, so you could define an "artwork" type which includes 
the fields you want, then let our plugin handle the editing and display.

Bob Wyman of PubSub mentioned a very similar use case a month or two 
back: creating an 'artwork' microcontent type, giving that to artists, 
then aggregating all artwork posts published.  He'd presumably use 
pubsub.com to do the aggregation.

Take a look at the plugin - there's a preliminary version available here 
(or you can wait for 1.0pre8, coming Tuesday morning USA time):

    http://structuredblogging.org/structuredblogging-wp-1.0pre7.zip

Look in the wpsb-files/microcontent/descriptions directory.  Start by 
copying something like review-cafe.xml as artwork.xml, then change the 
fields by editing the <field .../> elements.  There are some docs up at 
structuredblogging.org - click on 'resources' on the top menu.

Cheers,
Phil :)

steve cooley wrote:

> I think i could benefit for this kind of functionality.  I want to  
> build a fine art announcement and patron management plugin.  I can  
> see 90% of what I want to do in wordpress (specifically announcing  
> new artwork availability via posts, tagging genre and media types by  
> categories, RSS, art venues as subscriber level members), and I'm  
> looking at similar issues.  I'd like to be able to enter in meta data  
> like number of prints in an edition, media size, links to additional  
> photos...  all structured kinds of posts, same meta data every time.   
> It seems like the easiest way is to create a custom post.php file  
> that would let me enter in these custom fields, but then I run into  
> the same problems.
>
> so, to put it shortly: "Me too, please"
>
> -Steve
>
> On Dec 12, 2005, at 5:39 PM, Phillip Pearson wrote:
>
>> Hi all,
>>
>>
>> The reason I'm writing here is that to change the editing interface  
>> this extensively, we had to step outside the plugin API.  We've  
>> copied post.php to sb-post-common.php and edit-form.php to sb-edit- 
>> form.php, made our changes in there, and used them when publishing  
>> the new post types.  This isn't much fun, as it means we need to  
>> track post.php and edit-form.php and release a new version whenever  
>> anything important happens.
>
>
> ...
>
>>
>> I've been over the code and I think what we'd need is:
>>
>> - the ability to change where post.php redirects to after a post is  
>> published.
>>
>> - do_action() calls before and after the edit form (or maybe just  
>> the 'description' field) is displayed - so we could use ob_start()  
>> and ob_end_clean() to cut out the edit form and display our own  form 
>> in its place.
>>
>> - the ability to change the 'Write Post' heading into something else.
>>
>> If we submit a patch to add plugin API hooks to do these things, is  
>> there a chance of having it considered for WP1.6?
>>
>> Cheers,
>> Phil :-)
>