Automated Drupal 10 compatibility fixes

Created on 18 July 2022, almost 2 years ago
Updated 17 October 2023, 8 months ago

Problem/Motivation

Hello project maintainers,

This is an automated issue to help make this module compatible with Drupal 10.

To read more about this effort by the Drupal Association, please read: The project update bot is being refreshed to support Drupal 10 readiness of contributed projects โ†’

Periodically patches will be added to this issue that remove Drupal 10 deprecated API uses. To stop further patches from being posted simply close this issue (any status besides Active, Needs review or Needs work) or remove the "ProjectUpdateBotD10" tag from the issue.

The patches will be posted by the Project Update Bot โ†’ official user account. This account will not receive any issue credit contributions for itself or any company.

Proposed resolution

You have a few options for how to use this issue:

  1. Accept automated patches until this issue is closed

    If this issue is left open (status of Active, Needs review or Needs work) and the "ProjectUpdateBotD10" tag is left on this issue, new patches will be posted periodically if new deprecation fixes are needed.

    As the Drupal Rector project improves and is able to fix more deprecated API uses, the patches posted here will cover more of the deprecated API uses in the module.

  2. Leave open but stop new automated patches.

    If you want to use this issue as a starting point to remove deprecated API uses but don't want new automated patches simply leave this issue open but remove the "ProjectUpdateBotD10" tag from the issue.

    You can use Drupal Rector yourself to make these patches.

    If you want to receive automated patches again, add back the "ProjectUpdateBotD10" tag.

  3. Close it and don't use it

    If the maintainers of this project don't find this issue useful, they can close this issue (any status besides Active, Needs review or Needs work) and no more automated patches will be posted here.

    If the issue is reopened, then new automated patches will be posted.

    If you are using another issue(s) to work on Drupal 10 compatibility it may be useful to other contributors to add those issues as "Related issues" when closing this issue.

Remaining tasks

Using the patches

  1. Apply the patch in the comment by Project Update Bot โ†’ .
  2. Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.

Providing feedback

If there are problems with one of the patches posted by the Project Update Bot โ†’ , such as it does not correctly replace a deprecation, you can file an issue in the Drupal Rector issue queue โ†’ . For other issues with the bot, for instance if the issue summary created by the bot is unclear, use the Infrastructure project issue queue โ†’ using the component โ€œBot: Drupal Rectorโ€.

๐Ÿ“Œ Task
Status

Fixed

Version

2.0

Component

Code

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • ๐Ÿ‡ฌ๐Ÿ‡ชGeorgia almador

    Once the ckeditor4 is deprecated now, maybe the dependencies in info.yml should be updated to ckeditor5?

  • ๐Ÿ‡ฉ๐Ÿ‡ชGermany Istari

    Mysdiir โ†’ made their first commit to this issueโ€™s fork.

  • @mysdiir opened merge request.
  • ๐Ÿ‡ฉ๐Ÿ‡ชGermany Istari

    - Updated Drupalbreaks to CKEditor5 object orientated architecture
    - added DrupalbreaksFilterPlugin.php which uses FilterBase
    - FakeObject become obsolete

  • Status changed to Needs work about 1 year ago
  • ๐Ÿ‡ฎ๐Ÿ‡ณIndia Bushra Shaikh

    I applied the MR !1 got error:

    error: No valid patches in input (allow with "--allow-empty")

  • ๐Ÿ‡ฉ๐Ÿ‡ชGermany Istari

    Could you provide the steps which step you have taken untill the error message came up?

  • ๐Ÿ‡จ๐Ÿ‡ฆCanada phjou Vancouver/Paris ๐Ÿ‡จ๐Ÿ‡ฆ ๐Ÿ‡ช๐Ÿ‡บ

    Hello, I am trying to use the module on Drupal 10, I found your branch with fixes, but I cannot require the module because of the dependency on fakeobjects.

    Maybe I am missing something, but I do not understand the composer.json of this module.

      "require": {
        "drupal/fakeobjects": "~8.0"
      }
    

    It requires version 8? The drupal/fakeobjects is compatible Drupal10 but on version 1.2. So I am not really sure why it has 8.0. Am I missing something? Because 8.0 is not matching a branch name either. I changed the composer.json on a fork for 1.2 and the issue doesn't happen anymore. Could this be fixed on the Drupal 10 branch?

  • ๐Ÿ‡ฉ๐Ÿ‡ชGermany Istari

    Heya phjou,
    I will check this asap and give you feedback.
    For the CKEditor 5 migration fakeobjects should't be necessary anymore and maybe I've just overseen it to exclude it.
    I will give it a try asap :)

  • ๐Ÿ‡ฉ๐Ÿ‡ชGermany drupatz

    @Mysdiir

    in #10 you say "deleted fakeobject as dependency from composer.json" --- in which branch/tag did you do that?

  • First commit to issue fork.
  • ๐Ÿ‡ฉ๐Ÿ‡ชGermany Hydra

    @drupatz You can find the code from @Mysdiir here https://git.drupalcode.org/issue/ckeditor_drupalbreaks-3296752/-/compare... - This should probably be better done with a merge request.

    The suggestions made by @vanilla-bear don't seem much reasonable to me.

  • @mysdiir opened merge request.
  • Status changed to Needs review 9 months ago
  • ๐Ÿ‡ฉ๐Ÿ‡ชGermany Istari

    Sry forgot to open a MR the first time.
    MR2 in 3296752-migration-to-ckeditor5

    • dsnopek โ†’ committed 1ff9bd9f on 2.0.x
      Issue #3296752 by Project Update Bot: Automated Drupal 10 compatibility...
  • Status changed to Fixed 8 months ago
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States dsnopek USA

    I've merged the automated patch, plus some minor changes: switching the \Drupal::service('extension.list.module')->getPath(...) to $this->getModulePath(), and changing the fakeobjects version constraint to ^1.2 per #9.

    There's some good stuff in the MR from @Mysdiir which updates the plugin to work with CKEditor 5. However, (1) we should probably do the CKEditor 5 update in a different branch (2.0.x can stay compatible with Drupal 8, 9 and 10, with CKEditor 4 -- for which we need just the simple changes merged here), and (2) there's a bunch of miscellaneous other changes in there (.idea/, node_modules/, etc) and so it can't be merged as is.

    @Mysdiir: I'd recommend opening a new issue and reducing your MR to just the changes necessary to update to CKEditor 5

  • ๐Ÿ‡ฉ๐Ÿ‡ชGermany Istari

    Heya @dsnopek thx for your reply :)
    I will open up a new branch this week due to tight time schedule on DrupalCon.

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

Production build 0.69.0 2024