🇮🇳India @bmahesh03121

Refined patch #11

Changes :

changed search_published_contents_only to search_published_content_only

changed Search published contents only to Search published content only

bmahesh03121 → created an issue.

great work @skoro!

I was developing similar push notification functionality as well, my implementation looks very similar to this module,

i would like to actively participate in creating new feature requests, development and issue fixes for next few months

i will also suggest to create a slack group where people can connect for standardising this module as the base module for native push notifications functionalities

As push notifications are not part of the web page, we need to set the path alias(if exists) while registering the push notification.

  /**
   * Creates a block instance based on default settings.
   *
   * @param string $plugin_id
   *   The plugin ID of the block type for this block instance.
   * @param array $settings
   *   (optional) An associative array of settings for the block entity.
   *   Override the defaults by specifying the key and value in the array, for
   *   example:
   *   @code
   *     $this->drupalPlaceBlock('system_powered_by_block', array(
   *       'label' => t('Hello, world!'),
   *     ));
   *   @endcode
   *   The following defaults are provided:
   *   - label: Random string.
   *   - id: Random string.
   <del>*   - region: 'sidebar_first'.</del>
   *   - region: 'content'.
   *   - theme: The default theme.
   *   - visibility: Empty array (block will be visible on all pages).
   *
   * @return \Drupal\block\Entity\Block
   *   The block entity.
   *
   * @todo
   *   Add support for creating content block instances.
   */
  protected function placeBlock($plugin_id, array $settings = []) {
    $config = \Drupal::configFactory();
    $settings += [
      'plugin' => $plugin_id,
      'region' => 'content',
      'id' => $this->randomMachineName(8),
      'theme' => $config->get('system.theme')->get('default'),
      'label' => $this->randomMachineName(8),
      'visibility' => [],
      'weight' => 0,
    ];

@joachim looking at this, i found that the default value for region is

sidebar_first

, but in function definition its taking

content

as default region

+ will it be good idea to provide the example with few more settings like visibility, region, theme instead of just label.

Working on this

#11 tested and works fine, thanks joseph.olstad and gugalamaciek

Any update on the Drupal 10 compatible version release?

Any update on the Drupal 10 compatible version release?

Any update on Drupal 10 compatible version release?

Any update on Drupal 10 compatible version release ?

please check similar issue here https://www.drupal.org/project/drupal/issues/3378812#comment-15184658 🐛 "Content language and translation" form doesn't save "Custom language settings" data Postponed: needs info keeping this in review.

apologies, let me clarify, after selecting or deselecting the elements at the top in 'Custom language settings', it will show or hide the details field translations settings. if you want to disable translations you can deselect the fields translations in below details section for particular element and can also set the default value for 'Default language' as the site's default language. after saving that it will not show the element as selected at the top 'Custom language settings'. i understand your issue now. that by changing the settings at the top, it should disable the whole translation. but I think the best way should be to review the fields and enable/disable the translations as required. instead of disabling the translations absolutely with non-recoverable translation loss issues. keeping this in review. please share your thoughts.

Works as expected, after selecting an entity type you must select at least add default translation and one field. otherwise it will behave as default settings and will save the configuration.

changing the status, as this works as expected.

Hello @Tanuj, this works as expected, actually with content language as 'sites default' and language alterable false, it is Default settings. and the form build checks if the configuration stored matches the default configuration then there is no need to keep this. if you make any changes to the default config other than (content_language: sites_default, language_alterable: false.) then it will save the settings.

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