At 10:50 PM -0400 10/15/08, Justin J wrote:
>
Somehow in my first attempt to set up the sql backend I got caught in a loop where I ending up in the auto install and created a whole new list Not a serious problem, I restored from backup and got it on the second try One feature for new users is the auto set up creates the external config file which was good news for me as I had not previously made one Additionally, I noticed in there were additional folders in the same folder as the config file named archives backups lists logs templates tmp
In most of these are files with names related to the list name I used when the auto setup was doing its thing I renamed these folders so they don't mess my real list, but there they sit Most likely there's an explanation for them somewhere, but I haven't found it
Are there files I could/should install in these from my long term
existing list or should I just ignore them?
If you're list settings, archives and subscribers are all showing up correctly, then I think you're good to go - just leave the files where they lay If you're using the SQL backend and moved from the default backend to the SQL backend, there's going to be files in there, you're not going to be using anymore I just usually let them be, out of laziness, really
Can you show what the actually directory structure looks like? Re-reading what's going on, it sounds strange - you should have a directory structure like this:
dada_files- archives backups configs - dada_config lists logs templates tmp
and not:
dada_files- configs - archives backups dada_config lists logs templates tmp
If that makes sense,
Makes sense Here ya go The ones with MNM in them are my actual list The ones with SoCal in them were created by the aborted failed first try at updating--this list does not exist Under logs, I added a copy of the log MNM-clickthrough log there after opening admin and finding the clickthrough history gone I moved it to the below location and they reappeared
dada_files archives mj-SoCal-archive
backups
SoCal
settings
1224035500
1224079919
1224079991
configs
dada_config
lists
mj-MNM
mj-MNM-schedules
mj-SoCal
SoCal
authorized_senders
SoCal
black_list
SoCal
white_list
SoCal
list
logs
bounces
txt
dada
txt
errors
txt
MNM-clickthrough
log
templates
(empty)
tmp
(empty)
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.