jaspud

Hi, the issue was time-sensitive so I ended up switching to a different SEO plug in and corrected the issue. Thank you though!

For those with this issue, I found a workaround. The “From” email in the form configuration can’t be the same as the email that it’s being sent to. So, just change the from email on the site and it works fine.

For example, if you are sending the emails to [email protected] and you have that in the from and to columns, the reply-to won’t work. But, if you change the from column to something else like [email protected], it works again.

Just wanted to post in case anyone needed help.

As an update, I am able to change the SEO title and description from the quick change area in the full page list but the snippet and everything is still incorrect on the actual Edit page.

The actual URL where this is happening is https://pluginvegas.com/las-vegas-blog

Same problem as well. Have you figured out a solution yet or does anyone know another plugin that can be used to accomplish this?

Thanks for responding ??

We have been experiencing recent brute force flood against the xmlrpc.php file of the site that have been making the site inaccessible.

Just an update,

MailChimp’s response…

In this case, it would be possible to segment subscribers so that only subscribers with a eot_date value occurring after 1/1/1970, or any date of your choice, would trigger the automation. In order to do this, it would be necessary to define a segment looking like this: [eot_date] [is after] [1/1/1970] The segment for an automation can be defined in the List and Workflow step of the Automation Builder.

This works perfectly for what we’re trying to do.

The only thing that doesn’t seem to work is that when a Stripe user cancels their subscription and they are given an EOT date, it does not update over to Mail Chimp (at least how I have it set up) but I actually don’t want it to so that’s all good.

Thanks. This definitely got rid of the warning. My one question, it does now send an EOT for subscriptions of 12/31/1969 and I am using automations with Mail Chimp to send renewal notices based on users EOT dates. We don’t want users that are active on subscriptions to be getting renewal notices and I’m not quite sure how Mail Chimp is going to treat this date (they may just ignore and not send it the automation; I have a support ticket in to ask them).

If that is not the case, is there a way to have it send over EOTs for those with normal purchases and then nothing for subscription purchases?

I accomplished this through these steps…

1. Create a MailChimp account.
2. Create a profile field on your integrated list named eot_date
3. Create the file s2-hacks.php in the MU (must use) plugins folder
(There is a ton on google about how to do this)
4. Add the following code to that file.

<?php
add_filter('ws_plugin__s2member_mailchimp_merge_array', 'my_filter', 10, 2);
function my_filter($merge, $vars) {
	// $merge: Array of existing MERGE fields that s2Member passes by default.
	// $vars:  Array of defined variables in the scope/context of this Filter.

	$custom_merge = array(
		'eot_date'   => date('m/d/Y',get_user_option('s2member_auto_eot_time', $vars['user_id']))
	);

	return array_merge($merge, $custom_merge);
}

5. This will now automatically send the EOT date over when people register if you have the Mailchimp integration configured correctly.
6. Set up ‘Renewal Reminders’ using the schedule an email based on a date function in Mail Chimp. You can have emails sent however long before, day of, days after or all of them or whatever you want.

Definitely agree. Since you have a solid understanding of the program, any guess how intensive this custom coding might be/ heard of anyone doing it already?

Yea, these unfortunately unless I’m reading wrong won’t help. Basically as far as I understand, if you have a product that has an EOT of 6 months (as an example), the user is able to buy 1 of them and get an EOT 6 months away or buy 100 of them and get an EOT 600 months away. This is an extreme example but we’re trying to limit people from taking advantage of our renewal discounts.

We basically were wondering if there was a way to limit them to only being able to renew for the next year or 2 or something like that.

Just an update for everyone, still back and forth with Cristian to try and get to the bottom of this. We still have several of these coming in every week but at least with the hack they are defaulting to a role that they can see the content. Still have to go back in and add an EOT date for all of them and change them to the appropriate s2 or s3 level.

I don’t believe this exists yet :/ What we’ve done to go around it is sell specific page access to existing members and then on that page they can download a pdf with a gift certificate with a 100% off coupon code on it.

Not ideal, but works.

You can set a price on the product through s2member and then use coupon codes to give them 100% off. Basically, when they buy on the other portal, give them the 100% off coupon code, MAKE SURE to instruct them not to pay again on the other site (its a headache and a half sometimes) and then you’re good to go.

Any reason not to just have them pay on your home site?

We integrated another payment gateway onto our build and it works very well. It cost us about $800 bucks from a private developer but they did a great job and we lost no functionality.

So basically, can be done just needs to be built by someone who knows what they’re doing. I can refer you to the guys I used if you want.