πŸ‡ΊπŸ‡ΈUnited States @mizage@gmail.com

Account created on 12 June 2012, over 12 years ago
#

Recent comments

πŸ‡ΊπŸ‡ΈUnited States mizage@gmail.com

For D11 this worked for me:

$form['field_name']['#access'] = false;

πŸ‡ΊπŸ‡ΈUnited States mizage@gmail.com

Maybe post your composer.json file?

πŸ‡ΊπŸ‡ΈUnited States mizage@gmail.com

Did you try removing your composer.lock file?

πŸ‡ΊπŸ‡ΈUnited States mizage@gmail.com

I can confirm that the dev version with the core patch resolves the issue for me.

πŸ‡ΊπŸ‡ΈUnited States mizage@gmail.com

After updating from 10.1.0 to 10.1.6 the error has gone away and I was able to apply db updates cleanly.
I did use this patch:

https://www.drupal.org/files/issues/2023-11-10/FilterPluginBase.patch β†’

πŸ‡ΊπŸ‡ΈUnited States mizage@gmail.com

I'm seeing the following when applying the update:

[error]  SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1' for key 'PRIMARY': ALTER TABLE "publishing_options_bundles" ADD PRIMARY KEY ("pubid"); Array
πŸ‡ΊπŸ‡ΈUnited States mizage@gmail.com

Thanks again for the quick response.

πŸ‡ΊπŸ‡ΈUnited States mizage@gmail.com

Thanks for the quick response! Do we need an update hook for existing installations?

πŸ‡ΊπŸ‡ΈUnited States mizage@gmail.com

After upgrading I'm seeing this error:

Fatal error: Uncaught SimpleSAML\Assert\AssertionFailedException: Expected a callable. Got: array in /var/www/vendor/simplesamlphp/assert/src/Assert.php:364 Stack trace: #0 /var/www/vendor/simplesamlphp/simplesamlphp/src/SimpleSAML/Error/Error.php(264): SimpleSAML\Assert\Assert::__callStatic('isCallable', Array) #1 /var/www/vendor/simplesamlphp/simplesamlphp/src/SimpleSAML/Error/ExceptionHandler.php(33): SimpleSAML\Error\Error->show() #2 [internal function]: SimpleSAML\Error\ExceptionHandler->customExceptionHandler(Object(SimpleSAML\Assert\AssertionFailedException)) #3 {main} thrown in /var/www/vendor/simplesamlphp/assert/src/Assert.php on line 364

Any ideas. I didn't change any of my other configuration.

πŸ‡ΊπŸ‡ΈUnited States mizage@gmail.com

I wish I did.

Originally I migrated the site from 7.x to 9.x and then to 10.0.x a few months later. I'm wondering if something didn't migrate cleanly and I just never noticed an issue.

Does this look like a problem with the structure of a database table?

πŸ› | Entityqueue | D10.1Beta
πŸ‡ΊπŸ‡ΈUnited States mizage@gmail.com

Thanks for the response. I had to remove entityqueue to move forward so I can't give any more info on this.

πŸ› | Entityqueue | D10.1Beta
πŸ‡ΊπŸ‡ΈUnited States mizage@gmail.com

mizage@gmail.com β†’ created an issue.

Production build 0.71.5 2024