@pearls

Thanks @terry_kolodiy .
I just tested the MR!14 and it works perfectly.

pearls → created an issue.

pearls → created an issue.

Tested.
Interestingly enough, the 3-year patch (#15) worked for Drupal11 (v 11.1.5)
#39 and #44 didn't apply.

This error is now gone and after patch #15 I can delete referenced entities without errors

LogicException: The database connection is not serializable. This probably means you are serializing an object that has an indirect reference to the database connection. Adjust your code so that is not necessary. Alternatively, look at DependencySerializationTrait as a temporary solution. in Drupal\Core\Database\Connection->__sleep() (line 1297 of /home/pearls/public_html/d11site/web/core/lib/Drupal/Core/Database/Connection.php)

pearls → created an issue.

pearls → created an issue.

How about fetching image data from default field like user_picture ? (ex: field_image)

I'm not entirely sure after the latest updates(MS) but it's still relevant when using the message subscription module.

He talks about RealName ( https://www.drupal.org/project/realname → ) module support.
We can think of Realname as a name-surname phrase or a new nickname used instead of username.
In most scenarios, it is important to search for the user or author by their real name instead of username, so I think this support is also necessary.

The relevant error occurred after this merge. Rate module calling the Vote API with a missing argument.

MR !48 : https://www.drupal.org/project/votingapi/issues/3509000 📌 Strict typing and fluent interface for Vote entity Active

Ok.Thanks

Here's the log with rate module after this merged.

TypeError: Drupal\votingapi\Entity\Vote::setValue(): Argument #1 ($value) must be of type float, null given, called in /var/www/html/d11site/web/modules/contrib/rate/src/Plugin/RateWidgetBase.php on line 316 in Drupal\votingapi\Entity\Vote->setValue() (line 92 of /var/www/html/d11site/web/modules/contrib/votingapi/src/Entity/Vote.php).

ArgumentCountError: Too few arguments to function Drupal\votingapi\Entity\Vote::setValue(), 0 passed in /var/www/html/d11site/web/modules/contrib/rate/src/Plugin/RateWidgetBase.php on line 316 and exactly 1 expected in Drupal\votingapi\Entity\Vote->setValue() (line 92 of /var/www/html/d11site/web/modules/contrib/votingapi/src/Entity/Vote.php).

pearls → created an issue.

There is a nice alternative module for this feature but it is very limited. It even limit user 1 , administrator, all etc.
If anyone needs it, they can try it. https://www.drupal.org/project/flag_limits →

I think it would be better if the new release was compatible with d11.

pearls → created an issue.

Thanks @nicxvan MR/patches mentioned in #12 did not provide a solution. They are also not ready to be applied.

#5 works with Choices Autocomplete. Thanks for patch.
However, it controls after the selection and prevents the entity from being saved with a warning.
It is better to prevent selection when selecting an item that does not belong to the dependent list.

I have the same problem. The only difference is that I am experiencing this problem with the field encrypt module. When I remove field encrypt, the problem goes away. When I activate it, I experience it again. Usually, with the Drush updb command...

pearls → created an issue.

pearls → created an issue.

I have the same issue. Thanks to @blacksnipe . #2 patch solved the problem.

+1 for RTBC

pearls → created an issue.

I would love to create a MR for this, but unfortunately my skills are limited.
I found a solution with the Group → module.
Thanks for your support.

pearls → created an issue.

pearls → created an issue.

Is there any roadmap for Drupal 11 upgrade ?
Thanks

pearls → created an issue.

MR184 worked for me.

Hi dineshkumarbollu ,
It's 8.3.
But, I don't remember the exact version when I created the issue. It may be 8.3.9 .

Here are the logs when I tested with D11

When you try to reach "change request" settings;

ArgumentCountError: Too few arguments to function Drupal\Core\Form\ConfigFormBase::__construct(), 1 passed in /var/www/html/d11/web/modules/contrib/change_requests/src/Form/ChangeRequestsConfig.php on line 58 and exactly 2 expected in Drupal\Core\Form\ConfigFormBase->__construct() (line 44 of /var/www/html/d11/web/core/lib/Drupal/Core/Form/ConfigFormBase.php).

When you try to rebuild permissions;

So, You also cannot access the status report.

Error: Call to undefined function user_roles() in _change_requests_check_permissions() (line 207 of /var/www/html/d11/web/modules/contrib/change_requests/change_requests.module).

Any idea, please ? Thanks

@nidhi27 , It's ok for me. +1 for RTBC

1-ckeditor_mentions →
+The mentioned entity is in link format that links to its own page instead of string format by default.
+It works well with token module with satisfactory coverage. So you can easily create a notification system or integrate it with supporting modules like message → or ckeditor_mentions_notifications → .
--You cannot restrict or filter the entity type & role permission.
- It doesn't support all types. You can only mention user & node.

2-CKEditor5 Mentions →
+Seems to support all kinds of entities You can mention taxonomy term. Seems to support all kinds of entities (I have not tested other entity types except node and taxonomy)
It would be nice if there was a multiple choice option during selection.
+ Permissions to mention/to be mentioned.
+Notification system.Your need ckeditor5_premium_features → .
-The token scope is not as wide as the ckeditor_mentions.

Both modules work within the mentioned framework.
Both modules do not support specific node(entity) restriction. Customization required.

Currently, first module is more suitable for me, as I think its integration with the token scope is more flexible.

But with the support of ckeditor5_premium_features → , you can try different options with the second module. It comes with many different features (with registeration API). It has own ecosystem.

Ok. I found the problem. It's all about the inline entity form. If the field form format is inline entity form, then when you apply the patch it all gets deleted

Hi @swirt,
Thanks for support and advices.

Is there any news for this feature ? Or any other approaches, advice would be greatly appreciated.
Thanks

pearls → created an issue.

I guess your tests don't show anything like that. Then we can think that it's related to my test environment. Ignore it.

Thanks all. I just tested MR!2 now. It works fine with custom/default comment types.
Just started a new little problem;
There's a warning as "/history/get_node read timestamps" in recent dblogs when a member replies a comment.

pearls → created an issue.

I tried your advices. This patch is not for v5 and there has been no progress after a long time..It didn't work.
Also I tried this module ( Views Default Argument: Entity Field Values → - similar to your advice).

After three days, my searches and different attempts have not yielded any results.
I guess I have to go back to book module.
I have given up.
Thank you very much for your support.

I still think this feature is necessary because a book(any content) can be a creative final work that no one wants it to be expanded upon by others. There are situations where no one wants to interfere with other people's work.
Therefore, members should be limited to choosing their own content.
No one should be able to add their own content to someone else's book or parent content. Or, permissions can be extended or limited based on the type of node.
Another benefit is that the outline list will be shorter when selecting/searching for a book/parent from a bunch of books.

+1 for following
Facing same problem.

pearls → created an issue.

Hi Lee,
Yes , You're right. It'a about revisions.

I created two test.

First one
Parent:Course
Child:Lesson
Create new revision option: No

It worked perfect.

Then I created new one
Second example
Parent:Teacher
Child:Student
Create new revision option: Checked

When I create a lesson-course or class-teacher contents I saw the same error.
The same error appears in some of the contents(lessons) in the first example, which I do not understand.

I also created another block with revision id but the result is the same.

Then I deleted class-teacher contents and also content types.
Just only first example remained.

Now I can see sibling lessons again.

I couldn't understand why another type of content being revisable would cause an error.

So, any advice please. Thanks

pearls → created an issue.

pearls → created an issue.

pearls → created an issue.

I have encountered this error before, but I think the problem is related to MR!43.

Tested with Drupal 10.4.1 ECK 2.1.0-beta1 & 2.x-dev .
The error seems to be a bit serious. After these attempts, the test site cannot return to its previous state, sql:drop is required. A fresh test site was used each time.Since I could not pass this stage, I did not have the opportunity to test it with other related eck modules.

Here's the dblog records with fresh install.

When I try to add the entity type, if I don't select the revisionable option;

Drupal\Core\Entity\Exception\UnsupportedEntityTypeDefinitionException: The entity type organization does not have an "revision_created" entity revision metadata key. in Drupal\eck\Entity\EckEntity::revisionLogBaseFieldDefinitions() (line 35 of core/lib/Drupal/Core/Entity/RevisionLogEntityTrait.php).

If I select the revisionable option;

Drupal\Core\Entity\Exception\UnsupportedEntityTypeDefinitionException: The entity type organization does not have an "owner" entity key. in Drupal\eck\Entity\EckEntity::ownerBaseFieldDefinitions() (line 33 of core/modules/user/src/EntityOwnerTrait.php).

Detailed log

The website encountered an unexpected error. Try again later.

Drupal\Core\Entity\Exception\UnsupportedEntityTypeDefinitionException: The entity type organization does not have an "owner" entity key. in Drupal\eck\Entity\EckEntity::ownerBaseFieldDefinitions() (line 33 of core/modules/user/src/EntityOwnerTrait.php).
Drupal\eck\Entity\EckEntity::baseFieldDefinitions() (Line: 230)
Drupal\Core\Entity\EntityFieldManager->buildBaseFieldDefinitions() (Line: 195)
Drupal\Core\Entity\EntityFieldManager->getBaseFieldDefinitions() (Line: 454)
Drupal\Core\Entity\EntityFieldManager->getFieldStorageDefinitions() (Line: 490)
Drupal\Core\Entity\EntityFieldManager->getActiveFieldStorageDefinitions() (Line: 187)
Drupal\Core\Entity\Sql\SqlContentEntityStorage->__construct() (Line: 149)
Drupal\Core\Entity\Sql\SqlContentEntityStorage::createInstance() (Line: 280)
Drupal\Core\Entity\EntityTypeManager->createHandlerInstance() (Line: 84)
Drupal\trash\TrashEntityTypeManager->createHandlerInstance() (Line: 68)
Drupal\trash\TrashEntityTypeManager->getHandler() (Line: 51)
Drupal\trash\TrashEntityTypeManager->getStorage() (Line: 69)
Drupal\Core\Entity\EntityTypeListener->onEntityTypeCreate() (Line: 150)
Drupal\eck\EntityUpdateService->doEntityUpdate() (Line: 120)
Drupal\eck\EntityUpdateService->applyUpdates() (Line: 144)
Drupal\eck\Entity\EckEntityType->postSave() (Line: 563)
Drupal\Core\Entity\EntityStorageBase->doPostSave() (Line: 489)
Drupal\Core\Entity\EntityStorageBase->save() (Line: 257)
Drupal\Core\Config\Entity\ConfigEntityStorage->save() (Line: 354)
Drupal\Core\Entity\EntityBase->save() (Line: 617)
Drupal\Core\Config\Entity\ConfigEntityBase->save() (Line: 194)
Drupal\eck\Form\EntityType\EckEntityTypeFormBase->save()
call_user_func_array() (Line: 129)
Drupal\Core\Form\FormSubmitter->executeSubmitHandlers() (Line: 67)
Drupal\Core\Form\FormSubmitter->doSubmitForm() (Line: 597)
Drupal\Core\Form\FormBuilder->processForm() (Line: 326)
Drupal\Core\Form\FormBuilder->buildForm() (Line: 73)
Drupal\Core\Controller\FormController->getContentResult()
call_user_func_array() (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 638)
Drupal\Core\Render\Renderer->executeInRenderContext() (Line: 121)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext() (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 181)
Symfony\Component\HttpKernel\HttpKernel->handleRaw() (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle() (Line: 53)
Drupal\Core\StackMiddleware\Session->handle() (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle() (Line: 28)
Drupal\Core\StackMiddleware\ContentLength->handle() (Line: 32)
Drupal\big_pipe\StackMiddleware\ContentLength->handle() (Line: 116)
Drupal\page_cache\StackMiddleware\PageCache->pass() (Line: 90)
Drupal\page_cache\StackMiddleware\PageCache->handle() (Line: 57)
Drupal\advban\AdvbanMiddleware->handle() (Line: 50)
Drupal\ban\BanMiddleware->handle() (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle() (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle() (Line: 36)
Drupal\Core\StackMiddleware\AjaxPageState->handle() (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle() (Line: 741)
Drupal\Core\DrupalKernel->handle() (Line: 19)

pearls → created an issue.

I saw same issue as mentioned in #31. Patch #18 fails.

MR!3 ( #29) is applied but now other problems.

When creating a new pattern it shows

Drupal\Component\Plugin\Exception\PluginNotFoundException: The "node_type" plugin does not exist

For existing patterns, I see the error mentioned in the screenshot below.

Versions: Drupal version 10.4.1 Viev mode page: 4.0.3

+1 for "I need these answers too."

Thanks @shivam. MR !5 worked for me.
+1 for RTBC

I tested with Drupal 10.4 It may be about my test environment.
We can close this issue.

pearls → created an issue. See original summary → .

If a comparison cannot be made, I think there is no big point in Storage Module instead of using node revisions.
When I try to compare revisions in the views table the following log appears.

Symfony\Component\Routing\Exception\RouteNotFoundException: Route "entity.storage.revisions_diff" does not exist. in Drupal\Core\Routing\RouteProvider->getRouteByName() (line 211 of core/lib/Drupal/Core/Routing/RouteProvider.php).

Maybe the maintainer is so busy or has stopped supporting the module because the scheduling isn't working either.

pearls → created an issue.

MR22 worked but MR24 didn't work for me.

pearls → created an issue.

#22 worked for me.
+1 for RTBC

New warning (line 129 of ...) repeats 4 times in my project after #2 patch.

pearls → created an issue.

pearls → created an issue.

I have the same issue. Also, you cannot remove the module clearly.

Be sure to back up your database and configuration before trying this module.

There were errors validating the config synchronization.                                                                             
  Unable to uninstall the <em class="placeholder">User revision</em> module because: This module cannot be uninstalled because Drupal  
   doesn't support converting an entity type from revisionable to non-revisionable.   

MR!88 worked for me.
+1 for RTBC

Thanks.
#4 Patch-11 worked for me.
+1 for RTBC

MR!9 didn't work for me. Cron is not running, publishing is still not happening at scheduled time. It still shows unpublished.
I've been waiting for this to be resolved for a long time, I was hoping it would be fixed with version 1.4 but the same problem persists. Thanks

pearls → created an issue.

Hi @anybody,
If you check the screencast, you will see that all node types are skipped by protection even if their form ID is not in the excluded list.
But it works for comment forms. Validation cannot be bypassed unless added to the exclude list.

Suggestion 1:
It can work as designed. But, the entity from id should be allowed to be entered separately according to its type. For example: node_article_form, node_page_form, node_forum_form or custom_non-node_entity_type_form etc.

Suggestion2:
It can be specified in text formats-editors as the most comprehensive option.
Thus, there is no need for a form ID. Whether the correct ID is added or not is not a problem. It can be added or excluded in different scenarios in text formats and editors in a very flexible way. Check Wordfilter → module, please.In my opinion, this is the best option.

Suggestion3:
The last option can be allowed in the node type settings, which will be the most restricted option. It will be a problem for other custom entity types.

It cares about all bundle forms. When you exclude an id, it affects the entire bundle.Instead of including the entire bundle, it should exclude the types separately.

For example;The flexibility in the forum may not be in the articles. That was the opening purpose of this issue.

İf you exclude node_forum_form (forum type) it will also excludes node_article_form. It will also bypass protection on articles.
or
For comments;
İf you exclude forum comment form id (comment_forum_comments_form) it also excludes article comment form (comment_comment_form)

Also it doesn't work other custom type entity like ECK. It bypass them.
Thanks

Tested. #5 patch worked for me.
+1 for RTBC

#4 @murz Is this accurate information? How did you measure that view mode page module eats too much CPU and memory.
I would be very happy if you could enlighten me. Thanks

pearls → created an issue.

Sorry for the insufficient information.

I am trying to use entityconnect in storage → forms.

Reference field using select2 form. I also tested with autocomplete or other select widgets
Even if I change the field form format, the following error occurs.

Warning: foreach() argument must be of type array|object, string given in Drupal\entityconnect\EntityconnectFormUtils::validateForm() (line 101 of modules/contrib/entityconnect/src/EntityconnectFormUtils.php).

Could the problem be because I'm using custom entity(storage) instead of node type?

Thanks for support.

pearls → created an issue.

pearls → created an issue.

pearls → created an issue.

pearls → created an issue.

pearls → created an issue.

#93 worked for me. Drupal version : 10.3.8

Merge request !7274 could not be applied.

This issue still exists and I experienced it with a taxonomy term field.

Here's the dbLog when I try to add limit to media entities.

Warning: foreach() argument must be of type array|object, null given in Drupal\entity_limit\Plugin\EntityLimit\RoleLimit->getLimitCount() (line 213 of /var/www/html/d10site/web/modules/contrib/entity_limit/src/Plugin/EntityLimit/RoleLimit.php)

Could you also support custom entity types other than node type? It only works with node types.

MR 11 Tested.
During configuration import, warning "Missing bundle entity, entity type flag, entity id email_node." was not received.
+1 for RTBC

I have the same issue while importing the configuration.

The rank field is created via weight module which can contain negative numbers.
I thought it was related to negative number.s Even though the problem is solved (it is fixed here - #3484686 💬 Support: Indexable negative number Active .), I still get an error while importing the config.

I don't know if the problem is related to the negative numbers or weight module, but the problem with importing the configuration still persists.

 [error]  Drupal\search_api\SearchApiException while adding Views handlers for field Content » Rank on index Default content index: Could not retrieve data definition for field 'Rank' on index 'Default content index'. in Drupal\search_api\Item\Field->getDataDefinition() (line 487 of /var/www/html/d10Site/web/modules/contrib/search_api/src/Item/Field.php).
 [error]  Drupal\search_api\SearchApiException while computing Views data for index Default content index: Could not retrieve data definition for field 'Rank' on index 'Default content index'. in Drupal\search_api\Item\Field->getDataDefinition() (line 487 of /var/www/html/d10Site/web/modules/contrib/search_api/src/Item/Field.php).

There is a loop between the issues. Each one references each other and at the end of the day, it does not provide any solution. There is no different situation for Version 2. The problem still persists.By the way, patch in #24 is not applied and does not work.