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

Lesson infinitely updates when the Blocks CSS Plugin is used with Sensei #7598

Open
markcummins opened this issue Apr 25, 2024 · 1 comment
Labels
[Pri] Low Cosmetic issue, low impact, easy workaround [Status] Triaged Issue has been triaged [Type] Bug

Comments

@markcummins
Copy link
Contributor

Note: this seems to be the same issue as #7109.

Steps to Reproduce

  1. Install Sensei and Blocks CSS Plugins (https://wordpress.org/plugins/blocks-css/)
  2. Create a lesson and a quiz with at least one question and publish it.

What I Expected

The lesson should get published

What Happened Instead

The lesson continously tries to update. Every time it saves, it updates again.

PHP / WordPress / Sensei LMS version

PHP Version: 8.2.7
WordPress: 6.5.2
Sensei: 4.23.1
Blocks CSS: 2.6.10

Browser / OS version

Chrome: 124.0.6367.78

Screenshot / Video

sensei reloading

Context / Source

The issue seems to be in this file sensei-lms/assets/dist/blocks/quiz/index.js

@markcummins markcummins added [Status] Needs Triage Issue needs to be triaged [Type] Bug labels Apr 25, 2024
@merkushin
Copy link
Member

Reproduced with WordPress 6.5.3, Sensei LMS 4.24.0, Course 1.3.7, Blocks CSS 2.6.12.

I suppose it is related to a call to REST API to save the quiz. We probably clear out some changes from the quiz or questions that were added by Blocks CSS. The difference between content sent and received usually leads to the infinite loop.

@merkushin merkushin removed the [Status] Needs Triage Issue needs to be triaged label May 20, 2024
@donnapep donnapep added [Pri] Low Cosmetic issue, low impact, easy workaround [Status] Triaged Issue has been triaged labels May 29, 2024
@donnapep donnapep added this to the 4.24.2 milestone Jul 3, 2024
@donnapep donnapep modified the milestones: 4.24.2, 4.24.3 Aug 7, 2024
@donnapep donnapep removed this from the 4.24.3 milestone Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Pri] Low Cosmetic issue, low impact, easy workaround [Status] Triaged Issue has been triaged [Type] Bug
Projects
None yet
Development

No branches or pull requests

3 participants