Age | Commit message (Collapse) | Author |
|
|
|
Feature/rename ticket title to subject
|
|
|
|
|
|
* ensure that we only copy files for customization when restarting the app (#1300)
not every time a rake task is run (especially since some rake tasks get run
as root!)
* improvements to the download button
(proper localization, better image, better hooks for customization)
* added support for easier customizations via "config/customization" directory (#1300)
* log json request errors and their backtraces
* show Ticket with the appropriate error messages. (*4453)
* update readme to require ruby 1.9.3 instead of 1.8
* Token.destroy_all_expired to cleanup expired tokens (#4411)
* use the account lifecycle from UsersController#destroy (#4216)
* destroy all tickets created by a user when account is destroyed (#4216)
* integration test for blocking handles after account destroyed (#4216)
* disable identities to block handles after a user was deleted (#4216)
* notify user their account was successfully deleted (#4216)
* Fix button to enable account (#4246)
|
|
|
|
Feature/customize
|
|
|
|
time a rake task is run (especially since some rake tasks get run as root!)
|
|
image, better hooks for customization)
|
|
|
|
make sure we log json request errors and their backtraces
|
|
Feature/cleanup expired tokens
|
|
|
|
Maybe not ideal fix, but since there is no edit view, we want to show th...
|
|
|
|
show view with the appropriate error messages.
|
|
Feature/clear data of deleted user
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In order to keep the users engine independent of the tickets engine i added a generic load hook to the account model. The tickets engine then monkeypatches the account destruction and destroys all tickets before the user is destroyed.
The tickets are destroyed first so that even if things break there should never be tickets with an outdated user id.
I would have prefered to use super over using an alias_method_chain but I have not been able to figure out a way to make account a superclass of the account extension and still refer to Account from the users engine.
|
|
We'll use this to clean up after user destruction
|
|
|
|
has not been run yet.
|
|
also test one can't login anymore after destroying the account.
|
|
This is mostly for cleaning up after tests so far. But we might expand this to destroy all identities disabled before a certain date.
|
|
|
|
This way the identity model defines how identities should be disabled. We currently still destroy them. But it will be easy and nicely isolated to change this next.
|
|
notify user their account was successfully deleted (refs #4216)
|
|
* reset button state from 'loading...' after failed login attempt
(#4231)
* use https sources in Gemfiles and documentation(#4109)
* include Gemfile.lock to prevent unintended updates (#4174)
* fixed download urls to get latest versions for mac, android and
windows
* test api login with umlauts in password
|
|
Currently it expects both the session and the token to be cleared. This might change. But we'll always have a definition of what it means to logout we can test this way.
|
|
Also fixes a cornercase when admins deleted their own account. So far they would be redirected to the users list - which then refused access. Now they'll be redirected to the home landing page as well.
|
|
|
|
reset button loading... state on error (#4231)
|
|
|
|
including test
refactored error display some
|
|
|
|
|
|
|
|
test login through the API using python with umlauts
|
|
|
|
|
|
I don't think we need to list the sources again in common_dependencies.rb
|
|
They did not point directly to the download.
|
|
We had a broken production server lately because it had upgraded the couchrest model dependency to one that had a different naming scheme for a function we overwrite. So that broke production.
Let's prevent that by including the Gemfile.lock in our repositories.
|
|
|