Can PHP register_globals Be Disabled on an Already Established Database? Can PHP register_globals Be Disabled on an Already Established Database?
 

News:

CPG Release 1.6.27
change DB IP storage fields to accommodate IPv6 addresses
remove use of E_STRICT (PHP 8.4 deprecated)
update README to reflect new website
align code with new .com CPG website
correct deprecation in captcha

Main Menu

Can PHP register_globals Be Disabled on an Already Established Database?

Started by jeepguy_1980, July 16, 2009, 04:23:19 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Print
Go Down Pages1
User actions

jeepguy_1980

July 16, 2009, 04:23:19 AM
If I disable register_globals on my already established CPG database, should I expect any other problems?  I assume a backup prior to changing this setting is recommended.

Abbas Ali

#1
July 16, 2009, 05:47:47 AM
No problems. You can turn it off anytime.
Chief Geek at Ranium Systems

Joachim Müller

#2
July 16, 2009, 07:55:43 AM
Quote from: jeepguy_1980 on July 16, 2009, 04:23:19 AM
I assume a backup prior to changing this setting is recommended.
No backup needed for this operation. However it won't hurt to perform frequent backups anyway.

Coppermine doesn't need register_globals, it operates totally independantly of that toggle. Therefor, there will we absolutely zero impact on coppermine if you turn register_globals off. It's like swallowing a mouthfull of water when you're swimming in the ocean: absolutely no impact on the ocean. Except if you are Chuck Norris ;D
Print
Go Up Pages1
User actions