🇮🇳India @NivethaSubramaniyan

Account created on 10 August 2016, almost 8 years ago
#

Merge Requests

Recent comments

🇮🇳India NivethaSubramaniyan

Link Dialog is coming fine with background color

Steps followed to reproduce this issue:
1) In Drupal 10.1.2, I have added linkit 6.1.0
2) Configured the linkit profile and enabled them in text formats [ ckeditor ]
3) Then edited a content and tried adding a link.
4) The link autocomplete dialog is coming fine. ( I have checked as both authenticated and administrator user). I have attached the image for the reference.
5) I have used chrome browser.

I further debugged and checked ck-balloon-panel class has the background color settings which is automatically getting added.

🇮🇳India NivethaSubramaniyan

This issue exits and the given patch works fine. I have detailed the steps and attached the screenshots for the reference.

Steps to reproduce.
1) Enabled genpass:^2.0@alpha in drupal 10.1
2) Go to the account settings page /admin/config/people/accounts
3) Enable the option: Users must enter a password on registration. This is disabled if e-mail verification is enabled above. and save it
4) Logout as admin and try registering as a new user
5) After registering you will get the error message:
TypeError: Drupal\Core\Form\FormState::setValueForElement(): Argument #1 ($element) must be of type array, null given, called in /var/www/html/web/modules/contrib/genpass/genpass.module on line 270 in Drupal\Core\Form\FormState->setValueForElement() (line 79 of core/lib/Drupal/Core/Form/FormStateValuesTrait.php). [ Attached screenshot].
6) After applying the patch , it fix the issue.

🇮🇳India NivethaSubramaniyan

I applied the patch in drupal 10.1.0 instance with linkit 6.1.0.
After applying the patch, it seems to be working fine . I have attached screenshots for the reference.

🇮🇳India NivethaSubramaniyan

The given patch is working fine. We can go with is_numeric. I have detailed the steps and attached the screenshot for the reference.

Steps to reproduce:

1) Created a content with authored on date 15 May 1923.
2) Created a calendar view with content
3) Got the issue - InvalidArgumentException: The timestamp must be numeric. in Drupal\Component\Datetime\DateTimePlus::createFromTimestamp() [ Attached the image ]
4) Applied the patch.
5) Now I am able to view the content which I have created on date 15 May 1923. [ Attached an image ]

I have done this steps with drupal 9.5 and calendar_view-2.1.1.

🇮🇳India NivethaSubramaniyan

I tried the following steps and the issue was not reproducted. After deleting the field, it works fine for me.

Steps:

1) With drupal 9.5, I have added 'recurring date field' module [3.2.0].
2) Then in article content type added a field with this type recurring date field.
3) I go to uninstall page to uninstall this module.
4) It prevents me from uninstall since we are using this field. It shows the field name.
5) Then I go to the article content type and deleted the recurring date field which I have created.
6) Now again I go to uninstall page and I am able to uninstall the module.

Note: To confirm whether you have deleted all the recurring date type field. Visit the page admin/reports/fields and search for Recurring dates field and find out in which content type we are using and delete it.

I have attached the screenshot for your reference.

🇮🇳India NivethaSubramaniyan

Steps to reproduce:
1) I have installed the dynamic_menu_item module in drupal 9.5
2) Without doing any configuration, I opened the edit page of a content
3) We got an error 'TypeError: in_array(): Argument #2 ($haystack) must be of type array, null given in in_array()'.
4) I have uninstalled the module.
5) Applied the given patch and installed the module again.
6) repeating the step 2
7) Again I got the same error.

Even after applying the above patch still the issue exists.

I have attached the image for your reference.

Solution: We have to rename the file as dynamic_menu_item.settings.yml instead of dynamic_menu_item.config.yml inside config/install folder.

🇮🇳India NivethaSubramaniyan

I was able to reproduce this issue after installing devel module with field name module in drupal 10.1.
After applying the above patch, the issue was resolved. I have attached the screenshot for reference.

Production build 0.69.0 2024