Needing to upgrade but have no experience!

[KEA]

We are using version 1.1.6 on our web site - www.sawmillandtimberforum.com

I need to upgrade to the latest version but when I try I get the message telling me not to do this unless I know what im doing. (I Dont!)  When it test itself on the install below is the message I get.  Everything seems fine but step #9.  Any input to assist in this is greatly appreciated. 

Our goal was it install the upgrade so we can install the Meta Tags Mod but it is only compatablie with newer versoins than what I have so we are needing to upgrade.

Thanks

Installing this package will perform the following actions:  Type Action Description
1. Execute Modification ./index.php Test successful
2. Execute Modification ./SSI.php Test successful
3. Execute Modification ./Sources/Help.php Test successful
4. Execute Modification ./Sources/PackageGet.php Test successful
5. Execute Modification ./Sources/Packages.php Test successful
6. Execute Modification ./Sources/QueryString.php Test successful
7. Execute Modification ./Sources/Subs-Graphics.php Test successful
8. Execute Modification ./Sources/Themes.php Test successful
9. Execute Modification ./Themes/default/Packages.template.php Test failed
10. Extract File ./Packages/.htaccess

[Illori]

take a look at Manual Installation of Mods and apply it to the upgrade package instead of a normal mod.

[KEA]

One thing at a time.........PLEASE

How do I upgrade the version from 1.1.6 to what ever is current now?  When it runs the test item #9 fails.  I have no clue why and no clue what all the code means in the link you gave me. 

I have to get the version upgraded before I can even think about anything else. 

[Antechinus]

Our goal was it install the upgrade so we can install the Meta Tags Mod but it is only compatablie with newer versoins than what I have so we are needing to upgrade.

No offense, but that has to be one of the flimsiest reasons for upgrading that I've ever heard. The best reason is simple: security. That is why we bother to make patches in the first place. You're lucky you haven't been hacked.

I'm not sure what you hope to gain from the Meta Tags mod. If you're thinking it will improve search engine rankings then it most likely wont.

9. Execute Modification ./Themes/default/Packages.template.php Test failed

Attach the file here and somene can take a look at it.

[KEA]

No offense taken.  How do I even find the file?  Like I said, I have no expereince messing with this stuff. 

[KEA]

I THINK this is it?

[Antechinus]

This should work. Put your forum in maintenance mode. Install the patch regardless of warnings (it will still fail on that particular file but the rest will be fine). Then, use FTP to load the attached file back into the Themes/default folder.

[KEA]

How to I put it in Maintenance Mode?

[Illori]

admin -> server settings

[KEA]

Thanks.  Got the upgrade done but looks like I have to start a new topic for the multiple upgrades its telling me I need.  Hit a road block on this message.

HAVE NO CLUE HOW TO DO THIS!

Some of the files the package manager needs to modify are not writable. This needs to be changed by logging into FTP and using it to chmod or create the files and folders. Your FTP information may be temporarily cached for proper operation of the package manager.
FTP Server: Port:   
Username:   
Password:   
Local path to SMF:   

[Illori]

your host would be able to tell you that information

[cicka]

Thanks.  Got the upgrade done but looks like I have to start a new topic for the multiple upgrades its telling me I need.  Hit a road block on this message.

HAVE NO CLUE HOW TO DO THIS!

Some of the files the package manager needs to modify are not writable. This needs to be changed by logging into FTP and using it to chmod or create the files and folders. Your FTP information may be temporarily cached for proper operation of the package manager.
FTP Server: Port:   
Username:   
Password:   
Local path to SMF:   

You will need to chmodd the Packages folder. Also create a temp folder inside the packages folder and chmodd that too.

Or enter the ftp information at the Package manager and it will chmodd automatically for you.

You can try to do a little search in the forums as well as this kind of things has been discussed many of times before

[Illori]

there is usually a different error message when you only need to create a temp folder, it may need to chmod some other files as well.

[cicka]

there is usually a different error message when you only need to create a temp folder, it may need to chmod some other files as well.

Well, it is the same thing. At least that is what has happened to me. When the packages directory was not writable I got the same thing as the OP. Entering the ftp info did not solve it for me. After reading through the forums I came across several threads with the temp folder fix suggestion and that did the trick.

[KEA]

I dont know what a CHMOD is or how to do it.  When trying to install the upgrades this is the message I get.

1.0.19 / 1.1.11 update

Installing this package will perform the following actions:  Type Action Description
1. Execute Modification ./index.php Test successful
2. Execute Modification ./Sources/BoardIndex.php Test successful
3. Execute Modification ./Sources/Display.php Test successful
4. Execute Modification ./Sources/Load.php Test successful
5. Execute Modification ./Sources/ManageAttachments.php Test successful
6. Execute Modification ./Sources/ManageCalendar.php Test successful
7. Execute Modification ./Sources/ManageMembers.php Test successful
8. Execute Modification ./Sources/ManagePermissions.php Test successful
9. Execute Modification ./Sources/ManageSmileys.php Test successful
10. Execute Modification ./Sources/Modlog.php Test successful
11. Execute Modification ./Sources/PackageGet.php Test successful
12. Execute Modification ./Sources/Packages.php Test successful
13. Execute Modification ./Sources/Poll.php Test successful
14. Execute Modification ./Sources/Post.php Test successful
15. Execute Modification ./Sources/Profile.php Test successful
16. Execute Modification ./Sources/SplitTopics.php Test successful
17. Execute Modification ./Sources/Subs.php Test failed
18. Execute Modification ./Sources/Subs-Auth.php Test successful
19. Execute Modification ./Sources/Subs-Boards.php Test successful
20. Execute Modification ./Sources/Subs-Graphics.php Test successful
21. Execute Modification ./Sources/Themes.php Test successful
22. Execute Modification ./Themes/default/Packages.template.php Test failed 23. Execute Modification ./Themes/default/SplitTopics.template.php Test successful
24. Execute Modification ./Sources/ManageRegistration.php Test successful
25. Execute Modification ./Sources/Packages.php Test successful
26. Execute Modification ./Sources/PersonalMessage.php Test successful
27. Execute Modification ./Sources/Register.php Test successful
28. Execute Modification ./Sources/ManagePermissions.php Test successful
29. Execute Modification ./Sources/ManagePermissions.php Test successful
30. Execute Modification ./Sources/SplitTopics.php Test successful
31. Execute Modification ./Sources/Themes.php Test successful


The biggest goal now is to make sure we are running the most current version.  Safe to say I have to load each and ever patch/upgrade one at a time to get to the latest version? 

[Antechinus]

Well you could always grab a large upgrade pack and go straight to 1.1.14 in one go. It's a bit more work than installing one patch, but arguably no more work than installing a lot of patches.

Upgrading SMF