About: Brad

It is somewhat surprising that no one has posted a reply to my post after 3 days, not even to ask a question or clarify. In the meantime I have located the other piece of the puzzle. Jason added this line to the API / Notifications, Registration Notifications section:

http://www.mywebsite.com/webwoms.php?aid=%%cv2%%&email=%%user_email%%&fname=%%user_first_name%%&lname=%%user_last_name%%&s=JIECSKSLWETEDK

Note: mywebsite.com was used for this example. This is not the actual live URL.

So, even if I need 8 files (webwoms1.php, webwoms2.php, etc.) to change the aid value to match the autoresponder assigned to the level of the new registration and/or 8 input lines in the API / Notifications, Registration Notifications section, I still need to know how to make the new registration level number match an aid value (simply an autoresponder number on my system). This is basically all I need help with – how can I integrate the new registration level number to execute a specific file or how can I integrate the new registration level number to execute a modified php file that will determine the aid value based upon the new registration level number?

Can someone please help me with this?

• This reply was modified 4 years ago by  Brad. Reason: Added question mark to the question

Hello Jason,

As you recommended, I ran the role reset utility. However, I still receive the level 4 registration notification email and I still receive the level 4 characteristics in our custom software when creating a new Admin user account.

Keep in mind that the new admin user account does in fact operate as a level 9 within WordPress and s2Member everywhere else that I can think to check. Whatever that trigger is that generates the registration notification email at level 4 is apparently the same trigger data that my developer used to assign characteristics in our custom software.

Also, as I mentioned earlier, I tested this with the same results on a couple other sites (zero custom software) with the same results. You can see here –

That the role reset utility ran successfully showing 9 member levels on a second installation that has nothing but a handful of plugins. However, the notification email still says:

—–Original Message—–
From: WordPress
Sent: Sunday, May 20, 2012 9:13 AM
To: support@sitesteering.net
Subject: ( s2Member / API Notification Email ) – Registration

( s2Member / API Notification Email ) – Registration

role: administrator
level: 4
ccaps:
auto_eot_time:
user_first_name: Brad

I would be very surprised if you cannot duplicate this.

Thanks for your reply Raam.

Our software does not modify s2Member at all. We take s2member result data and then use that to create events in our software.

As a test, this morning I tested the same scenario in two other WordPress installations. Both fairly clean installs with nothing other than a handful of plugins. I modified the wp-config files to create the 9 membership levels, and then created another Admin account. There was no interfaced software to trigger, but the notification email reports that a level 4 account was created. Obviously, since Admin is supposed to be elevated to the highest level, this email should indicate that a level 9 was created. I think that you can easily perform this test on a WordPress installation to see for yourself, but make sure that your notification email is turned on. This is pretty clearly a minor s2Member glitch.

Importantly, the glitch does not affect the admin functionality as near as I can tell. I tried to change the admin account to s2Member level 9 as another test, but I lose admin functionality, and so had to switch it back. This is as closely as I can identify the glitch.

Please let me know how to fix/correct this issue, otherwise I will probably end up having to pay my developers to change our trigger points in an effort to avoid a glitch in level assignment.