{"action":"created","issue":{"url":"https://api.github.com/repos/RailsApps/rails-stripe-membership-saas/issues/127","labels_url":"https://api.github.com/repos/RailsApps/rails-stripe-membership-saas/issues/127/labels{/name}","comments_url":"https://api.github.com/repos/RailsApps/rails-stripe-membership-saas/issues/127/comments","events_url":"https://api.github.com/repos/RailsApps/rails-stripe-membership-saas/issues/127/events","html_url":"https://github.com/RailsApps/rails-stripe-membership-saas/issues/127","id":70813750,"number":127,"title":"Error message when loading \"Sign Up\" View","user":{"login":"DNSH","id":4742964,"avatar_url":"https://avatars.githubusercontent.com/u/4742964?v=3","gravatar_id":"","url":"https://api.github.com/users/DNSH","html_url":"https://github.com/DNSH","followers_url":"https://api.github.com/users/DNSH/followers","following_url":"https://api.github.com/users/DNSH/following{/other_user}","gists_url":"https://api.github.com/users/DNSH/gists{/gist_id}","starred_url":"https://api.github.com/users/DNSH/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DNSH/subscriptions","organizations_url":"https://api.github.com/users/DNSH/orgs","repos_url":"https://api.github.com/users/DNSH/repos","events_url":"https://api.github.com/users/DNSH/events{/privacy}","received_events_url":"https://api.github.com/users/DNSH/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-04-24T22:48:50Z","updated_at":"2015-04-25T19:53:46Z","closed_at":null,"body":"I have cloned the app from the repo and have run \"rails s\"\r\n\r\nThe homepage loads, but then when I click \"Sign Up\" I receive the following error message:\r\n\r\n**NoMethodError at /users/sign_up: undefined method `plan_class' for nil:NilClass,**\r\n\r\nThe output says the error is occurring on line 8 in \"app/views/devise/registrations/new.html.erb\":\r\n\r\n**'data-payola-plan-type' => resource.plan.plan_class,**\r\n\r\nI was wondering how I should proceed? Thanks\r\n"},"comment":{"url":"https://api.github.com/repos/RailsApps/rails-stripe-membership-saas/issues/comments/96271854","html_url":"https://github.com/RailsApps/rails-stripe-membership-saas/issues/127#issuecomment-96271854","issue_url":"https://api.github.com/repos/RailsApps/rails-stripe-membership-saas/issues/127","id":96271854,"user":{"login":"kathyonu","id":30484,"avatar_url":"https://avatars.githubusercontent.com/u/30484?v=3","gravatar_id":"","url":"https://api.github.com/users/kathyonu","html_url":"https://github.com/kathyonu","followers_url":"https://api.github.com/users/kathyonu/followers","following_url":"https://api.github.com/users/kathyonu/following{/other_user}","gists_url":"https://api.github.com/users/kathyonu/gists{/gist_id}","starred_url":"https://api.github.com/users/kathyonu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kathyonu/subscriptions","organizations_url":"https://api.github.com/users/kathyonu/orgs","repos_url":"https://api.github.com/users/kathyonu/repos","events_url":"https://api.github.com/users/kathyonu/events{/privacy}","received_events_url":"https://api.github.com/users/kathyonu/received_events","type":"User","site_admin":false},"created_at":"2015-04-25T19:53:46Z","updated_at":"2015-04-25T19:53:46Z","body":"Because these are tutorial materials .. \r\n and many new to Ruby on Rails will be using these materials .. \r\n and because the membership app is right now going through upgrade changes ..\r\n I am going to cover the gamut of what to do for a healthy running rails-stripe-membership-saas app.\r\n\r\nMay I recommend to anyone to do the following ..\r\n All of which will get your system in shape for the ..\r\n  New gems and tests now in the pipeline for inclusion into the master :\r\n\r\nAt the terminal_prompt:$ type these first four commands to keep your system up to date and humming.\r\nThese four commands make sure your RVM and Homebrew are up to date :\r\n\r\n__rvm get stable__\r\n\t# updates your rvm \r\n\r\n__brew update__\r\n\t# update your Homebrew (takes a while)\r\n\r\n__brew doctor__\r\n\t#  this will tell you all is well with your Homebrew (takes a while)\r\n\r\n__rvm list known__\r\n\t# this will show you the Rubies rvm knows about and \r\n\t#   can install : http://rvm.io/rubies/installing\r\n\t# if you do not see Ruby 2.2.2, we will cover what to do further below\r\n\t# now, change into your working directory :\r\n\r\n__cd rails-stripe-membership-saas__\r\n\r\n__rvm gemset list__\r\n\t# this makes sure you are on the right gemset\r\n\t# rails-stripe-membership-saas is the one you want\r\n\r\n__rails -v__\r\n\t# if not Rails4.2.1, see below instructions\r\n\r\n__ruby -v__\r\n\t# if not Ruby 2.2.2, see below instructions\r\n\r\nINSTRUCTIONS : \r\n\t# First, we are going to use the global gemset for this\r\n\r\n__rvm gemset list__\r\n\t# you will see the global gemset, now we use it with next command\r\n\r\n__rvm gemset use global__\r\n\t# you are in the global, run the list command again, you will see it is so\r\n\r\n__gem update —system__\r\n\t# self-explanatory\r\n\r\n__gem update rake__\r\n\t# self-explanatory\r\n\r\n__gem update bundler__\r\n\t# self-explanatory\r\n\r\n__gem update rubygems-bundler__\r\n\t# self-explanatory\r\n\r\n__gem outdated__\r\n\t# if you have any outdated gems, now is a good time to update the global gemset\r\n\r\n__gem update__\r\n\t# that will do it\r\n\r\n/\\ NOTE WELL : All of the above is done in the global gemset.\r\n\\/ Now, we change to the application’s gemset.\r\n\r\n__rvm gemset list__\r\n\t# choose your correct gemset, wihch is rails-stripe-membership-saas\r\n\t# if that gemset does not exist in the list, what i do is this :\r\n\t# Make sure the Gemfile shows Ruby at 2.2.2\r\n\t# Make sure the .ruby-version file shows 2.2.2 \r\n\t# You can use the command at the terminal_prompt$ open -e .ruby-version \r\n\t# Make sure the .ruby-gemset file reads rails-stripe-membership-saas\r\n\t# Now run this command : \r\n\r\n__ruby -v__\r\n\t# if not 2.2.2,  do this :\r\n\r\n__rvm use 2.2.2__\r\n\t# watch for rvm install instructions, if any, and use them\r\n\t# voila, you are now on 2.2.2\r\n\t# now, we can create the gemset\r\n\r\n__rvm gemset use rails-stripe-membership-saas —create —default__\r\n\t# at this point, I personally like to close that terminal window\r\n\t#  and open a new one, and watch the rvm magic show itself\r\n\t#  as it recognizes the new gemset if this is the first time you set it.\r\n\t# if you ever change gemsets, the way back is : \r\n\r\n__rvm gemset use rails-stripe-membershp-saas__\r\n\r\n__ruby -v__\r\n\t# should be 2.2.2\r\n\r\n__rails -v__\r\n\t# should be 4,2.1\r\n\t# If you are not yet on Rails4.2.1, this is the point that you do this :\r\n\r\n__gem install rails__\r\n\t# notice it is not, bundle install.  here, we use gem install\r\n\r\n__bundle update rails__\r\n\t# now we let Bundler do its work\r\n\r\n__bundle install__\r\n\t# now we install all the requisite gems, and dependencies\r\n\t# if you have difficulties here, try trashing your Gemfile.lock and \r\n\t# then run this command again.\r\n\r\n__rake rails:update__\r\n\t# do not miss this step, it is important to do everytime you upgrade Rails versions.\r\n\t# if the process asks you if you want to overwrite a file, type in :  diff  : and it will\r\n\t# show you the changes it is about to make.  If you have working code in your file,\r\n\t# that cannot be overwritten, and yet there is new code to be added, simply open\r\n\t# the file it wants to overwrite, and make those additions by hand, save the file, close it,\r\n\t# and choose n : do not allow the overwrite.  That preserves your code and adds new.\r\n\t# Example is, you will see codes with /spring/ in the bin file overwrite question, after\r\n\t# you type in ‘diff’ :  do not allow overwrite of spring codes in the bin/files\r\n\r\n\t# Now is a good time to update your bundled gems :\r\n\r\n__bundle outdated__\r\n\t# to see what is what\r\n\t# now it is up to you to decide if you need or want to update gems with :\r\n\r\n__bundle update__\r\n\t# bundler does its magic\r\n\t# follow any instructions bundler gives you while it updates.\r\n\r\n\t# Now, you have a choice .. the automatic pull command, or\r\n\t# the git fetch and git merge commands.  First, check your \r\n\t# git remotes ..  this works no matter if you are working with\r\n\t# a clone of the RailsApps/ repository, or your own fork repository :\r\n\r\n__git remote -v__\r\n\t# this will show your origin\r\n\r\n__git pull origin master__\r\n\t# this will pull down any changes in the remote master, and merge them.\r\n\t# this will also show you any merge conflicts .. open those files and fix them.\r\n\t# after you fix all merge conflicts, do a git commit.  \r\n\t# Your local master now matches your origin master.\r\n\r\n   OR, you can do it this way :\r\n\r\n__git fetch origin master__\r\n\t# pulls down the master branch into your memory .. waiting for the merge command\r\n\r\n__git merge__\r\n\t# you are in the master branch, it will begin the merge, and ..\r\n\t# if there are any conflicts, open the file(s), fix, and commit.\r\n\r\n\tOR .. if you are working wtih a fork of the app :\r\n\r\n__git fetch upstream master__\r\n\t# use this if you are working with your fork, then ..\r\n\r\n__git merge origin/master upstream/master__\r\n\t# again, you may see conflicts, if so, fix them and when done, commit the merge.\r\n\r\nYou are now in tune with where the RailsApps rails-stripe-membership-saas app is.\r\n\r\n__git status__\r\n\t\r\n\t You should be good to go.  \r\n\r\n\r\nOn Apr 24, 2015, at 3:48 PM, DNSH <notifications@github.com> wrote:\r\n\r\nI have cloned the app from the repo and have run \"rails s\"\r\n\r\nThe homepage loads, but then when I click \"Sign Up\" I receive the following error message:\r\n\r\nNoMethodError at /users/sign_up: undefined method `plan_class' for nil:NilClass,\r\n\r\nThe output says the error is occurring on line 8 in \"app/views/devise/registrations/new.html.erb\":\r\n\r\n'data-payola-plan-type' => resource.plan.plan_class,\r\n\r\nI was wondering how I should proceed? Thanks\r\n\r\n—\r\nReply to this email directly or view it on GitHub.\r\n\r\n"}}