πŸ‡ΊπŸ‡ΈUnited States @jedgar1mx

Detroit
Account created on 15 August 2017, over 7 years ago
#

Recent comments

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

Ahh ok, I think it's related to this issue.
https://www.drupal.org/project/tmgmt/issues/2998143 ✨ Delete job item when corresponding entity is being deleted Needs review

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

I'm unable to upgrade to `9.1.32`. It looks like there is a conflict between `varbase_core` and `vartheme_bs5` they required different version of `varbase-patches`

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

I'm running into issues upgrading ckeditor_media_embed to 2.x. Look like a patch in varbase_editor is not allowing the upgrade.

 - Upgrading drupal/ckeditor_media_embed (1.12.0 => 2.0.0-alpha4): Extracting archive
  - Applying patches for drupal/ckeditor_media_embed
    https://www.drupal.org/files/issues/embed_rich_content_in_WYSIWYG-2900313-2.patch (Issue #2900313: Add ability to embed tweets and other rich content in WYSIWYG)
   Could not apply patch! Skipping. The error was: Cannot apply patch https://www.drupal.org/files/issues/embed_rich_content_in_WYSIWYG-2900313-2.patch
πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

Removing theme hooks for swift and install requirement.

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

jedgar1mx β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

Tested @Stefdewa patch and it seems to correct the error for me. Thanks!!!

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

I'm also encountering this issue.

Currently running:

Drupal 10.2.2
Entity Browser 2.10
Responsive Preview 2.1.1

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

jedgar1mx β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

This is super helpful. Currently testing fix. Thanks @charcotrill!!

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

Just upgrade to Drupal 10 and started to get similar errors.

The recommended level for Drupal is "READ COMMITTED". For this to work correctly, all tables must have a primary key. The following table(s) do not have a primary key: taxonomy_term_field_data_delme, taxonomy_term_hierarchy_delme, url_alias_20180508_19, url_alias_20180509_11, url_alias_20180509_12, url_alias_20180510_14, url_alias_20180510_18, url_alias_20180511_11, url_alias_20180511_17, url_alias_20180514_12, url_alias_20180515_11, url_alias_20180515_18, url_alias_20180516_19, url_alias_20180517_11, url_alias_20180518_12, url_alias_20180521_12, url_alias_20180522_13, url_alias_20180523_12, url_alias_20180604.

No issues on 9.5.11 and this patch https://www.drupal.org/project/drupal/issues/1650930 πŸ› Use READ COMMITTED by default for MySQL transactions Fixed

Drupal 10.1.6
PHP 8.1
MySQL 5.7.29

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

I still can't stall it without the new release since composer keeps saying is not compatible. I'm curious how others were to install it on Drupal 10 sites.

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

I don't see the error anymore but the form view still doesn't show the no background as selected.

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

I think this was caused by trying to automate Drupal 10 fixes for deprecated twig templates on for loops. I updated the patch to match the new syntax.

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

Looks like the issue is with the key - item loops. They were split into a `for` and `if` statements which cause some weird behaviors. Probably caused by some linting tool since this affected all twig templates.

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

Great! Very exited to get a new release for Drupal 10

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

I noticed that the background selection for "no background" is not saving correctly. Probably the reason it returns the null warning.

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

Latest release fixed my issue.

Thanks

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

I'm using Claro 9.5.8

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

jedgar1mx β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

jedgar1mx β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

Hi @cilefen, I looked in the issue queue for an issue that matched this problem but I didn't find it.

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

Looks like 1.x is no longer supported

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

jedgar1mx β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States jedgar1mx Detroit

New release works. Thanks!!

Production build 0.71.5 2024