Is there a special syntax for using MIGX Management in MODX 3? Using MIGX 3.0.0-beta1.
I generated everything with MIGX, although when I generate the schema, a bunch of default MODX classes get addess as well - AccessActiondom, AccessCategory etc.
Table name is modx_emails_datoteke as in the schema.
When setting Package to emails and Classname to Datoteke in the MIGX config editor, and going to Columns → select db fields, it spits out this error:
Path specified for package emails is not a valid or accessible directory: /www/core/components/emails/model/
Could not load class: Datoteke from mysql.datoteke
What could be causing this? I’ve used MIGX for custom tables in MODX 3 before, haven’t had this issue yet…
Unfortunately, it doesn’t fix the issue. Could not load class: Emails\Model\Datoteke from mysql. emails\model\datoteke
File structure generates like this:
emails
schema
emails.mysql.schema.xml
src
Model
mysql
Datoteke.php
Datoteke.php
metadata.mysql.php
bootstrap.php
However, I’ve noticed this error - if it is connected to the problem. (ERROR @ /www/core/components/migx/model/migx/migx.class.php : 884) PHP warning: Undefined variable $configpath
If you are using $modx->addPackage() in some custom code, remove the line. Your package gets added in the file “core/components/emails/bootstrap.php”.
I’ve just done a fresh MIGX install and some weird stuff starter happening …
Unable to load processor for action "mgr/migxdb/getList", it does not exist as an autoloadable class that extends \MODX\Revolution\Processors\Processor, and also not as a file in "/www/core/components/migx/processors/mgr/migxdb/getList.class.php
I’l dive into this a bit. Seems like an issue on my side, but not sure what could cause this, since it’s a fresh install.
I completely wiped MIGX from the system, installed the package from the provider, and then “updated” it with 3.0.0-beta1 (will update to 3.0.1 later). After that, everything worked like a charm.