Moodle

Investigate violations of questions.modifiedby/questions.createdby

Details

  • Type: Sub-task Sub-task
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Duplicate
  • Affects Version/s: 1.9.3
  • Fix Version/s: None
  • Component/s: Questions
  • Labels:
    None
  • Affected Branches:
    MOODLE_19_STABLE

Description

16, 48.1, question, modifiedby, 942, 4956
15, 54.3, question, createdby, 1095, 4904

Issue Links

This issue duplicates:
MDL-16614 createdby and modifiedby assigned to wrong people when course restored to another site Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dan Poltawski added a comment -

All the modifiedby/createdby rows are set with a userid and aren't 0/null.

However every single question stamp contains a different hostname to the moodle in question - so seems pretty conclusively backup and restore problem.

Show
Dan Poltawski added a comment - All the modifiedby/createdby rows are set with a userid and aren't 0/null. However every single question stamp contains a different hostname to the moodle in question - so seems pretty conclusively backup and restore problem.
Hide
Permalink
Tim Hunt added a comment -

I'm thinking, in this case, it is almost certainly caused by backups without userdata that contain quizzes.

Probably all we can do here is set createdby and modifiedby to 0/NULL in the backup file as we generate it.

Jamie, if you have a moment, does that sound plausible?

Show
Tim Hunt added a comment - I'm thinking, in this case, it is almost certainly caused by backups without userdata that contain quizzes. Probably all we can do here is set createdby and modifiedby to 0/NULL in the backup file as we generate it. Jamie, if you have a moment, does that sound plausible?
Hide
Permalink
Jamie Pratt added a comment -

I may have forgotten to look at the case that a backup is done without user data. The default for the createdby field and modifiedby field is NULL for questions that have been upgraded from versions of Moodle that do not have these fields so it would make sense to set these fields to NULL when backing up and possibly when restoring if restoring without user data.

Show
Jamie Pratt added a comment - I may have forgotten to look at the case that a backup is done without user data. The default for the createdby field and modifiedby field is NULL for questions that have been upgraded from versions of Moodle that do not have these fields so it would make sense to set these fields to NULL when backing up and possibly when restoring if restoring without user data.
Hide
Permalink
Tim Hunt added a comment -

Actually, someone had already spotted this problem, and I am on the way to fixing it.

Show
Tim Hunt added a comment - Actually, someone had already spotted this problem, and I am on the way to fixing it.

People

Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Moodle. Try JIRA - bug tracking software for your team.