The Perl libraries need to get changed in the Config file, and all
scripts, and then all of the scripts need to be enabled on for the
menus, in the config file Not a simple upgrade that you want to do
every week
Not quite true - you can plop the Admin Menu stuff in the outside
config file, ala:
[snip]
$S_PROGRAM_URL = $PROGRAM_URL; my $PLUGIN_URL = $S_PROGRAM_URL; $PLUGIN_URL =~ s/mail cgi$//; $PLUGIN_URL = 'plugins'; my $EXT_URL = $PLUGIN_URL; $EXT_URL =~ s/plugins/extensions/;
$ADMIN_MENU ||= [
#
a whole bunch 'o stuff
];
[/snip]
Yeah, you gotta change it when new plugins/extensions comes out and
that is a pain, but for bug fix releases, this should work
Speaking
of which, that's one of the values of a bug fix only release
Another option is to have all the thingies on the admin menu sort of
self-register themselves, so if you have, say, "dada_bridge
pl" in
the, "plugins" directory, it'll automatically show up
That would be
nice
Another option would be a full-blown installer script, which would be
nice, but again, Yet Another Project for Justin :) Along with a,
"through the web browser" install, like Joomla has, you can also make
a Perlish makefile type deal, using something like this:
http://search
cpan
org/~adamk/Task-1
01/lib/Task
pm
The other problem is setting the Perl libraries in a script like
dada_bridge
pl
This has to be done, since the cronjob is run in a
different environment than when you run the program through the web
browser - I don't know what a better workaround is for that
(completely), but there is a way to just have the cronjob run
dada_bridge
pl as if it was doing so in the web env:
http://mojo
skazat
com/support/documentation/
dada_bridge pl html#setting_the_cronjob_the__easy_way
Which means you don't have to set the Perl libraries
Nothing to stop
me doing this for the bounce handler, scheduled mailer, or anything
else (the auto_pickup
pl proggy also already does this)
You shouldn't have to ever set the Perl library path in the Config
pm
file - never seen that required, is that something you've have to do?
I understand that it's still completely annoying to download,
uncompress, upload install/configure a dada mail for testing
But,
just running the test suite and reporting back on any problems would
be a huge world of good
If anyone needs help doing that for the next release, let me know
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:
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:
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.
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.