I'm adding a patch so that you can apply it through composer
I'm adding a patch so that you can apply it through composer
Added support for paragraph_view_mode field. Here is the error in Unit Test at the moment
1) Drupal\Tests\single_content_sync\Functional\SingleContentSyncImportTest::testSingleImport
Unable to install modules: module 'single_content_sync' is incompatible with this version of Drupal core.
Tests are performed for drupal 11, and core_version_requirement is specified in info.yml: ^9.3 || ^10
kuzyawkk → created an issue.
kuzyawkk → created an issue.
kuzyawkk → created an issue.
Yes, I added implementation for the ECA module similar to the Rules module.
I did not add any additional features on my own.
Yes, that's good. I'll take a look at it over the weekend and make some adjustments.
kuzyawkk → made their first commit to this issue’s fork.
I have implemented the logic, but I'm sure I could have made a mistake somewhere or overlooked certain conditions.
I'm sorry, I had a lot of unplanned work to do and didn't have any free time this weekend. I will definitely do it on the next one. But I would like to clarify if we are adding an “Inactive Expiration” field in the user creation form?
I added Token integration, but I don't think it's necessary for this module.
So I think it's better to close this issue without Token integration.
I will have some free time over the weekend and will complete this task.
Yes, I also think it's better to put it in a submodule.
This is still true for version 4.1. Therefore, I will try to implement this functionality
Hi @anybody, welcome. Yeah, I'm attaching screenshots with the result
I have encountered the same requirement on a project that required adding a “Cancel” button only for “Entity Add” forms. Therefore, I made a Merge Request in which I added a checkbox for each entity type, which is excluded by default. If you enable it, the button will appear only for the “Add Form” form
kuzyawkk → created an issue.
kuzyawkk → created an issue.
If the page already has any elements with position: fixed, then our stickynav will be placed below it. We also took into account the admin menu
This issue is still relevant for versions 8.x - 1.4. I'll take care of it and change the version to the most current one.
This issue is still relevant for versions 8.x - 1.4. I'll take care of it and change the version to the most current one.
Yes, I think it's a good idea. So I created a Merge Request in which I added a checkbox that adds a class '.body-stickynav-active' to the <body> element
kuzyawkk → made their first commit to this issue’s fork.
Hi kenyoOwen. Thanks for your review and changes. I have added these changes.
Hi, in comment
!4
🐛
"Language autocomplete (Tags style)" widget doesn't allow selection of languages with comma (i.e. Chinese, simplified)
Active
johnv described that the widget would work correctly if you wrap the language in quotes, then everything will work correctly. I added JavaScript, which automatically adds quotes when you select a language with autocomplete.
Before: Chinese, Simplified
After: "Chinese, Simplified"
KuzyaWkk → made their first commit to this issue’s fork.
KuzyaWkk → created an issue.
Thanks -mike for the review. I used the plural and added text with `additional examples`
Hi -mike, thanks for your check and request changes. I changed the data storage from configurations to StateApi. I also added additional checks if the data does not exist.
As for the password, this is an additional security feature. You must only enter a password if you plan to make AutoLoginUrl for any other account than the current one. The purpose: to provide secure access to any account. Suppose somehow an unscrupulous user gets administrator rights. In that case, they will not be able to access the login to any account without entering the account password for which the link is created.
If you plan to create a link for your current account, you do not need to enter a password.
Thanks,
-kuzya
KuzyaWkk → created an issue.
KuzyaWkk → created an issue.
KuzyaWkk → created an issue.
KuzyaWkk → created an issue.
KuzyaWkk → created an issue.
KuzyaWkk → made their first commit to this issue’s fork.
Added the ability to pass a parameter with an expiration value that will be stored in the database. If you do not pass anything, the value from the configuration will be pulled up. Also, wrote a hook_update_N that transfers values from the configuration to the database for all fields.
I think it's a good idea that hasn't been realized yet. I'll change the branch to the latest 2.0.0-alpha3 and try to make a patch.
I added a URL validation check. Now, if there is no user with the entered user_id, or the destination does not exist, FALSE will be returned instead of a broken link.
It is necessary to finalize the Functional Test for the pipeline to work correctly in GitLab.
KuzyaWkk → changed the visibility of the branch 3457800-detect-and-handle to active.
KuzyaWkk → changed the visibility of the branch 3457800-detect-and-handle to hidden.
uttam #4 ✨ Create Auto Login URL in Form Needs work thanks for yor review. I have reviewed the code and indeed the error is as you described. I updated the pull request, and now everything should work correctly.
KuzyaWkk → created an issue.
KuzyaWkk → changed the visibility of the branch 2930249-detect-and-handle to hidden.
Good idea, still not implemented in version 2.0.0 - alpha3. Since no patch has been released in the 3 years since ASSIGNED, I'll try to make one myself
Added the user ID to the hash itself. This may not improve the situation too much, but it's still better than it is now.
I had an idea to create an additional table in the database to store User ID and hash there. Then in the controller, get the uid from that table using the hash. This seems to remove the uid from the URL itself, but an additional table is not the best option.
I think it's a great idea that hasn't been implemented yet in version 2.0.0-alpha3. So I plan to do it and changed the version to the most current one
KuzyaWkk → created an issue.
KuzyaWkk → created an issue.
I faced the same problem using Drupal 10.3. I Used exposed filter widget "radio buttons/checkboxes". And if I didn`t select all the buttons, I got an error Warning: Undefined array key 1 in Drupal\content_moderation\Plugin\views\filter\ModerationStateFilter->opSimple() and AJAX didn`t work.
So, I installed the patch → and everything works correctly.
Thanks
KuzyaWkk → created an issue.
Created a separate configuration form for the user to choose which field to use. This will provide greater flexibility and the ability to choose any time calculation option