To those interested, here's a rundown of the differences between the v5 and v6, as well as the direct link to install,
Upgrading is fairly straightforward, with no need for any Dada Mail 5 to Dada Mail 6 SQL upgrade scripts.
When using the Dada Mail Installer (which you should use, when installing or upgrading), you will definitely want to create a new
.dada_configfile, when asked.
There is one new config variable,
$SUPPORT_FILESthat needs to be set up correctly. If you do not make a new
.dada_configfile, or install manually, without putting in this new variable, the upgrade will not work.
.dada_configfile that's generated by the included installer has undergone a few changes.
.dada_configfile, but are almost kept the same as the default, ala:
$FILES = $DIR . '/.lists'; $TEMPLATES = $DIR . '/.templates'; $TMP = $DIR . '/.tmp'; $BACKUPS = $DIR . '/.backups'; $ARCHIVES = $DIR . '/.archives'; $LOGS = $DIR . '/.logs';Instead of taking up extra space and line noise, these files are simply added to the
dada/DADA/Config.pmfile as the default. You may still add these variables in the
.dada_configfile to change their default, but it's not really recommended. The,
$DIRvariable has been added to the
dada/DADA/Config.pmas a true config variable, so you do not want to have the first line read,
my $DIR = '/home/account/.dada_files';Simply,
$DIR = '/home/account/.dada_files';Will be fine. Keeping,
mywill probably break things.
Added variable: $BACKEND_DB_TYPE; Removed variables: $SUBSCRIBER_DB_TYPE, $ARCHIVE_DB_TYPE, $SETTINGS_DB_TYPE, $SESSION_DB_TYPE, $BOUNCE_SCORECARD_DB_TYPE, $CLICKTHROUGH_DB_TYPEFor the SQL backend, all these variables are already set the same, ala:
$SUBSCRIBER_DB_TYPE = 'SQL'; $ARCHIVE_DB_TYPE = 'SQL'; $SETTINGS_DB_TYPE = 'SQL'; $SESSION_DB_TYPE = 'SQL'; $BOUNCE_SCORECARD_DB_TYPE = 'SQL'; $CLICKTHROUGH_DB_TYPE = 'SQL';For the Default backend, they're set like this:
$SUBSCRIBER_DB_TYPE = 'PlainText'; $ARCHIVE_DB_TYPE = 'Db'; $SETTINGS_DB_TYPE = 'Db'; $SESSION_DB_TYPE = 'Db'; $BOUNCE_SCORECARD_DB_TYPE = 'Db'; $CLICKTHROUGH_DB_TYPE = 'Db';To reduce line noise,
$BACKEND_DB_TYPEis being introduced. If set to,
SQL, it'll set the other variables accordingly. Same with setting this variable to,
(If you added additional configuration variables after an install has completed, you will still have to re-add these manually)
This can help save time during an upgrade and ensure that everything goes smoothly. You can also re-enable the installer, after a successful initial installation, to change your Dada Mail configuration - for example: add/remove a plugin.
They are now located in:
It's hoped that this directory move will make it easier for people to find the
templatesdirectory. This directory is still in the,
dadadirectory, instead of, say, the,
staticdirectory since template files are themselves little, simply programs, that need to be interpreted, and aren't themselves actually static.
Each plugin has its own directory for its templates, eg: dada/templates/plugins/tracker, etc.
The Scheduled Mailings plugin still has program generated and inline HTML. It's a big mess.
This change should help performance of the app. These files are also not cached in Dada Mail's Screen Cache, as they're going to be served faster by the webserver simply as static files.
NoConflictmode. We hope to move all Prototype/Scriptaculous code to jQuery eventually.
In previous versions of Dada Mail, these files were served via Dada Mail, creating a new running instance of the app per request, which is slow, awkward and confusing.
Both the server path, and URL to this directory will be saved in your
.dada_configfile, under the varible,
$SUPPORT_FILES. This variable is required to be correctly configured, for Dada Mail to work.
This does create an additional thing that needs to be configured for Dada Mail to be successfully installed, but we feel this extra step is worth it, for performance and for future features of the app.
<!-- tmpl_var list_settings.list_name -->are entered in the rich text (rather than source view) of the WYSIWYG editor, the "<", and, ">" characters are converted into their HTML entities, so the source of your message now looks like this:
<!-- tmpl_var list_settings.list_name -->Which breaks the tag, and you will see the original template tag, which will not be converted to its value.
In v6, Dada Mail will look for these types of conversions, and convert them back, fixing the template tag, to be parsed correctly.
DADA::App::DataCachemodule and can be enabled/disabled using the
$DADA_CACHEconfig variable. Old cached data will be removed periodically (1 hour), automatically. The data cache is located in the,
directory. The files, as well as the directory itself, may be safely removed at any time.
The new charts/graphs/maps are powered by the Google Visualization API. Data, in the JSON format is created for Dada Mail using the Perl CPAN module, JSON (http://search.cpan.org/~makamaka/JSON/). This module will need to be installed on your hosting platform for these charts/graphs/maps to be created.
Although not part of the standard Perl Library, the module proves to be so useful, that it's usually already installed on many hosting platforms (like LWP, CGI, etc).
http://maxmind.com, who also provide more accurate country/city data, on a subscription.
The distro of Dada Mail is much larger - around 20 megs. compressed, rather than ~7.5 megs for v5 of Dada Mail. This additional size is mostly from the bundled city-level Geo IP database.
Both the city, and country-level Geo IP databases can be found in the,
You may also copy the file, and place it in your,
directory, make your own changes/customizations, and the Bounce Handler will use your copy, instead of what ships with Dada Mail.
Unless rewritten, it will be removed in a future version of Dada Mail.