Hi Nathan,
So would this be possible with the addition of a small hook to the relevant core files? If so I’d be very interested to know more…
It would. I haven’t tested this, but a snoop through the code suggests you’ll need to add the following to mod.member_settings.php
, around line 1137:
$edata = $EXT->call_extension('member_update_profile', $m_data);
if ($EXT->end_script === TRUE) return;
However, this won’t cause everything to magically work, as the extension will probably need to be updated too (I think I have removed the “stub” code for the last release).
I’ll take a look at that, and make the necessary changes. It’ll probably be a couple of days before I can get to this though, so if you fancy having a hack, feel free to branch the project on github.
Hope that helps.
Stephen
Hi Nathan,
Hi Stephen, if you’re able to push a version live with the relevant stub in your code just commented out that would be awesome. We’re not quite at the stage where we need this right now but any time in the next week would be super. Really appreciate your help on this.
No worries. I’ll sort something out in the next few days and let you know when it’s done.
Cheers, Stephen
Hi Nathan,
A quick update on this… turns out I was looking in totally the wrong place when I mentioned the mod.member_settings.php
file. I tell you, it’s like a labyrinth in here.
Anyway, I’ve finally managed to locate the correct place for the extension call, but have run out of time to work on it today. I’ll try to get back to it tomorrow or Monday, and will keep you posted.
Cheers, Stephen
I’m trying to use the extension with a stand alone registration form.
The form itself is working and will register members to the site but I can’t seem to get the Freshview extension to send anything to Campaign Monitor.
Everything appears to be configured correctly and I have set up a custom profile field for “mailing list” then set that as the trigger field/value in the extension settings.
Will this extension only work with the default ExpressionEngine registration form? What am I missing?
Pete,
Will this extension only work with the default ExpressionEngine registration form? What am I missing?
I’m not aware of any issues when using a SAEF for the registration, assuming you’ve set the form up correctly. Are any errors being logged to the /system/extensions/sl_freshview_subscribe/log/
directory (the directory needs to be writeable)?
Stephen
I was just checking that actually. There was no log directory but this server has some odd permissions going on. I have manually created the log directory and made sure it’s fully writeable.
Let’s see!
Nope, doesn’t seem to be anything in there. The user has been registered but nothing is going on over at CM.
Equally if I check the registered member’s profile from the back end then none of the custom fields are populated.
I think perhaps I’m doing something wrong with the form. :/
EDIT: I got it to work - at least to add the user to the CM Mailing list - by removing the trigger field. So it looks like I AM doing something wrong with the form. Sadly the EE wiki and docs haven’t been much help regarding custom profile fields in a SARF.
I got it to work - at least to add the user to the CM Mailing list - by removing the trigger field. So it looks like I AM doing something wrong with the form. Sadly the EE wiki and docs haven’t been much help regarding custom profile fields in a SARF.
Are you using the “short name” to identify your Custom Profile Fields in the form? If so, that may be the problem; I suspect you have to use the field ID, as with a standard weblog SAEF.
Cheers, Stephen
Are you using the “short name” to identify your Custom Profile Fields in the form? If so, that may be the problem; I suspect you have to use the field ID, as with a standard weblog SAEF.
Ahh, interesting.
So instead of
<label>Company:</label><input type="text" name="company" value="" /></p>
I would need to use (assuming the field ID was ‘3’)
<label for="company">Company:</label><input id="company" name="3" type="text" value="" /></p>
I assume one would change the name parameter since an ID attribute’s value cannot be a number (or am I imagining that?)
Actually, I’m going to try it now 😊
Hmm. Although the extension is working and signging up the user to the mailing list, none of the custom fields info is sent to CM or stored within EE. There’s something fundamental I’m missing here. Since this isn’t really a problem with the extension I’ll start a new thread.
FINAL EDIT! Got it! There was another post in the forum with a similar problem. The fields must be referenced as:
<label for="company">Company:</label><input id="company" name="m_field_id_3" type="text" value="" /></p>
Now everything works both on site and at CM. Brilliant!
I’m having trouble getting an opt-in drop down to work.
I’ve created a custom member field (m_field_id 2), selected that as the trigger (with No and Yes options) to add to the mailing list on CM, but I can’t get the drop down select to pass the user’s email on sign-up. Not sure what I’m doing wrong. I’ve tried hardcoding the options to no avail.
Using the Solspace User module if that’s any help (which does work.)
Any ideas?
I’ve created a custom member field (m_field_id 2), selected that as the trigger (with No and Yes options) to add to the mailing list on CM, but I can’t get the drop down select to pass the user’s email on sign-up. Not sure what I’m doing wrong. I’ve tried hardcoding the options to no avail.
I’m not really following this… the select drop-down doesn’t pass the user’s email address, you still need to include the standard email address field on the sign-up form.
Does everything work without a trigger field?
Stephen
I’m not really following this… the select drop-down doesn’t pass the user’s email address, you still need to include the standard email address field on the sign-up form. Does everything work without a trigger field? Stephen
The form didn’t work with or without the trigger, I had the email address in a separate field (as part of the membership sign-up), I was just hoping to use the form to kill two birds with one stone.
I’ve decided to use a separate sign-up form for the newsletters (as auto generated in the Campaign Monitor options.) Due to the way this project works it seems it is the preferred method.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.