Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.RE: this discussion on SimpleNews and Domain Access (http://drupal.org/node/211261).
The newsletter issues are restricted by domain, and we can control where the Block displays of subscriptions go with the Domain_block module, so that's handy.
It would be nice if the Newsletter Subscription options were restricted by Domain, too, so that people in one state aren't invited to sign up for a newsletter from another state, and to reduce the number of newsletters presented to the user.
Any news on this topic?
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | noset-user_2968169_1.patch | 701 bytes | Gonzalo2683 |
| #8 | plein_8_simplenews_custom.zip | 3.38 KB | rolfmeijer |
Comments
Comment #1
agentrickardComment #2
uufsm CreditAttribution: uufsm commentedWill look into Domain Taxonomy and see if that helps.
Comment #3
davidshaw CreditAttribution: davidshaw commentedI think i've solved this by doing a domain table prefix on simplenews_snid_tid and Taxonomy - term_data.
Each domain then gets different newsletter options for subscriptions and those subscription ids are linked with Newsletter names (aka taxonomy terms) specific to that domain.
The downside of course is that other uses of taxonomy will not be available between domains...
Not used on a production install yet - so fingers crossed.
Dave Shaw
Tribe Rising
Comment #4
uufsm CreditAttribution: uufsm commentedSorry, I forgot to followup on this. The Domain Taxonomy module took care of this issue perfectly.
When creating a newsletter and on the simplenews subscription page, only newsletters that apply to that domain are visible. So, instead of subscribers having to sort through all the counties, they see only the state-wide newsletter and their county newsletter.
If I restricted the state-wide newsletter to only the state site, then that would stop county administrators from sending out anything on the state newsletter by accident (a good thing). However, that means that people would need to navigate to the state site to manage their subscriptions (an unlikely thing). So I've left the state-wide newsletter available on all counties, and the county administrators have been reminded to be careful.
Comment #5
designate CreditAttribution: designate commentedDomain Taxonomy works perfect indeed. I started with Domain Blocks which still showed all newsletters present upon subscribing. While installing Domain Taxonomy this problem was taken care off. One thing which needs to be fixed [in my opinion] is the sender's name which shows up in the confirmation email when subscribing [and maybe other types of mail or an actual sent newsletter as well]. The sender's name is the same for all newsletters/ domains. When I don't enter this name within the newsletter settings an emailaddress is shown which again is the same for all domains. Do you have this same issue or have you found a solution for it?
Comment #6
uufsm CreditAttribution: uufsm commentedI found that
- Domain blocks allowed control of the individual Subscription blocks, but not the Simplenews master subscription page.
- Domain Taxonomy allowed control of the Simplenews master subscription page.
-Newsletter settings allows control of the From address when a newsletter is actually sent.
The confirmation email sent upon subscription is configured at admin/settings/simplenews/newsletter, and I am having the same issue as you report. There is only one place to enter a "from" Email Name and Address. Even though it is followed by a list of Domains, and it says that the information on the page is Domain Sensitive and you could pick the domain you want the information to apply to, it doesn't seem to work. I have tried setting different addresses on the primary domain and when I'm at the subdomain, but I always get the same "From" address on email confirmations.
My work-around at this point is to use a non-specific Email name of our organization for Confirmation letters and apply it to all domains. The body of the email does contain the name of the newsletter and the domain it belongs to, so people are reassured that they did subscribe to the right newsletter.
Of course, that naming option won't work with all websites, since the subdomains may have very different names.
Are you going to submit this as a request?
Comment #7
Ice-D CreditAttribution: Ice-D commentedThis does totally not work here. I've configured Domain Taxonomy for newsletter vocab and yet it always shows all newsletter categories everywhere. Any ideas how to fix this?
Comment #8
rolfmeijer CreditAttribution: rolfmeijer commentedI made a small module so the form on the user account page respects the domain taxonomy grants.
It could be extended to other forms for subscribing to newsletters, but to start with this is what I needed. If time permits I will make it into a sandbox project (little cleaning up do) before vacation starts :-).
I’ll keep you posted.
Comment #9
rolfmeijer CreditAttribution: rolfmeijer commentedMade it into a sandbox project: https://drupal.org/sandbox/rolfmeijer/2050999
Comment #10
agentrickardNice. This is the proper solution.
Comment #11
Gonzalo2683 CreditAttribution: Gonzalo2683 as a volunteer commentedWhen I go to see the boletiones section in the user profile I get the following error:
The problem is that the user object does not have the property $ domain_user,
I have added a patch that needs revision
The patch:
https://www.drupal.org/project/2050999/issues/2968169#comment-12594538
Comment #12
agentrickardIssues need to be filed to the sandbox project.