Re: First migration steps from Plone 4.2 to Plone 4.3 not run because of 4.2 service releases

"David Glick (Plone)" <david.glick-z4DKO/[email protected]>
Newsgroups gmane.comp.web.zope.plone.devel
Message-ID <[email protected]>
On 9/25/14, 12:31 AM, Fred van Dijk wrote:
> Hi,
>
> Got a report from a customer yesterday where after a migration the sortable_title index was not
> updated. So as soon as individual documents where edited in Plone 4.3 the items in collections were not
> correctly sorted.
>
> I started noticing a pattern with other migrations we did where small things were off, like TinyMCE not being
> fully upgraded. It seems that when upgrading from latest Plone 4.2.7 to Plone 4.3. the migration steps in
> plone.app.upgrade  for 'to43alpha1' are not run at all.  Checking back in the zope logs for this customers'
> migration the logs start with 'Ran upgrade step: Upgrade Profiles for 4.3a2'
>
> Digging further: the latest metadata.xml for Plone 4.2.7 has now been pushed to 4212, as logged in the
> migration log by 'INFO plone.app.upgrade Starting the migration from version: 4212', but the to34alpha1
> step is registered with
>
>      <genericsetup:upgradeSteps
>          source="4208"
>          destination="4300"
>          profile="Products.CMFPlone:plone">
>
>          <genericsetup:upgradeStep
>              title="Miscellaneous"
>              description=""
>              handler=".alphas.to43alpha1"
>              />
>
>
> Auch. Sending this to the developers list as people here might be doing more migrations than usual so if
> you have done migrations recently, maybe check again if these steps have been executed. Filed a ticket
> as well under https://dev.plone.org/ticket/17336
>
> Would it be enough to put a * in plone.app.upgrade's first UpgradeSteps source to fix this?
>
>
Yeah, this looks like a bug in plone.app.upgrade. The source for that 
step needs to be updated whenever the profile on the 4.2 branch is 
incremented. Please feel welcome to fix it.

We can't use * because then it will run on every upgrade (IIRC).

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.