| Age | Commit message (Collapse) | Author |
|---|
|
Add xxx_installer::upgrade($version) method so that upgrade stanzas
are separate from install stanzas. In the old code, to do an upgrade
meant that you had to re-evolve everything from the initial install
because we'd step through each version's changes. But what we really
want is for the initial install to start off in the perfect initial
state, and the upgrades to do the work behind the scenes. So now the
install() function gets things set up properly the first time, and the
upgrade() function does any work to catch you up to the latest code.
See gallery_installer.php for a good example.
|
|
separator. Try to
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
|
|
|
|
returns an error, and log them appropriately. This should fix a slew
of import failures from corrupt G2 installs.
|
|
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
|
|
loading that user.
|
|
|
|
|
|
|
|
appropriately in g2_import.
|
|
code preamble for security.
Update File_Structure_Test::code_files_start_with_preamble_test to
check all the php files in var, too.
|
|
users about images that failed to import.
|
|
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.
|
|
gallery module. This type of mass update is prone to some small bugs.
|
|
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).
|
|
image instead so that we at least have a target for comments.
Fixes ticket #294
|
|
|
|
image" placeholder and keep on trucking. Oh, and notify the admin.
Fixes ticket #287
|
|
|
|
|
|
|
|
the user enters the path to G2 itself, we find the embed.php path from there.
|
|
|
|
|
|
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.
|
|
|
|
any resizes (or thumbnails).
Fix a case where we were over-weighting the max dimension for square
resizes and thumbs.
|
|
|
|
|
|
|
|
not installed.
Resolves ticket #276
|
|
else it interferes with thumbnail/resize generation during regular imports
|
|
|
|
doesn't exist.
|
|
saving its dimensions to the item.
Also, import originationTimestamp as captured field.
|
|
|
|
|
|
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.
|
|
call.
|
|
|
|
Fixes ticket #247.
|
|
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.
|
|
|
|
|
|
* Delete g2_map records when the corresponding item is removed.
* Improve text on g2 import settings page
* Minor comment fixes.
|
|
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).
|
|
duplication
|
|
appropriately.
|
|
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.
|
|
metadata, and doesn't import photos yet.
|
