Unable to publish Collection Type entries with complex schema due to non-existent database column #20284
Labels
issue: bug
Issue reporting a bug
severity: medium
If it breaks the basic use of the product but can be worked around
source: core:content-manager
Source is core/content-manager package
source: core:database
Source is core/database package
status: pending reproduction
Waiting for free time to reproduce the issue, or more information
version: 4
Issue related to v4
Required System Information
Describe the Bug
As a user, I cannot publish any content on this collection type due to Strapi's query engine generating a query that targets a nonexistent column name in table
files
Steps to Reproduce
Expected Behavior
As a user, I should be able to publish this content
Screenshots
On the admin panel UI, there's only the alert box saying
Internal Server Error
. But on the API server side, there are more useful information:And this is the current schema for table
files
:Right now, I'm still trying to figure out a workaround for this issue, but it is literally breaking the app on the user's side if they can't publish contents.
Note: I saw that #20188 has encountered a similar issue with
countDraftRelations
, except that it appears to be due to insufficient permissions. In this case, the generated database query is incorrect in the first place.The text was updated successfully, but these errors were encountered: