🇮🇳India @aman1248

Marcus_Johansson → credited Amandeep123 → .

Hy @Marcus_Johansson
I have reviewed it , It has a straight forward fix.

Please & Thank You.

** Marking this ticket as RTBC!!

RTBC +1

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

RTBC +1

Amandeep123 → changed the visibility of the branch 3449270- to hidden.

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

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

Hy alemadlei

I have reviewed the 1.0.0-beta2 version of the module .
Working absolutely fine with composer.
Can move the issue to be fixed
Please & Thank You.

** Marking this ticket as RTBC!!

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

Hy @ahmad-alyasaki these are the points giving the main reason for the difference between the two modules

Content Activities History:

1 Focuses on tracking CRUD operations (Create, Read, Update, Delete) for content, user accounts, taxonomy terms, and Drupal entities.
2 Provides centralized logging, filtering, searching, and detailed reports for system administrators.
3 Suitable for monitoring changes related to content management, user management, and taxonomy.

Audit Log:

1 Extends auditing to track entity views alongside CRUD operations.
2 Offers broader scope by monitoring views, inserts, updates, and deletes for all entities.
3 Suited for scenarios requiring detailed tracking of individual entity views, beyond standard CRUD operations.

please review
thanks.

"Hi @man-1982, it appears that the patch isn't applicable in our site. Could you please assist in resolving the issue and finding a suitable solution?"

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

Hy @eleonel @naveenvalecha

I have reviewed the changes in the the MR!3 , The MR! has a straight forward fix.
It can be merged.
Please & Thank You.

** Marking this ticket as RTBC!!

Hy @anoopsingh92 ,

I have reviewed the Theme , The Theme Is Working fine
You can Move The Status To Fixed
Please & Thank You.

** Marking this ticket as RTBC!!

Amandeep123 → created an issue.

Amandeep123 → created an issue.

Amandeep123 → created an issue.

"Hi @brandonpost, Your patch fixed the issue properly. Thanks!"

Amandeep123 → created an issue.

Hy @dww, @samit.310@gmail.com

I have reviewed the changes in the MR! 69, The MR! has a straight forward fix.
It can be merged.
Please & Thank You.

** Marking this ticket as RTBC!!

Hy @NexusNovaz

I have reviewed the changes in Your MR! The MR! has a straight forward fix.
It can be merged.
Please & Thank You.

** Marking this ticket as RTBC!!

Hy @marcoscano ,

I have reviewed the changes in the the MR!6 , The MR! has a straight forward fix.
It can be merged.
Please & Thank You.

** Marking this ticket as RTBC!!

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

Amandeep123 → changed the visibility of the branch 3447537-fixing_phpstan_issues to hidden.

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

"Hi @bleen, @Rajeshreeputra , I had replicated the aforementioned issue, implemented the necessary patches, and thoroughly tested Patch !24. It is now functioning properly, resolving the previously mentioned error. We can now move the ticket to RTBC. +1. Please review

Amandeep123 → changed the visibility of the branch 3447040-warning-foreach-argument to hidden.

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

Hello Folks!!

I have reviewed the changes in the MR! 23, The MR! has a straight forward fix.
It can be merged.
Please & Thank You.

** Marking this ticket as RTBC!!

Hello Folks!!

I have reviewed the changes in the MR! 9, The MR! has a straight forward fix.
It can be merged.
Please & Thank You.

** Marking this ticket as RTBC!!

Hi @marcoliver, the "open in new window" option looks good. I've reviewed and applied all the changes from the merge request. Everything appears to be in order. I'll be adding a screenshot after applying the merge request.

Hi @aasarava, I've checked merge request !4, and it's functioning correctly, resolving the error. Great work!

Hi @Robert Ngo, I've reviewed your patch, and it has effectively solved the issues mentioned above. It's very helpful!

Hi @Rajeshreeputra, we've tested patch #6, and it appears to be resolving the error as required.

Amandeep123 → changed the visibility of the branch 3327126-phpcs-drupal-coding to active.

Amandeep123 → changed the visibility of the branch 3327126-phpcs-drupal-coding to hidden.

Hy @Hai Nguyen, Solved the above error And Created The Merge request.
Please review,
Thanks.

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

Hello @Rajeshreeputra, solved the errors please Review Once.

Hello @Rajeshreeputra,

I have successfully resolved the error mentioned earlier and created a merge request for it. Additionally, I have included screenshots depicting the errors encountered for clarity.

Amandeep123 → changed the visibility of the branch 3355462-theme-hook-usernamepolicypatternelements to hidden.

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

Hy @Mav_fly , I followed the step to reproduce the error and encounter the same error that you are facing .

Patch not working for me , still the same error.

Hello @bleen and @Kasey_MK, the patch !11 has been reviewed and tested. It's working fine .

"Hello @Rajeshreeputra, your code successfully achieved the green checkmark on D9. Thank you.

"@Mav_fly, could you please provide detailed steps to reproduce the error that's occurring on your end?"

Hello @johnv, the latest development version does not have such an error; it's working absolutely fine on my project.

@soutams, the error for MR! is still there. But there were some cs warning which was a quickfix, which I have made. I am yet not aware about the unit test cases. So I worked only on the some warnings. Please & Thank You!!

Hi @Rajeshreeputra,

I've thoroughly tested merge request !26 and confirmed that it's working perfectly. I've addressed all the errors related to /Drupal calls and deprecated t() calls in classes. working properly.
thanks.

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

Hy @Rajeshreeputra, i have reviewed the above merge request necessary for the configuration . working fine.
thanks .

Hy @ravi kant, i have reviewed and tested the issue and also updated the merge request.
Thanks.

"Hi @ravi kant, the error mentioned above has been successfully resolved, and a merge request has been created to ensure its correction."

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

Hi @jrglasgow,
I've made the necessary updates to merge request !56, resolving all the CS errors. As you can see, PHPCS now has a green tick across the board.
Thanks

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

Hello @Rushikesh Raval , I have thoroughly tested the merge request and confirmed that the functionality for the slider to appear on the home page or anywhere else is working perfectly.

Hey Rajeshreeputra That's fantastic ! Successfully applied and tested the merge request #4 with strict types enabled is a significant step forward. Embracing strict types in Drupal not only aligns our codebase with modern PHP standards but also sets the stage for writing more resilient, maintainable, and efficient code.

By enforcing strict type checking, we're ensuring that our functions and methods operate with the correct types of data, reducing the chances of runtime errors and enhancing overall code reliability. It's a powerful tool for fostering a culture of quality and consistency within our development process.

Hy @Jibus,
The main difference lies in focus of both : the first module [REST Password Request ] specializes in password-related actions through REST with email interaction, while the [Rest Password Reset] offers a broader solution for username and password management via REST API endpoints, emphasizing frontend integration and configurability for decoupled applications.
Thanks

Hey nidhi27.

I wanted to express my sincere appreciation for your tremendous help!

Implementation of Changes: I successfully applied all the recommended modifications to my site.
Enhanced Email Validation: By integrating the constructor parameter, EmailValidatorInterface, into the ExceptionMailerConfigForm class, we've significantly bolstered email validation within the form. This ensures that all entered email addresses are properly formatted, thus enhancing communication reliability.
Improved Email Retrieval: The introduction of the new method, getConfigFormEmailAddress(), marks a pivotal advancement in our system. This method seamlessly retrieves email addresses configured within the form settings, facilitating the efficient retrieval of user-specified addresses for error notifications.
These transformative changes have undoubtedly elevated the functionality of the Exception Mailer module. Our email validation and retrieval mechanisms are now more robust and user-friendly, culminating in a superior error notification system.

Once again, thank you

Hy @ptmkenny , please check
thanks

Hy @ptmkenny ,

In the RenameAdminPathsSettingsForm class, you're already using the ConfigFormBase class as a parent class. The ConfigFormBase class has its own constructor that you don't need to explicitly call. When you call parent::submitForm($form, $formState);, it already executes the necessary logic from the parent class constructor.

So, there's no need to explicitly call the parent constructor in your RenameAdminPathsSettingsForm class. Just keep using parent::submitForm($form, $formState); as you're doing.

hy @matsbla, please review merge request 6 as this error is resolved on my site .
thanks

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

hy @matsbla. This change fixes the error showed in the screenshot and also sorts out the issues you had before. Now, you can move field groups from one column to another without any trouble. It makes everything smoother and easier to use. please review

Hy @matsbla ,please have a look at the merge request 5 created and working for the above issue
Thanks

Hi @lalitasaini,
I've created a merge request for the issue we discussed. Could you please review it?
Thanks

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

Hy @wundo
please review.
thanks

Hy @artem_sylchuk ,Raised Mr Please reviw once .

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

hello ,@Rajan Kumar@2026 , as mentioned the screenshot it is running fine in my drupal 10.2.

Hy @Ashutosh Ahirwal, just wanted to drop a note to say that the module you've created is running properly on the homepage. Thanks

Hey there, @Rajan Kumar@2026!

To fully unlock the potential of the Open Church theme, the first step is to ensure the core module, Open Church, is seamlessly integrated. Once this vital dependency is installed, the pathway to setting it as the default theme is illuminated, paving the way for a cohesive and efficient user experience.

🛠️ Installation Guide:

Begin by executing the command:
composer require 'drupal/openchurch_core:^3.0@alpha'
This step initiates the installation of the core module.

"Thanks, @lazzyvn! Your module works great, ensuring everything runs smoothly without any errors."

Working Properly
Thanks

Please review @florisg,
I have given the solution of above error ,
Thanks

Hy @florisg and @owenkaji,

I hope this message finds you well. We've identified a compatibility issue with the Rocket Chat module, particularly version 3.0.1, which is currently affecting its integration with Drupal 10. The root cause lies in its dependency on the Rocket Chat API module, which, unfortunately, isn't adaptable to Drupal 10 due to its reliance on Guzzle HTTP version 7.8.1. This poses a conflict as the Rocket Chat API module relies on Guzzle HTTP version 6.2.

Additionally, the Rocket Chat module is tailored to operate seamlessly with "drupal/core" versions 8.8 or 9, thus excluding compatibility with Drupal 10.

To resolve this issue effectively, we need to implement the following steps:

Upgrade Rocket Chat API Module: Update the Rocket Chat API module with the following adjustments:
Update Guzzle HTTP Dependency to version 7.8.1.
Set Drupal Core compatibility to version 10.
By making these enhancements, we aim to ensure seamless compatibility between the Rocket Chat API module, Guzzle HTTP version, and Drupal 10 environment.Here is The Link https://git.drupalcode.org/project/rocket_chat/-/blob/3.0.1/modules/rock... , that needs to be updated.

Please Review @florisg
Thanks You