I found out a few days ago about the auto upgrader feature via the client area.

So I thought I give it a go

I bosched in my FTP details, hit the big pink button and in less than 10 minutes, i went from 3.3.4 (i think) to 3.4.3, sweet.

It would have taken me longer to upload the files.

n1, give the people involved a payrise they deserve it.

I would say to anyone, give it a go, it's great - make sure you backup first, like you should anyway.

brill - cheers

Yeah it works great and much quicker than manually uploading files by ftp.

However not made clear is you need to delete config_global.php.dist and media_path.php.dist. You also need to chmod your config_global.php file back to 444 as the upgrader will change it to 777. Also if you replaced logo.png on the default / master skin with your own logo this will be overwritten and you'll need to replace it.

Those couple of minor things aside, I agree, brilliant :smile:

Yeah it works great and much quicker than manually uploading files by ftp.

However not made clear is you need to delete config_global.php.dist and media_path.php.dist. You also need to chmod your config_global.php file back to 444 as the upgrader will change it to 777. Also if you replaced logo.png on the default / master skin with your own logo this will be overwritten and you'll need to replace it.

Those couple of minor things aside, I agree, brilliant :smile:

Thanks you the extra info m8, I have re-chmod my config_global.php file and deleted the config_global.php.dist file, I don't think I have an media_path.php.dist file as I do not have IP.Content, do I? I have board and calendar installed.

this information should be put on the instructions and when doing the upgrade itself, as it is important.

Cheers

Glad you like it :)

Yeah it works great and much quicker than manually uploading files by ftp.

However not made clear is you need to delete config_global.php.dist and media_path.php.dist. You also need to chmod your config_global.php file back to 444 as the upgrader will change it to 777. Also if you replaced logo.png on the default / master skin with your own logo this will be overwritten and you'll need to replace it.

Those couple of minor things aside, I agree, brilliant :smile:

You don't need to do any of those things, except the logo if you changed it that way - but that's not the proper way to change a logo - if you use the logo changer in the ACP, the auto-upgrader won't override it.

Glad you like it :smile:

You don't need to do any of those things, except the logo if you changed it that way - but that's not the proper way to change a logo - if you use the logo changer in the ACP, the auto-upgrader won't override it.

leaving config_global.php as chmod 777 isn't good idea

My logo stayed the same after the upgrade, like you say if you use the logo changer it's not a problem.

Glad you like it :smile:

You don't need to do any of those things, except the logo if you changed it that way - but that's not the proper way to change a logo - if you use the logo changer in the ACP, the auto-upgrader won't override it.

Incorrect - config_global.php needs its permissions manually changing to 444. Leaving the 2 .dist files on-line won't do any harm.

Incorrect - config_global.php needs its permissions manually changing to 444. Leaving the 2 .dist files on-line won't do any harm.

I'm quite aware of what permissions the files in IPB require, thanks :)

0444 (not 444, it's an octal number) could be considered necessary if there were other users on the server who could access your home directory - but if that were the case, they could just write a web-accessible script to your /cache directory to read and manipulate the conf_global.php file.

Typically, one secures their server against such attacks through use of open_basedir.

If you wanted to change it, you could of course do so, but it's unnecessary and will prevent the auto-upgrader working when you go to upgrade again. If you were going to do that though, 0444 is still more permission than you strictly need - you'd only need read permission for whatever user PHP is running as.

(By the way, it's conf_global.php, not config_global.php)

Leaving config_global.php at 0444 hasn't prevented the upgrader working the last 2 times I have used it. All I know is the upgrader changes it. Then when you go into the ACP security centre there's a warning for "Make "conf_global.php" Un-writable". I change back to 0444 because running the tool now from the security centre changes it to this.