Jason (Lead Developer)

My Latest Replies (From Various Topics)
Author | Replies |
---|---|
Author | Replies |
Posted: Thursday Feb 21st, 2013 at 9:45 am #42723 | |
![]() |
|
Details received. Thank you!I was unable to gain Dashboard access however.
|
|
Posted: Thursday Feb 21st, 2013 at 9:25 am #42720 | |
![]() |
|
Thanks for the follow-up :-)On your installation this error is caused by an invalid PDT Identity Token. Please let us know if problems persist :-) |
|
Posted: Thursday Feb 21st, 2013 at 9:11 am #42716 | |
![]() |
|
Thanks for reporting this important issue.Yes, this is a bug. It’s been fixed for the next maintenance release. Coming later today. BUG FIX: Next maintenance release…
(s2Member/s2Member Pro) Bug Fix (Issue #43) A bug first introduced in the last release of s2Member® v130220 was preventing Administrative New User Notifications from being sent by s2Member®.
|
|
Posted: Thursday Feb 21st, 2013 at 8:52 am #42715 | |
![]() |
|
Thanks for the follow-up :-)No, that’s normal to have that; so long as they are loading up. It sounds like they’re not though :-( Please submit a Dashboard login and we’ll run diagnostics on your installation for you. Please use: s2Member® » Private Contact Form ~ Thanks! |
|
Posted: Thursday Feb 21st, 2013 at 8:44 am #42714 | |
![]() |
|
Hmm. I wonder if this is AWeber blocking consecutive emails to the same person. |
|
Posted: Thursday Feb 21st, 2013 at 8:39 am #42712 | |
![]() |
|
@ Jason eH Thank you for the KUDOS :-) |
|
Posted: Thursday Feb 21st, 2013 at 8:13 am #42707 | |
![]() |
|
Thanks for your patience.This is caused by a parsing issue against the field IDs. BUG FIX: Coming in the next maintenance release…
* (s2Member/s2Member Pro) **Bug Fix (Issue #41)** Custom Registration/Profile Fields with an ID that ended with `-[0-9]+` or `_[0-9]+` was sometimes failing JavaScript validation due to a parsing issue.
For now, you can resolve the issue on your installation by changing your Custom Registration/Profile Field IDs that end with disclaimer_3, disclaimer_4, etc — to disclaimer3, disclaimer4, etc (i.e. removing the underscores). Please change any IDs that end with _[0-9] or -[0-9] (by removing the dash or underscore). This will be fixed in the next maintenance release. Thanks for reporting it! |
|
Posted: Thursday Feb 21st, 2013 at 7:56 am #42705 | |
![]() |
|
Details received. Thank you!~ Investigating now. |
|
Posted: Thursday Feb 21st, 2013 at 4:02 am #42681 | |
![]() |
|
Thanks for reporting back on this. Much appreciated!
|
|
Posted: Thursday Feb 21st, 2013 at 3:59 am #42680 | |
![]() |
|
Thanks for your inquiry. ~ We appreciate your patience :-)The error that you’ve reported comes from ClickBank, and I’m seeing this error even on the default checkout page. See: http://1weekpas.janbella.pay.clickbank.net/ Please check Product ID# 1 in your ClickBank acct. and confirm this Product is still active. Thanks! |
|
Posted: Thursday Feb 21st, 2013 at 3:51 am #42678 | |
![]() |
|
Thanks for your patience.Unable to run a test transaction on your installation. An s2Member Pro Form Shortcode does not provide any way to accept payment on this installation for some reason. Have you made modifications to s2Member? Does not work properly on this installation:
See “Test Page (by Jason Caldwell)” on your installation. Saved as a Draft. |
|
Posted: Thursday Feb 21st, 2013 at 3:38 am #42677 | |
![]() |
|
Thanks for the follow-up :-)Running tests now. Please stand by. Thanks! |
|
Posted: Thursday Feb 21st, 2013 at 3:19 am #42676 | |
![]() |
|
Thanks for the heads up on this thread :-)
This feature was added in the latest release of s2Member®.
See: s2Member® » Unified Changelog %%role%% is now a valid Replacement Code. |
|
Posted: Thursday Feb 21st, 2013 at 3:18 am #42675 | |
![]() |
|
Thanks for your inquiry. ~ We appreciate your patience :-)We find the quickest way to resolve this issue, is to check your s2Member® log files. If you need assistance with this, please post a Dashboard login privately so we can investigate. |
|
Posted: Thursday Feb 21st, 2013 at 3:14 am #42673 | |
![]() |
|
Thanks for the heads up on this thread :-)
Please see this related article.
http://www.s2member.com/forums/topic/cache-needs-updating-error/#lead-topic-41260 The solution is to put your installation of PHP and WordPress® into production mode. You are currently running in DEBUG mode; which is why you are seeing NOTICES from PHP. |
|
Posted: Thursday Feb 21st, 2013 at 3:11 am #42671 | |
![]() |
|
Thanks for your inquiry. ~ We appreciate your patience :-)You can provide logged-in Users/Members with a link to /wp-signup.php See also: Dashboard -› s2Member® -› Multisite (Config) |
|
Posted: Thursday Feb 21st, 2013 at 3:08 am #42669 | |
![]() |
|
Thanks for the heads up on this thread :-)
See: wp_login_url() for this. You could use the
$redirect parameter.
|
|
Posted: Thursday Feb 21st, 2013 at 3:05 am #42668 | |
![]() |
|
Thanks for the heads up on this thread :-)
This sounds like mild database corruption (an incomplete migration). I would suggest that you go back to the developer that assisted you. This really falls outside the scope of our support. It sounds like your database did not get fully migrated over; or something was corrupted during the transition in some way. |
|
Posted: Thursday Feb 21st, 2013 at 3:00 am #42666 | |
![]() |
|
Thanks for the heads up on this thread :-)The current_user_is() function, is an API Function provided by s2Member®. So if s2Member® is disabled (which it IS momentarily during an update of the plugin); you will see this error. The solution is to disable your s2-hacks.php file during the update. Or, to use a function_exists check before you use this function. Ex: |
|
Posted: Thursday Feb 21st, 2013 at 2:56 am #42665 | |
![]() |
|
Thanks for the follow-up :-)Please post a Dashboard login privately and we’ll inspect your log files overall. Maybe we will spot something for you. Thanks! Please use: s2Member® » Private Contact Form |
|
Posted: Thursday Feb 21st, 2013 at 2:53 am #42664 | |
![]() |
|
This is now a configurable option in s2Member v130220. |
|
Posted: Thursday Feb 21st, 2013 at 2:53 am #42663 | |
![]() |
|
Thanks for your inquiry. ~ We appreciate your patience :-)Are you running WordPress® from a sub-directory perhaps? Please let us know if problems persist :-) |
|
Posted: Thursday Feb 21st, 2013 at 2:28 am #42660 | |
![]() |
|
What Bruce just said is correct. However, if an existing User/Member makes a Specific Post/Page purchase; s2Member® will keep a record of that on file. This is how the Shortcode example that I posted previously is possible. s2Member keeps a list of references of here.
|
|
Posted: Thursday Feb 21st, 2013 at 2:25 am #42659 | |
![]() |
|
Thanks for the follow-up :-)
Our average response time is 24-48 hours; tickets are answered in the order they were received. Please let us know what PayPal® reports back with. If s2Member® is not granted permission to make API calls, there’s not much we can do (for now). Once s2Member has permission, you should have something to report back with.
No, you won’t need to use hosted checkout pages with Pro Forms. Pro Forms keep things on-site; so that everything is processed through payment gateway APIs. The only exception to this, is with PayPal Express Checkout, where a customer chooses to pay you with PayPal; and they intentionally leave your site to complete checkout via PayPal.com. |
|
Posted: Thursday Feb 21st, 2013 at 2:18 am #42657 | |
![]() |
|
Thanks for the follow-up :-)What is your server’s IP address please? I will verify this with FireHost® (our hosting company). |