Non-core contributed modules

Thanks Jonathon,

I'm not a PostgreSQL man myself. Moodle is trying to reinstall the tables, however there should be no need for this if they were already set up.

If you haven't used the ILP at all yet, which I assume is the case, then deleting the tables from the database manually and rerunning the installation should resolve this. If you can do this and then let me know if it recurs at all that would be useful.

I'm going to be doing some more detailed work on the ILP over the next week, so I'll test for this on MySQL as well and see if it's a general error.

Yours
James

Hello James,

I deleted all the tables, but forgot I had added a concern and a target to a test course.

When I ran Moodle/admin no errors were displayed and the ilp table creation appeared to proceed successfully.

I subsequently opened the course and deleted the activities for Concern and target, both of which resulted in a message that the instance could not be found and had been deleted.

So far so good.

I then added a concern only to find that in the activity list concern was listed twice - both options appear to successfully create a concern.

Then I tried adding a target - unfortunately all attempts to add a target failed with the message

ADD INSTANCE CALLED
Could not add a new instance of ilptarget.

Its getting late now and my time is committed for tomorrow, so after the bank holiday I think I will have to roll back to the last virtual machine which was saved just before I installed ILP and then try installing ILP afresh.

I'll let you know how I get on.

Have a good weekend.

Johnathan

Thanks Johnathan,

I have tomorrow penciled in to do some work the ilp modules, in particular bringing the CVS version up to scratch with the previous version. I'll try and put your scenario through its paces and see if I can resolve it.

Have a good weekend,
Yours James

Hello James,

I updated my ILP files from CVS today (2nd June 2008) and ran moodle/admin.

The admin did not complete, generating three error messages all stating that the table mdl_ilptarget_posts does not exist. Clicking on continue resulted in a repeat set of error messages as the same routines presumably tried to run, so I can no longer open my Moodle test site. To try to resolve this I deleted all the tables with ILP in the name and re-ran the admin, but this just resulted in the same set of error messages.

I closed down the virtual machine (I'll refer to this as VM_current) and opened an earlier virtual machine (lets call this one VM_old), which predated my attempts to install ILP. The moodle admin call completed without error on VM_old. However comparing my notes on VM_current with my installation of ILP on VM_old, I am sure that VM_current had a "Concern" module listing in Site Administration / Modules / Activities but in this new installation (VM_old) I have only the Target Activity Module listing.

I took a note of the ilp tables that exist in the VM_old installation of ILP and then closed it down. I then re-enstated VM_current. When I lookded at the ILP tables listing in VM_current I was surprised to find out there were NO ilp tables at all!

I have no idea why it is that the installation routine is failing to create them.

If you have any ideas, they would be most appreciated, as It would save me a lot of work if I could avoid having to roll back to VM_old.

Kind regards

Johnathan

Hello James,

Sometimes it pays to sleep on things!

I have today deleted the two ILP module folders and the two module folders, this enabled me to successfully restart moodle.
I then used the Moodle admin to delete the ILP blocks and folders that it listed (shown then as "missing on disk")
I also checked that no courses contained any ILP blocks or modules.

When I then re-enstated the files obtained yesterday from CVS they installed correctly, all tables were recreated and the blocks and activites listed in Moodle.

Also I can see now that the Concern module is now listed as the Report module.

So it looks like the current files install OK.

I have no idea why the original problem occurred, but at least I am now up and running.

Thanks for your help with this

Johnathan