Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Content disapears when using console command gc/run #980

Open
yannkost opened this issue Jan 8, 2025 · 1 comment
Open

Content disapears when using console command gc/run #980

yannkost opened this issue Jan 8, 2025 · 1 comment
Labels
bug report status: unconfirmed A bug report that has not yet been reproduced by the maintainer(s), and more information is required bug report

Comments

@yannkost
Copy link

yannkost commented Jan 8, 2025

Bug Description

We have some content that seems to disapear from some neofields when running the garbage collector of Craft. After verification the neo blocs still exist in the database, but no corresponding neoblock_owner table row exist for these fields after it has run.
As a side note, this does not happen when resaving all neo blocks or resaving all entries through the command line.

As this is the website of an important client, we would like you to investigate the issue. We can provide the database and the composer.json which you will probably need. (And we can indicate an example entry (id=2278), where it happens.)

Steps to reproduce

Run craft gc/run in the console.

Expected behaviour

The garbage collector should run without removing the link of the neoblocks and the neobloc_owners in the database. (We did not look if other things happened, this is only what we have been able to analyse on our side.)

Neo version

4.2.23

Craft CMS version

4.13.9

What is the affected Neo field's propagation method?

userdefined {owner.translationStructure.value}

Does this issue involve templating, and if so, is eager-loading used?

This is not a templating issue

@ttempleton
Copy link
Contributor

Could you please send the Composer files and database backup from before gc/run to [email protected], and we'll have a look.

@ttempleton ttempleton added bug report status: unconfirmed A bug report that has not yet been reproduced by the maintainer(s), and more information is required and removed bug report status: new labels Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report status: unconfirmed A bug report that has not yet been reproduced by the maintainer(s), and more information is required bug report
Projects
None yet
Development

No branches or pull requests

2 participants