Problem/Motivation
Hello project maintainers,
This is an automated issue to help make this module compatible with Drupal 11.
Changes will periodically be added to this issue that remove deprecated API uses. To stop further changes from being posted, change the status to anything other than Active, Needs review, Needs work or Reviewed and tested by the community. Alternatively, you can remove the "ProjectUpdateBotD11" tag from the issue to stop the bot from posting updates.
The changes 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:
- Accept automated changes until this issue is closed
If this issue is left open (status of Active, Needs review, Needs work or Reviewed and tested by the community) and the "ProjectUpdateBotD11" tag is left on this issue, new changes 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 changes posted here will cover more of the deprecated API uses in the module.
Patches and/or merge requests posted by others are ignored by the bot, and general human interactions in the issue do not stop the bot from posting updates, so feel free to use this issue to refine bot changes. The bot will still post new changes then if there is a change in the new generated patch compared to the changes that the bot posted last. Those changes are then up to humans to integrate.
- Leave open but stop new automated changes.
If you want to use this issue as a starting point to remove deprecated API uses but then don't want new automated changes, remove the "ProjectUpdateBotD11" tag from the issue and use it like any other issue (the status does not matter then). If you want to receive automated changes again, add back the "ProjectUpdateBotD11" tag.
- 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, Needs work and Reviewed and tested by the community) and no more automated changes will be posted here.
If the issue is reopened, then new automated changes will be posted.
If you are using another issue(s) to work on Drupal 11 compatibility it would be very useful to other contributors to add those issues as "Related issues" when closing this issue.
Remaining tasks
Using the patches
- Apply the latest patch in the comments by Project Update Bot or human contributors that made it better.
- Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.
- Provide feedback about how the testing went. If you can improve the patch, post an updated patch here.
Using the merge request
- Review the merge request and test it.
- Thoroughly test the changes. These changes are automatically generated so they haven't been tested manually or automatically.
- Provide feedback about how the testing went. If you can improve the merge request, create a new branch and merge request and work from there.
Warning: The 'project-update-bot-only' branch will always be overwritten. Do not work in that branch!
Providing feedback
If there are problems with one of the changes 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 Project analysis issue queue.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | markdown.3.0.x-dev.upgrade_status.post_rector.txt | 23.93 KB | project update bot |
| #2 | markdown.3.0.x-dev.rector.patch | 1.34 KB | project update bot |
Issue fork markdown-3438472
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
project update bot commentedThis is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) is also openend and updated.
It is important that any automated tests available are run and that you manually test the changes.
Drupal 11 Compatibility
According to the Upgrade Status module, even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.1, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.ymlfile for Drupal 11 compatibility.The compatibility issues that Upgrade Status found after the Drupal Rector fixes were applied are attached to help you resolve them manually.
Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug information
These packages were used to generate the fixes:
Comment #4
scitoWe are in the Drupal 7 to Drupal 11 migration. Not having a Drupal 11 Release of the Markdown module is blocking for us. If it is not fixed in the meantime, I'll have a look at this issue.
Comment #5
interlated commentedNote - I use Markdown to include module documentation, not with the text editor.
* web/modules/patched/markdown/src/Annotation/ComposerPackage.php 34 Call to deprecated method getInstalledVersion() of class Drupal\markdown\Util\Composer. Deprecated in markdown:8.x-2.0 and is removed from markdown:4.0.0. No replacement.
Marked as deprecated. Delete now?
* web/modules/patched/markdown/src/Annotation/ComposerPackage.php 34 Call to deprecated method getVersionFromClass() of class Drupal\markdown\Util\Composer. Deprecated in markdown:8.x-2.0 and is removed from markdown:4.0.0. No replacement.
As above
* web/modules/patched/markdown/src/BcSupport/SubformState.php 16 Class Drupal\markdown\BcSupport\SubformState extends deprecated class Drupal\markdown\BcSupport\FormStateDecoratorBase. Deprecated in markdown:8.x-2.0 and is removed from markdown:3.0.0. Use Drupal\Core\Form\FormStateDecoratorBase instead.
Delete now
Delete the whole BCSupport package
I can't see the referenced @todo Move upstream to https://www.drupal.org/project/installable_plugins. Something here https://www.drupal.org/docs/drupal-apis/plugin-api?
I can't see any references to "InstallablePlugin" outside of markdown. Is this a custom concept for markdown to manage the parsers?
This refactoring does fall apart here.
* web/modules/patched/markdown/src/Exception/MarkdownFileNotExistsException.php 11 Class Drupal\markdown\Exception\MarkdownFileNotExistsException extends deprecated class Drupal\markdown\Exception\MarkdownException. Deprecated in markdown:8.x-2.0 and is removed from markdown:3.0.0. Use Drupal\markdown\Exception\MarkdownExceptionInterface instead.
Refactor now.
PluginBase
PluginInterface
Comment #6
interlated commentedWhat is a similar module? 'Crop'? Footnotes?
Comment #7
interlated commentedBreaks in drush
PHP Fatal error: Trait "Symfony\Component\DependencyInjection\ContainerAwareTrait" not found in /Users/jrobens/Sites/gardensofstone2/web/modules/patched/markdown/src/PluginManager/InstallablePluginManager.php on line 32
Means this module isn't usable for me.
The best shot I can find to implement plugins is from 'feeds tamper'. I can take a shot at implementing this if it helps
use Drupal\Component\Plugin\PluginManagerInterface;
use Drupal\Core\Plugin\DefaultLazyPluginCollection;
ContainerAwareTrait has been deprecated
https://www.drupal.org/project/drupal/issues/3431362
Comment #11
interlated commentedUsed git pull and enabled the markdown module:
Trait "Symfony\\Component\\DependencyInjection\\ContainerAwareTrait" not found in /web/modules/patched/markdown/src/PluginManager/InstallablePluginManager.php on line 32
ContainerAwareTrait is deprecated in Symfony.: https://www.drupal.org/project/drupal/issues/3415938
ContainerAwareInterface deprecated
Drupal\Component\Plugin
Comment #13
suryabhi commentedcurrent output of drush us-a markdown
Comment #14
suryabhi commentedComment #21
interlated commentedI have applied !37. The site ran OK.
The use case is atypical. Prints out the README.md file as part of help. An error that I will follow up on
The code is
This was on Drupal 10. The version of commonMark that was installed with Drupal 10 does not appear compatible. This problem does not occur on drupal 11. Original version league/commonmark:1.6.7
Comment #22
interlated commentedOne more error on Drupal 11
drush cr
In ContainerBuilder.php line 1345:
The service "markdown_plugin_manager" tagged "plugin_manager_cache_clear" must not be abstract.
Comment #24
sakthi_dev commentedGot an error on cache clear as follows so resolved the issue.
Please review.
Comment #26
megachrizI got a fatal error on a D10 site:
Error: Call to undefined method League\CommonMark\CommonMarkConverter::convert() in Drupal\markdown\Plugin\Markdown\CommonMark\CommonMark->convertToHtml() (line 183 of /Users/youri/Websites/drupal/modules/wip/markdown/src/Plugin/Markdown/CommonMark/CommonMark.php).
Is it possible that the code drops support for CommonMark v1? And is that necessary? I would say that should be handled in #3283349: Add support for Commonmark v2. So I think that commit 3283349 should be reverted.
Comment #27
kmonty@megachriz The module should probably drop support for Commonmark v1 given it is insecure / out of support. But I agree that is best handled in #3283349: Add support for Commonmark v2
Comment #28
megachrizI reverted a commit. I think it would also be a good idea to revert anything that tries to fix deprecations from Markdown itself. However, if fixing these deprecations is necessary for Drupal 11 support, they should of course be done, but even in that case I think it would still be better to handle these in an other issue first. Because it looks like that some attempts to fix these deprecations here introduced new bugs.
Comment #29
orkutmuratyilmazI've checked MR !37 and it says: "Test summary: 350 failed, 425 total tests"
Do we need to refactor it?
Comment #30
orkutmuratyilmazAlso, after applying the patch, I've scanned it with the upgrade status module. The result is below:
Comment #32
joelpittetThanks all for helping get this over the hump. There still might be bugs but I tested it and fixed most of the tests in D11 with CommonMark 2. I left common mark 1.6 support for any BC but anybody on that should jump to 2.7 because of the security stuff there.
Comment #36
fmb commentedThis is great, thanks! Could you publish a new release?
Comment #37
joelpittet@fmb not quite yet. Working on getting a bunch of fixes and phpstan clean up first #3373147: Fix phpstan deprecation errors Then I will feel more comfortable with a release.
Comment #38
fmb commentedAll right, thanks!
Comment #39
megachrizAnd I see lots of test failures with Drupal Core 11.3.x-dev, while all tests pass with Drupal Core 11.2.8. 🤔
I hope my client will give me some time to help with this.
Comment #40
m.stentaThis caused an issue with headings in CommonMark GFM: #3580640: CommonMark GFM does not format headings