🇺🇾Uruguay @jjose.quevedo

Thank you for the update and for the valuable resources! I appreciate the opportunity to contribute and the guidance provided.

I’ll review the recommended readings to improve my maintainership skills and will consider joining the review process for other projects to help the community. Looking forward to participating in #drupal-contribute on Slack/IRC as well.

Thanks again for your time and support—it’s greatly appreciated!

Thanks for your feedback, @avpaderno! I've fixed it

I’ve already fixed the reported issues, and it’s ready for review.

Thanks @vishalkadam!

Thanks guys, for your responses

I have already fixed all the issues mentioned, and it's ready for review again.

jjose.quevedo → created an issue.

jjose.quevedo → created an issue.

Hi folks, I've attached a patch for the webform.element.telephone.js file, adding additional options to the telephone element component.

Hi rodrigoaguilera and nicxvan, thank you for letting me know. FYI: I've had to reupload the patch due to an error I discovered. It should be working fine now.

I downloaded the patch from the merge request, but unfortunately, it didn't work for me. I'm currently using version 4.0.0-alpha5 and I've attached the patch that worked for me in case it helps others

jjose.quevedo → changed the visibility of the branch 5.0.x to hidden.

jjose.quevedo → changed the visibility of the branch 3449166-expose-color-changer to active.

jjose.quevedo → changed the visibility of the branch 3449166-expose-color-changer to hidden.

jjose.quevedo → changed the visibility of the branch 5.0.x to active.

jjose.quevedo → changed the visibility of the branch 5.0.x to hidden.

jjose.quevedo → created an issue.

Thanks for your comment, @berdir. I've already fixed it and tested it

jjose.quevedo → created an issue.

Hi, no worries. Close as fixed. Thanks!

This was solved it using this patch

jjose.quevedo → created an issue.

The issue was fixed

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

Thank you for providing the clarification. I attempted to reproduce the issue again, but I couldn't observe any problems using vanilla Drupal. I followed the steps you outlined, and I'm sharing the screenshots for your reference:

• This is the configuration
  
• This is the original node
  
• This is the translation form of the previous node
  

As you can see, the paragraph can't be added, deleted, or moved in the translated node. So, if there is anything specific you would like me to try or if you have any additional information, please let me know.

Hi, I was trying to reproduce this issue, but I couldn't. It seems everything is working properly using vanilla Drupal. Here are some screenshots:

• One field was hidden in the translation configuration
  
• The field don't appear in the translation of node
  

Hi, I was trying to reproduce this problem and I realized that the error couldn't be related to the Ctools module. I found the error in the paragraph module, so here is the issue #3376909 🐛 Drupal\Component\Plugin\Exception\PluginNotFoundException: The "wemikiwilacri" entity type does not exist. in Drupal\Core\Entity\EntityTypeManager->getDefinition() Needs review . Please take a look and I hope this fix is what you need

jjose.quevedo → created an issue.

I've tested it and everything works as expected

Updating the patch

Here is a patch to solve the issue. Please take a look

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

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

Hi @jrockowitz,

I've been attempting to reproduce the issue you mentioned, but found an error in the process. It's possible that I didn't replicate the issue accurately. Here are the steps I followed:

1. Created a new paragraph.
2. Added an email field to the paragraph.
3. Created a webform.
4. Added several fields to the webform.
5. Created a custom content.
6. Included the previously created paragraph as a field within the content.
7. Added the webform as a field and tried to insert a token, as shown in your screenshot.

However, I received the following error message:

Default submission data (YAML) is using the following invalid tokens

I'm wondering if I missed any steps or if there's something additional I need to do in order to reproduce the issue accurately.
Any guidance or assistance you can provide would be greatly appreciated.

Thank you!

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

Hi, after carefully reviewing both the current issue and issue 3362620 🐛 Incorrect path from token [:url:path] with slash Active , I have come to the conclusion that it would be beneficial to include the proposed change. We can ensure that when a user adds a forward slash (/) in front of the token string, it will be automatically removed before processing. This adjustment will help maintain consistency and prevent any potential conflicts or unexpected behavior.

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

Hi, I've added the patch, just in case someone needs it. Thought it might come in handy!

jjose.quevedo → created an issue.

Hi, this issue was solved with the patch posted here:
https://www.drupal.org/project/ds/issues/3329994#comment-15075969 🐛 Field groups not displaying when using display suite layout Closed: outdated

Hi, here is the patch I've created to resolve the issue at hand.

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

Hi, I tested this patch and it worked for me. Thanks

Hi, I've applied this patch and it worked correctly. Thanks

@mark_fullmer Great news! I successfully applied the patch, and I'm sharing it here just in case anyone else might find it useful

I used the syntax in #26 and it worked properly, but I'm curious as to why the patch file is not functioning as expected. Just to clarify, I downloaded the patch file from the merge request and copied it into my project. Is there anything else that needs to be done in order to apply the patch file successfully?

No, I didn't use that syntax. Instead, I used the following syntax:

            "drupal/url_embed": {
                "CKEditor 5 Support": "./patches/10.patch"
            }

Hi,

I wanted to provide an update regarding the patch I received from the merge request and my attempt to apply it. Unfortunately, the patch did not produce the expected results. Here is what I did:

1. Updated the contrib module to version 2.x.
2. Added the patch to the composer.json file.
3. Made an attempt to apply the patch.

Also, I found an error in the output:
"Could not apply patch! Skipping. The error was: Cannot apply patch."

I would appreciate any help in this regard

Hi, I've created a patch to solve the compatibility with Drupal 10

jjose.quevedo → created an issue.

Hi, I was trying to reproduce this issue, but couldn't. Please, could you provide more details?

Hi, I've added the seven theme as a required package in the composer.json file, as it is now a contrib theme

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

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

Hi, I've added the option to clone comments

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

Thanks a lot for your comment, Raineri. I was also able to solve my problem just by installing the package