summaryrefslogtreecommitdiff
path: root/app/views/admin/appearances
Commit message (Collapse)AuthorAgeFilesLines
* Show header and footer system messages in emailAlexandru Croitor2019-02-271-0/+9
| | | | | | | | | | | * Add email_header_and_footer_enabled flag to appearances table * Set email_header_and_footer_enabled default value to false * Add checkbox to appearance to toggle show header and footer in emails * Add email_header_and_footer_enabled to allowed params in controller * Add header and footer messages to the html and text email layouts * Remove the color styling for emails header and footer * Add empty_mailer layout for emails without layout, to have the header and footer applied
* Port EE System Header And Footer feature to CEDouwe Maan2019-02-212-0/+25
| | | | | | | | remove EE specific code remove EE licence checks move migration from EE to CE folder structure move specs from EE to CE folder structure remove EE specific flag specs
* Update UI of admin appearance settingsAnnabel Dunstone Gray2019-02-012-85/+90
| | | | | Updates the layout of the admin appearance settings to be consistent with other settings pages across GitLab
* Use header, favicon, and header_logo path in appearances admin formStan Hu2018-12-251-3/+3
|
* Align form labels following Bootstrap 4 docsAnnabel Dunstone Gray2018-09-211-3/+3
|
* Unite green buttons under one css classDmitriy Zaporozhets2018-09-192-2/+2
| | | | | | Rename btn-new, btn-create and btn-save to btn-success Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Remove FaviconUploader favicon_main versiondm-remove-favicon-main-versionDouwe Maan2018-06-151-3/+3
| | | | See https://gitlab.com/gitlab-org/gitlab-ce/issues/47677 for more information
* move favicon admin section upAlexis Reigel2018-06-061-19/+19
|
* hint the allowed image formats on favicon uploadAlexis Reigel2018-06-061-1/+3
|
* remove favicon preview on appearance pageAlexis Reigel2018-06-051-6/+1
|
* use inverted style for remove buttonsAlexis Reigel2018-06-051-3/+3
|
* create favicon overlay on the clientAlexis Reigel2018-06-051-4/+3
| | | | | | | | | | | | | the initial reason for this change was that graphicsmagick does not support writing to ico files. this fact lead to a chain of changes: 1. use png instead of ico (browser support is good enough) 2. render the overlays on the client using the canvas API. this way we only need to store the original favion and generate the overlay versions dynamically. this change also enables (next step) to simplify the handling of the stock favicons as well, as we don't need to generate all the versions upfront.
* call Gitlab::Favicon.status in serializerAlexis Reigel2018-06-051-1/+1
| | | | | | | | | this ways we can keep the `lib/gitlab/ci/status/*` classes to return the bare favicon name as it was before. also the favicon uploader versions are now have the same names as the stock favicons (+ `favicon_` prefix), which makes working with the status names easier.
* show avatar status versions on appearance pageAlexis Reigel2018-06-051-1/+7
|
* allow uploading favicon in appearance settingsAlexis Reigel2018-06-051-0/+17
|
* [skip ci] add col-sm-* for form-horizontal changes to keep layoutClement Ho2018-04-121-5/+5
|
* [skip ci] .input-group-addon to .input-group-prepend, .input-group-appendClement Ho2018-04-121-1/+1
|
* [skip ci] .form-horizontal => .form-group.rowClement Ho2018-04-121-6/+6
|
* [skip ci] .control-label to .col-form-labelClement Ho2018-04-111-5/+5
|
* [skip ci] Replace .pull-right with .float-rightClement Ho2018-04-091-1/+1
|
* Add custom brand text on new project pagesMarkus Koller2017-12-042-13/+25
|
* When a custom header logo is present, don't show GitLab type logoDrew Blessing2017-11-151-1/+1
| | | | | | | | In the new navigation header, when a user uploads a custom header logo GitLab will still show the 'GitLab' type logo. This is often undesirable as the user may want to upload a logo with their own name present. This change will toggle the GitLab type logo if a custom header logo is present.
* Change all instances of btn-sm to btn-small to keep things consistentJedidiah2017-09-191-2/+2
|
* Merge branch 'fix-links-target-blank' into 'security'Jacob Schatz2017-03-201-1/+1
| | | | | | Adds rel="noopener noreferrer" to all links with target="_blank" See merge request !2071
* Change show-gl-field-errors to gl-show-field-errorsBryce Johnson2016-11-021-1/+1
|
* Use Ruby 1.9 syntax in tab_single def and usage.Bryce Johnson2016-10-151-1/+1
|
* Make UX upgrades to SignIn/Register views.Bryce Johnson2016-10-151-7/+10
| | | | | | | - Tab between register and sign in forms - Add individual input validation error messages - Validate username - Update many styles for all login-box forms
* Fix markdown help referencesClement Ho2016-08-261-1/+1
|
* Update the help_page_path route to accept paths directly instead of using ↵Connor Shea2016-07-111-1/+1
| | | | parameters.
* Merge branch 'dz-fix-appearance-preview' into 'master' Jacob Schatz2016-06-212-28/+8
|\ | | | | | | | | | | | | Fix admin appearance settings preview Render appearance settings preview in devise layout instead of implementing it 2 times. See merge request !4792
| * Fix admin appearance settings previewdz-fix-appearance-previewDmitriy Zaporozhets2016-06-202-28/+8
| | | | | | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* | Put some admin settings in dropdowndz-admin-tabs-dropdownDmitriy Zaporozhets2016-06-201-5/+7
| | | | | | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* | Move appearance settings as sub tab to application settingsdz-admin-tabsDmitriy Zaporozhets2016-06-201-5/+5
|/ | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Standardize the way we check for and display form errorsrs-form_errorsRobert Speicher2016-04-041-4/+1
| | | | | | | | | | | | - Some views had a "Close" button. We've removed this, because we don't want users accidentally hiding the validation errors and not knowing what needs to be fixed. - Some views used `li`, some used `p`, some used `span`. We've standardized on `li`. - Some views only showed the first error. We've standardized on showing all of them. - Some views added an `#error_explanation` div, which we've made standard.
* Branded login page also in CE11489-branded-appearance-to-ceZeger-Jan van de Weg2016-02-263-0/+94
The only major difference with the EE version is the change from a light and dark logo to only a header logo The dark logo wasn't used anyway, so it seemed to make sense to me to rename the field to the actual function of it
View Lorry Controller Status