Problem/Motivation

Hello project maintainers,

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

To read more about this effort by the Drupal Association, please read: The project update bot is being refreshed to support Drupal 10 readiness of contributed projects

Patches will periodically be added to this issue that remove Drupal 10 deprecated API uses. To stop further patches 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 "ProjectUpdateBotD10" tag from the issue to stop the bot from posting updates.

The patches 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 patches 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 "ProjectUpdateBotD10" tag is left on this issue, new patches 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 patches 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 patches. The bot will still post new patches then if there is a change in the new generated patch compared to the patch that the bot posted last. Those changes are then up to humans to integrate.

  2. Leave open but stop new automated patches.

    If you want to use this issue as a starting point to remove deprecated API uses but then don't want new automated patches, remove the "ProjectUpdateBotD10" tag from the issue and use it like any other issue (the status does not matter then). If you want to receive automated patches again, add back the "ProjectUpdateBotD10" 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 patches will be posted here.

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

    If you are using another issue(s) to work on Drupal 10 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.

Providing feedback

If there are problems with one of the patches 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.

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

Project Update Bot created an issue. See original summary.

project update bot’s picture

Status: Active » Needs review
StatusFileSize
new1.17 KB

This is an automated patch generated by Drupal Rector. Please see the issue summary for more details.

It is important that any automated tests available are run with this patch and that you manually test this patch.

Drupal 10 Compatibility

According to the Upgrade Status module this patch makes this module compatible with Drupal 10! 🎉
This patch updates the info.yml file for Drupal 10 compatibility.

Leaving this issue open, even after committing the current patch, will allow the Project Update Bot to post additional Drupal 10 compatibility fixes as they become available in Drupal Rector.

Debug info

Bot run #127

This patch was created using these packages:

  1. mglaman/phpstan-drupal: 1.1.9
  2. palantirnet/drupal-rector: 0.12.0
project update bot’s picture

StatusFileSize
new692 bytes
new1.54 KB

This is an automated patch generated by Drupal Rector. Please see the issue summary for more details.

It is important that any automated tests available are run with this patch and that you manually test this patch.

Drupal 10 Compatibility

According to the Upgrade Status module this patch makes this module compatible with Drupal 10! 🎉
This patch updates the info.yml file for Drupal 10 compatibility.

Leaving this issue open, even after committing the current patch, will allow the Project Update Bot to post additional Drupal 10 compatibility fixes as they become available in Drupal Rector.

Debug info

Bot run #139

This patch was created using these packages:

  1. mglaman/phpstan-drupal: 1.1.24
  2. palantirnet/drupal-rector: 0.13.0
dishakatariya’s picture

Assigned: Unassigned » dishakatariya
Issue summary: View changes
dishakatariya’s picture

Assigned: dishakatariya » Unassigned
StatusFileSize
new74.54 KB
new66.53 KB
new37.5 KB

Verified patch #3 on Drupal 10.0.x and 10.1.x. Patch applied successfully and looks good to me.

Testing Steps:

1. Install drupal 10.0.x and 10.1.x version
2. Install the Better Login module (8.x-1.x-dev) version and save it in the Module folder
(git clone --branch '8.x-1.x' https://git.drupalcode.org/project/betterlogin.git)
3. Open drupal 10 or 10.1 and click on Extend
4. Check the Better Login module which unable to install
5. Now apply the patch [Where the Better Login module was saved i.e Module folder]
6. Reload the page and again check the Better Login module (Note: Clear all caches if required)
7. Now this module is enabled and also install successfully

The module can be installed after applying the patch and also work properly (For reference see attached Screenshots)
Can be moved to RTBC
RTBC+1

project update bot’s picture

Issue summary: View changes
rajab natshah’s picture

Priority: Normal » Major
Issue summary: View changes
rajab natshah’s picture

Thank you, Yogesh for having time to maintain this Better UI/UX login module.
Hoping for a soft commit. To ease testing with Drupal 10. and a soft tag release
Testing now with git clone --branch '8.x-1.x' https://git.drupalcode.org/project/betterlogin.git
and applying the patch.

rajab natshah’s picture

Priority: Major » Critical
rajab natshah’s picture

rajab natshah’s picture

mgstables’s picture

I can confirm, Patch #3 works well.

Drupal 10.0.7
PHP 8.1.6

Abdalhamid made their first commit to this issue’s fork.

Abdalhamid’s picture

When trying to update a Drupal 9 website to 10 , composer needs first to install the module and then apply the patch, but the module can't be installed because it's not compatible with Drupal 10, so I created a fork to download the module from until we have the new release.

devil2005’s picture

Hello,

Can we have a D10 compatible release please ?

Thanks a lot

devil2005’s picture

@Abdalhamid : can't update to D10 even with your branch :

 Problem 1
    - drupal/betterlogin 1.2.0 requires drupal/core ~8.0 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev] but it conflicts with your root composer.json require (^10).
    - drupal/betterlogin[1.3.0, ..., 1.x-dev] require drupal/core ^8 || ^9 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev] but it conflicts with your root composer.json require (^10).
    - Root composer.json requires drupal/betterlogin ^1.2.0 -> satisfiable by drupal/betterlogin[1.2.0, ..., 1.x-dev].

Thanks

yogeshsevak’s picture

devil2005’s picture

still can't up after applied patch

  Problem 1
     - Root composer.json requires drupal/betterlogin ^1.6 -> satisfiable by drupal/betterlogin[1.6.0, 1.x-dev].
    - drupal/betterlogin[1.6.0, ..., 1.x-dev] require drupal/core ^8 || ^9 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev] but it conflicts with your root composer.json require (^10).


Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

i'm using 1.6 and applied just patch for 1.6

devil2005’s picture

Hi,

Anybody can help please ?

Thanks :-)

rajab natshah’s picture

Status: Needs review » Reviewed & tested by the community

Hopping for a commit and a tag release.

rajab natshah’s picture

Facilitate a seamless upgrade process while maintaining compatibility with both Drupal 9 and Drupal 10 using a unified code base.

Only for testing:
Having the issue fork in the composer.json file.
In the repositories

  "repositories": {
    "drupal": {
      "type": "composer",
      "url": "https://packages.drupal.org/8",
      "exclude": [
        "drupal/betterlogin"
      ]
    },
    "drupal/betterlogin": {
      "type": "git",
      "url": "https://git.drupalcode.org/issue/betterlogin-3286226.git"
    }
  },

and in require

  "require": {
    "drupal/core": "~10.0",
    "drupal/betterlogin": "dev-3286226-automated-drupal-10 as 1.6.0"
  },
rajab natshah’s picture

Have the composer.json file back which was added by AbedAlhamid Ahmad to let the issue fork work with composer, but with Drupal 9 and Drupal 10 support.

The composer.json file will not be needed when merged to the 8.x-1.x branch.
I'm ok with having it tho.

Vishal Choudhary made their first commit to this issue’s fork.

vishal choudhary’s picture

devil2005’s picture

Hi,

Will you release a stable version of the module on d10? to up my websites with mass update :)

Thanks

seanb’s picture

Status: Reviewed & tested by the community » Needs work

The commit added in #25 adds better_login_form_config.module and better_login_form_config.info.yml. I think those are for the better_login_form_config module?

I'm going to revert this commit.

devil2005’s picture

Hi,

Yeah but composer doesn't find the new version on the repo... so i have to update manually.

Thanks

morepolarbears’s picture

Hi all,

Thanks a lot for your work.

I can confirm the current version of the fork (https://git.drupalcode.org/issue/betterlogin-3286226/-/tree/3286226-auto...) works on my Drupal 10.1.2 test install.

What's needed to go forward with the release of the updated package?

rajab natshah’s picture

Hoping for a commit and a release.
To have a smooth upgrade process for projects.

deaconblues’s picture

Hi everyone,

Just wanted to check in to see what the status is for the D10 release of the module. The code changes listed in morepolarbears's comment works great on my D10 site. What needs to happen to get a release of this code?

Thanks in advance!

adam-vessey’s picture

I gave a look at this in a ddev D10 env, and it indeed installed (after adding the repository entry and requiring the module accordingly); however, I found that there may be some styling updates desirable? As in: It seems like the flat 20% width in the CSS (https://git.drupalcode.org/project/betterlogin/-/blob/dfdd367b3f3937a01b...) causes overflow issues, with the username/password/etc fields being partially hidden with the default configuration.

That said, further examined our internal environment and found that we weren't actually using this module despite having it installed and enabled as gin_login was taking precedence; so in our instance, moving to remove betterlogin from our environment.

rajab natshah’s picture

Seems that no release for this module.
Used it for quite long time.
This is a blocker for upgrading to Drupal 10
Please, help us to have a smoother upgrade way
Only by committing and a tag release.

rajab natshah’s picture

This is a direct fork for the Better Login module
https://packagist.org/packages/vardot/betterlogin
https://github.com/Vardot/betterlogin

Following with changes from
#3286226: Automated Drupal 10 compatibility fixes
Started this Fork module on the 2.0.x branch
Switching to use the forked version

Dropped the use of this module in all new projects.
Hoping for a new branch 2.0.x.
Only help having a smooth upgrade process for old projects

seanb’s picture

Status: Needs work » Needs review

Let's start by getting this RTBC first, and then try to ping the maintainers for a new release.

deaconblues’s picture

The code based referenced earlier works. We just need to get the module maintainers to cut a release with the updated code.

https://git.drupalcode.org/issue/betterlogin-3286226/-/tree/3286226-auto...

dchaffin’s picture

Any update on a D10 release?

yogeshmpawar’s picture

Assigned: Unassigned » yogeshmpawar
yogeshmpawar’s picture

Status: Needs review » Fixed

First stable release created for Drupal 10 - https://www.drupal.org/project/betterlogin/releases/2.0.0

Very much sorry for not doing beforehand D10 released.

yogeshmpawar’s picture

Assigned: yogeshmpawar » Unassigned

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.