Read my comment in the ticket (and maybe all my posts in this topic). I won't hand out a specific list - I explained everything already.
Read my comment in the ticket (and maybe all my posts in this topic). I won't hand out a specific list - I explained everything already.
Code: Select all
$this->message = preg_replace_callback($regexp, function($matches) use($replacement) {eval('$str=' . $replacement[1]); return $str;}, $this->message);
According to your signature your forum is still under construction. If that's the case then why would you even bother with 3.0?
Just out of interest seeing as I run heavily modified 3.1 board, there's no way I can upgrade to 3.2. Is it simply a case of replacing preg_replace with something else in all files used by phpBB 3.1 to make it PHP 7 compatible. As that can done quite easy really using something like NotePad++ and doing a search and replace on mass files open up in it at onceFrank Rizzo wrote: ↑Sun May 17, 2015 10:47 am I note the bugtracker records for this problem such as here:
https://tracker.phpbb.com/browse/PHPBB3-13832
The issue is that 3.0.x and 3.1.x are using preg_replace with the /e modifier, which is deprecated in PHP7.
7.0 has already reached EOL and only gets security updates: http://php.net/supported-versions.php (as a remark: 5.6 security support runs approx. 1 month longer ) . So you can even stay on 5.6 to be on the same security level...