About: Iaeon

Hi Cristian

It seems as though you are correct and it should read useraction=commit – This is what page 28 of the document that is linked above says at any rate. Also explains further how the mechanism works.

I look forward to hearing back on this

Hi Christian

A trial Shortcode I am testing is:

[s2Member-Pro-PayPal-Form level="1" ccaps="" desc="$0.10 GBP / One Time (for 1 day access, non-recurring, no trial)" ps="paypal" lc="" cc="GBP" dg="0" ns="1" custom="staging.the-sra.org.uk" ta="0" tp="0" tt="D" ra="0.10" rp="1" rt="D" rr="BN" rrt="" rra="2" accept="paypal" accept_via_paypal="paypal" coupon="" accept_coupons="1" default_country_code="" captcha="0" /]

Settings:
Enable s2Member’s Auto-EOT System? – Yes (enable)
Membership EOT Behavior (Demote or Delete)? – Demote (convert to free)
Membership EOTs also Remove all Custom Capabilities? – Yes
EOT Grace Time (in seconds): – 120 [I am testing!]
Refunds/Reversals (trigger Immediate EOT)? – always trigger
Fixed-Term Extensions (Auto-Extend)? – Yes, default; extends

paypal.api.log:
a long entry which seems to be OK dated and ending as follows

-------- Output string/vars: ( Mon Apr 22, 2013 11:52:10 am UTC ) --------
  'PAYMENTINFO_0_ERRORCODE' => '0',
  'PAYMENTINFO_0_ACK' => 'Success',

==followed by== 
LOG ENTRY: Mon Apr 22nd, 2013 @ precisely 11:52 am UTC
PHP v5.3.3 :: WordPress® v3.5.1 :: s2Member® v130221 :: s2Member® Pro v130221
Memory 29.11 MB :: Real Memory 29.50 MB :: Peak Memory 29.14 MB :: Real Peak Memory 29.50 MB
mydomain.com/join-options/test-2/?s2member_paypal_xco=s2member_pro_paypal_checkout_return&token=xxxxtokenherexxx&PayerID=xxxpayeridherexxx
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/536.29.13 (KHTML, like Gecko) Version/6.0.4 Safari/536.29.13
-------- Input vars: ( Mon Apr 22, 2013 11:52:10 am UTC ) --------
array (
  'PROFILEID' => 'xxxprofileidherexxx',
  'METHOD' => 'ManageRecurringPaymentsProfileStatus',
  'ACTION' => 'Cancel',
  'VERSION' => '71.0',
  'USER' => 'xxxuseridherexxx',
  'PWD' => 'xxxpwdherexxx',
  'SIGNATURE' => 'xxxsignatureherexxx',
)
-------- Output string/vars: ( Mon Apr 22, 2013 11:52:11 am UTC ) --------
TIMESTAMP=2013%2d04%2d22T11%3a52%3a11Z&CORRELATIONID=xxxidxxx&ACK=Failure&VERSION=71%2e0&BUILD=5650305&L_ERRORCODE0=11552&L_SHORTMESSAGE0=Invalid%20profile%20ID&L_LONGMESSAGE0=The%20profile%20ID%20is%20invalid&L_SEVERITYCODE0=Error
array (
  'TIMESTAMP' => '2013-04-22T11:52:11Z',
  'CORRELATIONID' => 'xxxidxxx',
  'ACK' => 'Failure',
  'VERSION' => '71.0',
  'BUILD' => '5650305',
  'L_ERRORCODE0' => '11552',
  'L_SHORTMESSAGE0' => 'Invalid profile ID',
  'L_LONGMESSAGE0' => 'The profile ID is invalid',
  'L_SEVERITYCODE0' => 'Error',
  '__error' => 'Error #11552. Invalid profile ID. The profile ID is invalid.',

===
So it seems as though the profile ID is invalid. Would this be to do with testing from a staging subdomain or for another reason? Seems to work on the live site for Event Espresso (events booking plugin also in use). Also as I said before it seems to be fine when a new user is signing up which is odd… No entry from this existing user test (which fails to update the EOT) in the paypal-rtn.log or reg-handler.log There are entries in s2-http-api-debug.log

Thanks for your help.

Hi Eduan

Sorry, it was a bit shorthand… A Directory: Pages where a visitor to a website can see the names and selected details of registered users who have asked to be included in such a searchable list. Probably also organised in categories (see connections plugin for the gist of something like this)

Custom fields: Additional data about registered users some of which may be included in the directory. As I have posted over the last year the spec I have includes about 35 custom fields (or columns). This makes me very wary about adding it to the current S2member custom field handling because of the way the such ‘extra’ data is currently mashed together.

I know that in principal a new structure for custom fields has been in the works for ages. I believe that the same can be said for a directory feature. As I said though I am now out of time to wait any longer for an S2 release, so looking for inspiration of how best to handle this with one or more third party plugins. I wish this was not the case!

see also http://www.s2member.com/forums/topic/public-members-directory-and-custom-fields/
http://www.s2member.com/forums/topic/wp_usermeta-constraints/
and most other posts under my name.

Hi Raam

The core question I have is about likely ease of migration. Thinking about it I would assume that if / when the custom fields are handled differently by S2Member that S2Member will likely offer a graceful upgrade path for customers who have custom data in the ‘old’ format… Indeed I might imagine that this is a time-consuming aspect delaying any beta, but hey, that would be idle speculation!

Excellent news – breath bated in anticipation. Hopefully will not become too oxygen deprived in waiting for this release!

Hi Raam Thanks for your reply.

You do not say if there are any third party plugins that are known to work nicely alongside s2member to hold additional profile data.

I have to say though that if the timeline to the release is about a month I am tempted to hold on if I can delay things that long. Neater to be integrated …

Are you able to reveal if any querying / reporting is likely to be included?