latest stable versions: v150827 (changelog)

Old Forums (READ-ONLY): The community now lives at WP Sharks™. If you have an s2Member® Pro question, please use our new Support System.

About: Kevin Murphy

Sorry, I've not written a description yet. I'll get to it soon!


My Latest Replies (From Various Topics)

Viewing 11 replies - 1 through 11 (of 11 total)
Author Replies
Author Replies
Posted: Monday Aug 26th, 2013 at 3:59 pm #58700

Yeah, I thought that was currently the only way to do it. I’m not sure that it’s the most convenient option but it might have to do! Perhaps some kind of IPN API notification in the URL for users with accounts could be added to the the next generation plugin for specific post/page access — you’d have to have a whole load of custom capabilities for what we have in mind.

Thanks.

Posted: Tuesday Aug 20th, 2013 at 6:41 pm #56289

@innocsrlee would you mind elaborating on your solution, or posting a Git Gist?

We’re having the same issue with wanting to sell pay-per-post but assigning them to a user’s ID. Custom capabilities by ID sounds like a possible solution, be good to see how you tackled it.

More info on what we’re trying to achieve: http://www.s2member.com/forums/topic/specific-post-access-assign-to-users-id/

  • This reply was modified 3 years, 4 months ago by  Kevin Murphy.
Posted: Friday Aug 16th, 2013 at 11:03 am #56033

Good to know Bruce, we’ll consider our options and use the above as a last resort. The CSV upload isn’t so much the problem, if we were to enable the hooks we’d still have to loop through each user individually and add via the CRM api — so there may be an easier way to achieve this. Will have a think.

Thanks!

Posted: Wednesday Aug 14th, 2013 at 1:47 pm #55786

Also, as a side note, wouldn’t it be wise to have a header row for the CSV upload? Then you could simply include the fields you want and they’d be automatically synced.

Posted: Thursday Jul 18th, 2013 at 12:37 pm #53643

It’s the default theme I’m using, 2012 I think. It’s no big deal so long as I know what to avoid, but shortcodes generally ignore any content above/below them surely. ‘Tis odd.

Posted: Tuesday May 21st, 2013 at 12:54 pm #50295

Hi Bruce, no worries I assumed this would be the case. Perhaps we’ll be able to do something similar and create our own custom fields which we can add a timestamp to, or using the S2 member hook you’ve mentioned before.

Thanks.

Posted: Friday Apr 26th, 2013 at 1:46 pm #48508

MailChimp won’t tell s2Member when a User is deleted, so there’s no way for s2Member to do that. As far as double opt-in goes, s2Member can only control the box that is displayed on your site. You can’t disable the opt-in message MailChimp sends through s2Member. I believe there is an option for this in MailChimp, though.

Yep, I’ve already put in my vote for tighter Mailchimp API integration as disabling the double opt in is definitely possible with the API, as is creating static groups on the fly (rather than having to have pre-set ones). I’m pretty certain you can delete an account via the API also.

Failing that, perhaps having some way to show deleted users (if there isn’t already?), so we can cross reference this on other services — for instance, if we were to sync with custom code, how can we tell between these two:

  • The user the hasn’t been synced on signup for some reason
  • The member has deleted their account

It is supposed to change to a PayPal button when you select PayPal. Sounds like there is a JavaScript error on this page. Could you send us a link to your Pro Form?

I can do once it’s set up again, using the bog standard buttons for now.

Thanks!

Posted: Friday Apr 26th, 2013 at 1:37 pm #48507

Thanks Bruce, that gives us a good starting point. The only thing is the Mailchimp stuff:

You noted that email addresses could be used as Usernames. If you did it that way, WordPress won’t allow you to change it.

If we’re using the default Mailchimp S2 Member signups/upgrades, it’ll be using the email field, which is editable — so unless we replaced everything with custom scripts, we’d still need to disable both the username and email (and edit by admin if required). Like I say I guess JS could be used to add “disabled” to the inputs, though perhaps not the best way.

Posted: Sunday Apr 7th, 2013 at 7:19 pm #46817

I guess I shall have to wait and see what you’re cooking up then, would be helpful to have a roadmap to save hacking away on features that’ll be in the new version ;)

For support email notifications, I’m having to check in every so often to see if there’s been any replies. Suppose I could change the email for the time being.

Thanks!

Posted: Friday Apr 5th, 2013 at 12:59 pm #46716

Ah, yes. That’s it. All the errors and the odd character issues have now disappeared with debug set to false — it might catch others out as it looks a bit WTH when you’re first setting up so good to hear you’re working on it!

Any timeframe for the new S2 member? It’d be great to get a sneak peek as we’re not going live for 5 months yet, although I expect it’s going to be backwards compatible.

Is there anyway I can add a secondary email notification address? I’m using the clients account.

Thanks,

Rob

Posted: Thursday Apr 4th, 2013 at 11:05 am #46619

Ok, so I’ve now tested with the default Twenty Eleven theme and the same thing is happening, I’ve deleted the .htaccess file and generated the new one with basic permalink rewrites only. Some more errors that I’m seeing when I’ve changed the template:

Notice: Undefined variable: cache_needs_updating in ~/Sites/domain/wordpress/html/wp-content/plugins/s2member/includes/classes/cache.inc.php on line 94

Warning: Cannot modify header information - headers already sent by (output started at ~/Sites/domain/voluntaryarts/wordpress/html/wp-content/plugins/s2member/includes/classes/cache.inc.php:94) in ~/Sites/domain/wordpress/html/wp-includes/option.php on line 568

Warning: Cannot modify header information - headers already sent by (output started at ~/Sites/domain/wordpress/html/wp-content/plugins/s2member/includes/classes/cache.inc.php:94) in ~/Sites/domain/wordpress/html/wp-includes/option.php on line 569

Also, I’m getting some weird character bugginess (see image below).

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

Old Forums (READ-ONLY): The community now lives at WP Sharks™. If you have an s2Member® Pro question, please use our new Support System.

Contacting s2Member: Please use our Support Center for bug reports, pre-sale questions & technical assistance.