General developer forum

I have not tried this in the specific context you are working with; however, I have generally tended to ignore modinfo. My assumption is that it is calculated and populated as it needs to be. It is a strange field - so strange that I decided just to ignore it. Have you experienced a particular error if you just add the course data and then add the questionnaire data?

It's a serialized array. Grab it from the DB and do $array = unserialize($string). Fiddle with the array and use serialize to prepare it to be stored again. Cheers!

As Marting L says, it is a serialised array.

I managed to corrupt that field in my test database, and the following sequence fixed it up:

1. Switch to edit mode.
2. Click the edit button next to the broken module.
3. Don't change anything, just click "Save changes".

Presumably it is somthing in stage 3 that recomputes what the modinfo field should be, and saves it back to the database. If you could work out what function call that is, you could write a scritp that you run after loading all the data into your database, that calls that function for every module on every course you have just loaded.

If you work out how to do that, it would be really great if you could post what you find back here. We will be investigating automatically loading courses into the database in the new year, and we would love to learn from you.

Thank you very much,

Tim.