mahara-contributors team mailing list archive

[Robert Lyon <2006637@xxxxxxxxxxxxxxxxxx>]

** Changed in: mahara/22.10
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: mahara-contributors
https://bugs.launchpad.net/bugs/2006637

Title:
  Issue with upgrade and setting the blocktype_installed_viewtypes
  values correctly

Status in Mahara:
  Fix Committed
Status in Mahara 21.10 series:
  Fix Committed
Status in Mahara 22.04 series:
  Fix Committed
Status in Mahara 22.10 series:
  Fix Committed
Status in Mahara 23.04 series:
  Fix Committed

Bug description:
  When we add a new view type we update the blocktype_installed_viewtype
  table to know what blocks can be used on this new view type.

  But if we have an upgrade path where we add two new view types in one
  upgrade session then the information is not correct from
  Blocktype::get_viewtypes() because it is set to be static.

  We need it to ignore this static-ness on upgrade.

  To test:

  Install a 20.04_STABLE site
  Upgrade to main
  Run the following command in database:
  select * from blocktype_installed_viewtype where viewtype = 'activity' order by blocktype;

  Should see:
  29 (or 30) rows including 'placeholder' and 'image' blocktypes

  Actually see:

  21 (or 22) rows and 'placeholder' and 'image' blocktypes are missing

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/2006637/+subscriptions