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

Editing book child content failure (Bug) #46

Open
schoenid opened this issue Mar 12, 2022 · 1 comment
Open

Editing book child content failure (Bug) #46

schoenid opened this issue Mar 12, 2022 · 1 comment

Comments

@schoenid
Copy link

schoenid commented Mar 12, 2022

After saving a book child content and reopening it, wether for corrections or other changements, leads to errors in saving, if the cache was not cleared before. There are SQL errors, trying to create a page duplicate.
The result is a scrambled books structure.
The reopened book page does not show the previously defined Book outline. The field shows the entry instead of the book it was created in.
This happens primarily, if the child page is reopened and no other book pages or contents were saved between and the cache is not cleared manually.

This does not happen, if the og module is disabled, or if the book is not defined as a group content.

Backdrop 1.21.3
Modules:

  • Organic groups
  • Organic groups access control
  • Organic groups UI

In the meantime I've realized, that this happens not only for book child content, but even for every book content.
If a new book page is created, which has a defined Book outline, the Book outline setting disappears, after reopening it.
If one tries to save it then, it leads to a duplicate page and to SQL errors, so the reopened book may not be saved correctly.
If again a new book content is created and then deleted, the previuosly opened book with missing Book outline setting, has the correct settings in the Book outline, if opened again. So this must be a caching problem.

@schoenid schoenid changed the title Editing book child content failure Editing book child content failure (Bug) Mar 22, 2022
@argiepiano
Copy link
Collaborator

argiepiano commented Apr 27, 2022

Hi @schoenid. I'm working on fixing issues for OG. Would you be able to post step-by-step directions of how to reproduce the error? Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants