Re: [PLIP-Advisories] [Plone] #9328: content im-/export
#9328: content im-/export +--- Reporter: csenger | Owner: csenger Type: PLIP| Status: assigned Priority: minor | Milestone: 4.x Component: Infrastructure |Keywords: +--- Changes (by mylanium): * cc: mylanium (added) -- Ticket URL: http://dev.plone.org/plone/ticket/9328#comment:39 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
Re: [PLIP-Advisories] [Plone] #9328: content im-/export
#9328: content im-/export +--- Reporter: csenger |Owner: csenger Type: PLIP| Status: assigned Priority: minor |Milestone: 4.x Component: Infrastructure | Resolution: Keywords: | +--- Comment(by chervol): The branch http://projects.quintagroup.com/products/browser/quintagroup.transmogrifier/branches/plone-4 (this was earlier merged from GitHub) was moved to http://dev.plone.org/collective/browser/quintagroup.transmogrifier/trunk. -- Ticket URL: http://dev.plone.org/plone/ticket/9328#comment:38 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
Re: [PLIP-Advisories] [Plone] #9328: content im-/export
#9328: content im-/export +--- Reporter: csenger |Owner: csenger Type: PLIP| Status: assigned Priority: minor |Milestone: 4.x Component: Infrastructure | Resolution: Keywords: | +--- Changes (by sargo): * cc: sargo (added) -- Ticket URL: http://dev.plone.org/plone/ticket/9328#comment:37 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
Re: [PLIP-Advisories] [Plone] #9328: content im-/export
#9328: content im-/export +--- Reporter: csenger |Owner: csenger Type: PLIP| Status: assigned Priority: minor |Milestone: 4.x Component: Infrastructure | Resolution: Keywords: | +--- Comment(by interra): We still have the same errors. See: * [http://db.tt/Pm98Xs Plone-3.3 slave buildout.cfg] and [http://go.quintagroup.com/vchop test results] (failure) * [http://db.tt/dIOhTD Plone-4.0 slave buildout.cfg] and [http://go.quintagroup.com/uchop test results] (failure) There is a chance we should be testing in some other way (at the moment we do `bin/test -s quintagroup.transmogrifier`)? Replying to [comment:35 tomster]: Replying to [comment:33 tomster]: Replying to [comment:32 interra]: We've went on and evaluated the [http://github.com/tomster/quintagroup.transmogrifier/commits/plone-4# Plone 4 branch]. It is vast step forward. However [http://projects.quintagroup.com/products/build/quintagroup.transmogrifier_plone4/3576#step_test Plone-4 test fails] with `testcaselayer.ptc` import error that seems easy to fix. i'll look into that ASAP. i've added an explicit dependency on ptc for testing in http://github.com/tomster/quintagroup.transmogrifier/commit/b05d712dc71ff6b502a3334e711f627fe40dbe68 can you check, if that fixed it? [snip] how are you guys running the tests under Plone 3.3? I currently cannot get them to run here at all. I've tried using plonenext and http://svn.plone.org/svn/plone/buildouts/plone-coredev/branches/3.3 but i wasn't able to create a working bin/test for either. do you have a plone3.3 buildout you could point me to, so i could reproduce the test failure? [snip] -- Ticket URL: http://dev.plone.org/plone/ticket/9328#comment:36 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
Re: [PLIP-Advisories] [Plone] #9328: content im-/export
#9328: content im-/export +--- Reporter: csenger |Owner: csenger Type: PLIP| Status: assigned Priority: minor |Milestone: 4.x Component: Infrastructure | Resolution: Keywords: | +--- Comment(by tomster): Replying to [comment:33 tomster]: Replying to [comment:32 interra]: We've went on and evaluated the [http://github.com/tomster/quintagroup.transmogrifier/commits/plone-4# Plone 4 branch]. It is vast step forward. However [http://projects.quintagroup.com/products/build/quintagroup.transmogrifier_plone4/3576#step_test Plone-4 test fails] with `testcaselayer.ptc` import error that seems easy to fix. i'll look into that ASAP. i've added an explicit dependency on ptc for testing in http://github.com/tomster/quintagroup.transmogrifier/commit/b05d712dc71ff6b502a3334e711f627fe40dbe68 can you check, if that fixed it? and [http://projects.quintagroup.com/products/build/quintagroup.transmogrifier_plone4/3575#step_test Plone-3.3 test fails] with extra `transmogrifier(u'quintagroup.transmogrifier.tests.datacorrector')` test. i encountered this, too. it seems the order is returned differently in Plone 3 and 4. shouldn't be too difficult to make the rest robust... how are you guys running the tests under Plone 3.3? I currently cannot get them to run here at all. I've tried using plonenext and http://svn.plone.org/svn/plone/buildouts/plone-coredev/branches/3.3 but i wasn't able to create a working bin/test for either. do you have a plone3.3 buildout you could point me to, so i could reproduce the test failure? Let's clean up this stuff first and move on with collective initiative then. absolutely. i'll look into it ASAP and update here. -- Ticket URL: http://dev.plone.org/plone/ticket/9328#comment:35 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
Re: [PLIP-Advisories] [Plone] #9328: content im-/export
#9328: content im-/export +--- Reporter: csenger |Owner: csenger Type: PLIP| Status: assigned Priority: minor |Milestone: 4.x Component: Infrastructure | Resolution: Keywords: | +--- Changes (by duffyd): * cc: duffyd (added) Comment: I just received notification from Volodymyr @ Quintagroup indicating that they're ready to move quintagroup.transmogrifier to the Collective but due to some failing tests in the Plone 4 github branch from the Cathedral sprint (referenced above) they have halted this process. How's things progressing with this as it would be great to have q.transmogrifier moved to the Collective so more people could collaborate on this. Thanks, Tim -- Ticket URL: http://dev.plone.org/plone/ticket/9328#comment:34 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
Re: [PLIP-Advisories] [Plone] #9328: content im-/export
#9328: content im-/export +--- Reporter: csenger |Owner: csenger Type: PLIP| Status: assigned Priority: minor |Milestone: 4.x Component: Infrastructure | Resolution: Keywords: | +--- Comment(by tomster): Replying to [comment:30 limi]: Could we ask Quintagroup to donate it to the Foundation? you just did... all three developers have added themselves cc: to this ticket already some time ago :) If we're going to do this, it should be in the Plone repository — or at the very least in the Collective. Private repositories are painful. :) indeed. seeing that none of them has responded yet (neither to this thread nor to my PM) we might consider copying the necessary bits from quintagroup.transmogrifier into plone.app.transmogrifier (q.transmogrifier is contains more features than we really need for this plip, anyway.) also, from a UI perspective i've been thinking of adding a 'proper' click here to dump and click here to import your old site controlpanel instead of sending people to the ZMI. and that could live in p.a.transmogrifier, or we create a new package p.a.contentmigration or somesuch. IMHO we should have two separate products, one which you install into your old site for exporting and one for importing that dump which you install into your plone 4 (or later plone 5) site. any feedback on this approach? -- Ticket URL: http://dev.plone.org/plone/ticket/9328#comment:31 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
Re: [PLIP-Advisories] [Plone] #9328: content im-/export
#9328: content im-/export +--- Reporter: csenger |Owner: csenger Type: PLIP| Status: assigned Priority: minor |Milestone: 4.x Component: Infrastructure | Resolution: Keywords: | +--- Changes (by interra): * cc: koval.bog...@gmail.com (removed) * cc: ko...@quintagroup.com, cher...@quintagroup.com, krom...@quintagroup.com (added) Comment: Replying to [comment:29 tomster]: We have decided on moving forward using quintagroup.transmogrifier since it currently offers the most complete solution of all the approaches evaluated. Our assessment was that while it seems a bit 'rough' and doesn't have a lot of test coverage it is the only solution that currently actually produces workable results. OOTB we were able to export a sample Plone 3 site and re-import it into a vanilla Plone 3 site, however importing that export into a vanilla Plone 4 site did ''not'' work. We then spent the remainder of the sprint working on improving quintagroup.transmogrifier so that importing into Plone 4 would be possible. Since the code lives in quintagroup's read-only repository and we wanted to get started immediately, we created a [http://github.com/tomster/quintagroup.transmogrifier clone on github] and worked on a [http://github.com/tomster/quintagroup.transmogrifier/commits/plone-4# Plone 4 branch], where we now have complete tests for exporting and importing a plone site. We've went on and evaluated the [http://github.com/tomster/quintagroup.transmogrifier/commits/plone-4# Plone 4 branch]. It is vast step forward. However [http://projects.quintagroup.com/products/build/quintagroup.transmogrifier_plone4/3576#step_test Plone-4 test fails] with `testcaselayer.ptc` import error and [http://projects.quintagroup.com/products/build/quintagroup.transmogrifier_plone4/3575#step_test Plone-3.3 test fails] with extra `transmogrifier(u'quintagroup.transmogrifier.tests.datacorrector')` test. Let's clean up this stuff first and move on with collective initiative then. -- Ticket URL: http://dev.plone.org/plone/ticket/9328#comment:32 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
Re: [PLIP-Advisories] [Plone] #9328: content im-/export
#9328: content im-/export +--- Reporter: csenger |Owner: csenger Type: PLIP| Status: assigned Priority: minor |Milestone: 4.x Component: Infrastructure | Resolution: Keywords: | +--- Comment(by tomster): Replying to [comment:32 interra]: We've went on and evaluated the [http://github.com/tomster/quintagroup.transmogrifier/commits/plone-4# Plone 4 branch]. It is vast step forward. However [http://projects.quintagroup.com/products/build/quintagroup.transmogrifier_plone4/3576#step_test Plone-4 test fails] with `testcaselayer.ptc` import error that seems easy to fix. i'll look into that ASAP. and [http://projects.quintagroup.com/products/build/quintagroup.transmogrifier_plone4/3575#step_test Plone-3.3 test fails] with extra `transmogrifier(u'quintagroup.transmogrifier.tests.datacorrector')` test. i encountered this, too. it seems the order is returned differently in Plone 3 and 4. shouldn't be too difficult to make the rest robust... Let's clean up this stuff first and move on with collective initiative then. absolutely. i'll look into it ASAP and update here. -- Ticket URL: http://dev.plone.org/plone/ticket/9328#comment:33 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
