Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-4364

Upgrade to 5.0 fails to maintain some package names

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.0
    • Fix Version/s: 5.1.0
    • Component/s: None
    • Labels:
      None

      Description

      The upgrade to remove packages.name and the other language based columns assumes that the multi-language table (i.e. package_names) contains the same content. However, though the 4.5 migration did migrate the contents of packages.name to package_names, it was possible for packages created after the migration to set packages.name but not package_names. In this case the 5.0 migration removes the only existing record of the package name.

      To resolve this, let's update the the 5.0 migration to use a query to map values from packages.name to package_names if no record currently exists for the package in package_names. We should also check the other language based columns to make sure no similar issue exists.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            jonathan Jonathan Reissmueller
            Reporter:
            jonathan Jonathan Reissmueller
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              6/Jul/21

              Agile