Page 1 of 1

s2Member v3.2.7 ( new Custom Fields )

PostPosted: September 26th, 2010, 3:47 pm
by Jason Caldwell
s2Member v3.2.7 is now available.
[ Download the latest version of s2Member here ]

You can read the full Changelog here:
[ http://www.primothemes.com/readme/914/#rm-changelog ]

s2Member (Pro) v1.2.7 is also available now!
[ http://www.s2member.com/ ]

Changelog for s2Member v3.2.7

* Custom Fields ( new features ). s2Member is now equipped with a VERY powerful set of features; designed to extend the functionality of Custom Fields. s2Member now supports Text Fields ( single/multi-line ), Checkboxes ( single/multi-option ), Radio Buttons ( single/multi-option ), and Dropdowns ( single/multi-option ).

In addition, with s2Member it is now possible to configure Custom Fields differently for each Membership Level. Other tools: including Validation Formats and Visibility are also available. For full details, check your Dashboard under: s2Member -> General Options -> Custom Fields.

* Attn Developers ( before upgrading ). Hooks/Filters ( e.g. those related to Custom Fields ) have been modified in ways that may break custom scripts you've created to work with previous versions of s2Member. We suggest dropping all of your Hooks/Filters related to Custom Fields. Instead, use the NEW improved tools w/s2Member v3.2.7+. Please see: s2Member -> General Options -> Custom Fields.

* BuddyPress/Multisite. A plugin conflict was resolved between BuddyPress/s2Member when both of these plugins were installed on a Multisite Network together. BuddyPress bypasses the default Filter ( pre_site_option_registration ) and instead, it uses: bp_core_get_site_options(). This has been resolved in s2Member v3.2.6+.

* Bug fix. A bug was found in s2Member's handling of Custom Fields columns. This minor bug was conflicting with other plugins that attempt to create User-based columns. This was been resolved in s2Member v3.2.7+.

* New Shortcode attribute. s2Member's PayPal Button Shortcode now accepts a new attribute ( ta="0.00", Trial Amount ). In the past, if you intended to offer a "paid" initial period at a different price, you had to use the Full Button Code. Now you can just change the ta="0.00" attribute ( which is easier ).

* More informative. s2Member now generates warnings for newbies that create conflicts between their Membership Options Page and Login Welcome Page. s2Member is now capable of detecting the most common conflicts, in order to produce informative messages that assist site owners.

* Login/Registration Design. s2Member v3.2.7+ includes additional customization tools that allow font sizes and font families to be configured for the Login/Registration system. In your Dashboard, go to: s2Member -> General Options -> Login/Registration Design.

* Bug fix. The Default Profile Editing Panel ( e.g. /wp-admin/profile.php ) was NOT validating Custom Fields. s2Member v3.2.7 resolves this for Users/Members. Administrators are exempt ( the intended functionality ).

* Better instructions inside in the General Options panel for s2Member. Just a few subtle improvements based on User feedback. Hopefully these will make life a little easier for newbies.

Re: s2Member v3.2.7 ( new Custom Fields )

PostPosted: October 2nd, 2010, 1:39 pm
by stonecoldcnc
Hi
I tried to create a new field to be able to choose a country in "select menu ( multi option )" and copied a long list of countries in the "Option Configuration File: * ( one option per line )" but somehow that messed up my login page completely as you can see in the attached image or when you try to login to my site stonecoldcnc.com. It seems it had created a new field for every country but totally messed up.

That is part of the code I inserted:

" "|(please select a country)
--|none
US|United States
AU|Australia
CA|Canada
DE|Germany
CN|China
CA|Canada
GB|United Kingdom
IT|Italy
ES|Spain
JP|Japan
TR|Turkey
MX|Mexico
BR|Brazil
FR|France
AF|Afghanistan

I tried to delete all the custom fields but even when the are all deleted the login page still shows funny entries.

Any idea on how to fix this ? Your help would be much appreciated.

Juergen

Re: s2Member v3.2.7 ( new Custom Fields )

PostPosted: October 2nd, 2010, 11:49 pm
by stonecoldcnc
Many hours later and I finally managed to get rid of all this funny field entries. Every time I thought I had cleaned them all out they appeared again. And when I created a new custom field they appeared again in even bigger numbers.

I tried to replicate what a was doing before on my local test setup but there it was working fine. Then I disabled all plugins on my live page which then allowed me to delete all the funny field entries. After that the standard login page looked okay with no errors or messed up characters.

Then I was able to create custom fields again without problem. At this stage I thought that one of the plugins may have caused all the problems. But after enabling the plugins one by one right to the last one all is working fine. So I'm not sure what caused all this problems perhaps just a computer glitch in the system somewhere. At last all is working.

Thanks for keeping this great plugin S2Member free.

cheers

BTW in my previous email I said I selected "select menu ( multi option )" which was wrong I meant "select menu (drop down)"

Re: s2Member v3.2.7 ( new Custom Fields )

PostPosted: October 3rd, 2010, 4:21 am
by stonecoldcnc
UPDATE 2

Not sure what is going on, it looked like it was working before but when I checked the login page again a little while later everything was messed up again.

I then spend another few hours disabling/enabling all plugins one by one. When I get to one which messes up the login page and then disable the plugin again, and recreate the custom reg field then the login page is still messed up until I switch all plugins off again and start from scratch.

I can not pinpoint what or which plugin is causing all the problems. For now I'll not be using any custom reg fields until the next update or someone else finds out whats causing it. The only thing I found out is that when I turn all plugins off then everything works fine.

Here is the list of all the plugins I'm using, perhaps someone has an idea which ones are conflicting with S2Member

AddToAny
Adminer
Akismet
All in One SEO Pack
Broken Link Checker
Contact Form 7
Exec-PHP
Google Analytics for WordPress
Google XML Sitemaps
Welcome Email Editor
Mystique Extra Nav Icons
Official StatCounter Plugin
p2pConverter
s2Member
Scroll to Top Button
Search Meter
Send link to friend
SI CAPTCHA Anti-Spam
Subscribe To Comments
TinyMCE Advanced
WP-DBManager
WP Hide Dashboard
WP Maintenance Mode
WP Show IDs
WP Super Cache

cheers

Juergen

Re: s2Member v3.2.7 ( new Custom Fields )

PostPosted: October 9th, 2010, 1:38 am
by gregfielding
I'm having the same issue.

Re: s2Member v3.2.7 ( new Custom Fields )

PostPosted: October 9th, 2010, 1:59 am
by stonecoldcnc
I guess we can only wait for the next update to see if that fixes the problem. Have you tried to pinpoint which plugin is conflicting?

Before the latest update 3.2.7 the custom registration fields were working fine on my site. That's why I'm sure the problem was created with the latest update.

Re: s2Member v3.2.7 ( new Custom Fields )

PostPosted: October 9th, 2010, 4:11 pm
by gregfielding
Not yet - I use about 20 plugins and have some fairly extensive hacking beyond that. Troubleshooting is tough - besides, if we've got this issue then a lot of others probably do as well.

Jason,
If you want access to my site to play with it, let me know.
-Greg

Re: s2Member v3.2.7 ( new Custom Fields )

PostPosted: October 10th, 2010, 11:12 am
by stonecoldcnc
After many more hours of trial and error I got it working, but with restrictions.
I was turning all plugins off and then turned them back on, one by one and after every plugin I created a new custom reg field to check if it caused a problem.

I managed to do this for every single plugin without a problem. So again I have no idea which plugin causes the problem. It seems that it is a combination of plugins.

Then I remembered what I have done before all the problems started in the first place. I had created an Unique ID with a space "website url".

So I created again the ID with space and that broke everything. So I thought I'm a step closer but not quite because once things are messed up I have to turn off all the plugins except s2member to be able to clean up the mess.

Try this steps below once you have clean up the mess:
1. turn off all plugins except s2member
2. create all the custom reg fields you need( don't use Unique ID's with a space )
3. save
4. turn the plugins back on
5. DON'T go back to change any of the custom reg fields

Now things should work but you cannot go back to edit or change any of the custom reg fields as this will break everything again.

Hope that helps anyone.

Re: s2Member v3.2.7 ( new Custom Fields )

PostPosted: October 16th, 2010, 9:27 pm
by Jason Caldwell
Hey guys. Sorry for the delay on this topic.

I just took a look at all of the reports above, and ran some tests of my own. I've not been able to reproduce the errors being reported here on a default installation of WordPress® with a default PHP configuration. However, I WAS able to reproduce this under an installation of PHP where `magic_quotes_sybase = On`.

Possible solution:

Adjust your server configuration, by setting this in your php.ini file:
Code: Select all
magic_quotes_sybase = Off
http://php.net/magic-quotes-sybase

In my tests, the application of spaces, or any special characters did not have an impact on this. If any of you continue to have trouble with this, please reply back and I'll dig deeper. It would be helpful if you could tell me what browser version and operating system that you were using as well; as much of this is handled via JavaScript on the client-side.

Jason,
If you want access to my site to play with it, let me know.
-Greg

Greg. That would be great. If you're still having trouble, please send a Dashboard login to me for testing. You can send it privately through our contact form here: http://www.s2member.com/contact/

Re: s2Member v3.2.7 ( new Custom Fields )

PostPosted: October 21st, 2010, 5:54 pm
by gregfielding
Jason,
Made the change in php.ini and problem is still there.

Related question about custom fields...any experience getting a mailchimp subscription coded into there? It would be great to have a check box to subscribe to a newsletter, but the email would have to sync.

Thanks!

Re: s2Member v3.2.7 ( new Custom Fields )

PostPosted: October 22nd, 2010, 3:44 am
by Jason Caldwell
Thanks for the follow-up.
gregfielding wrote:Jason,
Made the change in php.ini and problem is still there.

Related question about custom fields...any experience getting a mailchimp subscription coded into there? It would be great to have a check box to subscribe to a newsletter, but the email would have to sync.

Thanks!

s2Member comes pre-integrated with MailChimp and also with AWeber.
Take a look in your Dashboard under: s2Member -> API List Server -> MailChimp.

Re: s2Member v3.2.7 ( new Custom Fields )

PostPosted: October 26th, 2010, 1:58 am
by Jason Caldwell
Is anyone else having problems like the ones reported here?
Or were these isolated incidents?


We've been unable to reproduce this so far.

Re: s2Member v3.2.7 ( new Custom Fields )

PostPosted: October 26th, 2010, 11:40 pm
by Jason Caldwell
OK. We were finally able to reproduce this bug and determine its cause.

The issue has been resolved in s2Member v3.2.9+.
== Changelog ==

= 3.2.9 =
* Compatibility. s2Member's Custom Field interface was being negatively impacted by the Prototype library for JavaScript; which is utilized by some other popular plugins, such as WP-O-Matic. As a result, on some installations of s2Member ( depending on your plugin combination ), a few site owners were seeing a jumbled mix of fields in their General Options panel for s2Member. This conflict with the Prototype library has been resolved in s2Member v3.2.9+.

If ( and ONLY if ) you were experiencing this issue in previous versions of s2Member, it is recommended that you delete all of your existing Custom Fields for s2Member and re-create them. If you don't delete all of your corrupted Custom Fields and start over, the issue may appear to still exist; but it HAS been corrected.

Thanks to everyone who reported this.