Support Ticket
Standard upgrade to 1.13.0 with no errors Javascript seems to be missing?+issues
All I get is a main page + CSS, Javascript is not loaded... Any thoughts?
Hmm... so I had a clean Ubuntu install on my VM... apparently "rake wagn:migrate" fails with a missing ExecJS error, had to do a "sudo apt-get install nodejs" apparently nodeJS is required now? After this the upgrade went through.
Snapshots were great here since I just reverted back to a previous one a couple of times...
Had to "reboot" the server since I was then getting errors rendering sign in view... and all seems to be well now...
Also the symlink > cd [appdir]; ln -s [gemdir]/public
is no longer necessary and can be removed. I've updated the install instructions at http://wagn.org/wagn_in_production to reflect this, it's still there but I moved it further down.
Ah, thanks so much for the documentation help.
I'm way behind on my documentation chores (which is why I *still* haven't sent out the Wagn 1.13 email), but this ticket inspired me to update both the Updating card (the documentation of standard upgrade procedure) and the Upgrade Notes card on Wagn 1.13 (Wagn 1.13+Upgrade Notes).
To your issues:
1. You do need an ExecJS now. Your nodeJS solution sounds fine if it works, but the easiest way to do this is probably by adding "gem 'therubyracer'" to your Gemfile as is (now) documented on the upgrade notes. Newly created wagns will now all have that in their Gemfile already. (This isn't treated as a gem dependency, because mac users don't need to install an ExecJS, and in fact that installation often causes problems, so we're currently putting rubyracer directly in the deck's Gemfile for non-mac users).
2. As for the symlink, you're correct that it's no longer needed. However, you may want the public/assets directory symlinked. As I just wrote in the upgrade notes, you can now do that (and perform migrations and other things) by running `wagn update`.
Great!
I've taken the liberty of editing this: http://wagn.org/installation because it was the guide I found first and followed to the letter.
Taking this old part out:
LATER EDIT: Realized the process was a little different so I put them back in and made some edits to preserve exact history of versions and their own upgrade mechanisms. Much better now!
Also edited this line:
NOTE: The following assumes you're already using a Wagn gem. If you're version 1.12.6 or earlier, you will need to upgrade to the Wagn gem. It's also possible to upgrade from one pre-gem version to another. But the gem is much better!
The second link was damaged. Fixed!
LATER EDIT: Realized the process was a little different so I put them back in and made some edits to preserve exact history of versions and their own upgrade mechanisms. Much better now!
Also edited http://wagn.org/upgrade_notes it was saying 'gem "rubyracer"' instead of 'gem "therubyracer"' and I was following that, got an error with gem not found. Also switched step 1. and step 2. between themselves. Following step by step makes you fail at step 1. then do step 2. and then redo step 1. Now it's so easy you don't even have to think.
Tried following the steps in /upgrade_notes, but when we got to wagn update, it produces an error that the command was not recognized.
The gem update wagn did appear to work, though. Just the next command didn't. We tried the old rake wagn:migrate which did appear to do some things including upgrading the gem but did not result in the site showing a new version number, so we assume that it didn't upgrade.
Mir S., thank you for all the help! Good points re "therubyracer".
Lora, this may be an unrelated issue, so we might want to move this to a separate ticket if the conversation grows, but let's start here. The first thing is to make sure you're actually getting Wagn 1.13 code.
What happens if you do "wagn -v"? (With all these commands you might try adding "bundle exec" before them if they are failing. Eg "bundle exec wagn -v".
If you're not seeing "Wagn 1.13", I'd have a look at your Gemfile and make sure it says something like "gem 'wagn'" and does not specify a lower version. That would explain why the update would work but the version wouldn't change.
if you are seeing Wagn 1.13, can you run "bundle exec wagn update" and tell me what you see?
well, wagn -v just gives me a list of possible commands without giving me a version number, and bundle exec wagn -v says Could not locate Gemfile
hmm, "Could not locate Gemfile" suggests you may be not running this command from the right place. You should be in your deck's root directory, where you see files things like Rakefile, Gemfile, and config.ru, and you'll see folders like config, files, and tmp. Are you getting "Could not locate Gemfile" there?