-
Bug
-
Resolution: Fixed
-
Critical
-
2.5
-
MOODLE_25_STABLE
-
MOODLE_25_STABLE
-
wip-
MDL-40136-m26 -
-
if you move your Moodle site files (dirroot) to a different location this causes the site to fail like this:
Coding error detected, it must be fixed by a programmer: Request for an unknown renderer class block_navigation_renderer
|
line 230 of \lib\outputfactories.php: coding_exception thrown
|
line 1384 of \lib\outputlib.php: call to standard_renderer_factory->get_renderer()
|
line 754 of \lib\pagelib.php: call to theme_config->get_renderer()
|
line 208 of \blocks\navigation\block_navigation.php: call to moodle_page->get_renderer()
|
line 292 of \blocks\moodleblock.class.php: call to block_navigation->get_content()
|
line 238 of \blocks\moodleblock.class.php: call to block_base->formatted_contents()
|
line 951 of \lib\blocklib.php: call to block_base->get_content_for_output()
|
line 1003 of \lib\blocklib.php: call to block_manager->create_block_contents()
|
line 353 of \lib\blocklib.php: call to block_manager->ensure_content_created()
|
line 3 of \theme\base\layout\frontpage.php: call to block_manager->region_has_content()
|
line 847 of \lib\outputrenderers.php: call to include()
|
line 777 of \lib\outputrenderers.php: call to core_renderer->render_page_layout()
|
line 99 of \index.php: call to core_renderer->header()
|
this is because the cache returns the old dirroot instead of the correct new one.
It would be nice if we could do some form of sanity check on the cache to see if $CFG->dirroot (which is correct after directory change) matches whatever is coming from the cache.
This is also an issue as some deployment software (like MS Web Matrix) allow a user to package Moodle on their local system and then deploy to an external webserver taking both moodleweb and moodledata across to the external system.