Any thoughts on getting this to work across multiple sites?

It's easy with profile.module since it uses its own tables, but looks like it will be pretty messy with Bio.

Comments

jjeff’s picture

jjeff commented

Please describe how this is "easy" with profile.module. Is it doable without custom coding?

I'm not even sure what you are asking for here. You would like bio.module to store its data somewhere other than the node table? Then the bios would not be nodes, essentially defeating the entire purpose of this module.

If you are doing custom coding to solve this issue, you can use db_set_active() to select the database from the "central" site before loading the bios. You will need to set up a new db connector called 'central' in your settings.php, but your code would look something like this:

db_set_active('central');
$bio = node_load(bio_for_user($uid));
db_set_active('default');
eli’s picture

eli commented

Thanks for the reply. I'm in a tricky spot since I've got several sites on one database that share users/profiles, but not content (nodes).

It's easy to make it work with profile.module because profile stores all its data in its own tables. So I can just set the $db_prefix in settings.php so that all the sites point to the same profile tables and I'm done.

Yeah, I realized after I submitted this, that even if I could get it to work, it would probably defeat most of the usefulness of Bio. I've got some ideas on ways to actually share certain nodes between sites, but that's a task for another day. I think I'm gonna be stuck hacking profile.module for now.

I'll definitely take a look at db_set_active() though, I was not aware of that function.

Thanks again,
Eli

allie micka’s picture

allie micka
she/her
commented
Status: Active » Closed (won't fix)

I'm going to mark this as "won't fix", because, as you say, it's a pretty non-trivial undertaking. Since Bio nodes are, well, nodes, there's no teling what kind of fields, nodeapi activities, workflow, etc. might be involved in the loading and display of a node.

Perhaps this can be solved with a content sharing/deployment/feed/you-name-it module.

I imagine that this difficulty will be introduced by D7 as well, what with the lack of a compact profile_data table for database sharing.