Should there be a MySite for Drupal 6
| Project: | MySite |
| Version: | HEAD |
| Component: | Miscellaneous |
| Category: | task |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
So, just after I answered another question about the future of the module, I got more deeply involved in the discussion here: What are the future plans for integration of Panels and MySite modules?.
To quote myself:
For Drupal 6, it looks like Panels is the next step towards some unified data API tools that we need. Trying to compete with that momentum doesn't really advance what I'm trying to accomplish.
So, I'm thinking that the best route for MySite in Drupal 6 is as follows:
-- Replace the MySite API (the backend data structure) with Panels.
-- Work on porting Panels -- particularly in making richer data available.
-- Work on Panels Profiles (if needed) -- perhaps by integrating the MySite Icons module.
-- If needed, create a MySite module that fills the gaps that other modules leave behind.
-- Create an update process that lets MySite 5.x users seamlessly upgrade to the new version of whatever the tool is.
Now's the time, MySite users. What do you think we should do for Drupal 6?

#1
I am still evaluation mode (was testing 3.0 Beta). There is certainly some overlap betwwen panels and mysite. But the overlap is not big enough to completely discontinue mysite.
-- Replace the MySite API (the backend data structure) with Panels.
Does this mean making mysite content available to panels? And all mysite plugins to work inside panel?
If yes then that would be the right thing to do.
#2
-- Replace the MySite API (the backend data structure) with Panels.
Means the use the Panels APIs in place of the MySite APIs. It would have the effect of making all mySite content available to Panels and vice versa.
#3
One smart thing you did for mysite is to provide support for gadgets. That opened up the whole new world of non-drupal centric components (gadgets) content. I would vote for that feature be made available as well with panels (panels supporting gadgets)
#4
That is the plan. The idea is to merge the feature sets of the two on the backend -- allowing content, themes, layouts, and styles to be defined through a single API. Then we'd layer different function "front-end" solutions on top.
#5
A newbie to Drupal and just saw mysite and am very impressed with it. Installed Drupal 6, so cannot use panels or mysite, but wishing that I could. After seeing mysite and reading about it, it seems amazing.
#6
Hello. I saw the test of mysite for d6. Bright future for the mysite. Any clue on the current status of it? I would love to give a hand in the rapid development of it.
#7
@kankan
You could start writing patches against HEAD. I'm thinking about doing a straight port before diving into Panels integration.
Problem is, jQuery Interface will need to be replaced by jQuery UI.
#8
I confess my knowledge of PHP coding is less than my knowledge of Latin. All I know in Latin is "Carpe' Dium" and I don't even think I spelled that right but I vote for MySite in Drupal 6. I started with Drupal 5.1 I think and have recently upgraded to D6 without looking to see if the modules I had installed under D5 were D6 compatible. I was disappointed to find that there wasn't a MySite for D6. I even tried to kluge it in as they say but the Drupal developers have taken steps to protect us from ourselves and not allow that. I suppose that's for the best but some of us like to take risks.
*grins*
Especially if there's something we really like and I like MySite!
I tried to read the thread explaining the various reasons and discussions regarding the pros and cons of integrating MySite and Panels but alas since I am not a coder of PHP, js or SQL I didn't get much out of it. I haven't used Panels so I can't say much there except that it seems like, judging from the discussion, that integrating the two into one module might take longer than getting MySite and Panels D6 compatible individually and, well, I'm really anxious to have MySite available on D6.
Thanks for the opportunity to toss my opinion out there.
#9
I am developing a site in Drupal 5.7 for which I would love to use MySite, but have been holding off using it for production until I know if I'll be able to upgrade to Drupal 6.x and still use it. I think using Panels as the back end would be brilliant, but a straight-up port would be great, as well, especially if one could start with the regular port and then switch over to using Panels as the back end.
#10
The problem with the port is that all the JQuery parts need to be rewritten -- and that is not a trivial task. This seems like a big waste to me, since Panels will provide that library.
The plan is to provide an upgrade path from MySite 5.x to Panels [name of module] 6.x.
#11
Just curious which features of Jquery? If it is just drag and drop, it may not be that critical to users. If it degrades gracefully without javascript, I am wondering is jquery part is that important. In other words if 6.x post is available some users may be ok without jquery fancy stuff.
#12
Subscribing
#13
Well, without the jQuery elements, the 4.x version got almost no usage. It is the drag-and-drop that makes the module attractive to most users.
#14
subscribing
#15
subscribing
#16
http://drupal.org/project/jquery_ui could also be an option for the JS stuff.
#17
Yup, hooray!
#18
subscribing
Hi,
first of all: i'm a noobie in Drupal.
When i've read the description yesterday, i was really amazed about the possibilities of this plugin.
I'm using jquery already in a different CMS but i looked hard for the functions the plugin have.
I would really appreciate, if MySite can be rewritten for using it in Drupal 6! or Drupal 7 ;)
#19
Although integration of modules with similar functionality is a great idea, I found no mentioning of plans to adapt panels 2 to D6. Am I right?
#20
Once Panels 2 is stable, it will be ported.
See http://drupal.org/node/223994
#21
subscribing
#22
+subscribing
We really need MySite functionality in 6.0, and might end up having to port the existing 5.x version on our own if nothing is produced by the community by the time we get to developing this part of the website...
#23
Get it out ASAP (like last week :P). My company is becoming more and more dependent on mysite in many of our large sites, and while i understand it's still under development, having a version that worked with drupal 6 at this current moment would make many mysite fans say - hurray! =D
#24
@darius123, Not trying to be a preacher here. But if your company is dependent on mysite for large sites, why not submit patches to make it move faster towards 6.x? Or create a bountry for attracting more developers?
#25
^not my call really, I'm just an eager fan cheering this module on! ^^
#26
I smply don't have time right now, and have been patiently waiting for Panels 2 to hit D6.
If you want to talk about professional upgrades, send a note using the contact form at http://www.palantir.net