🇮🇳India @imalabya

imalabya → created an issue.

imalabya → created an issue.

Adding a patch for 2.0.x branch

imalabya → created an issue.

@kristen pol Removed the component from the starshot_demo subtheme.

The recent dev changes have made the title, sources, poster, width, height & fallback_text the required prop in the component.yml for iframe. IMO, it should be the sources. Updated the MR with the same.

@kristen pol Removed the component from the starshot_demo subtheme.

The recent dev changes have made the vertical_spacing the required prop in the component.yml for iframe. IMO, it should be the url Updated the MR with the same.

https://git.drupalcode.org/project/demo_design_system/-/blob/1.0.x/components/01-atoms/iframe/iframe.component.yml?ref_type=heads

I went through the document and it made sense for a simple start as mentioned in #6

However, here is my experience working with Search functionalities for client projects. Most of the time, clients require tracking of the search keywords and search results. Search API Tracking → has been the go-to module for this with some modifications sometimes based on the requirement, but the module does provide good foundational tracking. This can be used in conjunction with the Dashboard → recipe by providing a widget.

A few of the modules which I generally use when working on projects

• Editoria11y Accessibility Checker →
• Block ARIA Landmark Roles →
• HTML Purifier →

the_g_bomb → credited imalabya → .

imalabya → changed the visibility of the branch 3468918-content-block-types to active.

imalabya → changed the visibility of the branch 3468918-content-block-types to hidden.

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

imalabya → created an issue.

@ifrik @Ruturaj Chaubey
When configurations are synchronized, should we also show the block with a status message?

Opened an initial patch to export the allow_override config. The tests are failing though.

imalabya → created an issue.

Facing a similar issue. Have a base Content type recipe that has a dependency on the core/recipes/editorial_workflow that has a workflows.workflow.editorial configuration.

Now there are 2 scenarios one which works without an issue other one throws an error

1. Page content type recipe have a dependency on the base Content type recipe. The Page content type recipe is applied when my profile recipe is applied and it applies successfully without any error.
2. Article content type recipe also has a dependency on the base Content type recipe. However, the Article content type recipe is not applied during the profile recipe installation. So when the profile recipe is applied, I try to apply the Article Content type recipe it fails with the error The configuration 'workflows.workflow.editorial' exists already and does not match the recipe's configuration coming from the editorial_workflow recipe.

The Image field throws the below error for images with Spaces in the filename.

Exception: [src] Invalid URL format in Drupal\experience_builder\Plugin\Adapter\AdapterBase->validateConformanceToJsonSchemaType() (line 68 of /var/www/html/web/modules/experience_builder/src/Plugin/Adapter/AdapterBase.php).

@gauravvvv Try uploading an image with a simpler file name like banner.jpeg That will work

@Wim Leers Images with spaces in the file like Filename here.jpg will throw the error. However, this works on a normal image field

Added myself to the ping list

@Kristen Pol Below are the findings

- Used the conversion script to generate the yml file and README.md
- The video.component.yml & README.md file were generated inside demo_design_system/components/01-atoms/video
- Copied the demo_design_system/components/01-atoms/video to demo_design_system/starshot_demo/components/01-atoms/video
- Verified the SDC component in the SDC Registry

@Kristen Pol Below are the findings

- Reviewed the SDDS SDC conversion guide
- Used the conversion script to generate the yml file and README.md
- The iframe.component.yml & README.md file were generated inside demo_design_system/components/01-atoms/iframe
- Copied the demo_design_system/components/01-atoms/ideam to demo_design_system/starshot_demo/components/01-atoms/iframe
- Verified the SDC component in the SDC Registry

@Kristen Pol Below are the findings

- Reviewed the SDDS SDC conversion guide
- Used the conversion script to generate the yml file and README.md
- The image.component.yml & README.md file were generated inside demo_design_system/components/01-atoms/image
- Copied the demo_design_system/components/01-atoms/image to demo_design_system/starshot_demo/components/01-atoms/image
- Verified the SDC component in SDC Regs

The issue persists on Drupal 10.3 with the Claro admin theme.

@Grimreaper The issue was due to a wrong link preprocess. This has been rectified. You are correct, it's working fine now. Patch is not required.
My apologies.

Added a patch

imalabya → created an issue.

Adding a patch for 2.0.x branch.

Hi @gisle, I am Malabya, Drupal Practice Head at Specbee
On behalf of Specbee, I would apologize for such behavior from one of our team members. However, she is not working with us any longer.

Thanks, @ressa @Frederikvho for highlighting the issue. We have reached out to Nupur about this and explained what was she doing wrong. We are also conducting internal training to make people aware of the Code of Conduct while working on issues to mitigate such instances in the future.

This is something we don't promote or sponsor at Specbee. We have been active contributors to the community since we started using Drupal and always encourage our team members to do their bit to drive the project forward. Although we do conduct regular Code of Conduct sessions, these mentioned instances clearly imply that we need more such sessions conducted internally. Again, I'd like to thank you for bringing this to our notice.

Please reach out to me, on Slack or contact mail, if you notice any such cases in the future.

Regards.

The patch didn't address the wildcard entries in the pages. Adding a patch to fix that.

Updated the patch to fix path_alias.manager.

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

This issue exists in Drupal 9.5 with entity clone

Steps to reproduce:

• Add a Block which have a media reference in a Layout Builder enabled node
• Clone the node
• Go to layout of the new cloned node and edit the block.
• Remove the arrached media reference and try to add a new Media reference (Either by selecting existing media item or upload new)
• Throws an AJAX error Non-reusable blocks must set an access dependency for access control.

imalabya → created an issue.

Adding a patch 8.x-1.x branch

imalabya → created an issue.

The patch doesn't apply

error: while searching for:
      'field_infographic',
    ];
    // Get image files are being used by paragraph.
    $img_fids_by_paragraph = \Drupal::database()->select('file_managed', 'fm');
    $img_fids_by_paragraph->join('file_usage', 'fu', 'fu.fid = fm.fid');
    $img_fids_by_paragraph->fields('fu', array('fid', 'id'));
    $img_fids_by_paragraph->fields('fm', array('uri', 'filename'));

error: patch failed: src/MediaSitemapGenerator.php:77
error: src/MediaSitemapGenerator.php: patch does not apply

imalabya → created an issue.

Here is a patch to make the Token field a textarea.

Here is a patch to make the Token field a textarea.

@AaronBauman Can you please help us with the release? We can't use the dev version of the module since it breaks our pipelines. So, we are dependent on stable releases only.