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

I upgraded from SL Freshview Subscribe v.1.1 to 1.2 today.

Now when I “get clients”, I am presented with a drop down with the selections “M” and “8”, neither of which are clients set up in my Campaign Monitor account.

I have triple-checked my API and it is definitely the correct value.

Any thoughts?

Now when I “get clients”, I am presented with a drop down with the selections “M” and “8”, neither of which are clients set up in my Campaign Monitor account. I have triple-checked my API and it is definitely the correct value. Any thoughts?

Um, nothing springs immediately to mind. I suppose the obvious first question is what happens if you select either of those clients, and click “Get Lists”..?

Stephen

Hi Stephen,

When clicking “Get Lists,” I receive the message “There are no mailing lists associated with this client.”

It’s very odd. I do have another account with Campaign Monitor. I will try that API key and see if anything changes.

Strangely enough, it works perfectly with a different API key. Looks like the issue is with Campaign Monitor.

Thanks!

Strangely enough, it works perfectly with a different API key. Looks like the issue is with Campaign Monitor.

Thanks for letting me know Chad.

Cheers, Stephen

Hi Stephen,

Great extension, but I’m experiencing the same issue as Chad:

Now when I “get clients”, I am presented with a drop down with the selections “M” and “8”, neither of which are clients set up in my Campaign Monitor account.

I’ve tried a couple of API keys, all of which I’ve also triple checked.

any ideas at all?

PS I think CM possilby did make some API changes recently, as a group of other sites I admin that use the CM API (but which run on a custom CMS) are also having similar woes…

Hi metadaptive,

Great extension, but I’m experiencing the same issue as Chad:

Ok, thanks for the heads-up. I’ll try to recreate the problem here, and have a chat with the guys at Freshview, to see if they have any idea what might be causing this.

More soon (hopefully)…

Cheers, Stephen

Ok, the latest version should address the issues that metadaptive and Chad were experiencing.

Many thanks to metadaptive for his help in pinpointing the problem.

Cheers, Stephen

I’m seeing some PHP notices and warnings after clicking the member activation email that triggers Freshview Subscribe.

Notice: Use of undefined constant BASE - assumed 'BASE' in /path/to/system/extensions/ext.sl_freshview_subscribe.php on line 97

Notice: Use of undefined constant AMP - assumed 'AMP' in /path/to/system/extensions/ext.sl_freshview_subscribe.php on line 97

Notice: Use of undefined constant AMP - assumed 'AMP' in /path/to/system/extensions/ext.sl_freshview_subscribe.php on line 97

Notice: Use of undefined constant AMP - assumed 'AMP' in /path/to/system/extensions/ext.sl_freshview_subscribe.php on line 97

Notice: Use of undefined constant AMP - assumed 'AMP' in /path/to/system/extensions/ext.sl_freshview_subscribe.php on line 97

Notice: Use of undefined constant BASE - assumed 'BASE' in /path/to/system/extensions/ext.sl_freshview_subscribe.php on line 98

Notice: Use of undefined constant AMP - assumed 'AMP' in /path/to/system/extensions/ext.sl_freshview_subscribe.php on line 98

Notice: Undefined index: custom_fields in /path/to/system/extensions/ext.sl_freshview_subscribe.php on line 177

Warning: Invalid argument supplied for foreach() in /path/to/system/extensions/ext.sl_freshview_subscribe.php on line 177

I was logged in as a super admin, so my normal users won’t see those errors. My email was successfully added to Campaign Monitor, so these are probably just nuisance messages, but thought you’d want to know.

I’m on EE 1.6.7 Build: 20090320 and SL Freshview Subscribe 1.2.1.

Nice extesion!

Hi siffring,

Yeah, I was aware of this bug before release. I ignored it because it only affects administrative users who are logged-in, and confirming a new (separate) site registration email.

In other words, I couldn’t imagine a scenario where this could possibly affect “normal” site users.

Still, it is annoying… I’ll see if I can track down the root cause for the next release.

Cheers, Stephen

Hey Stephen,

I get a blank Extension page with the extension in the folder and extensions set to “n” in config.php

Hi Steven,

I get a blank Extension page with the extension in the folder and extensions set to “n” in config.php

Hm, I’m not getting that at all, running on EE 1.6.7 (tried it with PHP 4 and 5). Are there any other extensions that could be causing the problem?

Stephen

Hi Steven-

Love the extension. Two questions:

1) I’m curious if there’s a way to get clients’ lists using their API key vs. using our API key and revealing all of our clients - if someone were to access the extension and take a look. Not a huge issue, just curious why it works that way (I’m sure there’s a reason).

2) Is there a way to specify what information gets passed to CM? In other words, I have a newsletter signup on the site which asks for name and email. But when someone gets added via SL Freshview/member registration, their Screen Name is used instead - and I don’t see a way to specify that.

Thanks.

Geoff,

I’m curious if there’s a way to get clients’ lists using their API key vs. using our API key and revealing all of our clients - if someone were to access the extension and take a look. Not a huge issue, just curious why it works that way (I’m sure there’s a reason).

I’m pretty sure there’s no such thing as a client API key. There’s a client API ID, which is something totally different (it’s how you identify the client when using the API). This page should clarify matters.

Is there a way to specify what information gets passed to CM? In other words, I have a newsletter signup on the site which asks for name and email. But when someone gets added via SL Freshview/member registration, their Screen Name is used instead - and I don’t see a way to specify that.

The screen name of a user usually is his name. Are you using different fields to hold the name?

Stephen