Dada Mail Developers Archives

 

dadadev Re: dadadev Re: dadadev Re: Default Values for New Lists

April 20th 2009 UTC

At 11:45 AM -0400 4/20/09, Frans Gouverne wrote: >No idea, but it seems that I have successfully merged my extra >features repository into v3.0.3 stable now, see: > >http://github.com/zwerfkat/dada-mail-3.0.x/tree/ExtraFeatures303 > >Please note the clone list settings feature shows up in the "create >new list" screen only, so it is not available for existing lists. >But you can remove an existing list (be sure to export the email >addresses first), create a new one and use the ...Continue Reading

Re: dadadev Re: dadadev Re: Default Values for New Lists

April 20th 2009 UTC

> At 11:40 PM -0400 4/16/09, Justin J wrote: >> >>* The code changes won't be, no. I did make the changes for the 3.1 alpha >>release - they're in there, but I don't suggest using that version yet for >>production. > > Would it work to install 3.1a and clone the lists and then delete it and > go back to 3.03? > Or would stuff get messed up? No idea, but it seems that I have successfully merged my extra features repository into v3.0.3 stable now, see: http://github.com/zwerfk ...Continue Reading

Re: 3.0.3 Released, 3.10 Alpha 1 Released

April 19th 2009 UTC

----- Original Message ----- From: "Justin J" To: "[list_settings.list_name] Subscriber" Sent: Friday, April 17, 2009 12:20 AM Subject: [dadadev] Re: 3.0.3 Released, 3.10 Alpha 1 Released [...] > One thing, to look forward, is to branch the main Dada Mail git to have > some sort of facilities to support multiple languages, which currently, > it does not. Until that happens, multiple language support may never get > into the program, sadly. Hopefully, with git, this should be e ...Continue Reading

dadadev Re: dadadev Re: Default Values for New Lists

April 19th 2009 UTC

At 11:40 PM -0400 4/16/09, Justin J wrote: > >* The code changes won't be, no. I did make the changes for the 3.1 >alpha release - they're in there, but I don't suggest using that >version yet for production. Would it work to install 3.1a and clone the lists and then delete it and go back to 3.03? Or would stuff get messed up? ...Continue Reading

dadadev Re: dadadev Re: dadadev Re: Default Values for New Lists

April 19th 2009 UTC

Thank you. Yes I using 3.03. At 2:50 PM -0400 4/19/09, Frans Gouverne wrote: >>> >>>* There was someone on the list that added this feature in 3.0.x - they >>>may be willing to share their tweaked copy >> >>Dear someone, if you're reading, please post this--thanks, J > > >Here it is in the archive: >http://dadamailproject.com/cgi-bin/dada/mail.cgi/archive/dadadev/20081218162906/ > > >I have added this feature to 3.0.1, see my public git repository at: >ht ...Continue Reading

Re: dadadev Re: dadadev Re: Default Values for New Lists

April 19th 2009 UTC

----- Original Message ----- From: "John Collins" To: "[list_settings.list_name] Subscriber" Sent: Friday, April 17, 2009 6:56 AM Subject: [dadadev] dadadev Re: dadadev Re: Default Values for New Lists > > At 11:40 PM -0400 4/16/09, Justin J wrote: >>>1) Is the code in this link compatible with vers 3.03? >> >> >>* The code changes won't be, no. I did make the changes for the 3.1 alpha >>release - they're in there, but I don't suggest using that version yet ...Continue Reading

Re: Physical Address Different in HTML Emails

April 17th 2009 UTC

>> You can also add it via SQL, something like: >> >> ALTER TABLE dada_subscribers ADD COLUMN your_new_field TEXT >> >> will do the trick (in 3.0.x). > > I was talking about adding subscribers not subscriber fields to the > db. I need to add them via an external cron, is it enough to > populate the dada_subscribers database, or is there something else > that needs to be done? > Ah! Even easier: INSERT INTO dada_subscribers(email, list list_status) values('email@P ...Continue Reading

Re: Physical Address Different in HTML Emails

April 17th 2009 UTC

> the code's there, it's just not used... to be the point where I > can't figure out why not. Yup, that was easy enough. In 3.0.3 at least, find these lines in the file, dada/DADA/App/FormatMessages.pm: if($content){ # And, that's it. $content = DADA::Template::Widgets::screen( { %screen_vars, -data => \$content, } ); and change them to: if($content){ ...Continue Reading

Re: Physical Address Different in HTML Emails

April 17th 2009 UTC

On Apr 17, 2009, at 1:12 AM, Yehuda Katz wrote: > > It should be simple to "webify" any string. Most languages have a > function to do this automatically. > Ex. PHP, $string = nl2br($string) > sorry, i am not sure about perl The template system in Dada Mail actually has it as a feature of the system - figures out newlines fairly smartly, changes links to be clickable - even encodes email addresses to be spam-proof - the code's there, it's just not used... to be the point where I can't ...Continue Reading

Re: Physical Address Different in HTML Emails

April 17th 2009 UTC

It should be simple to "webify" any string. Most languages have a function to do this automatically. Ex. PHP, $string = nl2br($string) sorry, i am not sure about perl. On Fri, Apr 17, 2009 at 1:51 AM, Justin J wrote: > The issue is just that the plain text that you enter in for the physical > address isn't changed to HTML, so that the line breaks are seen. In HTML, > things like whitespace and line breaks don't really mean much (and there's > good reasons for that). Because of that, you have to ...Continue Reading
  • This mailing list is a public mailing list - anyone may join or leave, at any time.
  • This mailing list is a group discussion list (unmoderated)
  • Start a new thread, email: dadadev@dadamailproject.com

This is the developer discussion mailing list for Dada Mail.

If you are just looking for support Dada Mail, consult the message boards at:

https://forum.dadamailproject.com

Documentation for Dada Mail:

https://dadamailproject.com/d

Specifically, see the Error FAQ:

https://dadamailproject.com/d/FAQ-errors.pod.html

To post to this list, send a message to:

mailto:dadadev@dadamailproject.com

All subscribers of this list may post to the list itself.

Topics that are welcome:

  • Constructive critiques on the program (I like, "x", but, "y" needs some work - here's an idea on how to make this better...)
  • Bug/Error reports
  • Bug fixes
  • Request For Comments on any changes to the program
  • Help customizing Dada Mail for your own needs
  • Patches
  • Language Translations
  • Support Documentation/Doc editing, FAQ's, etc.
  • Discussion of any changes that you would like to be committed to the next version of Dada Mail -

Dada Mail is on Github:

https://github.com/justingit/dada-mail/

If you would like to fork, branch, send over PRs, open up issues, etc.

Privacy Policy:

This Privacy Policy is for this mailing list, and this mailing list only.

Email addresses collection through this mailing list are used explicitly to work within this email discussion list.

We only collect email addresses through our Closed-Loop Opt-In system.

We don't use your email address for any other purpose.

We won't be sharing your email address with any other entity.

Unsubscription can be done at any time. Please contact us at: justin@dadamailproject.com for any help regarding your subscription, including removal from the mailing list.

All mailing list messages sent from us will include a subscription removal link, which will allow you to remove yourself from this mailing list automatically, and permanently.

All consent to use your email address for any other purpose stated at the time of the mailing list subscription will also be revoked upon mailing list removal.