paid_up 0.6.4 → 0.6.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 3da440f110cb2c7900df15cd655e181faea974fc
-  data.tar.gz: fbfd85d1d6d4dcb2367fb00d13060358bcbce8cf
+  metadata.gz: 1052e49f3dbc4c3610455e9ca70d8e95a135127f
+  data.tar.gz: ea8140ab388b3dbeff901f6bff42138f1d2b7c1c
 SHA512:
-  metadata.gz: 85dcd359e26971af61032e4a8e750e65f9fce815351837d8d0912bc469594aa058e264762bf744ecafdb015de2069fe1da13c03180d7066240db30b5116b84c3
-  data.tar.gz: 2f60836f4ae5772b94e2c5f359809613f4049ff047e823790045ff9236005650f76e58cc0e65d18f3e798f4fe93066bb367583bd6128be728aadaead62abc719
+  metadata.gz: c5c98c4bb074579736e4dd3fafe623d7d2572f011b945a103c9f05a2501c379bf845910aa1da9d31a3c12aee29026af4faa257a43928ab5ebad180cce428db00
+  data.tar.gz: 32df91b89d7052946a29be395ca38e414ac029a2a244b47f83cdf02cc79e272400eee30fe41a7655f8259fd0c28bf25c638995ccd70aa6f00300b3b936723bb9

data/README.md

@@ -49,11 +49,11 @@ Possible `:setting_type` values are: `boolean`, `table_rows`, `rolify_rows`. The
 
 #### Setting Type: Table Rows
 
-In the `table_rows` case, the table and its model must exist. the table should have a `:user_id` column, and from there the appropriate `has_many` and `belongs_to` relationships will be created for you.
+In the `table_rows` case, the table and its model must exist. the table should have a `:user_id` column, then you need to add `paid_for` to the model, and from there the appropriate `has_many` and `belongs_to` relationships will be created for you.
 
 #### Setting Type: Rolify Rows
     
-In the `rolify_rows` case, the table and its model must also exist. Once that is done and the corresponding `PaidUp::Feature` is created, the resource model will run the `resourcify` method, and the User method will have had the `rolify` method added to it during install, so no further setup is required.
+In the `rolify_rows` case, the table and its model must also exist. Once that is done and the corresponding `PaidUp::Feature` is created, add `paid_for` to the model. This means the resource model will run the `resourcify` method, and the User method will have had the `rolify` method added to it during install, so no further setup is required.
 
 ## Enabling Javascript
 

data/VERSION

@@ -1 +1 @@
-0.6.4
+0.6.5

data/paid_up.gemspec

@@ -2,16 +2,16 @@
 # DO NOT EDIT THIS FILE DIRECTLY
 # Instead, edit Jeweler::Tasks in Rakefile, and run 'rake gemspec'
 # -*- encoding: utf-8 -*-
-# stub: paid_up 0.6.4 ruby lib
+# stub: paid_up 0.6.5 ruby lib
 
 Gem::Specification.new do |s|
   s.name = "paid_up"
-  s.version = "0.6.4"
+  s.version = "0.6.5"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.require_paths = ["lib"]
   s.authors = ["Karen Lundgren"]
-  s.date = "2015-05-27"
+  s.date = "2015-05-28"
   s.description = "Allows a model of your choosing (such as users) to subscribe to a plan, which enables features."
   s.email = "karen.e.lundgren@gmail.com"
   s.extra_rdoc_files = [

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: paid_up
 version: !ruby/object:Gem::Version
-  version: 0.6.4
+  version: 0.6.5
 platform: ruby
 authors:
 - Karen Lundgren
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-05-27 00:00:00.000000000 Z
+date: 2015-05-28 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails