| Age | Commit message (Collapse) | Author |
|---|
|
the masthead can only handle content of a limited width.
Alternatively we could make the masthead title wider and add padding on the left so it still aligns nicely with the mask. However the wider we make it the worse it looks on small width displays.
Another option would be to make the masthead contain multiple lines. However vertical aligment to the middle of 1 OR 2 lines of text is a real pain.
So I went with a super simple masthead and the Caption goes below.
|
|
hide srp forms when no js is available
|
|
|
|
|
|
Hiding them using two mechanisms in case one fails:
.hidden class - bootstrap hides them then
style='display:none' - so they are hidden even if css load fails
|
|
adopt pricing view to current service_level format
|
|
|
|
keeping the platform detection for now.
|
|
To use bitmask services:
Download Bitmask
|
|
|
|
the loading... text on the buttons was not capitalized before.
So in order to change this in a (more or less) single place i added
new button types to simple_form:
button :wrapped - normal button, with loading and an optional cancel button wrapped in the classical bootstrap action div.
cancel option contains the url to go to when canceling.
button :loading - simple button with loading text capitalized by using i18n (simple_form.buttons.loading)
Conflicts:
engines/support/app/views/tickets/new.html.haml
|
|
Feature/api quota support + current_user null pattern
|
|
let's devide the partials rather than having super specific parameters (on_user_page)
|
|
|
|
The changes to the configuration required some non minor changes to the platform and also added some flexibility we don't require yet - and thus some new possibilities for errors.
So instead we still use the allow_..._certs and ..._cert_prefix options.
They basically provide the framework in which service levels can operate.
The service level configuration will not include the cert prefix anymore.
It only states if the service level is rate limited or not.
This avoids conflicts between the two configuration options.
I also removed the anonymous service level entirely.
It was also turning a boolean decision (do we provide anonymous eip or not) into something way more complex. Instead I added the AnonymousServiceLevel class to handle the corner cases for people who are not logged in.
Furthermore i renamed the UnauthenticatedUser to AnonymousUser so it matches the Anonymous Service Level nicely. It's also shorter and more intuitive.
|
|
|
|
|
|
|
|
|
|
flexible.
|
|
contact.
|
|
|
|
|
|
APP_CONFIG[:braintree] into APP_CONFIG[:billing][:braintree]
|
|
Conflicts:
billing/config/locales/en.yml
|
|
we were only using Users#show to redirect to the edit action. So I replaced that with the overview and we have no more use for the extra controller.
This also simplifies linking to the users in question a lot.
|
|
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.
|
|
customer in any way.
|
|
|
|
identities controller will replace it.
|
|
specify which gems for which environments.
Here, we have the billing gem included for the development and test environments only, hardcoded in the Gemfile.
Then we show the links to billing based on a config file setting. The setting itself could be used to specify different types of billing, but isn't yet.
|
|
|
|
disable, must remove billing engine from Gemfile (and re-bundle)
|
|
Feature/identity rewrite
|
|
|
|
Conflicts:
app/views/home/index.html.haml
|
|
|
|
customer.
|
|
PGP setting has been moved into account settings. It's using the API now issueing an Ajax request without any visual feedback.
This obviously is not what we want but it hopefully suffices for uploading gpg keys for testing purposes before the Identity UI is in place.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Conflicts:
app/views/layouts/_messages.html.haml
app/views/layouts/application.html.haml
users/app/assets/javascripts/users.js.coffee
|
|
|
|
|
|
|
|
admins) or stay as a nested resource for a particular user (for normal users and when you visit the tickets list of a particular user).
|
