strapi-plugin-navigation: Strapi V5: Can't select entities in an empty menu

Hello,

I am migrating to Strapi 5. Having issues with the navigation plugin. After the migration I am not able to add any Entities to my nav items.

First I emptied tables navigations, navigations_items, navigations_items_audience_lnk, navigations_items_master_lnk, navigations_items_parent_lnk, navigations_items_related_mph from the database, since I got errors when deleting from Strapi. I also deleted the plugin_navigation_config row in strapi_core_store_settings table.

I have several locales and all the menus are ampty now, but I am still not able to add any entities to the menu.

Image

strapi: 5.10.3 strapi-plugin-navigation: 3.0.8

Any ideas?

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 3
  • Comments: 21 (14 by maintainers)

Commits related to this issue

Most upvoted comments

The issue is very tricky and not yet found the root cause, we’re working on it as a top priority to deliver the fix. Be patient please 😃

@sven-ra @SalahAdDin @bureauberg @vassaf @datsenkoboos

we’ve released the 3.0.9-beta.1 version with this fix. Kindly make a try and let us know if the reported issue was solved.

Hello, Running Strapi v5.10.2. and v.5.10.3 2 with v3.0.7 and v.3.08 plugin on my local with node v20.18.2. I have the same issue with Strapi v5.10.3, and Strapi v5.10.2 with v3.0.7 and v3.0.8. However, when I ran Strapi v5.10.2 with v3.0.7 without using i18n ( I didn’t use multilingual at first), no issue with the navigation plugin occurred. After activating i18n in Strapi v5.10.2 with v.3.0.7, multiple issues occurred, like after deleting the navigation, it still showed up in the plugin dropdown. Also, after clicking the ‘Manage’ button > All navigations, the panel was empty. When selecting the ‘id’ field and clicking ‘delete’, it showed ‘2 entries’.

After uninstalling, new build and reinstalling the plugin, I can’t select entities anymore in an empty, new menu. This occurs both in Strapi v5.10.2. and v.5.10.3 2 running v3.0.7 and v.3.08 of the plugin.

Could it be that the plugin (or Strapi) has some leftovers in the database, and therefore, the plugin gets confused, thinking that all entities have already been mapped and are in use by the plugin?

Update March 4th: I did another test with a new Strapi instance with a new, local Sqlite database but with the very same Strapi code base (e.g. schema). I first activated i18n in Strapi v5.10.2 on node v20.18.2 without installing the nav plugin. After configuring the single & collection types, I installed v3.0.7 of the plugin, after which the nav plugin works perfectly fine. Feels to me like it is highly recommended to first configure i18n and only then install & configure the nav plugin. Maybe that is common practice but I didn’t come across it in the docs. Hope this helps a bit! I can do more tests, if needed.

I’m going to check what has changed between the versions as the fetch mechanism wasn’t touched - just the bump of Strapi version - what might have an impact.

Downgrading to v3.0.7 resolves the issue

I have the same issue in the v3.0.7 version!

There is a closed issue handling it.

@CodeVoyager , @cyp3rius, I will continue the track of my closed issue here.

And yeah, I have published posts:

Image

So, about the endpoint, we get:

Image

There is no such http://localhost:1337/navigation/content-type-items/aspi::posts.posts?locale=en fetch in the network.

same issue with strapi v5.10.3 and navigation v3.0.8

Downgrading to v3.0.7 resolves the issue

Can confirm downgrading to v3.0.7 fixes the issue

Downgrading to v3.0.7 resolves the issue