🇮🇳India @er.garg.karan

er.garg.karan → made their first commit to this issue’s fork.

er.garg.karan → created an issue. See original summary → .

I have updated to the latest version of paragraphs i.e. 1.18. I am using the Gin theme and this issue is fixed for me.

The provided patch doesn't work with latest version of Paragraphs 1.18. Contributing a new patch that works with 1.18.

The code of the patch is exactly same as the one submitted previously under https://git.drupalcode.org/project/paragraphs/-/merge_requests/32.patch

The prodivided patch code in MR 32 can not be applied to Paragraph 1.18.0

er.garg.karan → created an issue.

As mentioned in the Release notes of tmgmt_smartling 8.x-9.8 → , this was changed. That is the cause of this issue.

Thanks @vikramsaini1609 for this patch.

It worked well for me.

@Loparev Can we consider this patch implemented in the module?

I expected a credit for my patch contribution in #74.

Hi @__VINAY

I see you have copied exactly same code from my patch in #17.

I tried deleting a block group manually. It worked like a charm.

But when I exported my configurations and imported them using drush config:import, I got the same error repeatedly until I applied the patch provided in #2.

I am using block group 2.0.0 and Drupal 10.2.

The patch #6 worked perfectly for me until I upgraded from Drupal 10.2 to 10.3 where this patch failed.

I was not able to apply this patch as it kept failing. Created a new patch (with the same code changes) for Drupal 10.3

I have worked on creating this patch to support social media links field. Hope this helps others too.

er.garg.karan → created an issue.

The https://www.drupal.org/project/social_media_links_graphql → is not actively maintained and there is no stable version out even once. Can we reconsider this issue?

Patch #13 works for me.

I have fixed this via a custom code. Basically I am adding an overlay (the old css trick) that does not allow further action until current ajax request finishes.

// mymodule.module file

function my_module_page_attachments(array &$attachments) {
  $attachments['#attached']['library'][] = 'my_module/ajax';
}

// mymodule.libraries.yml file

ajax:
  css:
    theme:
      css/ajax.css: { }
  js:
    js/ajax.js:
      minified: true

// js/ajax.js file

/**
 * Overrider drupal default ajax behavior.
 */
(function ($, Drupal, drupalSettings) {
  Drupal.behaviors.myModuledminAjax = {
    attach: function (context, drupalSettings) {
      'use strict';
      /**
       * Theme override of the ajax progress indicator for full screen.
       *
       * @return {string}
       *   The HTML markup for the throbber.
       */
      Drupal.theme.ajaxProgressIndicatorFullscreen = () =>
        '<div class="ajax-progress-overlay"><div class="ajax-progress ajax-progress--fullscreen"><div class="ajax-progress__throbber ajax-progress__throbber--fullscreen">&nbsp;</div></div></div>';
    }
  };
})(jQuery, Drupal, drupalSettings);

// css/ajax.css file
.ajax-progress-overlay{position:fixed;z-index:1000;top:0;width:100%;height:100%;background:rgba(0,0,0,.4)}

This issue has been fixed with this patch.

Contributing a patch with a few coding standard changes.

er.garg.karan → changed the visibility of the branch 3418394-itemcount-validation-issue to hidden.

er.garg.karan → created an issue.

The patch #65 not working for me when I am trying to add a #required state.
Drupal version 9.5.9

Any update on this issue?

I am using "2.0.0-beta11" version of graphql_compose and still see this issue. When can we have this fix released in a stable version?

Is this issue still being worked on? I am facing this issue too often.

er.garg.karan → created an issue.

#3372741-3: Support for reference link → , the paraagraph description field currently is a textarea. There is no editor there

er.garg.karan → created an issue.

I was able to create this patch. It works for multiple versions of Drupal.

I am also facing this issue.

Steps to reproduce

1. Create a content type "Blog". Make sure you choose to show the language selector drop-down on the node create and edit page.
2. Set the default language of the content type as "Not Specified".
3. Go to blog add form.
4. Choose the language as "French" and add a custom URL "/my-custom-url-for-blog".
5. Save the node and you will be able to create the blog node.
6. Repeat steps #3, #4, and #5 and you will be able to create a new node in French with the same URL "/my-custom-url-for-blog".

Cause
The class Drupal\Core\Path\Plugin\Validation\Constraint\UniquePathAliasConstraintValidator has validate function and it checks for the duplicate URL in a particular language. But the variable "$langcode" in line 49 gets the langcode from the path entity and it is always the default language you choose in Step #2. In my case, it is always "Not Specified".
This works fine when you edit one of the blog because by this time, the language of path alias has been set to "French".

Propose solution
The language should be used from the language dropdown if it is visible on the node add form.

er.garg.karan → created an issue.

Contributing patch for the issue. Just a very basic check was missing.

er.garg.karan → created an issue.

This patch worked great for me until I found a setting "CSRF whitelist" which has a max length of 255 and I wanted to add more domains.

Contributing a patch for that.

This is because the Acquia purge module checks if the shield module is installed and it has username in shield settings.
It should also check if shield is enabled via the "Enable Shield" checkbox or not.

Was a quick fix. Sharing the patch.