Merge lp://staging/~doctormo/inkscape-web/inkscape-web-inkpicture into lp://staging/inkscape-web
Proposed by
Martin Owens
Status: | Merged |
---|---|
Merged at revision: | 1432 |
Proposed branch: | lp://staging/~doctormo/inkscape-web/inkscape-web-inkpicture |
Merge into: | lp://staging/inkscape-web |
Diff against target: |
420 lines (+294/-8) 11 files modified
cmsplugin_image/__init__.py (+3/-0) cmsplugin_image/cms_plugins.py (+50/-0) cmsplugin_image/migrations/0001_initial.py (+34/-0) cmsplugin_image/migrations/0002_auto_20160907_2044.py (+35/-0) cmsplugin_image/migrations/0003_auto_20160907_2241.py (+23/-0) cmsplugin_image/models.py (+95/-0) cmsplugin_image/templates/cms/plugins/picture.html (+18/-0) cmstabs/models.py (+1/-1) inkscape/settings.py (+1/-1) inkscape/static/css/main.css (+34/-5) utils/requirements.txt (+0/-1) |
To merge this branch: | bzr merge lp://staging/~doctormo/inkscape-web/inkscape-web-inkpicture |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Hachmann (community) | Approve | ||
Review via email:
|
Description of the change
Fixed up the previous merge request and make sure the initial migration keeps existing data from the djangocms_picture plugin.
To post a comment you must log in.
Beside the missing closing ) in the comment on the plugin, it looks almost perfect.
The 'longdesc' field has not been removed (as the migration thinks), it has been renamed to what it is: title.
This does loose data on the website, as I added titles (at least) on the Sponsors page (how did you check for data loss?). So I guess it will need to be named back to its original name, and only the 'verbose' and 'help text' parts need to be changed.
Why is compatibility with the old plugin important? I liked the name ;-)