Added a possible work around to prevent this to the issue description.
I know this is possible because I have used onKernelResponse events to modify CacheableResponse response's CacheMetadata for other things.
Changing title to reflect that the attached patch also improves tracking paragraphs back to the 'linkable' source (e.g. node, etc.) and not just the parent item. This is independent of if embedded paragraphs are used.
FYI - This issue prevents entities that cause this problem from being selected as sources.
✨ Limit source entities in settings to ones that have fields Active
Here's a version that solves these concerns:
1. & 3. - The tracker now checks that embedded_paragraphs can be used as sources and that paragraphs can be targets. If not true, no tracking occurs and a logger message is output once per instance.
In addition, the settings form now has a validation that will not let this tracker be selected unless emebedded_paras is an allowed source and paras are an allowed target. Message also suggests they should be target/sources too.
Also, the tracker plugin is disabled unless the paragraphs_entity_embed provider module is enabled. (provider annotation)
2. - The required info is retrieved via 2 queries now instead of loading entities.
Here's the patch
cgmonroe → created an issue.
Patch for issue
cgmonroe → created an issue.
Just found that the #5 patch was incomplete. It allowed more chars in the form but when it was exported to a config yml file, it got truncated. Attached is a patch that also changes the config schema to use text instead of string. This lets long extensions values get exported correctly. Will not effect any existing yml files as the syntax is the same.
IMHO the #5 patch which just increases the max car lenght is the way to go.
The patch with a textarea needs some extra code to handle cases like on extension per line, blank lines, extra spaces before/after the lines, and possible other user input cases created by using a text area.
The majority of cases will only have a handful over extensions easily managed on one line. But there are special cases where there are dozens of accepted extensions (e.g. site sharing scientific research results that come in many flavors.. I know use zip..but researchers don't like it...) that the max length now supports. This keeps it simple and works for all but extreme conditions.
Here's the simple patch.
cgmonroe → created an issue.
Needed this function but my organization requires patched releases and not dev versions. Here is a patch that adds in the drush support.
Mea Culpa - missed new confirmation form in patch. Here's the right one.
Here's the patch for this.
cgmonroe → created an issue.
Needed to generate a view of last revision usage stats that was sort-able / filerable by usage.
Here's a patch that make the source_id sortable and filterable as well.
Forgot to change status.
Hit the same problem. Here's a patch that works with the current release/dev.
FYI - This is already possible using the form alter hook. I added how to do this to the Embedding Media With CKEditor documents a couple of years ago. See:
Haven't tried it yet, but don't see why this will not work for CKEditor 5 as well.
Perhaps the focus of this issue should be to add tests to ensure that code using this method does not break.
Semi old request but in case anyone has a need like this there is a module that will do what the requestor asks for:
https://www.drupal.org/project/user_expire →
No need to add code to this module.
cgmonroe → created an issue.
Hmm, not sure why the token test failed. Trying a different variation that just skips setting the name if the originame parameter does not exist.
Patch to fix this problem
cgmonroe → created an issue.