Am really new to this, so pardon elementary nature of the question:
I’m refactoring an existing module for a site, and want the code for it to be version-controlled, so I yanked the code out of the manager and put it in assets/modules/myModule/code.php
Then I replaced it with
$modPath = $modx->config["base_path"]."assets/modules/myModule";
include_once $modPath . "code.php";
after added error_reporting(E_ALL) I realized that it’s throwing a bunch of
Notice: Use of undefined constant SNIPPET_INTERACTIVE_MODE - assumed ’SNIPPET_INTERACTIVE_MODE’
and
Notice: Use of undefined constant SNIPPET_INSTALL_MODE
and consequently not executing the same functionality. Do I need to globalize these constants, or re-set them inside the module code prior to the include?
And/or
Is the snippet "install mode" different now that I’m putting the code in a file rather than the dB?
Dang, that was a red herring I guess. When I added E_ALL to the original module, the same undefined-constant notices appear, and the module breaks (i.e. after all the notices, it doesn’t show the CRUD functionality it did before)
