I found this message:

Aktualisierung #8102

Drupal\Core\Database\DatabaseExceptionWrapper: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'NULL DEFAULT NULL COMMENT 'Save entity as the last action of the task'' at line 1: ALTER TABLE {br_schedule} ADD `update_entity` NULL DEFAULT NULL COMMENT 'Save entity as the last action of the task'; Array ( ) in business_rules_update_8102() (Zeile 40 in ...my-domain/docroot/modules/business_rules/business_rules.install).

CommentFileSizeAuthor
#6 3043734-Update-to-beta7-fails-5.patch1.75 KByseki

Comments

quixxel created an issue. See original summary.

c.e.a’s picture

This issue has been added here: #3041221: List of all 'Bug reports' that need immediate support Assigned to: yseki
Thank you

c.e.a’s picture

Version: 8.x-1.0-beta6 » 8.x-1.x-dev
Assigned: Unassigned » yseki
Priority: Major » Critical
yseki’s picture

Hi @quixxel,

Thanks for the report. I'm fixing it on dev.

c.e.a’s picture

Drupal\Core\Database\SchemaObjectExistsException: Cannot add field br_schedule.update_entity: field already exists. in Drupal\Core\Database\Driver\mysql\Schema->addField() (line 414 of \web\core\lib\Drupal\Core\Database\Driver\mysql\Schema.php).

yseki’s picture

Status: Active » Needs review
StatusFileSize
new1.75 KB

Here is the patch

  • yuriseki committed e71f1b2 on 8.x-1.x
    Issue #3043734 by quixxel, C.E.A, yuriseki: Update to beta7 fails:...
c.e.a’s picture

Working.... thank you @yuriseki

c.e.a’s picture

Status: Needs review » Fixed
cesarg’s picture

Patch #6 fixed the updatedb issue for me. Thanks!

kris77’s picture

Patch #6 fixed the updatedb issue for me too.

Thanks!

samhadr’s picture

How can I apply patch #6? New to Drupal - searching for business_rules directory/files - not seeing anything.

c.e.a’s picture

Run the composer command:

composer require 'drupal/business_rules:1.x-dev'

It will remove beta-6 and install for you the latest dev version release which includes the patch in #6

samhadr’s picture

Got it - that fixed the issue!

henrik23’s picture

Thank You.
After returning to the backup your command
composer require 'drupal/business_rules:1.x-dev'
was very helpful!

Status: Fixed » Closed (fixed)

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

gil'barbare’s picture

Hi guys,

This works for me too.

Still I am worried.

Wondering if it will be possible after requiring a dev version of this module to simply update to next beta release (beta-8).
I mean with a simple 'composer update drupal/business_rules --with-dependencies'.

This may seem obvious... thanks for your help!

c.e.a’s picture

@Gil'Barbare your question is general and composer based, make sure to read more articles about composer and how it works with Drupal.

When the beta-8 release will be out, simply use: composer require 'drupal/business_rules:^1.0'.

Composer then will remove the current installed dev release version and install in place the latest beta release of this module without affecting the configuration of the module (rules, actions, conditions, variables...)

gil'barbare’s picture

Fine, thank you @C.E.A.
I was just having a doubt because 'dev' version is intermediate.