I know that Drupal offers an option to share a user database in multisite situations. Is this also possible with the subscriptions for Simplenews? Same procedure? Do you know of sites that do the same?
Many thanks
TR
I know that Drupal offers an option to share a user database in multisite situations. Is this also possible with the subscriptions for Simplenews? Same procedure? Do you know of sites that do the same?
Many thanks
TR
Comments
Comment #1
theorichel commentedI have tried this and was not very successful: added this to the settings.php of the site that is NOT supposed to carry the subscriptions:
$db_prefix = '';
$db_prefix = array(
'default' => 'KLIMA_',
'users' => 'GRK_',
'sessions' => 'GRK_',
'role' => 'GRK_',
'authmap' => 'GRK_',
'sequences' => 'GRK_',
'profile_fields' => 'GRK_',
'profile_values' => 'GRK_',
'users_roles' => 'GRK_',
'simplenews_subscriptions' => 'GRK_'
);
where GRK is the prefix of the other domain in the multisite.
When I add an emailadresses at the site with the Klima-prefix and I confirm the subscription, it is still added to the Klima-site, not the GRK list as I hoped.
New RegisteredUsers do not display the problem: they are added to the GRK-prefixed table, so are shared.
Any ideas to solve this?
Thanks
TR
Comment #2
theorichel commentedI am a little hesitant with experimenting, but some browsing in PHPMyadmin gives me the idea that the SNID_TID_table might need to be shared to.
Am I right?
Thanks
Well after 5 minutes I thought that I had been hesitant long enough so I tried it, changing the SNID_TID prefix reference, and it effectively did the trick, the table of subscribers is shared!
Comment #3
sutharsan commentedsimplenews_subscriptions = who is subscribed + status of newsletter send-progress
simplenews_snid_tid = who is subscribed to which newsletter (taxonomy tag)
simplenews_newsletters = newsletter (node) settings
To share subsciptions you need to share the first two tables. It requires the taxonomy to be shared too.
Comment #4
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.