The standard <http://php.net/manual/en/migration55.deprecated.php>action seem to be to use preg_replace_callback <http://php.net/manual/en/function.preg-replace-callback.php> instead.
Simon On 5 June 2013 05:59, Petko Yotov <5...@5ko.fr> wrote: > This is bad, bad news. > > The PmWiki Markup engine relies heavily on the /e modifier. Even if we > manage to fix the core, this will break almost any and all recipes. > > Unless we find a way to automatically convert the replacement PHP code > into an anonymous function. How much more secure it will be?!? > > I'd like to read some ideas and suggestions from the community. > > Petko > > > > Kevin Clevenger writes: > >> Is there any timeline or ETA for updating PmWiki to accommodate the >> recent depreciation of preg_replace /e in php 5.5? >> >> Seeing a ton of these since upgrading to php 5.5: >> Deprecated: preg_replace(): The /e modifier is deprecated, use >> preg_replace_callback instead in /home/common/Sites/pmwiki/**pmwiki.php >> on line ... >> https://wiki.php.net/rfc/**remove_preg_replace_eval_**modifier<https://wiki.php.net/rfc/remove_preg_replace_eval_modifier> >> >> > ______________________________**_________________ > pmwiki-devel mailing list > pmwiki-devel@pmichaud.com > http://www.pmichaud.com/**mailman/listinfo/pmwiki-devel<http://www.pmichaud.com/mailman/listinfo/pmwiki-devel> > -- ____ http://kiwiwiki.co.nz
_______________________________________________ pmwiki-devel mailing list pmwiki-devel@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-devel