3 issues / feature request

Hello Kristopher,

Here are my answers that I know, through reading the forums daily:

The major issue is the what s2 handles profiles fields. Storing the data as a serialized string is a no-go for many reasons. One is for site searches. Another is migrating data from dev-to-live. The third is general manipulation of this data. Are you guys moving towards storing this data as db rows?

I believe I’ve seen Cristián mention a couple of times, that they are gonna implement this into the database in the next major release of s2Member.

My clients don’t understand the “Automatic EOT Time” field and how its used. Can’t we simply this by calling it an “expiration date” and just go by date? I would guess that most customers don’t need an expiration time either. Simple is probably better here for most people.

I see your point here, I’ll forward this to Cristián and see if he can forward this to Jason (lead developer). ;)

Lastly, what’s the status of automatic renewal emails when or shortly before a membership expires? I understand this feature has been talked about but not implemented. Kinda important feature, eh?

You mean, like sending an email after a membership has expired? Or before the membership is about to expire? If it’s before it expires, then it is definitely coming in the next major release of s2Member.

Hope this answers your questions. :)

Glad I was able to help Kristopher,

I can’t wait for that release either. :)