We have to call post.save in the posts/index specs, because post_path
fails unless the post has been persisted (and hence had its slug
generated). I think. That fixed the failing tests, anyway.
- add Permalink
- show Reply instead of "Comment" (iff you can comment)
- Edit link shows if you have permission to edit
- reorganised tests for post/_single
- posts/_single now requires current_user; patch tests for comments.
Added a couple of tiny methods on Crop, and delegated them across to
Planting, to easily display the default/first scientific name, and to
show the number of times a given crop's been planted.
Sadly, the tests randomly fail on my box saying "No route matches
{:controller=>"plantings", :action=>"show"}" which is just nonsense. I
have no idea why it's doing that, so I'm committing it anyway, in the
hopes that either someone can tell me what's up, or else it's just a
glitch on my dev box.
Because our default timezone for the app is UTC, at certain times, some
tests could fail outside of UTC. This commit fixes that by changing a
single call to Time.now to Time.zone.now.
* dev: (28 commits)
Upgrade bootstrap by running `rails g bootstrap:install`
added .to_i to times to attempt to pass tests on travis
stubbed Time.now to prevent test failures
Added friendly IDs for forum and role
General prettification and making it look nice.
show forum name in post meta
Added a rake task to create an admin user.
hooked roles up to cancan
Added roles, but haven't yet hooked them up to CanCan
PT story 41985889, Hides 'new garden' tab on other member's pages
Add forums to top nav
Display posts in summary on forum page
tests for markdown
post in (or not in) a forum
prettifying forum views
added associations between forums, posts, and members
rails g scaffold Forum
Rearranging password fields
Attempted rearranging settings page, broke something
Upgrade to Rails 3.2.12, after *another* security flaw.
...
Conflicts:
spec/models/member_spec.rb
We have added a sequence for login_name which is similar to the one for
emails in which the member name is incremented each time a new member is
saved.
In addition, we have updated all specs which asked for an explicit
login_name of member1 to use a regex looking only for member and some
digit.
You should only have to do this once, after deploying. Subsequent
admins can add new ones via the web interface.
The syntax is:
rake growstuff:admin_user name=skud
or, on heroku:
heroku run rake growstuff:admin_user name=skud
Now only admins can create/edit forums, or mess with roles.
To add an admin user:
rails c
m = Member.find('skud')
r = Role.create(:name => 'admin')
r.members << m
We'll have to do this on the server to bootstrap the admin stuff.
Though actually, we should really write a rake task to generalise this.
Skud