🇳🇵Nepal @sujan shrestha

Thanks, Bryan Toapanta! I’ll review the changes to address the compatibility fixes and see how we can update the module for Commerce 3.0 support.

Hi Tamer Atef, thank you for your update. Regarding the issue with the text not appearing on top of the slider, have you made sure that the correct Twig template files are being used and that the proper variables are passed through? Also, please ensure that you've cleared the cache after making any changes. Sometimes that step can be overlooked but is crucial for the changes to take effect.

additionally could you try enabling 'Twig development mode' to see if any issues arise in the template processing? this might help in identifying any issues with the Twig templates or variables. let me know how it goes!

Hi Adria Grau, Thanks for the bug report! Did you happen to use the theme before July 16th (on a dev version)? There have been some fixes to the libraries since then that might resolve this issue. Could you try pulling the latest dev version and see if the error still occurs?

Hi Blaine, thanks for the patch and fixes – I appreciate it!

Hi Tamer, Thanks for reporting the issue. To help me investigate this further, could you please provide a few additional details? Specifically, I would need to know the version of Drupal you're using, as well as any relevant entries from the recent log (you can find these under Admin > Reports > Recent log messages). Additionally, if you could check your browser's console for any error messages and share those with me, it would be helpful in pinpointing the cause of the issue.

Hi @revathi.b @Vinodhini, Thanks for testing and confirming. I've added the merge request.

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

Thank you for the patch.

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

The issue with the playlist has been resolved.

I have identified that if the site does not include 'basic_html' or 'full_html' formats, the dropdown will not allow selection of other options. To fix this, I have replaced the static allowed text format with all available dynamic text format machine names on the site.

Hi Enzo, Thank you for providing the detailed error log! I’ll look into it and get back to you soon.

Hi jaumepc, Thank you for providing the detailed information about the issue. Based on your description, it seems like the issue might be related to the available text formats. Currently, the allowed formats are statically set as $allowed_formats = ['basic_html', 'full_html'];. Could you please confirm whether your format includes either basic_html or full_html? You can check this by visiting /admin/config/content/formats to see which formats are available. This will help me fix the issue if that’s the cause.

Hi @Enzo De Simone, Thanks for the bug report! Could you please provide your browser details (e.g., Chrome, Safari, etc.) and check if there are error log messages or any console errors when you try to use "Playlist" mode? If you could send those over, it would be really helpful for debugging the issue.

Hi @transmitter, Thanks for the bug report! I’ll look into it and get back to you.

Hi Brian Eller, Thanks for reporting the issue! Could you please let me know which version of Drupal you're using? Also, could you check the recent log messages for any errors related to this module and share any error details if found?

Hi @checdedon, Thank you for reporting this issue. Could you please provide the version of Drupal you're using? Additionally, please check the log messages to see if there are any errors that could help us identify the cause of the problem.

Hi @saranya ashokkumar, Thank you for pointing that out. I’ll implement the necessary fixes and update the patch in the new version. Thanks again for catching that!

Hi saranya ashokkumar, Thank you for reporting the issue and for creating the patch. I will implement the necessary tests and apply the patch in the new version.

Hi @hkirsman , Thanks for reporting this issue and for the patch! I'll take a look.

Hi saranya ashokkumar,

Thanks for the update and for making the patch. I'll review it.

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

Hi @vishal.kadam, Thank you for the update.

Thank you for providing the detailed guidelines. I have made the necessary adjustments based on your feedback:

1. FILE: timeline_block.libraries.yml Updated the version field as per your suggestion.

2. FILE: timeline_block.module Updated the description to match the standard format for .module files.

3. FILE: src/Plugin/Block/TimelineBlock.php Simplified the constructor to match the recommended format.

I’ve made the changes, and the code is now ready for review.

Hi @avpaderno, thanks for the update. The project is ready for review and i have updated the status accordingly.

sujan shrestha → created an issue.

Hi @enzo de simone,
Could you please try uploading the images again and see if the issue still happens? Also, please check the logs to see if there are any errors or permission problems.

tag added

Related content  updated

overview changes

Youtube video guide

Added link of the theme

Hi Sady, Thank you for reaching out and for your contributions to the module. I've been busy with other projects, so i couldn’t manage this one. I appreciate your work on the listed issues, and it’s great to hear the module is working well in production. I’m open to adding maintainers to the modules i’ve created. Thanks again for your efforts!

Hi Vladimir, Thank you for the update. Could you please try clearing the cache and check if the issue persists?

The compatibility issue has been fixed.

The compatibility issue has been fixed.

The coding standard issue has been resolved in the latest version update.

The compatibility issue has been fixed in the latest version update.

The Drupal 11 compatibility fixes for leave_confirm have resolved the issues.

Thanks Bram for the suggestion! I've removed the console.log as requested. Let me know if there's anything else.

Hi Peter, Apologies for the delay in getting back to you. The issue has been fixed. Please let me know if anything else comes up.

Hi @coaston @sarwan_verma, Apologies for the late response! The Drupal 10 and 11 versions of the module are now available.

The Drupal 11 compatibility issues for have been fixed.

Thank you for the patch and guidelines. I have followed them and fixed the issues. If there are any remaining, please let me know.

Thank you for the patch and guidelines. I have followed them and fixed the issues. If there are any remaining, please let me know.

The Drupal 11 compatibility issues for have been fixed.

Apologies for the delayed response, and thank you for providing the patch. I’ve implemented it and addressed the issues reported by PHPCS.

Thanks for the update, Erik! I’ve implemented the patch and it’s fixed. Let me know if anything else comes up.

Hi João, thanks for addressing the issue. I’ve reviewed it and removed the unnecessary JS file since it wasn’t needed. I appreciate the update, and let me know if anything else comes up.

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

The Drupal 11 compatibility issue has been fixed.

The issues reported by PHPCS have been fixed. Thanks for the patch!

Thank you! The issues reported by PHPCS have been fixed.

The compatibility issue has been fixed.

The compatibility issue has been fixed.

Thanks for the patch! The issue has been resolved and everything is working perfectly now.

Thank you for the patch and your support. The issues reported by PHPCS have been fixed.

The compatibility issue has been resolved.

Hi Karol, I apologize for the late response. I have merged the changes according to your suggestions. Thank you for the code and for bringing this issue to my attention. Please let me know if there's anything else that needs improvement.

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

The compatibility issue has been resolved.

Thank you for providing the patch and the guidelines to resolve the PHPCS issues. I have applied the fix, and I'm happy to confirm that the issue has been addressed in the latest version. Thanks again for your support!

Hi Pomelov, Apologies for the late response, and thank you for identifying the issue. The issue has been fixed in the latest version. Could you please update and check if the problem is resolved? Let me know if you need further help!

Thanks David! Better Social Sharing Buttons and Better Social Share do seem to overlap in functionality, with both focusing on social sharing. However, Better Social Share offers more extensive customization, such as supporting over 100 social media platforms, including major networks like Facebook, Twitter, LinkedIn, WhatsApp, and Pinterest. It also allows for flexible integration into content entities, letting you configure sharing options from the manage display interface or embed sharing blocks on pages.

In terms of customization, Better Social Share gives you control over which icons are displayed, their order, and the ability to configure these settings with a "more" button that reveals additional social media icons, their placement, and other display settings. Plus, you can fine-tune the appearance of the icons with size and color adjustments, and use custom Twig for custom layouts, CSS, and JavaScript to enhance functionality.

These features might make Better Social Share more flexible compared to Better Social Sharing Buttons, depending on the level of customization needed. Additionally, I’d welcome any new feature suggestions or improvements that could enhance the product further!

The Drupal compatibility issue has been resolved.

I've moved this to 'Fixed' now that Patch #2 has been successfully implemented.

The Drupal compatibility issue has been resolved.

The Drupal compatibility issue has been resolved.

The Drupal compatibility issue has been resolved.

Hi James, Thank you for the feedback, and I apologize for the delayed response. I’m planning to add the feature you mentioned, allowing the end user to specify the payment amount. I’ll let you know once it’s implemented.

Thank you for your feedback, and I apologize for the delayed response in addressing this issue. I’ve resolved the PHPCS-related issues. Thanks again!

Thank you for your feedback, and I apologize for the late response. I’ve updated the function names and also fixed the PHPCS-related issues.

Hi jcandan, Thank you for the feedback, and I apologize for the late response. I’ve updated the documentation as per your feedback regarding the composer require drupal/stripe_pay instructions. Thank you!

Thank you for the feedback, and I apologize for the delayed response. I’ve reviewed the feedback and the patch files, and I’ve fixed the issues reported by phpcs.

Thank you for the feedback, and I apologize for the delayed response. I’ve reviewed the feedback and the patch, and I’ve made the necessary changes to the documentation comments for the files, classes, functions, and methods. The issues have now been fixed.

Hi @gbyte @aaron.ferris , Apologies for the late response, and thank you for your feedback! I’ve updated the stripe-payment.html.twig file so that the price is pulled from the field value instead of being hard-coded. I also made a change in the StripeController.php file, where I added $productPrice = $productPrice * 100; to convert the price into the smallest unit of the currency (like cents). Could you please review the changes and let me know if everything looks good?

Hi tart0, Thanks for the feedback! Glad to hear the patch worked for the .yml file and you didn’t run into any problems. I agree, testing the more advanced features would be a good next step to confirm everything is working. Please test the module according to the "Getting Started" steps in the documentation from this link: https://www.drupal.org/project/stripe_pay → . I’ll also be adding more details to the README file and updating the documentation. Let me know if you need any assistance!

Hi @moolahtoshi, Thank you for reaching out regarding this issue. The error you're encountering has been addressed in the latest version. Please update to the latest version to resolve the problem. Additionally, I’m actively working on further improvements to enhance the overall experience. If you encounter any further issues or need assistance with the update, feel free to let me know.

The compatibility issue has been fixed.

Hi @inst, Thank you for your kind words. I’ll keep releasing stable versions that follow Drupal’s security rules. Making sure the module stays secure and reliable is very important to me. Let me know if you have any other suggestions.

Hi @w01f, Thank you so much for the kind words and feedback! Apologies for the delayed response. I really appreciate your suggestion about a horizontally-aligned version. I’ve actually been considering ways to implement this and am working on plans to make it feasible. I’ll keep this in mind as we continue to refine and improve the module.

The compatibility issue with Drupal 11 has been resolved in the latest version.

Hi @bwoods, Thanks for the feedback! Glad you got it working with processed_text. Using that approach avoids the need for the raw filter, which is great for security. I’ve fixed the media issue for the text field with RendererInterface in the latest version. Please check it out and let me know if there’s anything else!

Thanks for the patch! I’ve implemented the changes accordingly.

Hi @yhe @jaydev bhatt, Thanks for the update! I’ve moved the issue to fixed. If you come across any further issues or need additional guidance, please feel free to create a new issue.

Hi @radheymkumar, Thanks for the patch! I’ve implemented the changes accordingly.

The compatibility and other issue has been fixed.

The Drupal 11 compatibility has been resolved.

The Drupal 11 compatibility has been resolved.

The Drupal 11 compatibility has been resolved.

Hi @w01f, Thanks for sharing your findings on the AddToAny module—it's great that you're looking into the third-party sharing and privacy implications. I’d be happy to weigh in or offer any perspective on this! From my experience, privacy concerns around social sharing modules are definitely something worth investigating closely. I’d be happy to help if you’d like, especially with other module options or privacy concerns. Let me know how I can contribute.

The problem with Drupal 11 compatibility has been resolved.

Hi @michelrrr, Thanks for letting me know about these issues.

The Pinterest button issue has been fixed in the dev version(1.1.x). Could you please test it on your end? If everything works fine, I'll go ahead and create a new version.

Regarding the problem with removing buttons in the configuration, could you please share a screenshot of the page? This will help me troubleshoot and fix the issue.

Hi @w01f, thanks for sharing your thoughts! It's great to hear you're testing out the module on some new sites. I’d be really interested to hear about your experience and how it compares to AddtoAny once you've had a chance to dive in.

I also appreciate the mention of Better Social Sharing Buttons and the distinction between the two types of social sharing. It could definitely be helpful to clarify that for newcomers, so they better understand the difference between “Informative” sharing (linking to social media profiles) and “Sharing” (allowing users to share content directly).

The Better Social Share Drupal module enhances social sharing on the website without relying on third-party integrations like AddThis or AddToAny. It optimizes native sharing methods from popular social media platforms for a smoother, more efficient experience. With the supported social media platforms and extensive customization options, it helps expand reach and improve content sharing across online communities. Additionally, we can place the sharing blocks on pages or nodes to allow users to easily share the current page on social media.

Thank you for your patience and for pointing that out. After some thorough investigation and hard work, the fix has been implemented in version 2, and it’s now working correctly, including in the comments. Please feel free to test it on your end, and let me know.

The Drupal 11 compatibility issue has been fixed.