Mercurial > kallithea
view docs/usage/debugging.rst @ 7044:eaf600434cf5
less: change markup and styling for the logo shown in the top left corner
Based on work by Dominik Ruf, but in this changeset, the goal is just to
improve markup and styling while keeping exactly the same look and feel. In
that process, it also fixes some browser specific issues that gave odd
spacing/positioning.
All styling (especially the logo image URL) is moved to CSS/LESS, using
background-image styling instead of an img tag.
The logo image is made a :before on the site branding text and will usually
have to align with this text, so we use inline-block to align to the baseline.
We set the right amount of negative margin-bottom so the image can go below the
baseline.
We use a "big enough" negative margin-top to allow the image to bleed outside
the line height and into the 12px top padding.
We assume the background image doesn't need cropping or panning and do thus not
set background-size, background-position, or background-repeat.
| author | Mads Kiilerich <mads@kiilerich.com> |
|---|---|
| date | Mon, 27 Nov 2017 02:55:44 +0100 |
| parents | 87ac42db389c |
| children |
line wrap: on
line source
.. _debugging: =================== Debugging Kallithea =================== If you encounter problems with Kallithea, here are some instructions on how to debug them. .. note:: First make sure you're using the latest version available. Enable detailed debug --------------------- Kallithea uses the standard Python ``logging`` module to log its output. By default only loggers with ``INFO`` level are displayed. To enable full output change ``level = DEBUG`` for all logging handlers in the currently used .ini file. This change will allow you to see much more detailed output in the log file or console. This generally helps a lot to track issues. Enable interactive debug mode ----------------------------- To enable interactive debug mode simply comment out ``set debug = false`` in the .ini file. This will trigger an interactive debugger each time there is an error in the browser, or send a http link if an error occurred in the backend. This is a great tool for fast debugging as you get a handy Python console right in the web view. .. warning:: NEVER ENABLE THIS ON PRODUCTION! The interactive console can be a serious security threat to your system.