🇮🇳India @manishvaity

MR!22 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

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

MR!3 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

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

manishvaity → created an issue.

manishvaity → created an issue.

MR!2 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

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

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

manishvaity → created an issue.

Patch worked added in MR
https://git.drupalcode.org/project/opigno_calendar_event/-/merge_request...

manishvaity → created an issue.

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

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

HI everyone,

we are also facing issue in drupal 10 and drupal 11.

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

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

MR!6 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

HI claudiu.cristea,

Removed file as suggested.

Thanks,
Manish Vaity

MR!3 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

manishvaity → created an issue.

MR!3 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

manishvaity → created an issue.

MR!12 Makes this module compatible with Drupal 11. Functionality is working as expected.

manishvaity → changed the visibility of the branch 3431537-d11_ready to hidden.

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

MR!4 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

MR!5 Makes this module compatible with Drupal 11. Functionality is working as expected.

manishvaity → created an issue.

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

MR!5 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

MR!10 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

manishvaity → created an issue.

MR!20 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

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

MR!6 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

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

Hello Team,

Currently, we have good team for managing this module.

Also, we are working on field states ui of Drupal 10 to field states ui of Drupal 11 project. In future, we will plan to upgrade in Drupal 12.

Can you please grant me access of co-maintainer so we will do good work in this module.

manishvaity → created an issue.

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

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

manishvaity → created an issue.

manishvaity → created an issue.

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

MR!3 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

MR!8 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

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

manishvaity → created an issue.

manishvaity → created an issue.

Drupal 10 already released

MR!2 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

MR!4 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

MR!7 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

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

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

MR!6 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

manishvaity → created an issue.

MR!1 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

manishvaity → created an issue.

manishvaity → created an issue.

MR!5 Makes this module compatible with Drupal 11. Functionality is working as expected.

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

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

MR!17 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

MR!5 Makes this module compatible with Drupal 11. Functionality is working as expected

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

MR!4 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

Tested on:
- Drupal 11.1.0
- PHP 8.3.14
- MySQL 8.3.14

Verified:
- Seven can be installed in "Appearance"
- Seven can be used as the Administration theme
- Seven settings can be view and saved (/admin/appearance/settings/seven)
- Layout is the same as the Drupal 10 version
- Image widget appears as expected

MR!8 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

Problem/Motivation

Hello project maintainers,

This is an automated issue to help make this module compatible with Drupal 11.

Changes will periodically be added to this issue that remove deprecated API uses. To stop further changes from being posted, change the status to anything other than Active, Needs review, Needs work or Reviewed and tested by the community. Alternatively, you can remove the "ProjectUpdateBotD11" tag from the issue to stop the bot from posting updates.

The changes will be posted by the Project Update Bot → official user account. This account will not receive any issue credit contributions for itself or any company.

Proposed resolution

You have a few options for how to use this issue:

1. Accept automated changes until this issue is closed

   If this issue is left open (status of Active, Needs review, Needs work or Reviewed and tested by the community) and the "ProjectUpdateBotD11" tag is left on this issue, new changes will be posted periodically if new deprecation fixes are needed.

   As the Drupal Rector project improves and is able to fix more deprecated API uses, the changes posted here will cover more of the deprecated API uses in the module.

   Patches and/or merge requests posted by others are ignored by the bot, and general human interactions in the issue do not stop the bot from posting updates, so feel free to use this issue to refine bot changes. The bot will still post new changes then if there is a change in the new generated patch compared to the changes that the bot posted last. Those changes are then up to humans to integrate.

2. Leave open but stop new automated changes.

   If you want to use this issue as a starting point to remove deprecated API uses but then don't want new automated changes, remove the "ProjectUpdateBotD11" tag from the issue and use it like any other issue (the status does not matter then). If you want to receive automated changes again, add back the "ProjectUpdateBotD11" tag.

3. Close it and don't use it

   If the maintainers of this project don't find this issue useful, they can close this issue (any status besides Active, Needs review, Needs work and Reviewed and tested by the community) and no more automated changes will be posted here.

   If the issue is reopened, then new automated changes will be posted.

   If you are using another issue(s) to work on Drupal 11 compatibility it would be very useful to other contributors to add those issues as "Related issues" when closing this issue.

Remaining tasks

Using the patches

1. Apply the latest patch in the comments by Project Update Bot → or human contributors that made it better.
2. Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.
3. Provide feedback about how the testing went. If you can improve the patch, post an updated patch here.

Using the merge request

1. Review the merge request and test it.
2. Thoroughly test the changes. These changes are automatically generated so they haven't been tested manually or automatically.
3. Provide feedback about how the testing went. If you can improve the merge request, create a new branch and merge request and work from there.

Warning: The 'project-update-bot-only' branch will always be overwritten. Do not work in that branch!

Providing feedback

If there are problems with one of the changes posted by the Project Update Bot → , such as it does not correctly replace a deprecation, you can file an issue in the Drupal Rector issue queue → . For other issues with the bot, for instance if the issue summary created by the bot is unclear, use the Project analysis issue queue → .

manishvaity → created an issue.

manishvaity → changed the visibility of the branch 3492886-d11_ready to hidden.

MR!2 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

MR!3 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

MR!1 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

manishvaity → changed the visibility of the branch 3481048-d11_ready to hidden.

manishvaity → changed the visibility of the branch 3481048-drupal-11-compatibility to active.

manishvaity → changed the visibility of the branch 3481048-drupal-11-compatibility to hidden.

MR!2 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1