Causes a 500 error

Comments

djdevin’s picture

djdevin
he/him
Primary language English
Location Philadelphia
commented

Yep probably call to non-object.

I'm wondering what the best solution is here...disable or delete the object referencing the content?

jlongbottom’s picture

jlongbottom commented

Yes disable sounds reasonable.

It could also do the same thing as deleting a node before you remove it from the outline. It results in a course object with no node reference.

djdevin’s picture

djdevin
he/him
Primary language English
Location Philadelphia
commented
Version: 7.x-1.0-alpha2 » 7.x-1.x-dev
Status: Active » Fixed

Committed, afd9657

It should still show up in the course outline with a broken message, and when taking the course it will just return an error message.

I don't want to disable it just in case it was required for course completion ( to prevent the user from skipping over it).

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

  • Commit 85c6f7e on 7.x-1.x, 7.x-1.x-fieldable-entities, course-object-entity-view by djdevin: 
    #1865850: fallback to broken CourseObject if class cant be instantiated
  • Commit afd9657 on 7.x-1.x, 7.x-1.x-fieldable-entities, course-object-entity-view by djdevin:
    #1865850: catch broken course objects in other places