This issue will serve as a central hub for discussions regarding the planned features and issues that need to be addressed before finalising the TFA Email OTP Plugin.

The tasks outlined here are expected to be included in the 1.0.0 release, which is currently scheduled for the end of this year.

Let’s use this thread to monitor progress and refine the release plan as needed.

Feature enhancements

#3469826: Disable Verify button on first landing to the tfa form

Bug reported

#3469238: Incorrect Redirect link when TFA TOTP is set as default method

Comments

tarawij created an issue. See original summary.

mingsong’s picture

Issue summary: View changes
mingsong’s picture

Assigned: Unassigned » mingsong
lmoeni’s picture

Hi, thanks for this module :)
Do you already have a approximate date in mind to release 1.0.0?

mingsong’s picture

Issue summary: View changes
mingsong’s picture

It is aiming for the end of this year.

It depends on when we can get those issues solved.

The following new feature requires help on test, particularly PHP and JavaScript functional test script.
#3469826: Disable Verify button on first landing to the tfa form

casey’s picture

What is the status of this issue? Can we have a new release for #3519636: Drupal 11 compatibility ?

mingsong’s picture

The dev version is already compatible with D11.

https://www.drupal.org/project/tfa_email_otp/releases/1.0.x-dev

You can download or composer require 'drupal/tfa_email_otp:1.0.x-dev@dev'

casey’s picture

Yes I noticed, thanks! Can you also tag a new (beta2?) release so we don't have to use the dev version in production?

mingsong’s picture

Issue summary: View changes
Status: Active » Fixed

There are more 500 sites using this module. I think we are now confident to say that this module has been stable enough for production sites.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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