Closed (fixed)
Project:
Campaign Monitor
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
2 Sep 2011 at 16:48 UTC
Updated:
25 Sep 2011 at 10:01 UTC
Jump to comment: Most recent file
I am trying to get the name field for campaign monitor to use the name field i have created for the user registration page. I am a bit confused at how this works. Before I selected the "Display name field" option it was defaulting to the username. When I selected the "display name field" checkbox, i got a new box for name field and it had the username token already loaded in it. When i changed the token to reflect the profile field I had created for name, i still only get the username when users sign up. I am not sure if I am doing something wrong or if its a bug. Any help would be appreciated. Thank you very much!
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | fix-token-replacing-7.x-1.x.patch | 588 bytes | bdawg8569 |
| #2 | add-admin-instructions-7.x-1.x.patch | 3.27 KB | bdawg8569 |
Comments
Comment #1
cableman0408 commentedI'll try to look into this, I think this is how it works. But that might not be optimal :-)
Comment #2
bdawg8569 commentedIt took me a bit of playing with things to realize that the token support isn't for the registration. I wasn't using the block that allowed sign ups. All i really wanted was to have the option to sign up when creating an account and it was a bit confusing for me. After looking thru the code and playing with things, i saw that the token support had to do with the block, and the option to expose the name field was for the block. I fixed a small error there. If you are using a token that isn't converted, the name field displays the token itself rather than nothing. Here is a patch to fix that. I am hoping to create a way to use a name field for user registrations too, if you are interested in that solution.
I also needed the ability to change the language under the list of available newsletters (which for me is always only 1 per site). My boss didn't like the fact that it says "campaign monitor" cause most of our users don't know what that is. I created another patch to add a textfield to the general settings to allow it to be changed. I thought i'd include it in case you wanted to think about using it or in the event that its helpful to somebody else.
Comment #3
cableman0408 commentedBoth patches have been applied to the development branch and will be part of the next release :-)
If you look into the name field for user registration, which would be grate, you should look at this issue http://drupal.org/node/955046.
Comment #4
bdawg8569 commentedI have read through that issue and I can see why you haven't implemented anything yet. Having multiple lists complicates things tremendously. On all of our sites thus far, we only have one campaign per site. I'm not sure how to implement something that would allow for custom fields and multiple lists. What about a sub-module that would depend on campaign monitor (maybe even packaged together if you are willing to do so) that would override some of the core functionality if you need to use custom fields on the user registration form. I know limiting it to a single list isn't ideal, but I am not sure how to get around the problem you address in the issue you mentioned above. I'm open to ideas and willing to help.
Comment #5
cableman0408 commentedyeah, there are some difficulties with sites that have more that one list active, but I think that it may be a small subset of the installations. Maybe the best solution would be to allow fields (name and custom) to be shown on the registration page if only one list have been selected.
It would be possible to show each list in it's own fieldset, if more than one list have been selected to be shown on the registration page.
But I think it would be a grate improvement to have the fields available with one active list and I would appreciate help implementing this :-)