🇺🇸United States @robphillips

Another re-roll so this can be applied to 11.1.x.

Fixed an issue and opened a MR.

Opened a MR that includes 2493853-24-d9-wrong-comment-count.patch for the contrib module.

robbiehobby → made their first commit to this issue’s fork.

robbiehobby → created an issue.

MR includes the following fixes that are applicable to Claro and Gin:

1. Previous patch to fix the check/uncheck control
2. Fixed check/uncheck visibility when "Multiple" is not selected
3. Fixed position of color legend (for gin)

robbiehobby → made their first commit to this issue’s fork.

This is working in Drupal 11.1.4.

Opened a new merge request for version 11.x. It includes several bug fixes, improvements, and test adjustments. I did my best to model all changes based on pre-existing solutions in the node revisions implementation.

I haven’t figured out how to resolve the core/modules/jsonapi/tests/src/Functional/CommentTest.php test. Maybe someone who is familiar with that test can jump in? The other failing tests do not seem related to these changes, but I could be wrong.

There probably needs to be new tests created for comment content moderation and for the user cancel changes. Unfortunately, I won’t have time to work on these immediately. Please feel free to jump in if you'd like.

1. Added the missing revision keys to the config and tests.
2. Added the revision UI, links, and access control.
3. Kept the existing comment permission structure with administer comments being the permission that can perform revision CRUD operations.
4. Removed the base field alter hook because this should be configured in the content moderation workflow rather than in the code.
5. Added shared table indexes for the comment_revision table.
6. Created comment_mass_update, a carbon copy of node_mass_update, to primarily handle hook_user_cancel operations gracefully. It includes a new $syncing option to prevent the creation of new revisions when reassigning comments to the anonymous user account. A similar issue for nodes exists at [ https://www.drupal.org/project/drupal/issues/3062900] → ( https://www.drupal.org/project/drupal/issues/3062900 → ).
7. Added a comment moderation handler.
8. Updated the comment links renderer to be aware of revisions.

robbiehobby → changed the visibility of the branch 11.x to hidden.

Attaching a patch file that applies cleanly to version 2.0.0-alpha3.

A new MR has been opened for version 2.x. Test cases and PHPCS issues have been fixed. There are some additional warnings from cspell and stylelint that are not related to these changes.

robbiehobby → changed the visibility of the branch 8.x-1.x to hidden.

robbiehobby → changed the visibility of the branch 2.0.x to hidden.

robbiehobby → changed the visibility of the branch 2746715-runtime-should-be to hidden.

robbiehobby → changed the visibility of the branch 8.x-3.x to hidden.

I could not confirm this issue. Non-existent entity pages with dynamic path aliases correctly displayed a 404 error. Please reopen the ticket with additional information if the problem persists.

robbiehobby → made their first commit to this issue’s fork.

Closing due to insufficient information to confirm the issue. Please reopen when you have additional details.

I understand how comments could be useful, however, this module relies on the Drupal core conditions API, which manages path parsing. I prefer not to introduce changes that deviate from the core's behavior or add unnecessary code. Thanks for the recommendation though.

As a workaround, you could keep a plain text note or README in the project to describe the configuration.

Drupal 11 support has been released. Thanks for the co-maintainer offer.

Merged. New release will be up shortly. Thanks for the reminder.

robbiehobby → made their first commit to this issue’s fork.

greggles → credited robbiehobby → .

You'll also need to exclude the Ajax autocomplete URL. It usually looks like /ajax/autocomplete. If you're not sure, take a look at your network tab in the developer tools.

Re-rolled for 8.x-1.7

robbiehobby → created an issue.

robbiehobby → created an issue.

robbiehobby → created an issue.

robbiehobby → created an issue.

robbiehobby → created an issue.

robbiehobby → created an issue.

+1 RTBC

robbiehobby → created an issue.

Unfortunately, no because Uppy.js considers uploads as unordered. See https://github.com/transloadit/uppy/issues/1779#issuecomment-522512989. I may build an extension in the future if they don't add some kind of order support soon.

robbiehobby → created an issue.

Thanks. Merged and will be included in the next release.

+1 RTBC

Re-rolled for 10.3.x

Re-rolled for 10.3.x

robbiehobby → changed the visibility of the branch 9.1.x to hidden.

robbiehobby → created an issue.

Could you also provide the Drupal version, module version, and specify any other file related installed modules.

What does your configuration look like? I'll need more information to be able to assist you.

BramDriesen → credited robphillips → .

Took a crack at the problem. Search API Solr offers up a similar solution. Re-index is only triggered when a indexed field has changed. Tested with both in-site configuration changes and using configuration sync. There might be some edge cases. Definitely needs more eyes on it.

https://git.drupalcode.org/project/search_api_solr/-/blob/4.x/src/Plugin...

robphillips → made their first commit to this issue’s fork.

robphillips → created an issue.

At the moment it can only be added to an entity form display. Leaving this open as I might find time to convert to a form element type.

You need to re-install the module and disable the filter on every text format before uninstalling. This is a known issue in Drupal core.

robphillips → created an issue.