I think the only way to stop it is to really put the core outside the web root.
Hi, unfortunately the error still exists.
I have updated a instance with one context from MODX 2.3.6 to 2.4.0, my core is outside the web root and I have no errors.
My second instance with 3 contexts, MODX 2.4.0 on the same server and core outside I get the error:
[configcheck] check core lockdown curl err: 28
I use an easy ContextSwitch plugin, like this:
<?php
#System Events: OnHandleRequest
if ($modx->context->get('key') == 'mgr') {return;}
switch($modx->getOption('http_host')) {
case 'www.homepage1.tld:80':
case 'www.homepage1.tld':
$modx->switchContext('web2');
break;
case 'www.homepage2.tld:80':
case 'www.homepage2.tld.de':
$modx->switchContext('web3');
break;
default:
$modx->switchContext('web1');
break;
}
btw: At the moment I use PHP 5.5.28 and my dashboard has no configuration warnings. Curl is enabled on the server and the extra installer is working.
[ed. note: krischel last edited this post 11 years, 1 month ago.]
