Bug Report? I need Help.

[egonkab]

Hello, I Have 2 Errors.

A runtime error occurs when using the DetachAction within a Relation Manager:
Call to a member function detach() on null {"userId":1,"exception":"[object] (Error(code: 0): Call to a member function detach() on null at /app/vendor/filament/actions/src/DetachAction.php:50)

When starting Laravel Octane or running php artisan route:cache, the following exception is thrown:
Unable to prepare route [temp/products/{product}] for serialization. Another route has already been assigned name [products.show]. {"exception":"[object] (LogicException(code: 0): Unable to prepare route [temp/products/{product}] for serialization. Another route has already been assigned name [products.show]. at /app/vendor/laravel/framework/src/Illuminate/Routing/AbstractRouteCollection.php:248)

laravel-2026-01-01 (3).log

[egonkab]

laravel-2026-01-01 (4).log

[Cybrarist]

here i can see that there's an error in exchange key api, if you have specified a currency in your profile, you need to set the api key in the code.
otherwise, remove the currency from the profile and that error should be fixed.

[Cybrarist]

may i know what were you trying to do when you got the first error.

the second is just a warning, you can ignore it.

[egonkab]

Hello everyone,

Sorry for my bad English. Thank you for the quick help!

I'm encountering the following error:

Error #1:
Unable to prepare route [temp/products/{product}] for serialization. Another route has already been assigned name [products.show]. {"exception":"[object] (LogicException(code: 0): Unable to prepare route [temp/products/{product}] for serialization. Another route has already been assigned name [products.show]. at /app/vendor/laravel/framework/src/Illuminate/Routing/AbstractRouteCollection.php:248)

The same error appears in the Portainer logs of the container.
portainer_db_log.txt.txt

What I understand:
It seems there are two routes defined with the same name products.show - one at products/{product} and another at temp/products/{product}. Laravel cannot handle duplicate route names during serialization.

Error #2:
Call to a member function detach() on null {"userId":1,"exception":"[object] (Error(code: 0): Call to a member function detach() on null at /app/vendor/filament/actions/src/DetachAction.php:50)

The delete operation fails - entry remains in database
This error occurs consistently when I follow this workflow:

How can I fix this so that I can delete/remove entries again?

[Cybrarist]

ah yea I need to remove that button really.

anyway, you don't delete a link, it's a design decision I made for couple of reasons.

the correct way for the link to be removed is to remove it from the product that its attached to, then there's a job that runs every day that removes orphan links.

the reason for this decision are:
1- another use might add the same link after you remove, so it's kept so the other user can still have a history.
2- in case you remove it and other users still have it, especially as admin, it will create issues for other users.
3- in case you delete a link from product by mistake let's say, and that link has no other products, then you will lose all data crawled and history ( similar to case 1 ).

but anyway , the app should be working fine.

[mrizkyn]

The issues are unrelated and have different causes.

The first error is due to duplicate route names. Two routes are registered with the same name products.show, which Laravel cannot serialize when running Octane or route:cache. Route names must be unique, otherwise Laravel throws this exception.

The second error is by design. The DetachAction fails because links are not meant to be deleted directly. Links should only be removed from the product they are attached to, and a background job later cleans up unused links. The delete button is therefore invalid and should be removed.