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

San Francisco
Account created on 23 June 2008, over 16 years ago
#

Recent comments

πŸ‡ΊπŸ‡ΈUnited States codesmith San Francisco

We've also been using #11 in production for over a month with no issues. +1 RTBC.

πŸ‡ΊπŸ‡ΈUnited States codesmith San Francisco

This just happened to me and the MR fixes the issue.

πŸ‡ΊπŸ‡ΈUnited States codesmith San Francisco

Here's the drush command to turn off the filename_transliteration:

drush config:set dropzonejs.settings filename_transliteration false --input-format=yaml

πŸ‡ΊπŸ‡ΈUnited States codesmith San Francisco

This worked pretty well for me on Drupal 10/CK editor 5. I had to re-add the button to the editor and enable the "Process the output of the Drupalbreaks CKEditor plugin" filter. Existing content that had a teaser break worked fine on the front end. When editing however, the double red teaser line isn't shown.

<!--break-->

is in the code but is not highlighted - only the new " " is highlighted.

So while this does work, I'd agree with #17 that there needs to be an upgrade to convert "

<!--break-->

" in content to " "

πŸ‡ΊπŸ‡ΈUnited States codesmith San Francisco

I got this working by creating a custom Twig filter for html_entity_decode and then adding it to a filter-caption.html.twig template override. Bit clunky though. Looks like Drupal Media can handle HTML in captions just fine.

πŸ‡ΊπŸ‡ΈUnited States codesmith San Francisco

codesmith β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States codesmith San Francisco

As per #3069730 to not use wikimedia/composer-merge-plugin I was able to get drupal/chosen and jjj/chosent to install correctly by:

1) Manually add to "repositories" section

    "repositories": [
        {
            "type": "package",
            "package": {
                "name": "jjj/chosen",
                "version": "2.2.1",
                "type": "drupal-library",
                "extra": {
                    "installer-name": "chosen"
                },
                "source": {
                    "url": "https://github.com/JJJ/chosen.git",
                    "type": "git",
                    "reference": "2.2.1"
                }
            }
        }

2) Then from your project's root directory

composer require 'drupal/chosen:^4.0'
composer require 'jjj/chosen:^2.2'
πŸ‡ΊπŸ‡ΈUnited States codesmith San Francisco

I just ran into this issue on Drupal 10. I used the starterkit to create a theme that had capital letters in the theme name. All block machine names were created with capital letters in them and now unable to make changes to blocks due to this error.

"The machine-readable name must contain only lowercase letters, numbers, and underscores."

πŸ‡ΊπŸ‡ΈUnited States codesmith San Francisco

This just happened to me updating a site from Drupal 9.5 to Drupal 10. The site uses the Claro theme for both front and back end. Drush not working and only getting the WSOD. From #27 above I did the second part of this comment and was able to get a bootstrap. Then clearing the cache fixed the issue.

https://www.drupal.org/forum/support/upgrading-drupal/2023-05-30/migrati... β†’

πŸ‡ΊπŸ‡ΈUnited States codesmith San Francisco

codesmith β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States codesmith San Francisco

I just installed this module on a Drupal 10 site and same issue when setting this up as a block. I get the title but no tags shown. I made sure the correct taxonomy machine name was set. My taxonomy is used for Media items though - maybe this only works with Nodes?

πŸ‡ΊπŸ‡ΈUnited States codesmith San Francisco

Workaround in #8 worked for me - thanks!

πŸ‡ΊπŸ‡ΈUnited States codesmith San Francisco

@smustgrave - could you elaborate on what you think is needed? If disable_resize defaults to false on upgrade, looks existing max_resolution handling will still be fine.

πŸ‡ΊπŸ‡ΈUnited States codesmith San Francisco

@rcodina - wouldn't it be better to change the "int" parameter in file_validate_is_image() to "bool", rather than switching the schema to an "int" - bool seems more appropriate here. Thanks for your work on this! I'm about to do a follow up patch to get this working for webform.

πŸ‡ΊπŸ‡ΈUnited States codesmith San Francisco

I just updated to 7.x-2.14 and I'm now getting this issue.

The value input for field When Start date is invalid:
The value 01/27/2023 09:15 pm does not match the expected format.

This is a content type with Date field type, Calendar popup, optional End Date but not enabled in this case.

Is this the same problem as this issue or should I open a new one? Seems like the fixes here broke things. I rolled back to 7.x-2.13 and changing the date works again.

Production build 0.71.5 2024