Conversation
|
Referencing the ExternalModules class directly is actually the faux pas, not simply the static call. At a glance, this one seems like an easy correction though. Since this module doesn't specify a |
includes/send_rx_functions.php
Outdated
|
|
||
| $q = ExternalModules::getSettings('send_rx', $project_id); | ||
| if (!db_num_rows($q)) { | ||
| $projSettings = $externalModule->framework->getProjectSettings($project_id); |
There was a problem hiding this comment.
| $projSettings = $externalModule->framework->getProjectSettings($project_id); | |
| $projSettings = $externalModule->getProjectSettings($project_id); |
Enabling the module fails if using ->framework:
REDCap crashed due to an unexpected PHP fatal error!
Error message: Uncaught Error: Call to a member function getProjectSettings() on null in /var/www/html/modules/send_rx_v0.0.0/includes/send_rx_functions.php:40
Removing ->framework makes it function properly. Likely that we don't have access to framework because the module does not specify a framework_version.
…bse to retrieve the project specific values.
Changing from ExternalModules call to get project settings from the framework call