leo liao → created an issue.
leo liao → created an issue.
This has been resolved in 3.5 and 3.4.2.
Updated to version 3.5
leo liao → created an issue.
A usable patch has been generated for the current official version 1.5.
I found two related questions.
https://www.drupal.org/project/drupal/issues/3415478
🐛
\Drupal::entityTypeManager()->getStorage('user_role')->load() can't load non-english string
Closed: won't fix
https://www.drupal.org/project/webform/issues/3415445
🐛
Search Chinese in /admin/structure/webform cause error: Illegal mix of collations
Closed: duplicate
When investigating webform/src/Plugin/WebformElement/DateBase.php:183, we found that it directly uses DateFormat::load('Y年') for query. In drupal, the format of id has requirements that do not allow the use of '年'. This kind of character.
leo liao → created an issue.
leo liao → created an issue.
Try reapplying the patch https://www.drupal.org/files/issues/2022-03-07/296693-243.patch → from https://www.drupal.org/project/drupal/issues/296693 🐛 Restrict access to empty top level administration pages Fixed .
#284 @Simon Georges
I'm creating an issue for this.
https://www.drupal.org/project/drupal/issues/296693
🐛
Restrict access to empty top level administration pages
Fixed
leo liao → created an issue.
Supports 10.2.x
leo liao → created an issue.
Sometimes it is determined whether the wrong node is a translated node, such as when it exists in a historical node.
Sometimes it is determined whether the wrong node is a translated node, such as when it exists in a historical node.
When the media's default language is not the site's default language, the checkbox will not be displayed.
When returning from preview, the route will change.
Displays the status of the translated version and a link to the translated version.
If you click Preview when creating a translation, and then return to the editing interface, you will no longer have permission.
Make sure the language we want to operate on won't be available in this version.
The language may have been removed in a version after this one.
leo liao → created an issue.
When used with the https://www.drupal.org/project/quick_node_clone → module, even if the node is not new in the clone interface, it should be a new node.
According to adjustment #10, after we display a specific language, we want to directly display the link and title of the language, and usage in is no longer needed.
In any case, you should have permissions when adding new ones.
leo liao → created an issue.
If translation is not enabled for the field, an error will be reported.
My version is 10.1, so I'm not sure if it's the same problem as yours.
The email is plain-text, and the length of the link obtained by [user:one-time-login-url] is 96.
Finally got a result:
https://xxxxx-xxx.xxxx.xxxx002.com/xxxxx/en/user/reset/206/1696748244/zs...
In the email it will be displayed as:
https://xxxxx-xxx=
..xxxx.xxxx002.com/xxxxx/en/user/reset/206/1696748244/zsf4sEAXUIZj9qfHBJUwdj=
PfAbed1ZIyL4ipsaP7_Ws
As you can see there are two '.'s in the domain name causing it to become an incorrect and unusable link.
I think this is due to the lineLength control of the Headers in the email, causing line breaks.
If the line break happens to start with '.', then it will produce two '.'
The notification sometimes returns a null value, I know this is not expected, but it does happen sometimes in my actual scenario.
For example, if the approver's role is set up, when the approver leaves the job at a certain time, there is no new approver to replace him.
At this point in our project his work will be taken over by the super administrator.
But the approver's notification settings will not be updated because this will only last for a short period of time.
But you will encounter this problem here, the notification actually has no recipients.
leo liao → created an issue.
#66 Support 10.1.2
I am not a professional front-end, did not find the root cause, this is just a temporary solution.
Or is there a more professional front-end developer willing to follow up?
leo liao → created an issue.
#66 Support 10.1.1
leo liao → created an issue.
leo liao → created an issue.
Add translation of code.
It couldn't be applied in 1.4, so I made a temporary patch.
It can't be applied in 1.6, so I made a temporary patch.
So any progress so far?
leo liao → created an issue.
leo liao → created an issue.
An available patch was created based on 8.x-1.0-beta3. We will use this until the new release.
We will use this patch in drupal 10 until it is officially released.
leo liao → created an issue.
TFA supports drupal 10 only in version ^2.
leo liao → created an issue.
leo liao → created an issue.
ConfigManagerInterface::findConfigEntityDependentsAsEntities() is deprecated in drupal:9.3.0 and is removed from drupal:10.0.0. Instead you should use ConfigManagerInterface::findConfigEntityDependenciesAsEntities(). See https://www.drupal.org/node/3225357 →
leo liao → created an issue.
This patch is modified according to #10. Although part of the code in this issue has been merged, the problem still exists. When I apply paragraphs in a block, this block is applied in layout build. When saving the layout, this error will be prompted.
drupal version is 10.1
leo liao → created an issue.
Infinite loop updb.
Following the advice from #112, from #97, that seems more reasonable.
Also, this is only in 9.5.x.
fixed test.
Support for 9.5.x based on #111.
Then I made some adjustments, and when both translation and Content Moderation were enabled in the site, an exception occurred.
Steps, 1 Add node in en language, and publish en language.
2 Add the translation of ja language for it, but do not publish ja language.
At this point there will be no information about the language in the taxonomy_index table.
It cannot be displayed in the view.
This is considered an unusual error on our site. Published languages should be visible to anonymous users.
Unpublished languages may be checked in the normal workflow, it cannot affect the normal published display.
I used the patch of #14, but there is a problem, when the user enters the full path of the current site with the domain name in the link field, the window still pops up, I try to fix it.
Sorry for ignoring it, I found the answer here:
https://www.drupal.org/project/content_moderation_notifications/issues/3... →
https://www.drupal.org/project/content_moderation_notifications/issues/3... →
The status of authenticated users is adjusted in this Tiket, but other more roles seem to ignore this problem.
leo liao → created an issue.