🇹🇷Turkey @orkut murat yılmaz

any updates?

I've installed 1.1.x-dev version with @prudloff's patch and it is working:)

Is it okay to create a new release now? Maybe a beta one?

@greg boggs, are you going to release a new version, including this fix?

@b.khouy, thanks for fixing:)

Are you going to release a new version?

Can you refactor the patch for 10.3.x?

any chance for update?

orkut murat yılmaz → created an issue.

orkut murat yılmaz → created an issue.

@vinodhini.e, thanks for testing:)

@sanduhrs, thank you:)

I'm changing the issue's status as fixed.

any chance for merge?

any updates?

any updates?

I've tested it with the upgrade status module and it works. Can someone review it too?

orkut murat yılmaz → created an issue.

@robert castelo thank you:)

@gaurav.kapoor, thank you. I've just sent 2 messages to @sandeep_jangra about this issue.

thank you @jsacksick :)

When are you going to release a D11 version?

Maybe we should refactor the module for D11 too?

@bobburns, have you tested the latest commits on 2.0.0-alpha0?

I'm changing the issue's title and status too.

any updates on this?

Can we migrate this issue to drush project?

How can we proceed with this?

Hi everyone,

I would like to inform you that I would be happy to act as co-maintainer on the project if @gaurav.kapoor approves.

I wish you all a great week.

@pearls, I do agree with you. Should I contact one of the maintainers?

I can also confirm that too. Thank you @benjifisher :)

Sorry, I forgot saying that, I've applied the MR as a patch and scanned entity limit with upgrade status module:

No problems found

any chance for applying this to 4.x?

@pearls, can you review the @jdvc's MR too?

I've just tested the latest version and it looks stable.

Thanks for all the efforts:)

any chance for merge?

any chance for merge?

@rakesh.gectcr, thanks for the patch. I can confirm that, patch #49 can fix this issue too.

any chance for merge?

@vinodhini.e thanks for all the tests:)

@vinodhini.e great:)

@vinodhini.e thank you:)

It will be fixed, if the MR of this issue 💬 Please develop the module for Drupal 10 Active is accepted.

Please consider my issue ✨ Disable email field on user registration form, if it is set as optional Active too. :)

@vinodhini.e, can you also test these issues too?

https://www.drupal.org/project/optional_email/issues/3530927 ✨ Disable email field on user registration form, if it is set as optional Active

https://www.drupal.org/project/optional_email/issues/3443982 💬 Please develop the module for Drupal 10 Active

if they work for you too, please change the status as RTBC for both of them:)

I've just re-scanned the module with the patch applied, using upgrade status module and there is an error, preventing the upgrade, which I paste below:

file: web/modules/contrib/faq/faq.install

line: 59

error: Relying on entity queries to check access by default is deprecated in drupal:9.2.0 and an error will be thrown from drupal:10.0.0. Call \Drupal\Core\Entity\Query\QueryInterface::accessCheck() with TRUE or FALSE to specify whether access should be checked.

I'm changing the issue's status as "needs work".

Can you review my MR please?

orkut murat yılmaz → created an issue.

@drupal.ninja03, I've tested your patch and it is working. Thanks for your contribution:)

The patch does not work. @sandeep_jangra

I've created a Merge Request, using Upgrade Status module → 's scanning function. It works on my development and test environments.

Can you review it please?

the patch #28 works great:)

any updates?

@jurgenhaas, thanks for your kind and quick answer:)

The error is gone, when I switched to dev version.

any chance for merge?

orkut murat yılmaz → created an issue.

@jfeltkamp, thanks for the patch. I works well:)

Also, problem still exists with cookies 2.0.0-alpha3 (and 2.x-dev) too.

I've updated my Drupal core to 11.2.0-rc2 today, but the problem doesn't disappear.

The changeset looks mergeable.

It's not directly related to this issue, but this blog post has given some ideas to me:

https://www.gomomento.com/blog/valkey-turns-one-how-the-community-fork-l...

After a few cache clear and drush updb, upgrade to Webform 6.3 went well. I'm closing this issue.

Thanks for everything.

Sorry for the previous message.

I've just tested the MR as a patch and scanned with Upgrade Status module. The result is:

There is an error in user_one_time_login/src/Form/UserOneTimeLoginConfigForm.php file, line 36:

Call to deprecated function user_role_names(). Deprecated in drupal:10.2.0 and is removed from drupal:11.0.0. Use Drupal\user\Entity\Role::loadMultiple() and, if necessary, an inline implementation instead.

orkut murat yılmaz → created an issue.

any updates on this?

This is the output of the audit command:

composer audit
Found 1 security vulnerability advisory affecting 1 package:
+-------------------+----------------------------------------------------------------------------------+
| Package           | drupal/faq                                                                       |
| Severity          |                                                                                  |
| CVE               | NO CVE                                                                           |
| Title             | Frequently Asked Questions - Critical - Unsupported - SA-CONTRIB-2019-077        |
| URL               | https://www.drupal.org/sa-contrib-2019-077                                       |
| Affected versions | *                                                                                |
| Reported at       | 2019-11-13T18:00:36+00:00                                                        |
| Advisory ID       | SA-CONTRIB-2019-077                                                              |
+-------------------+----------------------------------------------------------------------------------+

Thanks for the merge:)

@ressa, thanks for the improvement:)

orkut murat yılmaz → created an issue.

thanks for the merge:)

any updates on this?

Sorry, I forgot doing "drush updb" after the update.

orkut murat yılmaz → created an issue.

The MR 21 works:)

@greg boggs thanks for refactoring and the missing comments too:)

any chance for review?

Thanks for the merge:)

any chance for merge?

any chance for merge?

any chance for the merge?

Can someone test and review this?

It is a little commit, but looks working. Can someone review and test it too?

orkut murat yılmaz → created an issue.

any updates?

@axelm, thanks for correcting my mistake, D10 support will be over in a year.

It is very interesting that the status of this issue has remained as "Needs review" for 6 months. Also, Drupal 10's support will be over in 6 months.

The feeling of abandonment is a heavy burden to carry for everyone.

We need to analyze this case carefully and find out what can be done for the benefit of our community.

I've created an MR, with the help of ollama and gemma3 :)

Can you review it please?

@andeersg, any chance for reviewing this issue too?

@andeersg, thank you:)