Is there a way add placeholder text and get rid of the label titles. Also is there a way to re-arrange the order of my fields?

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

lasseitorp’s picture

Any news on this? Is this on the Drupal or MailChimp side of things?

sui_page’s picture

I ended up using the embed code supplied from the Mailchimp website instead. I find it's more flexible and you can easily move HTML around and add any placeholders

helmo’s picture

Version: 7.x-2.10 » 7.x-3.x-dev
Status: Active » Needs review

Here's a patch that adds a placeholder attribute.

I had the configuration for this in a feature, making it easy to add a line in the 'mergefields' array.
Like:
"placeholder" : "First name*",

Hiding the regular label can be done with CSS, e.g. "display: none;" on #block-something label

helmo’s picture

nlarow’s picture

Is there a way add placeholder text?
Looks like helmo handled that..

..and get rid of the label titles?
For the form/entry itself, this is easily accomplished via CSS per the previous comments.

However, if you're talking about removing it from email/notifications, you either hard-code the labels/tokens manually into a email template and use MimeMail, or in my case.. I created an entire new theme just for "Viewing" submissions that outputs the "Submission" as valid XML with massive edits to the field.tpl. I then used the ThemeKey module to have it switch templates when viewing submitted data. This allows us to use submissions to import data into a customized CRM.

Also is there a way to re-arrange the order of my fields?
Under "Manage Display" you can change the output/order, as well as other options on how to output the values.

ruscoe’s picture

Assigned: sui_page » Unassigned
Status: Needs review » Closed (won't fix)

We're going to be ending support for the 7.x-3.x branch due to the upcoming deprecation of the v2.0 MailChimp API. If you'd still like to do this, please feel free to reopen for the 7.x-4.x branch.

helmo’s picture

Re rolling the patch on 4.x was trivial :) here it is.

However I also found #2754819: Allow use of HTML5 placeholder attribute which looks like it's solving the same thing ... So leaving this closed until I've had time to review that issue's patch.