In my thinking, I would keep the '&' blocked in the core, and then in the plugin, for php5 versions unblock that character and make any other changes needed for allowing html entities in page names. That way if you install the plugin you get the functionality you want (assuming php5), otherwise it is blocked (by default).
Cheers, Dan On Fri, Oct 23, 2009 at 1:01 PM, Hans <[email protected]> wrote: > > The problem is to adapt for backwards compatability with pre php5 versions. > > One way to do that could be to abort with an invalid page name message > whenever an input in a page name field is made which includes a html > entity code, and the php version is pre 5. > > I tried to find a way to do that, but failed. I don't know where to > check the input from the page name field. The BOLTsavepage() function > seeemed a good place top check the $target name, but there it is > already converted to url. The I got lost trying to find the way input > is processed. > > ~Hans > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
