Last updated by agentrickard on Sun, 2007-09-02 14:28
Note: this is a Wiki page. If you make a change, please annotate it.
Current Release: 5.x.2 series
The 5.x.2 series is stable and in bugfix mode. No new features will be added unless they are glaring holes in the user experience.
The plugin system should allow extension of the module without new core features being added.
The 5-2 branch forked on 02-SEP-2007 so we can begin would on multi-page features for 5.x.3.
5.x.3 Release?
There are a number of interesting feature requests that could be part of a 5.x.3 release. Here's the overview.
Pages -- the ability to add entire pages (whether current content like Blog posts) or entirely new content pages. Would include some limited HTML/CSS design options. Multi-tabs for content (http://drupal.org/node/145423) is part of this request. See notes at http://drupal.org/node/145423
Access control -- the ability to restrict access to MySite items at the block level.
MySite OG -- integration with Organic Groups. There are several requests for this functionality, which would likely live in a submodule. References:
Content locking -- allow the administrator to force content into each user's collection that cannot be removed. http://drupal.org/node/152917 -- Added to 5.x.2.6 release!
Default content restore -- http://drupal.org/node/153560 -- Added to 5.x.2.6 release.
I think that Pages and Access control can be handled by sub-modules (like the MySite Icons module), with some simple checks in the core module.
Content locking and default restore have gone into MySite core.
OG integration would require some fundamental changes to the module structure (see http://drupal.org/node/91420#comment-149710). The rest of the functionality would go in a separate module set.
At this point, I think 5.x.3 will include pages and a change to the storage system to allow OG-style group definitions. What that means is that the {mysite} table, which used UID as the primary key, will split to a multi-key, with OID being an arbitrary 'owner id' and 'owner_key' being the UID or GID and 'owner_type' being 'user' or 'group' or some other identifier. This will allow the definition of MySite pages that belong to different types of users.
Panels integration
Added by agentrickard on 13-Jul-2007. Ref: http://groups.drupal.org/node/5047
Some Panels integration ideas.
- Allow site admin to select Panels layouts or MySite layouts for content display. (Or merge the two.)
- Create translation API for MySite content (defined by http://therickards.com/api/function/mysite_type_hook_data/MySite) to be displayed by Panels. (Perhaps a mysite.inc file for Panels.)
- Enable panels to be converted into Droplets.
- Create a Component style callback method for pulling content defined by MySite into a block, view, node, etc. A function like
mysite_element($type, $type_id, $format = 'default', $settings = array())would work pretty well. Might need to pass a $uid or $user object as well.
MySite 6.x
See http://groups.drupal.org/node/4983
I'm committed to upgrading the module to Drupal 6. Likely after DrupalCon Barcelona in September. It is also possible that this upgrade will cause some API changes in MySite. Most of my development efforts in the last half of 2007 will go towards improving the API and porting to D6.