Forum Replies Created
-
Posts
-
It may be that this wasn’t included previously, but MailChimp API 3.0 now allows email address updates, so it would be a useful feature to have. It would need to check if the original email was on the list first, in case the user wasn’t actually signed up when they originally subscribed via SWPM. 🙂
There’s no way to do this through the core plugin. I have had to write a separate plugin to calculate and monitor SWPM expiry dates and send two notification emails – one upon expiry and one slightly later as a reminder. It would be a very useful function to have built into the core.
Fantastic! Many thanks. Just to check, does this work with form builder (which I also use)? Many thanks.
Yes, which is why I posted. There is nothing in documentation that depicts a hook after a user has updated their information. It would be very useful if there was one. 🙂
Kana has identified the problem. I have found the same issue and switched the short php tag for the full version and the screen is now displaying again. The use of short tags is discouraged because not every system has them enabled, so best to avoid them. I assume that the plugin developer will address this for the next release? Thanks 🙂
I don’t have a cache plugin. Clearing the browser cache does nothing, nor does raising the memory yet further.
I will check with this host tomorrow to see what the score is, however it remains the case that our site has been running fine with SWPM until this most recent update, and we have changed absolutely nothing else other than upgrading the core SWPM plugin. How could that create memory issues?
I have this problem too. We have FOUR members listed in the plugin’s db on our test site (identical setup to live) and get a blank page. We have many more on the live site and get the same blank page.
My PHP core has 64M. Not sure what the memory is for the website package itself is, however I run more resource intensive things than this plugin without issue, and it worked fine until the recent update. Something must have changed.
It’s a pretty serious problem because it means I can’t manage the membership at all!
I haven’t changed anything else, so it must be the update.
