BelongsToMany edit not work and no needed

[approached]

• Laravel Version: 5.6.39
• Nova Version: 1.1.7
• PHP Version: 7.1

Description:

I have BelongsToMany connection. If click on edit i can't edit it. This problem i have on all models.
I have no extra fields, so me don't need the edit function. Is that possible to disable?

BelongsToMany::make('Products that use this attribute', 'products', \App\Nova\Product\Product::class),

Steps To Reproduce:

2.

[approached]

I'm just follow the documentation: https://nova.laravel.com/docs/1.0/resources/authorization.html#policies

Just attach and detach is possible to control.

[carloshc]

It's make senses. It's not necessary to edit a BelongsToMany relation.

[cristafortuno]

Running on a similar issue.

I would like to hide the Edit button (and probably the View button as well) so as to leave just the Attach and Detach functionalities.

Is there a way to do this?

[93gaurav93]

@taylorotwell I also want to hide the Attach button. Do we have any solution?

[jeffcaulfield-morphsites]

I struggled with a similar issue for some time. It wasn't at all obvious from the Nova documentation how to hide the "edit" button for simple pivot relationships where it isn't needed or wanted, though the solution makes sense in hindsight.

Let's assume you have an Attribute resource and a Product resource and that each manages a model of the same name. Further, let's assume that there is a belongsToMany(Product::class) relationship called products on the Attribute model and the Attribute resource has a corresponding BelongsToMany::make('Products') field.

First, you need to create an AttributePolicy class that defines what the user is authorised to do with this resource. You'll probably want to add policies for view, create, update and so forth. However, you should also define the following.

• attachAnyProduct—This determines whether the "Attach Product" button appears at the top of the list of products.
• attachProduct—See blow.
• detachProduct—This determines whether the "Detach" (rubbish bin) button is available for a particular product in the list.

You'll either want to hard-code attachAnyProduct and detachProduct to return true or implement a permissions model of some kind, but whatever the case, the key to getting rid of the unwanted "edit" button is down to how you write the attachProduct policy.

public function attachProduct(User $user, Attribute $attribute, Product $product)
{
    if ($attribute->products->contains('id', $product->id)) {
        return false;
    } else {
        return $this->attachAnyProduct($user, $attribute);
    }
}

This checks to see if the relationship already exists between the current attribute and a given product; if it does, then you're not allowed to "attach" it again. This removes the unwanted "edit" button and also removes that particular product from the drop-down list when creating a new relationship (via "Attach Product").

Of course, if you also have the attributes relationship/field on the Product model/resource then you'll want to define the corresponding attachAnyAttribute, attachAttribute and detachAttribute policies in a ProductPolicy class as well.

Hopefully others will find this explanation useful.

PS> I'm using Nova 2.0.5, which I believe is the latest version.

[daniel-de-wit]

Thanks for clarifying @jeffcaulfield-morphsites, works great.

The default behaviour for attachAnyProduct is to return true.
So, it's possible to skip adding it yourself and use a somewhat simplified version of what you suggested.

public function attachProduct(User $user, Attribute $attribute, Product $product)
{
    return ! $attribute->products->contains($product);
}

[jbrooksuk]

This issue relates to an unsupported version of Nova. If you're still experiencing this in the latest version of Nova, please open a new ticket, thanks!

[YarinceP]

I struggled with a similar issue for some time. It wasn't at all obvious from the Nova documentation how to hide the "edit" button for simple pivot relationships where it isn't needed or wanted, though the solution makes sense in hindsight.

Let's assume you have an Attribute resource and a Product resource and that each manages a model of the same name. Further, let's assume that there is a belongsToMany(Product::class) relationship called products on the Attribute model and the Attribute resource has a corresponding BelongsToMany::make('Products') field.

First, you need to create an AttributePolicy class that defines what the user is authorised to do with this resource. You'll probably want to add policies for view, create, update and so forth. However, you should also define the following.

• attachAnyProduct—This determines whether the "Attach Product" button appears at the top of the list of products.
• attachProduct—See blow.
• detachProduct—This determines whether the "Detach" (rubbish bin) button is available for a particular product in the list.

You'll either want to hard-code attachAnyProduct and detachProduct to return true or implement a permissions model of some kind, but whatever the case, the key to getting rid of the unwanted "edit" button is down to how you write the attachProduct policy.

public function attachProduct(User $user, Attribute $attribute, Product $product)
{
    if ($attribute->products->contains('id', $product->id)) {
        return false;
    } else {
        return $this->attachAnyProduct($user, $attribute);
    }
}

This checks to see if the relationship already exists between the current attribute and a given product; if it does, then you're not allowed to "attach" it again. This removes the unwanted "edit" button and also removes that particular product from the drop-down list when creating a new relationship (via "Attach Product").

Of course, if you also have the attributes relationship/field on the Product model/resource then you'll want to define the corresponding attachAnyAttribute, attachAttribute and detachAttribute policies in a ProductPolicy class as well.

Hopefully others will find this explanation useful.

PS> I'm using Nova 2.0.5, which I believe is the latest version.

Thats so nice 💯 but i have a question.
How can I remove(or hide) Show Icon
of my related resource.

[YarinceP]

Running on a similar issue.

I would like to hide the Edit button (and probably the View button as well) so as to leave just the Attach and Detach functionalities.

Is there a way to do this?

Hi @cristafortuno , did you find a way to hide the view button?

[ThaDaVos]

Anyone found a way to hide the view button? This stuff is driving me crazy... I would have expected to just add a viewProduct function to the policy...

[foxx9]

I could not find an easy way either to hide the edit attached button that is useless in my use case.
What I did to only hide the "Edit attached" buttons and not the "Edit" buttons was to use that CSS :

[dusk*="-edit-attached-button"] {
    display: none;
}

[cristafortuno]

@YarinceP I think I wasn't able to remove it. Realized just now that maybe the Edit button is meant for editing any available pivot fields.