🇺🇸United States @loze

@idebr Thanks for the review!

We still need the TempStore for now, although it’s doing much less than it used to. I did try to remove it, but if I remember correctly, the issue was related to how the form is submitted in the controller. Some of the required data just wasn’t available at that point. I think it mainly had to do with identifying where replies belonged when multiple forms were present on the page. It’s been a while since I looked at that part, so I’ll need to step through it again to confirm.

The JS commands for items 2 and 3 are no problem.

This approach is working, but I think a cleaner long-term solution would be to create a dedicated FieldFormatter specifically for AJAX forms. That would give us more control over the structure and eliminate the need for complex alters and passing field settings around. I started going down that path but wasn’t sure if it was too big a departure from the original implementation. However, if we’re moving to a new branch where breaking changes are acceptable, I think that’s the way to go.

Tried testing the MR. it applied, but I was unable to get it to work.

The images appear to upload in dropzone. but when I click the submit button I get an error message "At least one valid file should be uploaded."

and in the js console i have

VM11500 drupal.js:64 Uncaught TypeError: Cannot read properties of undefined (reading 'element')
    at VM11522 dropzonejs_eb_widget.common.js:15:39
    at Array.forEach (<anonymous>)
    at Object.attach (VM11522 dropzonejs_eb_widget.common.js:14:60)
    at VM11500 drupal.js:166:24
    at Array.forEach (<anonymous>)
    at Drupal.attachBehaviors (VM11500 drupal.js:162:34)
    at HTMLDivElement.<anonymous> (VM11520 ajax.js:1404:18)
    at ce.each (VM11495 jquery.min.js:2:3129)
    at ce.fn.init.each (VM11495 jquery.min.js:2:1594)
    at Drupal.AjaxCommands.insert (VM11520 ajax.js:1396:19)

Both the EB Media Dropzone widget, and the EB Media Dropzone widget with edit widet.

The patch intended for 10.5 in #47 applies but did not work for me. Does someone have one?

I got this error

ajax.js?v=10.5.4:1143 An error occurred during the execution of the Ajax response: CKEditorError: Cannot convert undefined or null to object
Read more: https://ckeditor.com/docs/ckeditor5/latest/support/error-codes.html#error-Cannot convert undefined or null to object

loze → created an issue.

And here's a patch for composer

This is working as expected in my initial testing, I will continue to test it out with other providers. But this is now inline with what the core Media module is doing with the oEmbed field formatter.

loze → created an issue.

And here is a static patch to test with composer.

I've only tested this minimally but it appears to be working well for me. Thanks!

loze → created an issue.

I think this is pretty good now, Ive tested several different api reports methods and it seems to be retrieving the data correctly.
The latest code is in MR18.

This should now:

• Support all the reporting methods the api provides.
• Work if the params are cameCase or snake_case.
• Provides an option for forcing a cache refresh.
• Cleans up coding standards
• Better error handling when fetching data fails.

Here is a patch to use with composer if anyone want to test it out.

I made another improvement.

The static array key map that @mugesh.s added was good, but didn't cover all potential parameters. Instead of maintaining a static list, I added a method convertParamKeysToSnakeCase() that will replace all the first level keys in $params[0] with snake_case versions.

Ive added a few things to MR18

1. Supporting additional report request types

• RunPivotReportRequest();
• RunRealtimeReportRequest();
• BatchRunReportsRequest();
• BatchRunPivotReportsRequest();
• RunReportRequest();

2. Allow forcing a cache refresh for the api call.
you would call it like this in your module.

$service = GoogleAnalyticsReportsApiFeed::service();
$feed = $service->runReport($params, ['_refresh' => TRUE]);

GoogleAnalyticsReportsApiFeed::service()->runPivotReport($params); is not working.
I think we need to do something like this

switch ($func) {
      case 'runPivotReport':
        $params[0] = new RunPivotReportRequest($converted);
        break;

      default:
        $params[0] = new RunReportRequest($converted);
    }

It appears there is a setting for this in the dev version.

Created a MR of the 2 line patch in #10 to help move this along.

4 years later the patch still applies and works. +1

patch here works 📌 Support styling Hosted Fields RTBC

It looks like this module implements its own CSRF token logic. What was the rationale for not using Drupal’s built-in _csrf_token: TRUE in the router? From my understanding, defining this in the route (similar to the Flag module) could eliminate much of the custom token-checking logic and simplify the code significantly.

Would love to get tome input from the maintainers.

This MR does 2 few things.

1. It passes the parent entity to the oembed_lazyload_placeholder theme function.
2. Adds an option in the display formatter to choose the image field (if any others exist on the bundle) to use in the placeholder.

loze → created an issue.

Should we also clear any configured default membership type for this group bundle to keep programmatic removal consistent with the UI flow?

Yes, I think you are right.

This is a super old issue, but I am looking to do the same and didnt see a way to do it.

The field settings should allow you to specify a directpry and support tokens like an image field does.

I can work on this if the maintainers think this is something that will be added.

Added a small fix for an undefined variable error that was showing in the logs on a last page of comments.

heres a new patch for composer.

loze → created an issue.

And here's a patch you can use with composer.

I've updated the IS and made a few final updates to MR !13. All tests are passing.

Since this fundamentally changes how the module works (single comment insertion instead of full rebuilds), I suggest creating a new 2.x-dev or alpha branch. This way current users can stay on the stable 1.x branch while others can test the new approach.

I've been using this in production on several sites for a while now - it's been solid across different scenarios including sites with hundreds of comments, multiple comment fields, views, etc.

This issue has been open since 2020 and I've put a lot of work into making this a comprehensive solution. It fixes the original problems, resolves several related issues, and brings the module in line with how the D7 version and modern commenting systems work.
Would the maintainers be open to creating a 2.x branch for this?

Happy to help with any follow-up work needed.
Thanks!

I’ve been following this issue and testing the patches for a while. Overall, things are working well, but I did notice a couple of cases where the behavior isn’t what I would expect:

1. When a comment is denied access by returning AccessResult::forbidden() in a hook_comment_access() implementation, it is still visible in the thread. CommentDefaultFormatter::viewElements() doesn’t currently filter out inaccessible comments. It just calls viewMultiple(), which doesn’t perform access checks.

2. The comment field is hidden when the last comment is inaccessible.
CommentFieldItemList::lastPublishedCommentAccess() is used by CommentFieldItemList::access() to determine whether the entire field/thread is accessible. If the last comment in a thread is denied access, the entire field, including the comment form, is hidden. In this case, CommentDefaultFormatter::viewElements() is never called.

I've been testing this out and it works really well, thanks.

One issue I can see is, on the review page, all the users nodes and comments are listed.

If either of the users being merged have a lot of comments or nodes this can cause timeouts since we load every entity and then loop through them all to print the titles.

It would probably better to just show a summary of how many, grouped by bundle.

"X Article Nodes, Y Page Nodes, etc"

Or possibly list the first few and then print "and X more" sort of like how VBO does.

I've created MR5 which is @dipakmdhrm's work against 2.0.x which is the current branch.

I need some of these features for a product to get this more in line to what we were able to do in the D7 version. Until now there hadn't been an update to this issue since almost a year ago.

I would love to hear from the moderators as to the status of this module and their plans for a path forward.

@dipakmdhrm can you update the IS with the current status of the Remaining tasks so we can see what still needs to be worked on?

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

Ive added a composer.json file and made a few changes to the info.yml

loze → created an issue.

Also while working on this I noticed that the og settings config value og_group_manager_full_access is never used anywhere.
The description of that field is "When enabled the group manager will have all the permissions in the group."

Is the intent of this setting to grant all permissions for the administrator role? If so, perhaps this MR should solve that too since its related.

When enabled the admin checkboxes would then be disabled, forcing group administrators/managers to have all perms.
When the setting is disabled, the checkboxes would be enabled allowing the site admin to set which permissions a group administrator/manager would get.

@amitaibu - I've taken a stab at adding a test, and it passes. Can you take a look and see if this is what you wanted?

Thanks

All tests are green now.

Ive added quicktabs.post_update.php. Is this more along the line of what you are asking for?

All tests are green now.

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

I tried this out and it didnt quite work for me.

the <!--break--> tag is still ignored when creating the trimmed version.

For the record there is a contrib module that allows <!--break--> in ckeditor https://www.drupal.org/project/ckeditor_drupalbreaks →

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

I realize this is an old post, but I am seeing exactly what described in #11 and #12 in the latest 8.x-2.4 release, so I am reopening it.

with debug: true
views UI preview has CDATA on the description tags
front end has CDATA on the description tags

with debug: false
views UI preview has CDATA on the description tags
front end DOES NOT have CDATA on the description tags

I don't have any template or preprocess overrides for views_rss

I'm using Drupal 10.5

I too am seeing my html email escaped due to the html_convert_format being limited to filters that escape the html.

Isn't this defeating the purpose? What was the rational to limiting the filters to these?

I'm interested feature. I will take a stab at getting this patch to work with the current version.

I tried to get this to work with 4.1.x.

It does appear to be batching the command now.

loze → changed the visibility of the branch 3348339-batch-fix-references to active.

loze → changed the visibility of the branch 4.0.x to hidden.

loze → changed the visibility of the branch 3348339-batch-fix-references to hidden.

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

loze → created an issue.

loze → changed the visibility of the branch 3202896-oembed-error-message to hidden.

There is the hook spambot_registration_blocked that is invoked on both user registration and webform submissions.

But no hook is triggered when spam is detected on a cron run.

loze → created an issue.

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

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

I have created a MR that removes the readonly properties from PrivateMessageForm. This resolves the issue for me.

loze → created an issue.

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

here is a screenshot of the checkbox becoming active after the patch.

Unfortunately, I'm not really sure what to do for adding a test. Hopefully someone else can help out with that.

MR43 Removes setting #disabled for default roles, it only sets them for the admin role.

Also if I'm not mistaken, there isn't a need to set the default value here, the defaults for each permission have already been populated.
Without doing this, permissions that have a default role to able to be unchecked.

This allows me to uncheck the "subscribe to group" permission for non-members.

loze → created an issue.

I also wanted to chime in to say I would like the font sizes and colors to insert css classes into the html instead of hardcoding css values in the style attribute.

I just realized that the UUID for title I am seeing is do to the patch here ✨ Add an option to only let paragraphs be used once Postponed: needs info . I still feel that there should be an option (maybe per embed button) to disable displaying these status messages.

loze → created an issue.

MR11 checks if the entity is an instance of EntityChangedInterface and seems to resolve the issue for me.

loze → created an issue. See original summary → .

loze → created an issue. See original summary → .

loze → created an issue.

I see this in 10.5. Close button is missing.

Can someone roll it for 10.5?

Ive added an update hook which sets the new default value on all existing QT instances.

Added the config variable to QuicktabsConfigSchemaTest but I am unsure how to go about testing the actual functionality and could use some help, thanks.

Ignore MR14, that is no longer valid and I am unable to close it.

MR37 is the latest, against 4.0.x

Here is a patch for composer that should work with the 4.0.x dev branch

loze → changed the visibility of the branch 3189439-last-clicked-tab to active.

loze → changed the visibility of the branch 3189439-last-clicked-tab to hidden.

Yes, there is an event for views_infinite_scroll.new_content. However this is triggered when the content is loaded and BEFORE it is populated in the DOM. Therefore if your custom js relies on the new items being in the DOM you need to use setTimeout() and give it enough time to populate before executing your code.

the patch in #6 still applies and adds the event views_infinite_scroll.new_content.appended wich triggers after the content is added to the DOM.

In my use case I am adding slides to a custom carousel script, and I need to refresh the carousel when new slides are added to the DOM.

Reopening this issue for reconsideration.

Ive been using this and it works, but I think it would be nice if we could specify a different progress type for views pager vs views filters.

Currently the js looks for this.$view.find('[data-progress-type]') this returns the value of the first element in the view with the data-progress-type attribute.

If this logic could be modified to instead look for the closest element with the attribute from the triggering element, You would able to specify different values on the pager and views filters wrapping elements.

Does anyone have this working for D10+ ?