Plugin wrong link with glpi 11 update

[SaillyMaxence]

Code of Conduct

• I agree to follow this project's Code of Conduct

Is there an existing issue for this?

• I have searched the existing issues

GLPI Version

11.0.1

Plugin version

1.22.1

Bug description

In the GLPI left menu, under Setup → Fields, the link points to .../var/glpi/marketplace/fields/front/container.php → leads to error / 404.

But from Plugins → Fields → Configuration, it properly points to .../plugins/fields/front/container.php → the correct page loads.

We are running GLPI in Docker environment.

We tried uninstalling and reinstalling the plugin, without success.

Relevant log output

Page URL

No response

Steps To reproduce

Upgrade GLPI from a prior version (e.g. v10) to v11.

Install (or keep) the Fields plugin.

In the GLPI menu, go to Setup → Fields.

Click the link.

Observe the error (or wrong path).

Expected behavior

The setup menu link should point to plugins/fields/front/container.php (or the correct plugin path) so that the configuration page loads correctly.

Actual behavior

The setup menu link points to var/glpi/marketplace/fields/front/container.php (wrong path) and fails to load properly.

Your GLPI setup information

No response

Anything else?

No response

[stonebuzz]

Hi @SaillyMaxence

can you try this -> #1040

[SaillyMaxence]

Hello,

I have to update the plugin or make modification manually ?

[SaillyMaxence]

i made modification but same error

[SaillyMaxence]

Hello,

Its ok, we had cache on app, in private navigation, the link is good,

Thanks u

[SaillyMaxence]

Thank you for your response. The first part is now working correctly.

However, we have discovered a new issue. When we set up additional fields related to tickets, it becomes impossible to save — clicking the Save button does nothing.

If we disable the additional field itself (not just make it non-mandatory), the ticket form works again. But as soon as we re-enable the field, it stops working.

It seems like there might be a missing or broken function call causing this behavior.

[stonebuzz]

Please open new issue