This is caused by #1846172: Replace the actions API.

Attached patch does a db_table_exists('{actions}')

CommentFileSizeAuthor
core-system-action-table-exists.patch1.89 KBclemens.tolboom
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Berdir’s picture

Berdir
Primary language German
Location Switzerland
CreditAttribution: Berdir commented

This is only a 8.x -> 8.x problem, action.module is enabled in system_update_8021() so sites coming from 7.x will have it always enabled.

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
CreditAttribution: tim.plunkett commented
Status: Needs review » Closed (works as designed)

@Berdir beat me to it.

clemens.tolboom’s picture

clemens.tolboom
Primary language Dutch
Location Groningen, 🇳🇱/🇪🇺
CreditAttribution: clemens.tolboom commented
Status: Closed (works as designed) » Active

Well I was upgrading D8 -> D8 ... so when do we support that upgrade path? After the first alpha? Which we already have 8.0-alpha1

So what policy is there?

I myself have a `production` site on D8.

Works as designed is not enough for me :(

clemens.tolboom’s picture

clemens.tolboom
Primary language Dutch
Location Groningen, 🇳🇱/🇪🇺
CreditAttribution: clemens.tolboom commented
Status: Active » Closed (won't fix)

From IRC I understand this is a won't fix due to no head2head only after first beta.

See
- #1333898: Support unstable2unstable upgrades? [policy, no patch]
- #1867972: Make HEAD2HEAD updates work

It does not work as designed imho so a won't fix.

effulgentsia’s picture

effulgentsia CreditAttribution: effulgentsia commented

@clemens.tolboom: see also https://drupal.org/core/release-cycle