Well I have always recommended that all depreciated vars be replaced as a matter of course when editing any page, I`m surprised that osC still includes them when they've been so long depreciated.
Why wait till you have to fix when you can prevent that now.
How many add-ons are still using depreciated because of this attitude? Its just creating un-neccessary issues?
Latest News: (loading..)
21 replies to this topic
#21
Posted 18 April 2012 - 09:44 AM
Sam
Remember, What you think I ment may not be what I thought I ment when I said it.
Contributions:
Auto Backup your Database, Easy way
Multi Images with Fancy Pop-ups, Easy way
Products in columns with multi buy etc etc
Disable any Category or Product, Easy way
Secure & Improve your account pages et al.
Remember, What you think I ment may not be what I thought I ment when I said it.
Contributions:
Auto Backup your Database, Easy way
Multi Images with Fancy Pop-ups, Easy way
Products in columns with multi buy etc etc
Disable any Category or Product, Easy way
Secure & Improve your account pages et al.
#22
Posted 18 April 2012 - 11:21 AM
While I do agree with coding for the latest stable release of any code, I am no PHP wizard and when modifying an existing program, like osC, I code to match what is already there.
If I am modifying $bananas I use $bananas, not $apples.
Thanks for the heads up on the depreciated code, I just got an email from my host stating
I may do a simple S&R, though this cart is not on my servers.
If I am modifying $bananas I use $bananas, not $apples.
Thanks for the heads up on the depreciated code, I just got an email from my host stating
Quote
we will be removing PHP 4 and older versions of PHP 5, replacing them with the newer, more stable, and more secure PHP 5.3.10.
I may do a simple S&R, though this cart is not on my servers.
Edited by nobodyfamous, 18 April 2012 - 11:23 AM.
