Fetch "User ID from route context" views' contextual filter for any entity

Thank you very much, it works

But I encounter another small problem.

1) I want to exclude the node or product from the current page. So I added to my view a pop-up filter to exclude the ID.

It would be interesting to replace:
"Identifier (ID) of the content from the url"
by :
"Identifier (ID) of the entity from the url"

2) I installed the "Commerce" and "Group" modules.

In contextual filters, I have:
- Identifier (ID) of the content from the URL.
- Group ID from URL.
- Store ID from the current store.

Why not group these 3 filters in:
- Identifier (ID) of the entity from the URL.

The patch works for me, but it does not work with the profile module page.

Every user on my site has a personal profile. I want to display a block with the nodes of the same author as the current profile.

Thank you for your help.

Sorry I've been searching for it, the patch is working properly ;-)

I hope it will be applied for the next update.

This patch is working for me.......
Thanks

@drugan thanks for working on this issue. This patch needs a test that proves it works for entities other than nodes.

Also...

1. +++ b/core/modules/user/src/Plugin/views/argument_default/User.php
   @@ -92,10 +92,12 @@ public function getArgument() {
   +      $entity = reset($bag);
   

   Will the entity always be the first route parameter? That seems a big assumption.

2. +++ b/core/modules/user/src/Plugin/views/argument_default/User.php
   @@ -92,10 +92,12 @@ public function getArgument() {
   +      if (method_exists($entity, 'getOwnerId')) {
   

   Here we're are assuming we know what the getOwnerId() method does and returns. But this is not at all enforced. We need to check whether or not the parameter implements \Drupal\user\EntityOwnerInterface - then getOwnerId() is safe to call.

In general this looks good.

-      '#title' => $this->t('Also look for a node and use the node author'),
+      '#title' => $this->t('Also look for an entity and use the entity author'),

Are we fine with saying "entity" in the UI? I remember that it was discouraged before, but I guess that ship sailed a long time ago.

+    $parameter_bag = $this->getMockBuilder('Symfony\Component\HttpFoundation\ParameterBag')
+      ->disableOriginalConstructor()
+      ->getMock();

Do we still allow non-Prophecy mocking to be added in new tests?

I like the general feature. It is always nice to get rid of hardcoded stuff for node, especially because the label "User ID from route context" totally indicate that already.

+++ b/core/modules/user/tests/src/Unit/Views/Argument/UserIdTest.php
@@ -0,0 +1,82 @@
+ * @coversDefaultClass \Drupal\user\Plugin\views\argument_default\User
+ * @group user
+ */
+class UserIdTest extends UnitTestCase {

I think I would have written a kernel test rather.

This works great!
Only thing is that I can't use the Product ID contextual filter to exclude a product if it is the same as the current product.
Using 'Content ID from URL'. Just like #3.

This patch works great. Use it on nodes.

Thank you very much.

The patch works with 8.6

Hi guys, it's been 2 years since I applied the patch on my site and it works for me. Do you think that one day it will be applied to the kernel ?

Thank you

thanks, the patch #23 works for me

Hi, do you know if the patch will finally be applied to drupal 8.8 ?

@drugan Hi, was the patch applied to the kernel? If I test a blank installation on simplytest, there is the parameter user ID from the context of the route.

Drupal 8.8.2

Fixed failed commands on #23
Attached patch against Drupal 10.1.x

The Needs Review Queue Bot tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.

This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request as a guide.

This could use an issue summary update using the default template. Steps to reproduce? Was the suggestion what was used in the solution?

Taking this setting away seems like it could affect existing views. If so they'll need upgrade paths.

Hours of searching, and I keep on finding this post so I need to ask some questions.

I'm converting my site from Drupal 7 to 10, where on D7 I had multiple views with a contextual filter that properly got the userid from the node the block was on, so I could show other nodes from this author. I have spent hours trying to get it to work, is this post stating this is not working in Drupal 10+?

I have the option, "Also look for a node and use the node author" checked so I'd assume since that option is in there it should be working? This seems to be a feature I'd think many sites would need, so maybe I'm just not doing something right?

I'd try this patch, but it looks like it has issues now and I'm on 10.1. If this is the patch to try I can help test, as I'm not a programmer but I will help how I can.

I found a work around, instead of basing my view on node/content, I based it on users and used the authour/user relationship to pull nodes and it works great.