Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Fix EZP-26412: Query error when publishing content on clean eZ Platform install #1793

Merged
merged 1 commit into from
Oct 13, 2016

Conversation

emodric
Copy link
Contributor

@emodric emodric commented Oct 5, 2016

https://jira.ez.no/browse/EZP-26412

Largest content ID is 51, but ezcobj_state_link table references IDs 52, 54 and 56, which causes create content operation to crash for content which gets those IDs.

@crevillo
Copy link
Contributor

crevillo commented Oct 5, 2016

good catch! i experienced this some days ago.
+1.

@yannickroger
Copy link
Contributor

Would a cleanup script also be needed ?

@emodric
Copy link
Contributor Author

emodric commented Oct 10, 2016

No, because as soon as you start adding your own content, and go past initial 4-5 fatal errors (which only happen when you first create the content, not when you edit it again or publish it), problem corrects by itself :)

@andrerom andrerom changed the base branch from master to 6.5 October 12, 2016 09:34
@andrerom
Copy link
Contributor

@emodric could you rebase on 6.5 and create issue for this?

@emodric emodric changed the title Fix query error when publishing content on clean eZ Platform install Fix EZP-26412: Query error when publishing content on clean eZ Platform install Oct 12, 2016
…rm install

Largest content ID is 51, but `ezcobj_state_link` table references IDs 52, 54 and 56, which causes publish operation to crash for content which gets those IDs.
@emodric
Copy link
Contributor Author

emodric commented Oct 12, 2016

@andrerom Done.

@andrerom andrerom merged commit b8bacb3 into ezsystems:6.5 Oct 13, 2016
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants