Title: focuspulling's Replies | WordPress.org

---

# focuspulling

  [  ](https://wordpress.org/support/users/focuspulling/)

 *   [Profile](https://wordpress.org/support/users/focuspulling/)
 *   [Topics Started](https://wordpress.org/support/users/focuspulling/topics/)
 *   [Replies Created](https://wordpress.org/support/users/focuspulling/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/focuspulling/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/focuspulling/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/focuspulling/engagements/)
 *   [Favorites](https://wordpress.org/support/users/focuspulling/favorites/)

 Search replies:

## Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Featured Images in RSS for Mailchimp & More] Not all posts have a Featured Image, so what then?](https://wordpress.org/support/topic/not-all-posts-have-a-featured-image-so-what-then/)
 *  Thread Starter [focuspulling](https://wordpress.org/support/users/focuspulling/)
 * (@focuspulling)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/not-all-posts-have-a-featured-image-so-what-then/#post-5923880)
 * I don’t think the solution to anything is stacking dozens of plugins for every
   single feature we want. (FYI, the one you linked to was abandoned in 2013, and
   it doesn’t even come close to accomplishing what I described in simple detail,
   as it merely generates a picture file then does nothing with it.) Everything 
   I mentioned above is an easy, tiny, fitting complement to the plug-in at issue.
   Would love to hear from the actual developer on whether this will be implemented,
   otherwise I’ll look for another plug-in (or develop my own).
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[MC4WP: Mailchimp for WordPress] Responsive developer, sensitive to premium features issue](https://wordpress.org/support/topic/stingy-to-coerce-payment-for-trivial-boolean-feature/)
 *  Thread Starter [focuspulling](https://wordpress.org/support/users/focuspulling/)
 * (@focuspulling)
 * [11 years, 3 months ago](https://wordpress.org/support/topic/stingy-to-coerce-payment-for-trivial-boolean-feature/#post-7926658)
 * What can I say, you made good on this issue, thanks.
 * I’m still struggling with an issue that may be something I just need to figure
   out; some support history here suggests that I could use the NAME field (or is
   it called “merge tag”?) instead of separate FNAME and LNAME fields in a form 
   for a widget, and MailChimp would parse that with assumptions, breaking out the
   single NAME entry into first and last name entries. At a certain point in this
   plug-in’s history, it stopped happening. Any advice? I’m simply trying to save
   on screen real estate with one form field instead of two. The YIKES plug-in and
   Ninja Popups plug-in’s MailChimp implementation do allow this.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[MC4WP: Mailchimp for WordPress] NAME not splitting to FNAME/LNAME](https://wordpress.org/support/topic/name-not-splitting-to-fnamelname/)
 *  [focuspulling](https://wordpress.org/support/users/focuspulling/)
 * (@focuspulling)
 * [11 years, 3 months ago](https://wordpress.org/support/topic/name-not-splitting-to-fnamelname/#post-5589596)
 * I’ve had this problem since installing on a new site with the latest version 
   of the plug-in. In other words, NAME doesn’t send anything to my MailChimp list,
   though FNAME and LNAME do, separately. The developer here evidently hasn’t responded
   to you in a month, but perhaps it’s just that the functionality got broken, either
   by this plug-in’s update, or a WordPress update. Still want to know…
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[MC4WP: Mailchimp for WordPress] Responsive developer, sensitive to premium features issue](https://wordpress.org/support/topic/stingy-to-coerce-payment-for-trivial-boolean-feature/)
 *  Thread Starter [focuspulling](https://wordpress.org/support/users/focuspulling/)
 * (@focuspulling)
 * [11 years, 3 months ago](https://wordpress.org/support/topic/stingy-to-coerce-payment-for-trivial-boolean-feature/#post-7926648)
 * I should clarify, especially if, as you say, it “hurt a lot” to receive the criticism:
   using your words, when a coder says he/she is “working my ass of [sic] on a daily
   basis” I completely agree that it needs to be rewarded financially. I am grateful
   to the plug-in community when they generously offer free versions toward the 
   hope of bonus features accruing revenue.
 * Consistent with that principle, I took issue with your plug-in’s behavior because
   it goes in the opposite direction. With zero sweat equity (in other words, no
   labor hours _adding_ a feature), you disabled a free capability in MailChimp 
   to send a welcome email _for the sole and specific purpose to nudge your users
   into paying for the plug-in._ It’s that behavior, a subtle but not trivial distinction,
   which deserves criticism. So yes, you should change your mind on this one.

Viewing 4 replies - 1 through 4 (of 4 total)