Try drush sqlq "DELETE FROM profile_field__uuid__value WHERE uuid = '221abf3f-07eb-42dc-91c6-876672a6d381'"
Clear the cache.
Did you empty the basket?
Can you reverse the patch you applied because it's wrong, empty your basket, apply the attached patch and try again? Let me know how it goes.
That's a good idea. Fixed that. It will be released soon.
Yes, skipping the message is a better option @drumm.
How is this a support request?
Kartagis → created an issue.
Fixed and committed.
This is fixed and committed.
Kartagis → created an issue.
Kartagis → created an issue.
What do you suggest I do? Maybe alter the config?
@cilefen what exactly do you mean in #4?
Kartagis → created an issue.
Kartagis → made their first commit to this issue’s fork.
Kartagis → made their first commit to this issue’s fork.
I have run into this in multiple occassions, today being the latest incident.
Kartagis → created an issue.
I came across this issue because it just happened to me. It also seems the fix has been applied. I got the error when I attempted to use one time login link.
Patch attached.
Kartagis → created an issue.
Kartagis → created an issue.
@jurgenhaas active user's IP could be there.
What feature of encrypt might iyzipay need?
Please reopen as needed.
@jurgenhaas this happens to me as well. We could make a form to enter IPs individually (not ideal, but works) and/or make a button for administrators to exempt them from the ban.
I just noticed something. I didn't get any errors like I used to, but when I proceeded to translate https://localize.drupal.org/translate/languages/tr/translate?sid=12830 and hit Save changes, it stays on the screen like nothing has been done. Sure, I get the status message that translation added, but it's like no translation has been added.
I can also confirm. Thank you to those who have put serious effort in this.
@serkan.arikusu can you remind me how to grant permissions?
I'll check this tonight @kburakozdemir, thanks
Drupal 10 compatibility has been applied with the commit 9919cdf8d943c4a49a0f76ed505e53ef8a8cf48e.
This project has already been made Drupal 10 ready.
When are you getting this whitescreen? As long as you enable it?
The patch at #2 works for me, I don't know about the other issues mentioned.
Honestly, I think this feature must go and we must encourage composer use.
I have the same issue. In my case, it's 10.0.x HEAD. I removed the vendor directory and performed a composer install as longwave suggested, which didn't work. However, the reported file's location is different with me. It's `vendor/doctrine/lexer/src/AbstractLexer.php`. Please advise.
Hi edib,
I'm one of the administrators of the Turkish localisation group and I'm happy to report we found a workaround. While you can't translate @count via the UI, you can export a .po file, translate the @count strings, import it and be done with it.
Actually, dependencies are core modules, so here's the updated patch.
Kartagis → created an issue.
Kartagis → created an issue.
Fixed and committed. Thanks for reporting. Please update.
This is wrong. Since the dependencies are Drupal core modules, they should be namespaced with Drupal. I'm attaching a patch to revert the change.
Sadly, I wasn't able to reproduce the issue on a freshly installed site. What more information do you need?
New info, this happens when a use has the roles "Site Owner, User Manager, Content Publisher".
What kind of information do you need @jrockowitz?
Kartagis → created an issue.