MCQ creation doesn't account for revisions
Bug #273634 reported by
Cael Kay-Jackson
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| spenglr.org |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Editing an MCQ and selecting to store a new revision overwrites the old solutions with newly edited ones. (The body content is fine as Drupal handles that).
| Changed in spenglr-org: | |
| assignee: | nobody → spenglr-dev |
| milestone: | none → first-operational-version |
| status: | New → Confirmed |
Revision history for this message
| Cael Kay-Jackson (caelj) wrote | #1 |
Revision history for this message
| Cael Kay-Jackson (caelj) wrote | #2 |
| Changed in spenglr-org: | |
| milestone: | first-operational-version → feature-complete |
| Changed in spenglr-org: | |
| assignee: | Registry Administrators (registry) → nobody |
To post a comment you must log in.
This is slightly different to how I thought it was. Control of revisions is provided by the 'administer nodes' permission which is - by default - removed for spenglr admin role.
Provided that doesn't get re-enabled, this may no longer be an issue and maybe something that can instead be handled in the spenglr code - if we decide for revision support.