Upgrade from 4.1 to 4.3

[cranko]

Hello guys

I worked had last couple of month to setup my listing directory in adaptation of my listing business version. So i change several things in the code because i dont need list prices or other things, many things almost i cant remember now.

But now because a vulneravility i need to upgrade to the last version. This will screwup all my modifications again and i will need to work in the code repeat all the things i need to change.

This will take a lot of time again, code, bugs about foraing accenss, etc...

My question its ... How i can upgrade it just to fix the vulneravility and only to prevent it?

I dont want upload all the new code to start again over and over, just i need to fix the vulneravility thats all

Im not a programer and its to hard loss all my old code

Thank you

[Lhotch]

For starters, you should be documenting all of your code changes so they can be redone if needbe. For example, do YOU backup your site? Whats happens if your host lost a disk with your data on it? They say they have a backup right? If i had a dollar for everyone who lost a site thinking their host had them covered I would be a rich man. If its that important to you, document it and back it up.

Ok, off my soap box now. If you look at this post....

Important V4.0.2 is now released - Please Upgrade ASAP

It looks like at a bare minimum you should upgrade the includes/classes/kernel/Category.php file.

[cranko]

Thanks for you advices.

So if i undertand well, with that file

includes/classes/kernel/Category.php

I just fix the vulneravility problem?

If that is correct will be great and easy for me.

Anyway i will try to upgrade the whole site in the future. I have backup but i dont have relation of my old changes so will take lot of time to review the whole code again.

Thank you

[juven14]

I know the feeling, I always hate upgrades, but it is just the nature of using 3rd party scripts. A few things you can do to reduce the work when upgrades do come down the pipe:

Move as many of your modifications to modules, will save you loads of time. There are a few articles/posts that walk you through the module system.

Document your code 2 ways. When you make a change, add comments around it so that you can easily spot it when viewing the source. Something like:

PHP Code:

//added 5-8-2008 adds new ability juven14
$something = new_feature_i_added();
$class_tpl->assign('something', $something);
//end added 5-8-2008 adds new ability juven14 


Additionally, keep a text file handy and keep it up to date:
category.php | added new ability | 5-8-2008 | v4.01 | lines 200-203 | developer's name

Now, you can quickly go through the code and make you updates based on the text file. In the event that you skipped one or forgot to include it in your list, commenting it in the source will save you during a file compare.

Use a file compare application. I used to use ultracompare, but now use the one built into Zend Studio. When you compare the files, these comments can be searched for, they will also show up as a difference that is easily spotted.

Don't forget to comment your templates as well.

{*added 5-8-2008 adds new ability juven14*}
<br /> Some none default html/php/smarty code here
{*end added 5-8-2008 adds new ability juven14*}

By documenting your changes well, keeping backups of your work, using tools like file compare apps, and making your changes as modules, you will definitely not have to work as hard to upgrade your site. I've made major changes over time to several apps, and just by using ultracompare I was able to update the code in minutes. Get a system together and stick to it, as for upgrades this problem will not go away.

If anyone has other suggestions, please feel free to add them, I'm always looking for ways to improve my own processes.

[juven14]

Originally Posted by cranko

Thanks for you advices.

So if i undertand well, with that file

includes/classes/kernel/Category.php

I just fix the vulneravility problem?

If that is correct will be great and easy for me.

Anyway i will try to upgrade the whole site in the future. I have backup but i dont have relation of my old changes so will take lot of time to review the whole code again.

Thank you

This will address the known issue with v4.0.2 and Category.php, however, it will not address the additional issues identified during a recent audit of the system which are fixed in v4.0.3 along with some bug fixes.

[cranko]

Thank you guys for you awesome advices i always receive here

Cranko