| Age | Commit message (Collapse) | Author |
|---|
|
If you inherit respond to and call it again in your controller
it will not overwrite the previous but add to it.
Since we always have some exceptions from the rules it's probably
easiest to be explicit in the controllers that require it themselves.
|
|
It used to run the action and then trigger a 500 because the
template was not found.
fixes !3 .
|
|
use_database affects all uses of prepare_database - so also the one
in tmp_database. In order to avoid that we do not use_database but
just overwrite the database method itself.
|
|
We already did the same for other concerns. The way we load models
for couchrest migrations does not work well with concerns in the
model directory as they will be loaded twice.
|
|
for him/herself
So that it we do not expose the is_admin property to anyone else
including other admins.
|
|
feature/expose_admin_in_api
|
|
|
|
We saw errors from duplicate loading of LocalEmail and
LoginFormatValidation. The latter resulted in a crash.
In an attempt to ensure all subclasses of Couchrest::Model::Base are
loaded Couchrest::Model::Utils::Migrate requires all files in app/models.
We have an extension that does the same for the engines.
During this process LoginFormatValidation and LocalEmail were autoloaded
when 'identity' was required. Afterwards they were required again.
It looks like rails' autoload mechanism does not play nicely with require.
So to make sure they are not autoloaded first move the concerns and
helper classes into the lib directory and require them explicitly.
|
|
So that whoever consumes the API can use this attribute to
determine if admin functionalities should be made available to
the current user.
|
|
This expresses the intent rather than the implementation.
Also replace temp with query refactoring.
|
|
There was a lot of special case handling going on in the users_controller
for this. Lot simpler this way.
|
|
There's no route to this right now and it also seems to be tested
nowhere. Since i am about to split up the users_controller let's
get rid of this and put it in the place we want it once we actually finish
the implementation
|
|
Actually this should live in a service_level_controller.
For now fix the security issue.
|
|
Now we test both api versions. We want this for backwards compatibility.
|
|
|
|
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
|
|
This avoids overwriting the PROVIDER_JSON constant in the
StaticConfigController and thus fixes test warnings.
Also moved away from using instance variables in the
ControllerExtension::JsonFile - instead querying the corresponding
functions now - less sideeffects and easier stubbing.
|
|
|
|
and use content_tag inside the icon helper... html_safe is evil.
|
|
|
|
bootstrap3 now requires btn-default if no other btn option is present.
download button on home page was too small in german translation
|
|
import bootstrap-sprockets;
before importing bootstrap in the scss.
bootstrap now uses glyphicons which are based on fonts. So we always should use
a span.
Not sure what to do with big and huge icons yet.
|
|
|
|
exists? is deprecated in ruby 2.1
|
|
Not sure if this does what we need. But for now it fixes the tests
|
|
using twitter/typeahead instead which seems to have similar properties
|
|
|
|
|
|
We can also remove the backports now. :)
|
|
CouchRest > 1.2 does not use RestClient anymore. So we should not try to
catch its errors.
|
|
|
|
|
|
|
|
|
|
create/delete test & tmp users.
|
|
configured auth token.
|
|
token, "tmp" users are users that exist only in tmp db, "test" users are either tmp users or users named "test_user_x"
|
|
are configured in the static config, to be used for infrastructure monitoring.
|
|
the only race condition I can think of here is this...
somebody tries to authenticate with a token that is almost expired.
auth checks and notices it is not expired yet so starts to prolonge it.
Before the polonged token is written to the db the cleanup script discovers that it has just expired.
prolonged token is written to the db
cleanup script fails to delete it from the db as it has been updated.
So what we want in this case is to keep the token alive as it was renewed in the last minute.
|
|
get re-enabled.
|
|
anymore. closes #7690
|
|
general.
|
|
|
|
|
|
|
|
https://github.com/Alster-Hamburgers/leap_web into remove_couponcode
# Conflicts:
# lib/tasks/invite_code.rake
|
|
|
|
Braintree_implementation
|
|
Admin - Ability to enable/disable user
|
|
|
