Title: Shortcode stopped working – Using new ones
Last modified: September 1, 2016

---

# Shortcode stopped working – Using new ones

 *  [shypixel](https://wordpress.org/support/users/shypixel/)
 * (@shypixel)
 * [10 years, 1 month ago](https://wordpress.org/support/topic/shortcode-stopped-working-using-new-ones/)
 * [wpmem_field field=”user_login”] is no longer working for me, returns nothing.
 * [https://wordpress.org/plugins/wp-members/](https://wordpress.org/plugins/wp-members/)

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

 *  Plugin Author [Chad Butler](https://wordpress.org/support/users/cbutlerjr/)
 * (@cbutlerjr)
 * [10 years, 1 month ago](https://wordpress.org/support/topic/shortcode-stopped-working-using-new-ones/#post-7691167)
 * There was a fix to the [wpmem_field] shortcode in 3.1.4. With that fix, there
   appears to be a new issue with a couple of fields.
 * Currently, it seems to be specific to two fields in the wp_users table, user_login
   and user_registered; but not others such as user_email or user_url, and does 
   not appear to affect any wp_usermeta fields.
 * I’m looking into a fix.
 *  [NetMonkey](https://wordpress.org/support/users/headmonkey/)
 * (@headmonkey)
 * [10 years, 1 month ago](https://wordpress.org/support/topic/shortcode-stopped-working-using-new-ones/#post-7691174)
 * I’m experiencing the same problem. Hoping for a fix soon. Thanks.
 *  Plugin Author [Chad Butler](https://wordpress.org/support/users/cbutlerjr/)
 * (@cbutlerjr)
 * [10 years, 1 month ago](https://wordpress.org/support/topic/shortcode-stopped-working-using-new-ones/#post-7691176)
 * The problem turns out to be part of the new logic that was applied to handle 
   select (dropdown), checkbox, and radio fields. 3.1.4 had an improvement to this
   shortcode so that “display” values were used rather than stored values for these
   field types.
 * The flaw in this new logic is for any field type that may be displayed using 
   the [wpmem_field] shortcode that isn’t necessarily part of the form fields in
   the plugin’s fields setting. This would be fields like user_login, user_registered,
   and any custom user meta field that is not part of the settings array.
 * I have reworked the logic for this function so that it will handle the new process
   as intended while still supporting other fields like before. This update will
   be released this evening as 3.1.4.1.
 * In the meantime, the function can be updated manually. The function is wpmem_sc_fields()
   in the file /inc/shortcodes.php. It begins at line 552 in the file. It can be
   replaced with the function here:
    [https://gist.github.com/butlerblog/efb97220eec309ce0897ad800fcb999f](https://gist.github.com/butlerblog/efb97220eec309ce0897ad800fcb999f)

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

 The topic ‘Shortcode stopped working – Using new ones’ is closed to new replies.

 * ![](https://ps.w.org/wp-members/assets/icon-256x256.png?rev=1226414)
 * [WP-Members Membership Plugin](https://wordpress.org/plugins/wp-members/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-members/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-members/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-members/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-members/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-members/reviews/)

 * 3 replies
 * 3 participants
 * Last reply from: [Chad Butler](https://wordpress.org/support/users/cbutlerjr/)
 * Last activity: [10 years, 1 month ago](https://wordpress.org/support/topic/shortcode-stopped-working-using-new-ones/#post-7691176)
 * Status: not resolved