salted_login_generator 1.0.7 → 1.0.8

data/templates/README

@@ -8,7 +8,8 @@ this:
 
   class ApplicationController < ActionController::Base
     include <%= class_name %>System
-    helper: <%= singular_name %>
+    helper :<%= singular_name %>
+    model :<%= singular_name %>
     before_filter :login_required
 
 After you have done the modifications the the ApplicationController and its
@@ -23,7 +24,27 @@ file:
 require 'environments/<%= singular_name %>_environment'
 
 Under the 'enviroments' subdirectory, you'll find <%= singular_name %>_environment.rb.
-Edit this file as necessary...
+Edit this file as necessary.
+
+Also, you must properly configure ActionMailer for your mail settings. For
+example, I have the following in config/environments/development.rb (for a
+.Mac account, and without my username and password, obviously):
+
+ActionMailer::Base.server_settings = {
+  :address => "smtp.mac.com",
+  :port => 25,
+  :domain => "smtp.mac.com",
+  :user_name => "<your user name here>",
+  :password => "<your password here>",
+  :authentication => :login
+}
+
+You'll need to configure it properly so that email can be sent. One of the
+easiest ways to test your configuration is to temporarily reraise exceptions
+from the signup method (so that you get the actual mailer exception string).
+In the rescue statement, put a single "raise" statement in. Once you've
+debugged any setting problems, remove that statement to get the proper flash
+error handling back.
 
 == Requirements
 
@@ -35,8 +56,8 @@ You need a database table corresponding to the <%= class_name %> model.
     login VARCHAR(80) NOT NULL,
     password VARCHAR(40) NOT NULL,
     email VARCHAR(60) NOT NULL,
-    firstname VARCHAR(40) NOT NULL,
-    lastname VARCHAR(40) NOT NULL,
+    firstname VARCHAR(40),
+    lastname VARCHAR(40),
     salt CHAR(40) NOT NULL,
     verified INT default 0,
     role VARCHAR(40) default NULL,
@@ -50,8 +71,8 @@ You need a database table corresponding to the <%= class_name %> model.
     login VARCHAR(80) NOT NULL,
     password VARCHAR(40) NOT NULL,
     email VARCHAR(60) NOT NULL,
-    firstname VARCHAR(40) NOT NULL,
-    lastname VARCHAR(40) NOT NULL,
+    firstname VARCHAR(40),
+    lastname VARCHAR(40),
     salt CHAR(40) NOT NULL,
     verified INT default 0,
     role VARCHAR(40) default NULL,
@@ -65,8 +86,8 @@ You need a database table corresponding to the <%= class_name %> model.
     login VARCHAR(80) NOT NULL,
     password VARCHAR(40) NOT NULL,
     email VARCHAR(60) NOT NULL,
-    firstname VARCHAR(40) NOT NULL,
-    lastname VARCHAR(40) NOT NULL,
+    firstname VARCHAR(40),
+    lastname VARCHAR(40),
     salt CHAR(40) NOT NULL,
     verified INT default 0,
     role VARCHAR(40) default NULL,
@@ -75,7 +96,14 @@ You need a database table corresponding to the <%= class_name %> model.
   );
 
 Of course your <%= singular_name %> model can have any amount of extra fields.
-This is just a starting point
+This is just a starting point.
+
+Supplied with the generator is a .erbsql schema file. If you download the
+db_structure gem, you can run script/create_db to automatically create all of
+your databases and tables based on this file. ** BEWARE ** This script
+drops and recreates all tables in test, production and development databases.
+The supplied file has been tested with MySQL, though others have reported
+success with SQLite and PostgreSQL.
 
 == How to use it 
 
@@ -127,11 +155,28 @@ How do I...
        send the user to the login form. 
        After he logs in he will be send back to /articles/show/1
 
-
 You can find more help at http://wiki.rubyonrails.com/rails/show/SaltedLoginGenerator
 
+== Troubleshooting
+
+One of the more common problems people have seen is that after verifying an
+account by following the emailed URL, they are unable to login via the
+normal login method since the verified field is not properly set in the
+<%= singular_name %> model's row in the DB.
+
+The most common cause of this problem is that the DB and session get out of
+sync. In particular, it always happens for me after recreating the DB if I
+have run the server previously. To fix the problem, remove the /tmp/ruby*
+session files (from whereever they are for your installation) while the server
+is stopped, and then restart. This usually is the cause of the problem.
+
+A forthcoming release will probably fix this via a well placed reset_session
+call (or requirement to add it after running the generator) so that it is done
+automatically on startup.
+
 == Changelog
 
+1.0.8 Generator/schema fixes and some README fixes/improvements
 1.0.7 Fixed bad bug with missing attr_accessor :new_password in user class
 1.0.6 Proper delete support and bug fixes
 1.0.5 Lots of fixes and changes (see rubyforge.org/salted-login)

data/templates/controller.rb

@@ -67,7 +67,7 @@ class <%= class_name %>Controller < ApplicationController
     case @request.method
     # Render on :get
     when :get
-      @user = User.new
+      @<%= singular_name %> = <%= class_name %>.new
       render
     end
 
@@ -151,8 +151,8 @@ class <%= class_name %>Controller < ApplicationController
   end
 
   protected
-  
-  def destroy(user)
+
+  def destroy(<%= singular_name %>)
     <%= class_name %>Notify.deliver_delete(<%= singular_name %>)
     flash['notice'] = l(:<%= singular_name %>_delete_finished, "#{<%= singular_name %>['login']}")
     <%= singular_name %>.destroy()

data/templates/user_model.erbsql

@@ -3,8 +3,8 @@ CREATE TABLE users (
   login VARCHAR(80) NOT NULL,
   salted_password VARCHAR(40) NOT NULL,
   email VARCHAR(60) NOT NULL,
-  firstname VARCHAR(40) NOT NULL,
-  lastname VARCHAR(40) NOT NULL,
+  firstname VARCHAR(40) default NULL,
+  lastname VARCHAR(40) default NULL,
   salt CHAR(40) NOT NULL,
   verified INT default 0,
   role VARCHAR(40) default NULL,

metadata

@@ -3,8 +3,8 @@ rubygems_version: 0.8.8
 specification_version: 1
 name: salted_login_generator
 version: !ruby/object:Gem::Version 
-  version: 1.0.7
-date: 2005-05-08
+  version: 1.0.8
+date: 2005-05-11
 summary: "[Rails] Login generator with salted passwords."
 require_paths: 
   - "."