Access MySite data from an external theme or block

I'd rather not have forked code running around if we can agree on the best implementation strategy for the core module.

Let's stop an take a look at the three elements of this request.

I cannot seem to embed the mysite info into other pages

I've been thinking about this request and it seems that one solution is to have a User settings tab for MySite. This tab would have three base options:

- Show link to MySite on user page
- Show MySite content on user page
- Do not show MySite content on user page

Implementing this feature would give you content within the user profile array, which could be themed as needed. In order to accomplish this, we'd have to change the code so that you would also be able to fire a request to a function and return the mysite page content.

I think it has a great opportunity to act as sort of a "control panel" page, with notifications of new messages, buddy requests, etc, along with mysite content.

Personally, I think integrating this into the User page as the 'control panel page' is a better idea. I don't think we should replace 'core' functionality with MySite.

But you could make MySite a 'control panel' by writing includes for the modules you want to integrate. The current API would support a BuddyList include, for example. You could define how you want to display Buddy messages as part of that include.

You shouldn't need to edit default.php to do this; you would simply define what 'content' means from these sources.

That being said, I need to be able to set all mysite pages to private, then take away the ability for users to change that setting.

That seems perfectly reasonable, and should be a core setting for the module. The admin would have three options:

- All MySites are public
- All MySites are private
- User may choose (and default setting is public / private)

This would also go into the User settings tab.

Is there a problem with waiting for a v5 release such that this must be addressed in 4.7?

How are you doing the profile dashboard now? It's very cool.

The point I want to stress is that adding the profile functionality should be done through a profile.inc file -- and should be supported by the current code framework.

If you add features by hacking default.php, that's not using the API and other people can't (really) use the code. If we wrote a profile.inc file, it could become part of the distribution. I haven't written one yet due to time and a lack of direction. Your demo shows a good possible direction.

Take a look in the contrib folder of the download for examples. But since profile is a core Drupal module, it would become part of the core MySite download.

If you attach the code you wrote for that profile box, I'll take a look and see how it could be integrated using the API.

Yeah, that's a very non-Drupal hack; especially the use of $GLOBALS to pull vars.

I'll spend some time between now and New Year's building support for this concept.

There is a quick way to hook content from mysite and make it available to external functions. I just need to track down the implications.

It involves a change to mysite_page().

function mysite_page($uid = NULL, $pageview = TRUE) {

....

    if ($pageview) {
      print theme('mysite_'. $mysite->layout . '_layout', $content);
      return;
    }
    else {
      return $content;
    }

If $pageview is false and we pass a $uid, then the $content blob for a MySite page will be returned.

This has some cascading effects on .po files, so I have not committed the code yet.

This has been corrected in 4.7.x-DEV, 5.x.1-DEV, and HEAD.

See http://drupal.org/cvs?commit=55240

I updated the README. You now have the option of sending a UID and a $pageview flag to the mysite_page() function.

 $content = mysite_page($user->uid, FALSE);

This will return a $content object ready for theming.

Note that you cannot guarantee that all MySite format and layout files have been loaded -- those load on a user specific basis.