Mike (Volunteer Moderator)

My Latest Replies (From Various Topics)
Author | Replies |
---|---|
Author | Replies |
Posted: Thursday Aug 1st, 2013 at 10:54 am #54601 | |
![]() |
|
I just took a quick look at the source code which leads to this error.
See also: http://wordpress.org/support/topic/wp_memory_limit-vs-wp_max_memory_limit |
|
Posted: Thursday Aug 1st, 2013 at 10:31 am #54597 | |
![]() |
|
Nick. Please submit log files via Private Contact Form.
Please use this instead: s2Member® » Private Contact Form |
|
Posted: Thursday Aug 1st, 2013 at 10:28 am #54596 | |
![]() |
|
I don’t see anything in your reply about the category. Did you check that out? |
|
Posted: Wednesday Jul 31st, 2013 at 11:18 pm #54557 | |
![]() |
|
Try adding a new source like this. Does it work then?
|
|
Posted: Wednesday Jul 31st, 2013 at 10:41 pm #54555 | |
![]() |
|
That is a serliazed array of payment times. A couple of things you can do.1. When you do an export, choose the friendlier format for output. 2. Instead of going by this column, it’s better to go by the Role column and/or the Custom Capabilities column in the export file. If a user is NOT a subscriber they are likely a customer at one of these Roles. See: Knowledge Base » s2Member® Roles/Capabilities |
|
Posted: Wednesday Jul 31st, 2013 at 10:33 pm #54554 | |
![]() |
|
Can you reproduce this on a clean test installation of WordPress? It sounds like emails are going out in HTML format, and that’s not right. All emails should be going out in plain text. If they are going out in HTML, this would explain the missing line breaks, because HTML would expect |
|
Posted: Wednesday Jul 31st, 2013 at 2:44 pm #54529 | |
![]() |
|
Our developers looked into this and investigated your log files.We’re seeing an abnormal ratio of failed payments vs. new signups in your log files. Do you deal with a lot of payment failures? Is your particular business model prone to fake credit cards or high in fraud? Anything like that? Regarding the signups followed by an immediate cancellation.Our lead developer looked into this and he showed me several log entries that look like this.
Followed almost immediately by a cancellation IPN from PayPal.
Note that it says: ‘initial_payment_status’ => ‘Failed’,. This is happening because the initial payment is failing almost immediately after the customer completes checkout. You can prevent this from ever happening by switching s2Member® over to Real Time/Direct Pay mode when it comes to Recurring Billing. Please see: Dashboard -› s2Member® -› PayPal® Options -› Account Details and look at this configurable option. There is further documentation on this in your Dashboard. |
|
Posted: Wednesday Jul 31st, 2013 at 2:28 pm #54527 | |
![]() |
|
If s2Member® were running on that child blog you could use Shortcode Conditionals made possible by s2Member®. Since it sounds like it won’t be, I would suggest that you run ezPHP (also developed by us); and this will make it possible to do something like this inside a Post or Page.
See: Knowledge Base » ezPHP Plugin for WordPress® |
|
Posted: Wednesday Jul 31st, 2013 at 12:37 pm #54520 | |
![]() |
|
Yes, because if s2Member® is not even running there, you won’t have it’s functionality. However, you can use WordPress® itself to test permissions across blogs and that works just fine. So for instance, you might have an MU plugin file that looks something like this.Please create this directory and file:
|
|
Posted: Wednesday Jul 31st, 2013 at 12:03 pm #54516 | |
![]() |
|
This is the simplest way to handle that. Please see this API Function in the s2 Codex. See also: http://codex.wordpress.org/Function_Reference/current_user_can_for_blog |
|
Posted: Wednesday Jul 31st, 2013 at 10:30 am #54505 | |
![]() |
|
I took a quick look. When I am redirected I’m seeing this in the address. These are called MOP Vars by s2Member® and they tell the tale about why the redirection occurred. See also: Dashboard -› s2Member® -› API / Scripting -› Membership Options Page Variables (MOP Vars) From the following screenshot (click to enlarge please); it indicates that this post (calendar page) is inside a protected category that requires Level 1 access; based on your configuration of s2Member®. If problems persist, please post a screenshot of all of your coniguration sub-panels here. See: Dashboard -› s2Member® -› Restriction Options http://d1v41qemfjie0l.cloudfront.net/s2member/uploads/2013/07/7-31-2013-6-26-50-AM.png |
|
Posted: Wednesday Jul 31st, 2013 at 9:22 am #54501 | |
![]() |
|
s2Member® is unaffected by this change, because it uses an API Signature and not those certificates. Our tests against the Sandbox indicate that no change is necessary and this should not impact s2Member site owners. |
|
Posted: Wednesday Jul 31st, 2013 at 9:19 am #54500 | |
![]() |
|
Posted: Wednesday Jul 31st, 2013 at 9:10 am #54497 | |
![]() |
|
This video goes over some of this and offers some helpful tips that I think you’ll benefit from. Also, please post the full URL (including all of the query string variables) that appear in your address bar when you are redirected to the Membership Options Page. Those tell the tale, and with that we can be more specific for you. |
|
Posted: Wednesday Jul 31st, 2013 at 9:07 am #54496 | |
![]() |
|
It certainly sounds possible to me :-) It does sound you like you MIGHT need to adjust the defaults a bit though. Please take a look at this article which covers tweaks to the default Roles/Capabilities that ship with s2Member®. |
|
Posted: Wednesday Jul 31st, 2013 at 9:03 am #54494 | |
![]() |
|
Thanks for your purchase! :-) |
|
Posted: Wednesday Jul 31st, 2013 at 9:02 am #54493 | |
![]() |
|
You can get a list of all users at that Level like this.
See also: http://codex.wordpress.org/Function_Reference/get_users As for geolocation, you might try something like this. |
|
Posted: Wednesday Jul 31st, 2013 at 8:58 am #54492 | |
![]() |
|
The key with those is to be sure that you’re testing from within the action hook and not before. In your code, this line is correct.
Once that action is fired, and your routine runs; the s2Member® API Constants should be available. Are you sure that when you tested it was from within that function and after the action was fired by WordPress? |
|
Posted: Wednesday Jul 31st, 2013 at 8:51 am #54491 | |
![]() |
|
Very welcome :-). If you get a moment (we know you’re busy), but if you can do this I would really appreciate it! Please register @ WordPress.org and rate s2Member® NOTE: If you vote @ WordPress.org & LIKE us on Facebook, please reply back in the s2Member® Forums with a link to your nice comments (just to let us know). The company also has a way of saying thanks for this :-) |
|
Posted: Wednesday Jul 31st, 2013 at 8:50 am #54489 | |
![]() |
|
This explains the lack of log files in the Dashboard. This came out after that release. I suggest updating to the latest release to be sure we’re all on the same page when it comes to support. Otherwise, please take a look inside this directory on the server for your log files: /wp-content/plugins/s2member-logs/
|
|
Posted: Wednesday Jul 31st, 2013 at 8:39 am #54487 | |
![]() |
|
That’s not an s2Member® Pro feature. However, I’ve run s2Member® Pro together with this plugin and it works beautifully. Check out: http://wordpress.org/plugins/social-connect/ |
|
Posted: Wednesday Jul 31st, 2013 at 8:35 am #54486 | |
![]() |
|
Very welcome :-) Yea, I would go with PayPal Pro if I were you. It’s worth every dime. You’ll get more sales overall with that service because everything works better, and you expand your customer’s options during checkout. You’d be amazed how much better a customer will respond to paying you on-site via Pro Forms as opposed to going throug another service and then being returned to your site afterwards. ~ Good luck :-) Sorry to hear you had this trouble. |
|
Posted: Wednesday Jul 31st, 2013 at 8:29 am #54485 | |
![]() |
|
Thank you. Can you post the underlying s2Member Shortcode that you’ve used for that Pro Form please? |
|
Posted: Wednesday Jul 31st, 2013 at 8:26 am #54484 | |
![]() |
|
Closing this. I’m sorry, but this is BuddyPress-specific.
~ Please see: BuddyPress.org. |
|
Posted: Wednesday Jul 31st, 2013 at 8:25 am #54483 | |
![]() |
|
What version of s2Member® are you running please?Here are some screenshots of the logging area of the Dashboard in the latest release.
It sounds like you are sending emails out to folks, who may or may not be existing users on your site and inviting them to signup. If they are already an existing user, they will get an error during checkout (if cases where they are NOT logged into your site yet); because they may attempt to signup again under the same email address. Do I have this correct? If so, I would suggest using the modify=”1″ Shortcode Attribute on your Pro Forms where there is an expectation for an existing user to upgrade their existing account. That attribute will force them to login before completing checkout. This way their existing account can be upgraded and you won’t have redundant accounts and/or some of the confusion you mentioned. Please see: Dashboard -› s2Member® -› PayPal® Pro Forms -› Shortcode Attributes (Explained) |