So, if I understand this correctly… when you have multiple newsletters under the same Ghost account, users must subscribe to the main newsletter to receive emails from the added newsletter?
Is there a way to create a stand-alone subscription form for a second newsletter?
Ah apologies, perhaps I misunderstood your question.
When a person signs up through the Portal modal, they’ll be able to choose the newsletters that they’d like to receive. If not going through the native portal (i.e. an input on the homepage), new signups will be added to whichever newsletter(s) are set to Subscribe new members on signup in each newsletters’ settings.
Alternatively, if they’re existing subscribers, you can send them here https://EXAMPLE.ghost.io/#/portal/account/newsletters to allow them to manage their preferences / sign up to a second newsletter.
Is it possible to make that link ( /#/portal/account/newsletters) be one of the options on the link drop-down for Buttons? I was looking for that URL earlier today and couldn’t figure it out. I tried navigating to that screen from another portal URL, so I could copy the URL, but the URL didn’t change to /#/portal/account/newsletters. It’d be nice if that was more transparent.
Is it possible when turned off the portal?
I cannot display the different newsletters in the signup-process. Of course, they can choose in their account, but it’s not a very smooth procedure to promote different newsletters.
I’m not quite sure I understand what you’re asking. If you turn off portal and are using a custom sign up form, then your custom form would need to provide the list of newsletters, too…
When I turn on portal, a popup comes up after signup to choose a newsletter.
When I turn it off, there is no popup. ok. But I miss a way, to provide the signup to multiple newsletters without this popup. I don’t know, how to handle it.
The idea of an open form to manage subscriptions by providing member email felt like a security issue, so a part of the use-case is scratched out. (though this is possible on some other popular publication websites, possible privacy/security loophole)
Though the support for accessing members’ newsletter subscriptions in handlebars (theme) is open. So currently portal is the only way to manage your newsletter selection.
Assuming there’s a privacy concern for not exposing this data to theme too?
This is not true. There’s not a nice helper for it, but the data is present in the member object, and you can write some JavaScript to respond to checkboxes being checked and update the member.
@Cathy_Sarisky referring to the docs , it’s not listed as a property or maybe I’m missing something. Did you mean doing this through the admin API SDK?
Definitely not with the admin sdk. Last time I wanted to do it, I watched the network calls happening when I subscribed a member using portal, and used that as a starting point for my custom code.