and how do i get rid of them.

Inside the blocks for a maillist - the module puts out a couple of wrappers that imho have nothing to do there & adding a <small> + <em class="placeholder">
i have looked throught the souce code search high n low but cant seem to figure out where it comes from

Yup im picky like that & like my markup to be very lean n mean & dont having stuff that discurbs my semnatics (im looking at you <small>

Is there a way to get these pieces of markup or is it provided directly from Mailchimp?

Comments

googletorp’s picture

googletorp commented

<em class="placeholder"> most likely comes from using:

print t('Hallo %var', array('%var' => 'Morten'));
// Hallo <em class="placeholder">Morten</em>
nicholasthompson’s picture

nicholasthompson
Primary language English
commented

Agree on the t() thing by googletorp. Basically, thats rendered by drupal_placeholder... (didn't that used to be theme_placeholder?)

As for small.. How about form_process_machine_name?

nicholasthompson’s picture

nicholasthompson
Primary language English
commented

Is it possible <small> is coming from the inputted content? What context is it used in?

nodiscipline’s picture

nodiscipline commented

I have the same problem using a

t('inbox %var', array('%var'=> $num_of_mes))

in a menu displayed in a block using

drupal_render(menu_tree('my-folders'));

How do make my output showable?

output is:

Inbox <em class="placeholder">(2)</em>

levelos’s picture

levelos commented
Assigned: Unassigned » owenpaula
amytswan’s picture

amytswan commented
Issue summary: View changes
Status: Active » Closed (won't fix)

“And now our watch [for support of the 7.x-2.x version of the MailChimp module] has ended…” With the approaching deprecation of MailChimp’s API version 2.0, I’m sad to say we too must turn the page. This branch will become unsupported in early October and officially deprecated by the end of this year (2016).

Fret not! The 7.x-4.x and 8.x versions come highly recommended. Both are using Mailchimp’s new API 3.0 and are being actively maintained. If you find this issue still exists on either the 7.x-4.x or 8.x branches, let us know by opening a new ticket. “What is dead may never die, but rises again, harder and stronger!”