mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #36609
[Bug 1598990] Re: Cannot instantiate abstract class PluginImport
Hi Kristina,
I haven't been able to replicate it on my local dev environment. But,
one of our clients has this occurring. Unfortunately, they've disabled
the exporting to Mahara from Moodle and I can't test it there either.
They are using Moodle 2.7 + an old version of the submission plugin (I
don't know which version).
Leap2A is the default portfolio format in their Moodle (
/moodle/admin/portfolio.php?action=edit&pf=1 ) :
> Site administration > Plugins > Portfolios > Mahara ePortfolio >
Enable Leap2A portfolio support = Yes.
As it's going into the Mahara queue, the users are exporting large
pieces of data and choosing not to wait for the export.
For my testing purposes, I was going into the Mahara DB and manually setting the field to null / empty string:
* update import_queue set format = null where usr = xxx;
and
* update import_queue set format = '' where usr = xxx;
to see if null / empty string made a difference. Also, I was testing with a particular user.
Sorry I can't be much more help.
Cheers,
Ghada
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1598990
Title:
Cannot instantiate abstract class PluginImport
Status in Mahara:
In Progress
Bug description:
Mahara: 16.04.1
OS: Linux
DB: Postgres
Browser: Firefox
During the cron task run for core_import_process_queue, we are getting
this error:
PHP Fatal error: Cannot instantiate abstract class PluginImport in
/var/www/site-anu/import/lib.php on line 191
The import_queue table has a few record with format = ''.
It is trying to import leap2A data into Mahara from Moodle.
The Moodle version is 2.7 which is using an older version of the
submission plugin. But, that shouldn't matter.
I think we need 2 things:
1) Check that the format is correct in
PluginImport::class_from_format(). If it's not correct, default it to
leap.
2) When the importer is created in import_process_queue(), it should
be wrapped in the try/catch block.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1598990/+subscriptions
References