Daniel Carrera wrote:
Michel Morelli wrote:
- MIGRATION:
How can I transfer user accounts to the new sites?
copy table users
Thanks. That helps a lot. I can copy individual rows from the users table and that way I can move each user to their corresponding academy.
It's extra work, but what matters is that it's doable. Excellent.
How do you prevent users from one academy working with others data now? You could just copy the entire table and after a year, remove the ones from each site that haven't logged onto the site in that time.
I hope I can do something similar with the content. I guess I need to make a list of tables with content (e.g. node, node_revisions, etc).
Again, how do you filter the content for users now?
How can I transfer existing content?
Moving users and accounts to their respective sites seems quite difficult. I don't know what I can do there.
Hi, have you tried http://drupal.org/project/backup_migrate ?
Thanks. That could be useful.
And take a look at http://drupal.org/project/domain which could be a better solution for you.
- DRAWBACKS:
Are there any drawbacks I should know about?
I imagine that I would lose the ability to do an over-all search among all the sites. I can live with that. Maintenance would be more difficult because I'd have to create a new site every time we get a new school, but that seems manageable.
No no no. Multisite in drupal is maked with a subdirectory of sites/ path. One directory for one site.
Yeah, but I still have to run the installer, login as admin, and re-configure everything. Right? Or am I missing something?
Yes, and I think you don't want that. The more DB the greater the overhead. The Domain Access module I pointed you to above uses Drupal's Node Access system to determine which site get's what data.
*Click* Thanks! A lot of information there.
Yes, but don't get hung up on the dpkg-reconfigure thing. Automation is good but it can remove the thinking process. Manually creating the DB, the DB user and the sites directory can be check points.