[4.7.12 - IN_DEV] Core - front module without a controller triggers error

[Nathan Explosion]

Steps to reproduce:

1. Install a new instance of the suite
2. Put dev tools in place
3. Enable IN_DEV
4. Go to the Developer Center for 'System'
5. In Modules - Front, expand the 'Referral' row
6. Result is error below:

UnexpectedValueException: DirectoryIterator::__construct(C:\wamp64\www\dev\ips_47_dev_b/applications/core/modules/front/referral): The system cannot find the file specifi (code: 2) (0)
#0 C:\wamp64\www\dev\ips_47_dev_b\applications\core\modules\admin\applications\developer.php(290): DirectoryIterator->__construct('C:\\wamp64\\www\\d...')
#1 C:\wamp64\www\dev\ips_47_dev_b\system\Helpers\Tree\Tree.php(135): IPS\core\modules\admin\applications\_developer->IPS\core\modules\admin\applications\{closure}('referral')
#2 C:\wamp64\www\dev\ips_47_dev_b\system\Theme\Theme.php(4628) : eval()'d code(187): IPS\Helpers\Tree\_Tree->__toString()
#3 C:\wamp64\www\dev\ips_47_dev_b\system\Theme\Dev\Template.php(171): IPS\Theme\theme_core_admin_global_tabs(Array, 'modules-front', Object(IPS\Helpers\Tree\Tree), Object(IPS\Http\Url\Internal))
#4 C:\wamp64\www\dev\ips_47_dev_b\applications\core\modules\admin\applications\developer.php(150): IPS\Theme\Dev\_Template->__call('tabs', Array)
#5 C:\wamp64\www\dev\ips_47_dev_b\system\Dispatcher\Controller.php(118): IPS\core\modules\admin\applications\_developer->manage()
#6 C:\wamp64\www\dev\ips_47_dev_b\applications\core\modules\admin\applications\developer.php(69): IPS\Dispatcher\_Controller->execute('do')
#7 C:\wamp64\www\dev\ips_47_dev_b\system\Dispatcher\Dispatcher.php(153): IPS\core\modules\admin\applications\_developer->execute()
#8 C:\wamp64\www\dev\ips_47_dev_b\admin\index.php(13): IPS\_Dispatcher->run()
#9 {main}

Cause: there is no referral directory for that front module

 

[Marc]

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.

 

[Marc]

This issue was resolved in the recently released 4.7.13 release. Please update in order to fix this issue, and if you see any problem after that point, please let us know.