SL Freshview Subscribe v1.4.0 : Now fully compatible with Solspace's User module

Sounds great!

Campaign Monitor has their own Subscription Preferences Center, which allows users to manage their subscriptions, so I can use that for opti-in/out updates until I get something working with their API, or EE addresses your request.

For those interested, here are a couple Preferences Center descriptions: http://help.campaignmonitor.com/topic.aspx?t=113 http://www.campaignmonitor.com/blog/post/1804/new-feature-let-your-subscribe/

One thing I did learn from the CM forums, and which is shown in the above sample, is that they recommend creating a single, master list, then using a custom “Interests” field in conjunction with segments to create campaigns targeted at specific groups. This is due to the nature of separate lists – specifically that they don’t really “talk” to each other when updating custom field data (name, email, interests, etc.): http://www.campaignmonitor.com/forums/viewtopic.php?id=1387

So that got me wondering, would your extension allow me to pass some custom field “interests” data across at the time of registration, which would support the strategy CM recommends?

Also, I’m wondering if this approach might inform what you ask for from EE in terms of your feature request. Just something to consider.

Regarding beta testing, would love to. I will need to sign up for a CM account (my client has not bought in to CM yet, mainly due to the higher cost of CM for mailings). One issue is that I’m out of town from Thursday through the following week, so it would have to be in the next few days, or after the 23rd.

Again, many thanks.

I’ll second that desire for passing a custom field to CM. I’d like to have the user enter their zip code as well. (I’m bidding on a site for an artist, so having location would be relevant to sending concert alert emails.)

I’m also keeping watch for EllisLab to add the extension hook you require for member profile opt-in/opt-out.

Hello all,

Just a quick note to let you know that I’ve released a significant update to SL Freshview Subscribe. More information at the start of this thread.

Cheers, Stephen

Stephen,

Can’t wait to give this a test run. Will let you know how it goes.

From looking at your documentation, I’m assuming this extension talks to CM at the point of registration, but can’t be used to manage optin/out after that point, correct?

Also, I would like to follow a CM recommendation to create one master list, then use a custom “Interests” field to create campaigns/newsletters targeted at specific groups/interests: http://www.campaignmonitor.com/forums/viewtopic.php?id=1387

Does your extension allow me to pass custom field “interests” data across at the time of registration?

Hi drpudding,

From looking at your documentation, I’m assuming this extension talks to CM at the point of registration, but can’t be used to manage optin/out after that point, correct?

That’s correct… until EllisLabs implement this feature request (feel free to add a comment supporting it), there’s no way I can implement post-registration opt-in / opt-out for EE members.

Also, I would like to follow a CM recommendation to create one master list, then use a custom “Interests” field to create campaigns/newsletters targeted at specific groups/interests: http://www.campaignmonitor.com/forums/viewtopic.php?id=1387 Does your extension allow me to pass custom field “interests” data across at the time of registration?

Not yet… CampaignMonitor announced a greatly expanded API – which will make it much easier to support custom fields – just as I was putting the finishing touches to this version. The plan is to implement custom fields in the next 3 - 4 weeks, work commitments permitting.

Cheers, Stephen

One other key issue to solve relates to updating the CM email address via EE. I just learned that CM does not support email address changes via their API – and so EE users who want to change their account email need to be unsubscribed from CM, then resubscribed with the new address. Not perfect integration.

So we got custom field support, optin/optout after to reg, and email address updates. Can ya whip that off in the next week or so…

… oh, and can you do something about the economy, while you’re at it?

😉

Hi drpudding,

… oh, and can you do something about the economy, while you’re at it?

Relax, I’m on it.

One other key issue to solve relates to updating the CM email address via EE. I just learned that CM does not support email address changes via their API—and so EE users who want to change their account email need to be unsubscribed from CM, then resubscribed with the new address. Not perfect integration.

I think this will, once again, be dependent upon this feature request.

As a result of using Solspace’s User module, I’ve sort of got around this – without ever really noticing, until you pointed it out – by using the member’s email address as their username, and then not allowing them to change it.

Hardly ideal, I realise, but it’s the only “solution” I can think of at present.

I’ll get on with the custom field support whilst we wait for that FR to be fulfilled…

Cheers, Stephen

Interesting regarding the User Module. I considered using that to allow email addresses as usernames for simplicity sake, but abandoned at some point. Have you had any issues/problems with doing this?

Thinking out loud…

– do you require that the username be an email address (validate as such), or is that just an option? – I think you are still required by EE to capture email address in its own field, right? – I imagine that screen name becomes more important as a way for users to avoid having their email appear on screen. – if you don’t allow members to change their username email address, what happens when it is no longer valid?

I’ll start poking around the forums for more on this.

Thanks!

drpudding,

Interesting regarding the User Module. I considered using that to allow email addresses as usernames for simplicity sake, but abandoned at some point. Have you had any issues/problems with doing this?

The only snag worthy of note was with the default maximum length for usernames. I had to tweak a variable in core.validate.php, to allow for the length of some email addresses.

do you require that the username be an email address (validate as such), or is that just an option?

Required.

I think you are still required by EE to capture email address in its own field, right?

“Email address as username” is an option in the User module. If you select it, the module takes care of the rest.

I imagine that screen name becomes more important as a way for users to avoid having their email appear on screen.

That’s the way I’ve approached it, yes. It’s been a while since I implemented it, but I seem to recall automatically creating the screen name from the “First Name” and “Last Name” fields on the registration form.

If you don’t allow members to change their username email address, what happens when it is no longer valid?

Good question, and one I’ve never had to answer, due to the quite closed nature of the sites I’ve done this on. In my case, this is a situation that the site admins can deal with, but I can see that for a more “dynamic” or open site, that might not work.

Thinking aloud myself for a moment, you could get around that problem by using a SAEF for email address change requests, which then updates the CM subscribers list via the API… just a thought.

Cheers, Stephen

Thinking aloud myself for a moment, you could get around that problem by using a SAEF for email address change requests, which then updates the CM subscribers list via the API… just a thought.

Yes. That is my thinking, as well. But it would need to follow the ‘unsubscribe/resubscribe’ rule.

This extension looks great. I do have a few questions. Please forgive me if they seem elementary and are topics that will reveal their answers once the extension is installed.

I’ve read all of the discussions about the opt-in at registration but I don’t see much discussion about how a general mailing-list sign-up is handled; i.e. input for email address, hit submit to subscribe.

Is this process set-up in the same way we would set-up a mailing-list with the mailing-list module? And then we just select the list in your extension to import the existing addresses?

Or, does the setup process differ and I’ve just missed it’s documentation?

Thanks for the clarification.

Just wondering if anyone has been able to achieve this in a manner that provides the user an experiences that is similar to the mailing_list module sign up.

Is see it is possible to use a form template that CM provides but the confirmation experience, while not at all out of the ordinary, its not styled in the manner of the project I’m working.

I’ve tried to find documentation on their end to see if it’s possible to stlye the sign-up confirmation page. But I’ve had no luck.

Just wondering how others do this?

Just wondering if anyone has been able to achieve this in a manner that provides the user an experiences that is similar to the mailing_list module sign up. Is see it is possible to use a form template that CM provides but the confirmation experience, while not at all out of the ordinary, its not styled in the manner of the project I’m working. I’ve tried to find documentation on their end to see if it’s possible to stlye the sign-up confirmation page. But I’ve had no luck. Just wondering how others do this?

Seems to me there is a section in CM for under manage subscribers then customize subscribe process where you can setup custom confrmation page urls.

Ha! Thank you very much! Exactly what I was looking for!