Oh, nice...
Try replacing at line 536 (in /core/app) the explode("\n", part with preg_split('~\s+~',
This SHOULD work. Untested...
MultiformeIngegno
-
-
- Posts: 1,337
Nao
- Dadman with a boy
-
-
- Posts: 16,082
Nothing here...
I tried enabling and disabling.
I tried entering comma-separated, and line-separated.
Never got any errors.
Can you post the data you have in that page..? Because it's probably very specific, I suppose.
Try replacing lines 535 through 539 (the ones that treat $_POST) with just this line:
Code: [Select]
Does it work now..?
I think it'll work. I think the 'bug' was related to supplying an empty block list where Wedge expected some contents. The quick fix would be to actually take the '' (two single quotes) at the end of line 535, and turn them into array() -- and voilà. But it still doesn't say why you didn't indicate any IPs in there... ;)
I tried enabling and disabling.
I tried entering comma-separated, and line-separated.
Never got any errors.
Can you post the data you have in that page..? Because it's probably very specific, I suppose.
Posted: January 31st, 2014, 03:27 PM
Try replacing lines 535 through 539 (the ones that treat $_POST) with just this line:
$_POST['reverse_proxy_ips'] = !empty($_POST['reverse_proxy_ips']) ? implode("\n", array_filter(array_map('trim', preg_split('~[\s,]+~', $_POST['reverse_proxy_ips'])))) : '';Does it work now..?
Posted: January 31st, 2014, 03:34 PM
I think it'll work. I think the 'bug' was related to supplying an empty block list where Wedge expected some contents. The quick fix would be to actually take the '' (two single quotes) at the end of line 535, and turn them into array() -- and voilà. But it still doesn't say why you didn't indicate any IPs in there... ;)