🇳🇵Nepal @sujan shrestha

Thank you @avpaderno for the information. I'll ensure the status is updated accordingly.

Thanks for the feedback! I have added the missing README.md file.

Thanks for the feedback! I've updated the README.md template accordingly.

Thank you for reaching out. Currently, we do not have plans to integrate with COOKiES Consent Management. However, we appreciate your interest and will keep your suggestion in mind for future updates.

Added the missing README.md file and resolved compatibility issues with Drupal 11.

Hi @Joachim Namyslo Thank you for the bug report. I've adjusted the permissions for the route, and it appears to be working now. Could you please verify?

Hi @SirClickalot Thank you for reporting this issue! It has been fixed in version 1.1.4. Please update to that version and check if the problem persists.

Hi @SirClickalot, Thank you for sharing your feedback and suggestions. I'll definitely take your feature requests into consideration and work on implementing them.

Hi @wjackson @earthday47 Thank you for the patch! Your contribution is greatly appreciated. With this fix, we can now integrate the Feeds import with content that includes fields from the Simple Time Field module.

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

Hi @enchufe, thank you for the new feature request and for providing the patch for 'custom attributes to scripts' feature.

I have implemented the Xss::filter() function to properly sanitized before using raw to output the $script_attributes value. Here's how it's applied on the module file:

$script_attributes = Xss::filter($script_attributes);

Additionally, I've utilized the 'raw' filter like {{ script_attributes|raw }} on the twig file to display the HTML-encoded script attributes. For example, type="text/plain" data-category="analytics" was displayed as show on the attachment screenshot.

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

sujan shrestha → created an issue.

Hi @ecvandenberg Thank you for reporting the issue. It seems that when unsubscribing a user by unchecking the checkbox for a specific list, the user isn't being unsubscribed from that list. I'll investigate further and provide updates accordingly.

Hi @Promo-IL Thank you for letting me know. I'll review the code and ensure that everything aligns properly with the functionality. I appreciate your diligence in ensuring data integrity.

Hi @FiNeX Thank you for sharing the patch! I appreciate your effort in addressing these issues. I'll make sure to review the patch thoroughly and get back to you soon.

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

Hi @delacosta456,

Thank you for your interest in the module. While my current module isn't part of the Social Initiative modules, I do have plans to develop a separate module that functions similarly to 'social_post_facebook'. This new module will automatically post content to Facebook pages or groups upon content creation or with a cron job, featuring options for random or queued content with specific time intervals.

I've implemented the patch and the Drupal 10 compatibility issue has been resolved.

Hi @aman_lnwebworks @dineshkumarbollu , thank you for the feedback. I've implemented the patch, and the issue has been resolved.

I have fixed the PHPCS issue on the 1.1.x branch and ran the command to verify that the issues have been resolved.

phpcs --standard=Drupal --extensions=php,module,inc,install,test,profile,theme,info,txt,md,yml c
olor_pickr/

Hi @ecvandenberg Thank you for your suggestion! I'll look into updating the email address in Moosend or, if that's not possible, unsubscribing the old email address. It's a valuable feature request, and I'm planning to address it.

Hi @SandeepSingh199 @Nikolay Borisov Thank you for the patch. I have reviewed it and successfully implemented the changes. Much appreciated!

Hi @4goodapp @Mav_fly Thank you for your suggestion. I appreciate your effort in investigating the issue. I will research and I will work on adjusting the settings accordingly to ensure that Klarna, AfterPayor, Bancontact and other payment methods are properly displayed during checkout. I'll keep you updated on my progress.

Hi @Mav_fly Thank you for your suggestion. I appreciate your effort in investigating the issue. I will delve into researching the presentment currency of Euro and how it can be passed via the module to Stripe. Once I gather more information, I will work on adjusting the settings accordingly to ensure that Bancontact and other payment methods are properly displayed during checkout. I'll keep you updated on my progress.

Thank you @Nelo_Drup for providing the instructions. I will proceed to install the module as usual and follow the steps you've outlined. I'll replicate the environment you've mentioned with Drupal 10.2.3, PHP 8.1, MySQL 5.40, and NGINX server. After testing, I'll investigate the errors appearing in the console and work on fixing them accordingly.

Hi @cgeindreau thank you for the feedback. Could you please provide more details or suggestions regarding the lack of translation for the widget in the editor, despite checking in the interface translation? Any additional information would be helpful in resolving this issue effectively.

Hi @Nelo_Drup Thank you for bringing this to my attention. Could you please provide more details about the steps you're taking when encountering these errors and the Drupal version you are using? It will help me better understand and address the issue.

Hi @DamienMcKenna Thank you for your suggestion. I will opt the module into security advisory coverage to better support those who maintain sites with this requirement.

Thank you for reviewing MR! 2 and confirming the fix for the reported issue with phpcs. I'll review the fixes promptly.

Thank you @__i.am.prashant__ for the feedback. I will review the fixes.

Thanks @mrshowerman, I'll review it.

Hi @Falco010 Thank you for the feedback. I will explore the possibility of incorporating event dispatching into the module to enable functionalities like sending email notifications upon tagging someone.

Hi @mpmano Thank you for the feedback. I will review the issue and make the necessary fixes.

Hi @sickness29 Thank you for the feedback. The https://www.drupal.org/project/ckeditor_mentions → , was only compatible with CKEditor 4 at the time. However, I am pleased to note that the CKEditor Mentions module has recently been updated to also support CKEditor 5. I will update the 'About' section according to the proposed resolution.

Hi @apaderno yes, i am referring to the 1.1.2 release on February 21, 2024, in the Zoom on Hover. To ensure it is recognized as supported, I will proceed to set the release as supported on the specified link: https://www.drupal.org/node/3318818/edit/releases → . Thank you for your guidance.

Hi @larowlan Thank you for providing feedback and corrections. I'm glad to hear that the use of check markup looks good now.

Hi @mortona2k, Thank you for the feedback, I appreciate it. This module, along with the shield module, provides similar functionality for PHP authentication. However, while the shield module has served its purpose well in the past, it did not fully meet my some requirements for Role-Based Access Control and User-Specific access control for specific pages. I intended to implement configurations for these features on the backend, but due to time constraints, I was unable to do so. Nevertheless, I plan to incorporate these enhancements in the future.

Hi @larowlan I wasn't aware that automation would set it to closed fixed after two weeks. In the past, I manually closed issues as fixed after testing the module. Now that I understand the automated process, I'll make sure to align with it moving forward. Thank you for clarifying!

I have incorporated the check_markup into the build function. Please review it at https://git.drupalcode.org/project/tui_image_editor/-/blob/1.0.x/src/Plu....

In the past, I wasn't aware of branch naming conventions for module versions and the proper merge process after fixing issues. Consequently, I used to add fixed codes from contributors to my new branch and push it, and proceed. Now, I'm delving deeper into the process, learning the process from my mistakes and rectifying branch naming, descriptions, and addressing previous mistakes. I still appreciate guidance as it will encourage and motivate me to contribute to new modules and address the issues.Thank you.

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

I've implemented the patch #3 → , but I'm encountering the following error. To reproduce this error, please install the module and navigate to 'Structure' > 'Block' and place the 'Vocabulary Block' block. Could you please take a look?

The website encountered an unexpected error. Try again later.

ArgumentCountError: Too few arguments to function Drupal\vocabulary_catalog\Plugin\Block\VocabularyCatalogBlock::__construct(), 3 passed in /var/www/html/drupal-9/core/lib/Drupal/Core/Plugin/Factory/ContainerFactory.php on line 25 and exactly 4 expected in Drupal\vocabulary_catalog\Plugin\Block\VocabularyCatalogBlock->__construct() (line 43 of modules/custom/vocabulary_catalog/src/Plugin/Block/VocabularyCatalogBlock.php).

sujan shrestha → created an issue.

Hi @apadern Thank you for the information. Could you please help me understand why the release information is not appearing at the bottom of the page for the "zoom_on_hover" module details? This problem seems to persist across my other modules as well, which I have contributed on Drupal.org. I'm seeking assistance to resolve it. I would appreciate any guidance or assistance.

Module link
https://www.drupal.org/project/zoom_on_hover →

I have addressed all the PHPCS-related issues to ensure coverage for the Drupal.org security advisory. Could you please review the changes? Could you please help me understand why the release information is not appearing on the "zoom_on_hover" module details? Could you please take a moment to review the link below and the attached screenshot to help diagnose the problem?

Module link:
https://www.drupal.org/project/zoom_on_hover →

sujan shrestha → created an issue.

sujan shrestha → created an issue.

I have addressed all the PHPCS-related issues and have also removed the master and 1.1.2 branches to ensure coverage for the Drupal.org security advisory. Could you please review the changes?

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

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

sujan shrestha → created an issue.

Hi Vishal Kadam, thanks for the suggestions. I have created a branch, '1.1'. Could you please suggest the next steps for security advisory coverage?

sujan shrestha → created an issue.

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

Hi @everyone,
Thank you for the feedback.
I have reviewed and applied the patch to the new version. Please verify.

Hi nicolas,

Thank you for your enthusiasm and for raising valid concerns. I understand the importance of security and the need for a clear maintenance plan. Regarding the security advisory policy, I want to assure you that it's a priority for us. I'm actively working on getting the module covered by the policy, and I have plan to have this in place soon.

As for the long-term maintenance of the module, I want to emphasize my commitment to providing ongoing support. I understand the significance of maintaining a reliable and secure module. I'm dedicated to addressing any issues that may arise and ensuring that the module remains up-to-date with evolving requirements. Your input is valuable, and I'm committed to delivering a reliable and secure solution. Thank you.