After upgrade Strapi v4.26 → v5.33: existing entries show in Dashboard, but Content Manager is empty + /api/campaign returns 404 #25051
Replies: 4 comments
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @amit-scanova, I actually ran in to the same problem because the migration did not complete successfully. For some reason it did not add the documentId column to some tables. You could see if it's the same problem for you. What helped me was to just put my database backup back and running the migration again. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @boazpoolman, could you please explain a bit more? I am unable to do this. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @amit-scanova, You can use a database inspection tool like TablePlus (has a free version too) to see your database structure and content. If you inspect your database post-migration you can see if all the relevant tables have a document_id column. If not, that's a clear sign that the migration did not complete successfully and can explain the issues you're having. Even if you do have the document_id column in your tables, you can still re-try the migration by reverting your database to it's pre-migration state, aka your database backup. If you rerun the migrations and they complete successfully in one go, everything should be fine. If you need professional help with your migration we (from PluginPal) could help you with that. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Strapi community,
I upgraded my project from Strapi v4.26.x to v5.33.x and since the upgrade I’m not able to view existing data in the Content Manager.
What I’m seeing
In the Admin Dashboard, I can still see the data/counts (so it looks like the DB still has the entries).
But in Content Manager, the collection type(s) (example: Campaign) show no entries / no data.
I also don’t see the expected UI options like:
Open Campaign Page
click PUBLISHED
switch locale (if needed)
These options were suggested as troubleshooting steps, but they’re not available / not helping in my Strapi v5 admin.
API check
When I try to fetch data via REST, I’m getting a 404:
curl -i 'http://localhost:1337/api/campaign'
Response:
HTTP/1.1 404 Not Found
...
Project context
Host: Ubuntu server (running Strapi under /var/www/strapi)
Strapi runs on http://localhost:1337
I’m using i18n + Draft/Publish on content types (example schema has "draftAndPublish": true and localized fields via pluginOptions.i18n).
Expected behavior
I should be able to see and manage existing entries in Content Manager after the v5 upgrade.
REST API endpoints for these content types should not return 404 (or at least should return data/errors that explain what’s missing).
Ask
Has anyone faced this after upgrading to Strapi v5?
What should I check to make existing v4 data appear correctly in v5 Content Manager (permissions, i18n locale handling, required migration steps, API route changes, etc.)?
If needed, I can share:
content-type schema(s)
admin screenshots
logs around Content Manager requests / API calls
Beta Was this translation helpful? Give feedback.
All reactions