sandeld

Ok, I found that documentation buried in your FAQ’s on your main plugin website, but I think you should make it a little more obvious since using double-quotes in a programming language is an incredibly frequent possibility. So much that I can’t believe it breaks the functionality.

I deleted those fields and re-added them as suggested in the FAQ doc, but now my entire form is un-clickable. I cannot change, update, click, or move anything.

• This reply was modified 6 years, 2 months ago by sandeld.

So, it looks like adding any html breaks the edit/update button. I added some font styling: <font color=”red”> and now I can’t do anything else to that field.

Screenshot of summary

As a listed MailChimp Expert on your directory, I’m well aware what your e-commerce functionality is used for.

I’m also well aware that the feedback given is rarely incorporated as I have been with MailChimp for more than 4 years and none of my suggestions have been taken, despite being basic functionality for most other email marketing platforms.

Oh, yes, sorry. I remember that, but I assumed that an “update” was also considered a “new release”, or at least the update would come with a new revision number.

One quick update:

I just updated the plugin to the most recent version and the language “glitch” got rolled back. That means I’m going to have to remember to come back to this thread every single time I do an update so that the language changes back to English.

As for the button and bulk smush conflict — No, I have not had a chance to deactivate plugins and investigate which one is causing the conflict yet.

Hello, I managed to figure it out, though as someone that has to teach himself, it definitely wasn’t easy.

I’m sure this isn’t the most elegant PHP code in the world, but if anyone else needs this or wants to make suggestions on how to do it better, here is what I finally used.

add_filter( 'mailchimp_sync_user_data', function( $data, $user ) 
{
	$user_id = $user->ID;
	$plan_ids = array(539, 518, 511);
	$arrlength = count($plan_ids);
	for ($x = 0; $x < $arrlength; $x++)
	{
		$user_membership = wc_memberships_get_user_membership( $user_id, $plan_ids[$x] );
		if (!empty($user_membership))
		{
			$active_level = $user_membership->plan->name;
			$data['LEVEL'] = $active_level;
		}
	}
	return $data; 
}, 10, 2 );

I also need to add an else in there somewhere in case a user doesn’t have a membership level, but I’ll get to that later.

The problem is that your plugin virtually has no functionality beyond syncing e-commerce data to my list. Which is quite essential for an e-commerce website.

But because it lacks all capability of opting customers into specific groups or custom merge fields, it forces us to be an overpriced WooCommerce extension or try to use two different MailChimp plugins and avoid conflicts…which rarely happens.

I’m currently using your plugin just for the ecommmerce sync, and another plugin that has the capability of monitoring my WordPress users list and then syncing custom fields to MailChimp once it detects a change (which is front-end, user driven). Already this is causing problems in a couple different use cases whereby an already subscribed contact automatically gets unsubscribed as soon as they make their first purchase.

It’s a huge mess, but the only other option is to pay even more money for an already over-bloated WooCommerce bundle.

Update:

As you can tell, I’m a beginner php programmer, but I am starting to understand a little more. I’ve now changed the code to something like this, though it’s still not working:

add_filter( 'mailchimp_sync_user_data', function( $data, $user ) {
	$mem_level = wc_memberships_get_user_active_memberships( $user );
	$data['LEVEL'] = $mem_level;
    return $data;

I’ve even tried removing the intermediate step of $mem_level but that didn’t work either.

Oof! I completely forgot about this, and when I was doing the site maintenance, I ran into a bunch of other problems.

Anyways, the button is still broken which means there’s still a conflict, but at least the language thing is fixed.

Hello,

I’m back again with the same set of code.

Your suggestion above worked perfectly for desktop. You can see it if you visit the current website.

However, I’ve discovered that on mobile, the two fields are different sizes, and I’d like them to span the full width, just like the email field. You can see that if you visit the above link on your phone.

In the end, I’d like both fields to be the same size (whatever that ends up to be) on desktop and both fields to span the full width of the screen on mobile.

Is that possible?

Thank you.

I’ve realized there’s nothing I can do. Those “blocking” elements are there no matter what.

Changing the column number fixed everything. I’m an idiot, but thanks for your help. ??

That did the trick, thanks!

I’m going to be doing a bunch of other site maintenance and updates this weekend so I will report back on my findings with the conflict for why the Bulk Smush button isn’t working for me.

Yup, still confused. So just for the fun of it, I changed my user language to Spanish, checked the update page, visited the Smush plugin settings, changed my language back to English, visited the update page, and revisited the Smush plugin settings.

The entire time Smush remained in Spanish while the rest of the site changed.

The thing is, I installed Smush in English, I originally used it in English, and I’ve done many multiple updates of Smush while in English. The entire time, the site language has been in Spanish and that has never changed.

The only thing that has changed is the visible language of your plugin. So I’m at a loss…

Now you’ve really confused me. Downloading update for all the plugins? What?

Never in my 10 years of WordPress usage have I ever needed to go into a php file hosted on my server just to support site language vs. user language. Based on that and your comment about “that’s just how WordPress works” makes me think you don’t actually understand the actual problem. And especially given since your colleague, the first person to reply, said he could reproduce the error in his test environment.