To me that is the exact opposite of what you'd want to do... Register globals is bad and should be avoided... See
http://uk2.php.net/m…ecurity.globals.php for why register globals is off by default in latter
PHP versions. Register globals being on allows variables into your application that you've not asked for that and could, potentially, have a catastrophic effect on your logic, your application and your data.
All variables coming into the
PN framework should be obtained via the approved
API call - pnVarCleanFromInput. This is a pre-requisite to creating secure and stable code hence the reason the global extraction code was removed in .750. Too many modules worked based on the assumption (mostly indvertantly) that the variable existed - which it did due to the global extraction code.
While http_get_vars will work on even aincient (relatively)
PHP installs what's the gain by doing so?
PHP 4.10 was released in December 2001 (see
http://uk2.php.net/releases.php), the PostNuke project only begain in July of the same year (see
http://news.postnuke…&file=article&sid=2). There is a time on which you have to move on and the use of
PHP's superglobals is the obvious way in which to go hence
PN .750 drops supprot for
PHP 4.06 by using
PHP's superglobals.
While you suggestions will make things work they don't necessarily improve stability, reliability, security, coding standards, memory footprint or any of the other facets that
PN uses to seperate itself from
PHP-nuke and other such
CMS's.
-Mark
--
Visit
My homepage and
Zikula themes.
