On Mar 24, 2013, at 1:40 PM, AJ ajfasano@PROTECTED wrote:

I was experimenting with profile fields and partial list sending and noticed that the search was case sensitive I looked at the schema sql and the table is explicitly created with the utf8_bin collation Why not set it as utf8_general_ci?

Dunno! That's sort of just what I picked I doubt it would hurt things, if you changed for your install (barring any charset conversion problems) I can't say I know the difference between the two on the top of my head Since Dada Mail supports 3 different (SQL) backends, and all the backends are a little different, their schemas are also a little different So, for example, the PostgreSQL doesn't set a charset for any of the tables, 'cause (I think) ya don't, in PostgreSQL - rather you set the charset for the database itself

I noticed there is no support for required profile fields beyond the email address Looks like this could be handled fairly easily through a custom template and javascript, however, are there any plans to support this natively?

Def plans - but am not currently working on it Commissioning a feature is the fastest way to get a feature in, otherwise it's on my whim and fancy, and I've got a stout TODO list, and it's also my job to keep maintenance of the app (a usually thankless job), as well as everything else My main drive to add features, after commissions is "what will make people want to use Dada Mail?" and, "What's the fastest to implement?" Expanding Profile Fields is def wanted and a nice feature that many will enjoy, but it would take a good time to start and finish There's a ton of features like that, from internationalization, to moving to a mature web app framework - lots of things People all have their own favorite feature ;) My (messy) TODO list can be found at:

https://github
com/justingit/dada-mail/blob/master/dada/extras/developers/TODOlist
txt

It's really just a scratchboard to get my ideas down, so I don't forget I also invite anyone to add to the Wishlist:

https://github
com/justingit/dada-mail/wiki/WishList

Is there a way to set a profile field as a select list natively? Again this seems like something that can be done via a custom template

Custom template is the way to go My hope for expanding profile fields is to set the type of field, as well as the widget that is shown, as well as doing things like requiring fields, as well as what exactly the field needs to have in terms of data

Now I have a question about upgrading The version I have is pro 6 2 1 I noticed that there was a post about email tracking […] I noticed on Git that there is a branch for this as well as for 6 2 2 The email tracking branch has older timestamps Does the 6_2_2 contain that?

No That's why there's >1 branches - one for bug fixes, and one for features When I make up v6 3 0, I'll most likely merge branch bugfixes-6_2_2, features-email_tracking and features-password_protect_directories_additions into a new branch (6_3_0-dev, or something) and merge that with the master branch, when things have settled It's painfully easy to do in git If we wanted to get fancy, I could release v6 3 0 and v6 2 2, but it's only me, and releasing versions is time-consuming (to get right)

To upgrade, do I follow the same procedure used to install or simply extract the 6_2_2 branch over the existing install?

When I make a distro, I download from git, but there is another step, where I, uh, do a bunch of things, like add the WYSIWYG editors, and IP databases to the distro, as well as turn the documentation from POD to HTML (and other things I'm forgetting…) I should probably not have the perllib in the git repo either, as that's volatile and needs updating from time to time - another thing for my TODO ;) This "build" process is a perl script and a shell script (and I think now a ruby script?) and are embarrassingly ugly Also on the TODO list is to pop these on the git repo as well

And if I do, will that downgrade the subscription to the GPL version?

There's no difference in licensing - everything I make for Dada Mail, except the manual is GPL'd I don't think there are subscription/list quotas in the version that's up at github - that's something else I change when making a distribution