The update instructions for Forum Access 1.1 are clear: you must update Chain Menu Access API to 2.0 at the same time.

However, if (for whatever reason) FA 1.1 encounters CMA 1.x, and core tries to rebuild the menu cache, then this will fail, and you are unable to access any page on the site, because rebuilding the cache always precedes building any page. While FA 1.1 is running outside of its specs, it should not cause a catastrophic failure. (See #1768410: Errors after NOT updating Chain Menu Access)

The task here is to degrade more gracefully, so that we can recover from this situation.

CommentFileSizeAuthor
#3 forum_access_CMA_upgrade.1775204.3.patch4.33 KBsalvis
#1 forum_access_CMA_upgrade.1775204.1.patch4.26 KBsalvis

Comments

salvis’s picture

salvis
he/his
commented
Status: Active » Needs review
StatusFileSize
new forum_access_CMA_upgrade.1775204.1.patch4.26 KB

This turns it into a two-step process now: you can update FA and leave it at that, but you will be reminded that you should update CMA, too.

It's not so great code-wise, but it makes sense to do it that way for a transitional period.

Status: Needs review » Needs work

The last submitted patch, forum_access_CMA_upgrade.1775204.1.patch, failed testing.

salvis’s picture

salvis
he/his
commented
Status: Needs work » Needs review
StatusFileSize
new forum_access_CMA_upgrade.1775204.3.patch4.33 KB

Try again.

salvis’s picture

salvis
he/his
commented
Status: Needs review » Fixed

Committed to the -dev version (give it up to 12h to be repackaged).

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

salvis’s picture

salvis
he/his
commented

After some trouble with d.o, I've finally been able to release 7.x-1.2 with this patch.