|
|
Glad you figured it out. Thanks for the update! :)
|
|
|
Sorry, was away the past week. Jason and Bruce looked into this and couldn’t find that s2Member was doing it. I’m glad you narrowed it down go the WP you’re running. It’d be good to make sure that you have a good copy of the WP files in your site, verify that wp-login.php is not altered in some way.
|
|
|
So, is it just the s2Member signup confirmation email not being sent, but the WP new user one is?
Did you check the spam folder to see if the signup confirmation is there?
Do you have logging enabled? What does it mention the confirmation email being sent in one of the log entries for the transaction? [hilite path]Dashboard -› s2Member® -› Log Files (Debug) -› Logging Configuration[/hilite]
Have you followed all the suggestions in these?
Knowledge Base » Troubleshooting Email Delivery Problems
Knowledge Base » Common Troubleshooting Tips
|
|
|
|
|
|
|
I can’t tell much from the info there… But this seems to be unique to your installation. We haven’t seen this before during testing or from any other site owner that I remember.
Could you please try these? Knowledge Base » Common Troubleshooting Tips :)
|
|
|
$request = array ("x_method" => "cancel", "x_subscription_id" => $subscription_id);
$subscription_id seems to not be set, so there’s no subscription to cancel.
|
|
|
if ($my_field_data="Parent") {
You’re not comparing, you’re assigning that value to the var. You need to use two equal signs.
http://www.php.net/manual/en/language.operators.assignment.php
http://www.php.net/manual/en/language.operators.comparison.php
|
|
|
I still got a 414. I guess the webhost didn’t raise the limit enough, that URL has 692 characters. The limit should be quite above that in case another URL has more characters in the future.
|
|
|
|
|
|
|
Thanks for the info. So you set the redirection after login in your widget settings, but it’s not working, is that it?
Could you try all these? Knowledge Base » Common Troubleshooting Tips
|
|
|
I just got a reply from Jason. He confirmed that it’s s2Member escaping the HTML when displaying the field in a public profile. I was displaying the field with a shortcode or PHP, and in those cases, since you’re manipulating the data, it’s not escaped and you’re responsible for the risk of having HTML there. I had not noticed it in my installation because I don’t have BuddyPress, so I could only test as I explained above, but when displayed in the BuddyPress public profiles, s2Member escapes the HTML to prevent potential trouble. This is what Jason replied:
This would be a major security issue. By default, s2Member escapes any HTML code before output in any profile view.
See: /s2member/includes/custom-reg-fields.inc.php
If the site owner would like to modify these lines, I recommend they allow only basic HTML (e.g. specific tags) that would be considered safe (or safer than others at least). Perhaps just a link tag.
if($_editable_context === "profile-view")
$gen = strip_tags((string)$_value, "<a>");
See: http://php.net/strip_tags
|
|
|
Well, the cancellation would cause a demotion to Level 0 normally, so you could have a MailChimp list for Level 0 with that good-bye email. [hilite path]Dashboard -› s2Member® -› API / List Servers -› MailChimp® -> Level 0[/hilite]
Or you could do the good-bye email without MailChimp, instead use the cancellation notification to load a script that emails the good-bye message. [hilite path]Dashboard -› s2Member® -› API / Notifications -› Cancellation Notifications[/hilite]
|
|
|
Sure. I’ll forward this to Elizabeth in Billing.
|
|
|
Could you show me the shortcode you’re using, please?
Are you using a custom template for the pro-form?
I can take a look at your page with the pro-form and your configuration, if you send me the site’s info. Please leave me a reply here if you do, so I look for it. Thanks. s2Member® » Private Contact Form
|
|
|
But after the payment, Signup Confirmation Email is not sent…
Is the New User email with the login credentials being sent fine after registration? If not, then please try the tips here: Knowledge Base » Troubleshooting Email Delivery Problems
If the New User email is sent, but s2Member’s isn’t, could you make sure it’s not ending up in the spam box? You can improve inbox delivery customizing the Signup Confirmation email so it’s unique to your site. [hilite path]Dashboard -› s2Member® -› ccBill® Options -› Signup Confirmation Email[/hilite]
If that’s not it, could you enable logging, and after another problem transaction, review the log to see any mention of an error for that transaction? Does it mention the Signup Confirmation Email being sent successfully?
How can I send Signup Confirmation Email by manually?
You can generate a Registration Access Link and email it to him from your email account. See: [hilite path]Dashboard -› s2Member® -› ccBill® Buttons -› Registration Access Links[/hilite]
|
|
|
You can remove the checkbox from here: [hilite path]Dashboard -› s2Member® -› API / List Servers -› Registration Double Opt-In Box[/hilite]
The user would still be sent an opt-in confirmation email by MailChimp and he may not show up in your list before he’s clicked on the confirmation link.
|
|
|
You’d need a counter, but s2Member doesn’t have one. You could create save an option in WordPress with your count, and add to it with ever new free registration using the registration notification, I guess.
So your notification would load a custom script, that loads WP and then you update the counter. Then, where you have the free registration form to signup at the higher level, before showing it you check the counter and if it’s higher than 200, then stop giving the upgrade and just register them at level 0 as usual.
These would help:
[hilite path]Dashboard -› s2Member® -› API / Notifications -› Registration Notifications[/hilite]
Knowledge Base » Hacking s2Member® Via Hooks/Filters
http://adambrown.info/p/wp_hooks/hook/wp_loaded
[hilite path]Dashboard -› s2Member® -› PayPal® Pro Forms -› Free Registration Forms[/hilite]
http://codex.wordpress.org/Function_Reference/add_option
http://codex.wordpress.org/Function_Reference/get_option
http://codex.wordpress.org/Function_Reference/update_option
[hilite path]Dashboard -› s2Member® -› API / Scripting -› Advanced PHP Conditionals[/hilite]
|
|
|
Have you read this and followed its advice? Knowledge Base » Unable to Verify $_POST Vars Error
Got it on the server scanner results. The warning you get about the memory limit would not be causing you this problem.
If the above article doesn’t help, then could you please try these? Knowledge Base » Common Troubleshooting Tips
|
|
|
If PayPal doesn’t let you edit the subscription profile to add the custom value with your domain name, then I think you could try to solve this with an IPN script, which will fix the custom value before forwarding the notification to s2Member.
You can find a sample IPN script in the s2Member Pro Extras zip file, in your Account page. http://www.s2member.com/account/
|
|
|
Ah, yes, if you mean the EOT time set by s2Member, it’s at the end of the paid time. See: [hilite path]Dashboard -› s2Member® -› Authorize.Net® Options -› Automatic EOT Behavior[/hilite]
*Some Hairy Details* There might be times whenever you notice that a Member’s Subscription has been cancelled through PayPal®… but, s2Member continues allowing the User access to your site as a paid Member. Please don’t be confused by this… in 99.9% of these cases, the reason for this is legitimate. s2Member will only remove the User’s Membership privileges when an EOT (End Of Term) is processed, a refund occurs, a chargeback occurs, or when a cancellation occurs – which would later result in a delayed Auto-EOT by s2Member.
s2Member will not process an EOT until the User has completely used up the time they paid for. In other words, if a User signs up for a monthly Subscription on Jan 1st, and then cancels their Subscription on Jan 15th; technically, they should still be allowed to access the site for another 15 days, and then on Feb 1st, the time they paid for has completely elapsed. At that time, s2Member will remove their Membership privileges; by either demoting them to a Free Subscriber, or deleting their account from the system (based on your configuration). s2Member also calculates one extra day (24 hours) into its equation, just to make sure access is not removed sooner than a Customer might expect.
So the user may still have access because he hasn’t reached the end of the time he paid, but the subscription may already have ended in the payment gateway.
|
|
|
The settings “Membership EOTs also Remove all Custom Capabilities” and “EOT Grace Time (in seconds)” were added in v130220 (Feb 20, 2013).
You can review the changelog here: s2Member® » Unified Changelog
|
|
|
The log entry mentions the email having been sent, so s2Member is doing what it has to do and is getting no errors.
5 => 'Signup Confirmation Email sent to: "xxxxxxx <xxxxx@yyyyyyyyyyy.com>.',
Did you verify they’re not being marked as spam? You can try personalizing the Signup Confirmation email to make it unique to your site. This helps with inbox delivery. [hilite path]Dashboard -› s2Member® -› PayPal® Options -› Signup Confirmation Email[/hilite]
Is your New User email (the one with the login credentials) being sent when the user registers? If not, could you please try these? Knowledge Base » Troubleshooting Email Delivery Problems
|
|
|
Thanks for the feedback. I’ll add this to the feature requests and let Jason know about it. :)
|
|
|
Like I said, we’re not using BuddyPress, just bbPress. But I’ll ask Jason his opinion. :)
|
|
|
but with buddypress a normal link is clickable. With your form field, it is not. It has to be something to do with your code.
It’s the URL that’s clickable in the BP field, and that’s because they seem to parse URLs and autolink them, but it’s not doing it for s2 profile fields. The problem is the way BP is parsing this, not the value stored in the s2 field.
I don’t think removing BP would be the solution, because that’s what’s allowing you to have public profiles. Instead I’d work on customizing BP a bit so it doesn’t break the HTML, encoding parts of it (like [hilite mono]<[/hilite] or [hilite mono]>[/hilite]) to their HTML entities so they are displayed.
Have you asked in their forums how to prevent this encoding? http://buddypress.org/support/
I’ll ask Jason his opinion too.
|
Pre-Sale FAQs
Video Tutorials
Community Forum
Knowledge Base
News/Updates
s2 Codex / Docs
GPL v2 License
Contact A Human
About Us
Our Customers
Support Policy
Privacy Policy
Old Forums (READ-ONLY): The 
