Upgrading from SMS 2

Nova 2 Getting Started Install Guide

So you've been using SMS 2 since it came out or since you started your game. When Nova came out, you were hesitant to make the jump, but now that 2.0 is out, you decide that it's time to make the leap and start using Nova. But wait, what about the years of information you've accumulated in your SMS site? You don't want to lose that. We've already thought about that and have a simple solution to upgrade most (there are some pieces it just isn't possible to upgrade easily) of your SMS data to the newer Nova format.

What Will/Won't Be Upgraded?

You probably read the part above about "most" of your SMS data being upgraded, but what exactly will and won't be upgraded? The table below will show you the different pieces and whether they'll be upgraded or not.

Access Levels

If you've made changes to the default access levels in SMS they will not be saved since Nova uses a new user access control system.

Awards

Any awards you've put in to SMS will be upgraded to the Nova format.

Award Nominations

Award nominations that have been submitted will not be upgraded to the Nova format.

Chain of Command

Because of the complex way we move characters over to Nova and split out characters and users, the chain of command will not be upgraded.

Characters/Users

Characters and users from SMS will be moved to the Nova format. Users will have their passwords and access level automatically reset.

Database Items

Nova doesn't have a "database" feature like SMS, instead, we've built a mini-wiki called Thresher that does similar things. Any of your database entries that are stored in the database will be converted to Thresher pages. Any content on external pages linked through the Database will not be converted.

Departments

Departments stored in SMS will not be upgraded to Nova. New departments will be created based on the genre selected.

Settings (Site Globals)

The following settings will be upgraded to Nova: sim name, sim year, post count preference, email subject.

Menu Items

SMS menu items will not be upgraded to the Nova format.

Site Messages

The following messages will be upgraded to Nova: welcome message, sim message, join disclaimer, user accept email message, user reject email message, join codele post.

Missions

All missions will be upgraded to the Nova format.

News Items

All news items will be upgraded to the Nova format.

News Categories

All news categories will be upgraded to the Nova format.

Personal Logs

All personal logs will be upgraded to the Nova format.

Positions

Positions stored in SMS will not be upgraded to Nova. New positions will be created based on the genre selected.

Mission Posts

All mission posts will be upgraded to the Nova format.

Private Messages

SMS private messages will not be upgraded.

Ranks

Ranks stored in SMS will not be upgraded to Nova. New ranks will be created based on the genre selected.

Specifications

Only out-of-the-box specifications will be upgraded. If you have modified the specifications database table, your changes will not be upgraded.

Docking

Nova uses a new, highly dynamic form system and docking records will not be upgraded.

Strikes

There is currently no way to handle strikes in Nova and SMS strikes will not be upgraded.

Tour

Only out-of-the-box tour information will be upgraded. If you have modified the tour database table, your changes will not be upgraded.

Deck Listing

The deck listing will not be upgraded.

Before You Start

Upgrading from SMS to Nova 2 is a much different process than upgrading from SMS to Nova 1 (for those who did that process). With 10 fewer steps and a vastly improved user interface, doing a full upgrade from SMS 2 should take less than 10 minutes to do (this will depend on how much data you have to upgrade). In order to do an upgrade from SMS, you'll need to be running SMS 2.6.9 or higher and have the information below. If you don't know any of this, contact your host to get the information.

  • Your database location (localhost or some other means of connecting)
  • Your database name
  • Your database username and password (these may or may not be the same as your FTP username and password)
  • Your FTP username and password

Step 1 Backup and Remove

Before you get started, you should export your SMS database from phpMyAdmin as a .sql file in case something happens during the upgrade process. Don't drop the tables or do anything like that since you'll still need all the information in those database tables. You should also backup all your SMS files to your desktop in case you need them. Once you've done both backups, delete all the SMS files on your server.

Step 2 Upload Nova

Next, you'll need to upload the Nova 2 files up to your server where the SMS files were. If you're not sure how to upload the files to your server, contact your host for help with this step of the process or do a Google search.

Step 3 Configure Nova

Before beginning the upgrade, you can choose to change any of Nova's configuration options in the config files located in the app/config directory. This is completely optional and Nova 2 will install fine without any changes to any files in the config directory.

Step 4 Setting Up the Database Connection

This is the part where everyone panics and says it's too complicated and difficult to get started. This is also the part where we prove you wrong.

Setting up your connection to the database is dead simple. All you need to do is open your browser and navigate to the location on your server where you uploaded the Nova files. If your server was http://example.com and you uploaded Nova 2 to the root directory (often called www or public_html), then you'd navigate to http://example.com and you'd be automatically redirected to the Config Setup page. From this page, you'll be able to tell Nova the information for connecting to your database and then Nova will 1) attempt to connect to the database and make sure it can, then 2) write that information to a connection file. Pretty easy, huh?

If for some reason your server doesn't support creating files from a web script, the setup process will show you the code to copy and paste into the database connection file.

Explaining the Options

  • Database Name - The name of the database you're trying to connect to and install Nova to in to. If you don't know the name of your database, contact your host.
  • Username - The username used to connect to your database. This may or may not be the same as your FTP username, so if you don't know, contact your host.
  • Password - The password used to connect to your database. This may or may not be the same as your FTP password, so if you don't know, contact your host.
  • Database Host - This is where the database lives. 99% of the time, this will be localhost though if your host has a different setup, they may have sent you a different host name. If you aren't sure about this, contact your host.
  • Table Prefix - This is the word or initials that will prefix all table names. This helps to keep Nova's tables together and allows you to install other things in to the database without causing conflicts. This is set to nova_ by default.

Step 5 Upgrade to Nova

When you start in to the upgrade process, the first thing that will happen is that Nova 2 will be installed as normal, except you won't be prompted to create your character and set the system settings. Once Nova is installed, there are 3 distinct sections to the upgrade process, but don't worry, they're all very straightforward.

Select What to Upgrade

For anyone who attempted (or did) the SMS to Nova 1 upgrade, you'll quickly note the lack of a need to update a config file before starting. The new upgrade process handles everything right in the site. You'll be presented with a list of components and whether you want to upgrade those components to Nova. By default, it will upgrade everything in the list, but you can pick and choose based on your preferences. The upgrade process is smart enough to know when something depends on something else. For instance, if you didn't want characters and users upgrade, the upgrade process won't let you upgrade posts, logs and new items since they depend on characters and users.

Once you've set which things you want to upgrade, you can click on the button to run the first step. An indicator will point out which item is currently running. Once it's finished running icons will be displayed to indicate whether the upgrade of that component was successful, failed or has errors or warnings. Once the final component has run, you'll be able to click the button and move on to the next step.

Upgrade the Components

After doing the initial upgrade, there's follow-up work that needs to be done. All that's required for this step is to click the button. Like the first part of the process, an indicator will show you what's running an an icon will let you know its status after it's finished running. Once all the items have been run, you'll be able to click the button and move on to the next step.

Set Password and Administrator(s)

Because Nova uses a different method of hashing passwords, none of the SMS passwords will work. The final step of the upgrade process is to specify what you want the new password to be. This password is case sensitive and is the password you'll need to send to the entire crew. The first time a player logs in, they'll be prompted to update their password.

In addition, you can select the members of the crew that should have system administrator rights. Once you've set the password and selected the users, click the button to run the process. Once the process has finished running (you'll know because icons will indicate the success/failure of the two final steps), you'll be able to continue on to your site.

Step 6 That's It?

Yep, that's it. Pretty easy, huh?

One final thing to note is that at the end of the upgrade Nova will attempt to change several permissions in order to ensure all the backup and upload features work properly. It's possible that your host will have turned off the functions necessary to do this, so if you run in to any problems uploading to Nova, you'll need to change the file permissions on several directories to ensure they're writable (777). If you don't know how to change file permissions, contact your host. The following directories (and their sub-directories) need to be writable:

  • app/assets/images
  • app/assets/backups
  • app/cache
  • app/logs

Log in with your AnodyneID to rate this article or submit the article for review.