Advertisement:

Author Topic: Very basic questions about testing the 2.1 upgrade...  (Read 2050 times)

Offline shawnb61

  • Developer
  • Sophist Member
  • *
  • Posts: 1,337
    • sbulen on GitHub
Very basic questions about testing the 2.1 upgrade...
« on: December 11, 2016, 11:33:55 PM »
The sticky on this board says:
Quote
Copy the files you have to your server, ensuring they are in a separate folder from any live install you have running.

Is this saying that you do *not* test an upgrade from 2.0 to 2.1 by copying the 2.1 files on top of the 2.0 install, overwriting existing files (and merging folders)?

Related - is it true that prior to upgrading a 2.0 test environment to 2.1, you must de-install all mods? 

l'm trying to understand the proper steps to test upgrading my 2.0 test environment to 2.1. 
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp

Offline Antes

  • Evil Black Cat
  • SMF Friend
  • SMF Hero
  • *
  • Posts: 8,943
  • Gender: Male
  • Black cat rulz!
    • Antes on GitHub
    • merta on LinkedIn
    • @XinYenFon on Twitter
    • WoWSnips
Re: Very basic questions about testing the 2.1 upgrade...
« Reply #1 on: December 12, 2016, 04:58:31 AM »
You can overwrite 2.1 files on 2.0, but that'll leave its mark, say if a X file no longer in SMF 2.1, but in 2.0, it stays there and takes web-space, not like its going to cause huge error (unless it called by a modification). This is why we are strongly suggesting to cleaning old files first (mostly Sources & Themes folders only).

You don't have to uninstall/de-install any modification you installed on SMF 2.0.x, upgrade process already does that for you. Uploading fresh set of files will undo the manual changes, upgrade.php (running) clears the hooks. Do mind upgrade process won't delete your mod tables due to protect your data. So once the modification releases its newer version, you can pick up where you left off with the mod data.

There is little to no difference between upgrading from 1.1 to 2.0 & 2.0 to 2.1, but if you are using GitHub files, upgrade related files (upgrade.php / upgrade related sql files) located in other folder, if you are using our releases the required files are located in root so you just unzip and run upgrade.php

You can read further about upgrade process and upgrading with GitHub pack here;

* http://wiki.simplemachines.org/smf/Upgrading
* http://wiki.simplemachines.org/smf/Contributing_to_SMF
You can support me directly via Patreon

In Catnip We Trust.
The solution is Catnip!
Vote for Catnip!

Current Project(s): [ WoWSnips ]
Past Project(s): [ ezPortal ] # [ Lunarfall ] # [ RDD (HTML5) ]

Offline Illori

  • Project Manager
  • SMF Legend
  • *
  • Posts: 51,139
Re: Very basic questions about testing the 2.1 upgrade...
« Reply #2 on: December 12, 2016, 05:06:48 AM »
the idea is to move your current files to a new location so that you are not overriding what exists already and you setup a test install and go from there. this way you dont trash your current install in case something goes wrong.

Offline shawnb61

  • Developer
  • Sophist Member
  • *
  • Posts: 1,337
    • sbulen on GitHub
Re: Very basic questions about testing the 2.1 upgrade...
« Reply #3 on: December 13, 2016, 12:48:16 AM »
Thanks everybody.

Yes, I'd read all of the links above.  I didn't find anything that explicitly stated whether to overwrite files or not. 

I've done the 2.0 to 2.1 upgrade both ways, both seem to work.  I think I will settle on the 'fresh folder' approach, it seems much cleaner maintenance wise - no funky old unused code/files laying around. 

It might just be in my mind, but the 'fresh folder' method seems more stable...




Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp

Online Kindred

  • The Mean One
  • Support Specialist
  • SMF Legend
  • *
  • Posts: 58,430
  • Gender: Male
    • Kindred-999 on GitHub
Re: Very basic questions about testing the 2.1 upgrade...
« Reply #4 on: December 13, 2016, 09:22:50 AM »
personally, I take a backup and then delete everything other than settings.php, avatars and attachments
then upload the 2.1 files and run upgrade.

and this will be the method to upgrade your production site, once 2.1 is final as well...
Please do not PM, IM or Email me with support questions.  You will get better and faster responses in the support boards.  Thank you.

Offline shawnb61

  • Developer
  • Sophist Member
  • *
  • Posts: 1,337
    • sbulen on GitHub
Re: Very basic questions about testing the 2.1 upgrade...
« Reply #5 on: December 14, 2016, 11:16:04 AM »
Thanks, very helpful. 

I have a local EasyPHP system for initial 2.1 testing.  Crude but functional.  On this local system, I can spin up test environments pretty quickly, in 2.0 or 2.1, vanilla or loaded with my site's data, without impacting my hosted prod or test 2.0 systems. 

I'd like to help with the 2.1 effort, just facing a learning curve.  My current problem is understanding the logged issues on Github.  It's like y'all speak in shorthand.  Still learning the lingo. 
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp