removes debug gems
removes deprecation warnings due to old scopes syntax
fixes install task namespace, closes #25
updates README with correct install task command
fixes migrations not being installed, #29 related
Fix typo in English locale
Merge pull request #30 from brchristian/patch-1

Fix typo in English locale
fix typo
Allow Issue to get deleted Magazine and Mag_Issue

The `paranoia` gem adds a `default_scope` to `Spree::Product` that hides all deleted Products.

However, I can imagine that a site admin might want to see all the issues in a subscription even if those products are old and have been deleted.

This syntax allows the getter methods to use the unscoped versions of the Product model.

Note that this applies to `Issue.first.magazine` but does _not_ apply to `Issue.includes(:magazine).first.magazine` -- this is a known and outstanding issue in the `paranoia` gem.
Merge pull request #35 from brchristian/patch-2

Allow Issue to get deleted Magazine and Mag_Issue
Merge pull request #34 from brchristian/patch-1

fix typo
remove ruby version file from git repository
Correct spec for namespacing
Shortcut for ShippedIssue#magazine_issue

Here we can write `ShippedIssue.magazine_issue` rather than always needing to write `ShippedIssue.issue.magazine_issue`, similar to the way that Spree uses  `LineItem.product` as a shortcut for `LineItem.variant.product`.
Remove commented attr_accessible in shipped_issue
Merge pull request #38 from brchristian/patch-2

Remove commented attr_accessible in shipped_issue
Update admin view
Don't throw exception when product is soft-deleted

A long-running store may have Issue objects attached to Products which have been soft-deleted and removed from sale. For bookkeeping reasons, account history, and the like, we want to still be able to allow Issues to know which Magazine they're issues of. This is accomplished simply by using the `with_deleted` scope.
Update admin view for subscriptions search box

This updates the view for the admin subscriptions search box following the Spree 2.x conventions.
Fix shipped?(issue) method

This corrects what appears to have been a bug in the `Subscription.shipped?(issue)` method, where the logic had been:

    !shipped_issues.where(:id => issue.id).empty?

which seemed off to me -- the `:id` of a shipped_issue would be the shipped_issue's _own_ id, not the id of the issue being checked for. So I changed that to

    !shipped_issues.where(issue: issue).empty?

which I think is the original intention.

Note that I also suggested changing `!empty?` to `present?` for simplicity:

    shipped_issues.where(issue: issue).present?