Multi-site support?

I don't have experience maintaining a module for a multi-site install; just maintaining the install. Since any *tables* needed by the module should get created when the module is installed, the biggest problem is data that might be initialized at that time or later (such as user preferences). In the case we've been working with (issue #281600) it seems that the data isn't there for a user created in another site that shares the user table but not the subscriptions table (since the content tables aren't shared) so it would be best to initialize this data when it's detected that the info is missing.

Modules themselves shouldn't have to do anything other than use the proper Drupal calls for files and databases to "support" multisite. There are specific multi-site modules such as Domain Access that need specific support.

Any sort of funky database sharing / prefixing / etc. is essentially unsupported and will be custom for your particular implementation.

If you want more support, a helper module that interacts with Subscriptions would be the right way to handle it.

For me, only the user_ table is shared. Everything else is separate, cron, modules, etc.

"Do you run cron separately for each multi-site? If yes, you need a {subscriptions_queue} table per multi-site."

Yes, of course. Each site has its own subscriptions tables, and it works dandily.

The only problem I've encountered is {subscriptions_user}. If creation as needed is easy, then please implement it. Drupal AFAIK doesn't reuse uids even after the user has been deleted, so there would be no conflicts with future users. It wouldn't be clean, but the only people affected would be multi-site users, and it's an easy choice between that or having subscriptions not working at all. Maybe do a cleanup of dangling records on cron run?

@Boris

Modules themselves shouldn't have to do anything other than use the proper Drupal calls for files and databases to "support" multisite.

That's not true. Some modules have unnecessarily twisted logic that make them multisite unfriendly. Subscriptions already mostly works. And if creation as needed will easily fix the problem, then why not?

I apologize for my presumption in reopening the issue, but I want to use this module very very much. :)

Works fine, I don't see the error any more and in testing subscriptions are sent correctly.

Thank you so much!

Yes, I created a new user to test this, and I haven't encountered any problems.