Scott Reilly

Can you post an example of your usage of the shortcode that is not working for you?

As I stated, the problematic side effect of security changes introduced in 4.2.3 are with how a shortcode is used, not with how it is implemented in a plugin (though some plugins may output shortcodes in a problematic fashion).

In the case of Get User Custom Field Values, the plugin merely defines a shortcode, which was not something affected by the update.

Seeing an actual example of how you’re using the shortcode should provide better context for any further recommendations.

@htmadmin: Hi,

There was a security update made to all version of WordPress going back to 3.7, which includes the very latest, 4.2.3. This security update affected the Shortcode API within WordPress. You can read about it here: https://make.wordpress.org/core/2015/07/23/changes-to-the-shortcode-api/

Basically, the change affected how WordPress parses shortcodes, and in some cases it no longer recognizes them. In your case, more than likely this has to do with how you are using quotes around the shortcode. You might something like so:

<a href="[custom_field field="product_url" this_post="1" /]">Product site</a>

You have to make sure the quotes used for the shortcode attributes do not match the same quotes used for the HTML attribute (e.g. the “href” attribute). The above example should be changed to the following:

<a href="[custom_field field='product_url' this_post='1' /]">Product site</a>

(Note the shortcode’s attribute quotes were changed to single quotes so they differ from the use of double quotes for the ‘href’ attribute.)

If you’re still wondering how to change what you’ve got, feel free to provide the code snippet of how you’re using the shortcode and I can make a more specific recommendation.

Unfortunately I don’t have any recommendations for you with regards to layout builder plugins as I’ve never used any of them. I know some others don’t run standard filters (or any at all) which would prevent their text boxes from being accessible to this plugin, as you’ve experienced with this one.

Was the support personnel for the layout builder plugin you’re using not able to help out in any way?

Hi,

Allowing duplicate email addresses is less involved than allowing duplicate usernames. Email address is a piece of information associated with an account whereas the username is used to actually log into the system.

The login process would have to be adjusted to deal with duplicate usernames. For a login attempt, would WP keep comparing the password for every instance of the given username until it found which account is being logged into? Or would you be modifying the login form to require both username and email address to log in?

There’s also the issue of the password reset form, which can take the username. Without adjusting the handling and display of that form, you risk a user not being able to reset for their specific account.

And there’s also unique author slug generation.

Which is all to say, there’s a lot involved in allowing duplicate usernames, little of which overlaps with what the plugin currently does. It would warrant being its own plugin, but not one I’m looking to build at this point.

Cheers!

@jezzerisin : Hi,

A screenshot might help since I’m a little unclear on the nature of the issue you’re reporting. Feel free to send to coffee2code @ gmail. If you do send it to me, follow up here to let me know so I make sure to look out for it.

Thanks!

@jonas-lundman, @kiwi3685 : Check out v3.0.4 of the plugin which should fix the issue you encountered going forward.

It seems both of those plugins hooked the same action as Allow Multiple Accounts in such a way that they were getting the user email addresses before AMA had a chance to change them back to something proper.

Depending on how those newsletter plugins work, their copy of the user emails may or may not get fixed. (If they periodically resync, as kiwi3685 suggested MailPoet does, it may automatically clear up.)

Let me know the issue persists for either of you. Thanks for reporting it!

@imscenterprise : Hi,

It’s doable with some custom code since it’s not a built-in feature of the plugin.

The following code can be put into a .php file in wp-content/mu-plugins/, or less ideally in your theme’s functions.php file.

/**
 * Just before an export takes place, store all user comments counts in the
 * 'accc_comments_count' usermeta field.
 */
function store_user_comment_counts_in_meta() {
	// Don't do anything if Admin Commenters Comments Count isn't active.
	if ( ! class_exists( 'c2c_AdminCommentersCommentsCount' ) ) {
		return;
	}

	// Loop through all users.
	foreach ( get_users() as $user ) {
		// Get the count of the user's number of comments.
		$comments_count = c2c_AdminCommentersCommentsCount::get_comments_count( 'comment_author_email', $user->user_email, 'comment', $user->ID );
		// c2c_AdminCommentersCommentsCount::get_comments_count() returns an array that includes the number of
		// approved comments and the number of pending comments. This next line presumes you only want the count
		// of approved comments.
		$comments_count = $comments_count[0];
		// Store that count in user meta.
		update_user_meta( $user->ID, 'accc_comments_count', $comments_count );
	}
}
add_action( 'export_wp', 'store_user_comment_counts_in_meta' );

I tested it out and it worked for me.