| Age | Commit message (Collapse) | Author |
|---|
|
|
|
It was marked as submitted even when client side validations interfered.
fixes github issue #227
|
|
update all the dependencies.
minitest now wants assert_nil instead of assert_equal nil, ...
braintree now uses update_attributes rather than save.
|
|
This used to trigger a 500.
Fixes #8395
|
|
|
|
MX validations relied on network connection. Only using them
in production environment now. I want to be able to develop and
test when disconnected.
|
|
|
|
We still have strange urls requested like
/pt/users/AnonymousUser.../tickets/new
Not sure where they are coming from - but this should make sure we
respond with sth. meaningful instead of erroring out.
Conflicts:
app/views/layouts/_content.html.haml
|
|
CouchRest > 1.2 does not use RestClient anymore. So we should not try to
catch its errors.
|
|
Handing freshly generated invite codes to Factory Girl to make the tests pass
|
|
|
|
|
|
|
|
|
|
|
|
It removed most of the reduce functions... really not what we wanted
|
|
We completely ingnore the user_id param for non admins now. So if someone tries to show somebody elses tickets they will see their own instead.
|
|
only submit the params that differ from the defaults
|
|
When an admin sorted the tickets view in a different order it would take them to their own tickets list before
|
|
This was causing problems with zeus
|
|
|
|
|
|
close and open actions for plain opening and closing the tickets
respond_with so fields are not cleared on invalid update
the custom actions are not strictly restful. But adding a subresource felt like too much overhead and is conceptually hard to grasp (so we destroy the openess of the ticket to close it?).
|
|
|
|
|
|
This controller does too much - so the tests are also getting large and hard to keep track of
|
|
Ticket.is_creator_vlidated? now actually fetches the user from the db and returns false if it does not exist.
|
|
email and regarding user fields can be set to defaults based on
created_by user.
If these fields are emptied by the submitting user they will be set to whereas they are nil if they have not been initialized. In that case we will use meaningful defaults from the user who created the ticket.
|
|
We should respect the users choice. We can still get their email from the user id if we really need to.
|
|
|
|
Also renamed help to support so it's harder to confuse it with documentation
|
