be smart about it. If we see a comma or a semicolon, expect the keywords to be separated
by that delimeter. Otherwise, use space as the delimiter.
Fixes ticket #446
active, since the code may not even be present. This assumes that if
the G2 comment module *is* active that the code is present, but that's
part of the assumption that the G2 we're importing from is healthy.
Fixes ticket #409
and Gallery 3 have a class named Gallery. Clone a subset of the
Gallery 2 files and munge them so that we can rename the Galery 2
version to G2_Gallery.
Also, update the disclaimer in Admin > Settings > Gallery 2 Import.
Install: <module>_installer::install() is called, any necessary tables
are created.
Activate: <module>_installer::activate() is called. Module
controllers are routable, helpers are accessible, etc. The module is
in use.
Deactivate: <module>_installer::deactivate() is called. Module code
is not accessible or routable. Module is *not* in use, but its tables
are still around.
Uninstall: <module>_installer::uninstall() is called. Module is
completely removed from the database.
Admin > Modules will install and activate modules, but will only
deactivate (will NOT uninstall modules).
Refactor the general flow of g2_import_task::import() to simplify it
and make it more sensible. It had gotten a little overgrown. It's
still a little overgrown, but I don't see an easy way to simplify it
from here.
Significantly speed up the process by copying Gallery2 thumbnails and
resizes wherever possible instead of regenerating them. This requires
us to figure out the dimensions of the original G2 derivative and make
sure that it matches in some reasonable way.
To allow users to take advantage of this, calculate the optimal thumb
and resize size to set in G3 to match what was used in G2. While
we're at it, give the user some idea of how much data is available in
G2 to import.
item in the database. This fixes the problem that the import fails
the first time around because the various groups are mapped in the db
but aren't available in the request.
Notes:
* Don't store the g2->g3 map in the task; it gets too large and
overflows the context column.
* Import album sort orders
* Try to treat duplication in the summary and description fields
sensibly.
* Move the g2 import config page under the Settings menu
* Clean up the settings page slightly and send users to the
maintenance page to do the actual import (not an optimal UI, but it
works).
around in the task so that on subsequent import runs we don't try to
reimport stuff we've already pulled in. This also gives us a mapping
so that we will be able to translate old G2 urls into the hot new G3
urls.
