Users add nodes

Right. It might be possible to let users create droplets, but there are security issues. Users would never be allowed to add their own JavaScript or PHP to their page. That's just asking for security trouble.

As for adding individual nodes, the new Comment plugin lets users track the comments attached to specific nodes.

On the first request, I think we need another plugin which would search for nodes by type and by author. That wouldn't be too hard. The system doesn't do that now because "static" personal content wasn't rally in the original design.

On the second, MySite uses the input filter system for both Droplets and content. That is, if you display a node that is "Full HTML," MySite will render that as expected. Access to filters is set by role under Admin > Input Formats.

So the second issues is really handled already. What you want is the first option. I think that is doable. Look at the new Comment plugin for an example of how to search all nodes. The real problem is the UI challenge of searching by user.

Would it be enough to be able to search for one's own nodes? That would be simple to implement.

Yup. That will require a new plugin, though you might be able to tack something on to mysite_type_node_block_node().

No, it has to be a plugin, because we have to tell the _options and _data hooks how to handle the content.

I would call this 'post.inc' and write it to accept NID as the $type_id.

I'm incapable of complete answers today.

Items 1, 3, and 4 on your list are currently supports.

Items 2 & 5 require new and separate plugin handlers. I'd call them 'author' and 'post', respectively.

#2 is tricky and would require the use of the {mysite_content} table because you will effectively have a multi-key. $type = 'author' and $type_id = 'UID-nodetype'.

See http://therickards.com/api/function/mysite_get_myid/MySite for the logic and droplet.inc for an implementation.

Related: I was already thinking of writing a 'commenter' plugin that will track all comments by user.

Well, the function is complicated because what you are trying to do -- search data across two variables instead of one -- is complicated. But the implementation is rather trivial.

Take a look at /contrib/refine.inc for example. The function mysite_type_refine_block creates a new entry into {mysite_content} every time someone browses to a page with the path /taxonomy/term/x+y+z.

Filing against HEAD. I'd like to see someone take a stab at writing this.

I'd like to see someone other than me write that. That one is very simple. Look at comment.inc for the structure.

I haven't had a chance to test this. I think the "active" check is too complex for what you need.

For right now, change hook_active to:

/**
* Implements mysite_type_hook_active().
*/
function mysite_type_anode_active($type) {
return array($type => TRUE, 'message' => NULL)
}

The first problem is actually in mysite_type_anode(). Set

'include' => 'anode',

You had it as 'node'.

I'd like to revise this file and include it in the release. Please rename the file 'post' and change the functions accordingly. You also need to indent the file according to Drupal's coding standards.

Try this version. Your code got us about 70% done. I cleaned it a little and did a quick test.

Still a few text string issues to resolve, but it should work.

That last entry was not helpful. It works fine on my test machine (see attached). Be sure you use the attachment from http://drupal.org/files/issues/post.txt, not your original.

The 'could not find title' error is coming from a separate source. In my test case, it comes from blog posts without an author.

Note new issue: http://drupal.org/node/167364

Not the contrib folder. /plugins/types. The contrib folder is a distribution folder. See the README.

That was an oversight. This code is still under testing. New version fixes that problem. There may be more, so please report them.

Answers.

1) Tracking this bug here: http://drupal.org/node/167364. Think I fixed it but have not uploaded the new code.

2) I don't know. Probably, but I have been reluctant to tamper with that, since it is a core feature. There is a My Site tab on the profile page, currently.

3) Blog.inc is the perfect example for what you want, since it is by content type and by user. Clone it, change all the _blog_ function names and all the 'type' = 'blog' calls to use your new type.

I never saw the use-case for extending this to other node types, so I wrote the generic node.inc instead. While I would prefer to have a generic "add posts of type X by user Y" plugin, simply creating a new nodetype plugin will do. The weblinks.inc in the contrib folder is another example of this.

Why don't you just use the provided Profile plugin?

And no, I can't answer this one right now. Plus it complicates this issue (even more).

On Drupal.org, we try to keep threads to one issue at a time. In this case, either open a new Support request, or go post in the MySite group.

http://groups.drupal.org/mysite

The "post" plugin has been rolled into 5.x.2.7. It allows users to add individual posts to a MySite collection.