On Oct 15, 2008, at 6:55 PM, John Collins 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,