Custom themes and false bug reports

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • yuri
    Member
    • Mar 2014
    • 8442

    Custom themes and false bug reports

    If you use a custom theme and run into an issue on new versions, try any standard theme before reporting it as a bug.

    For those who create custom themes. Please use upgrade safe ways. Your theme should include the default theme CSS, use CSS variables and add an additional CSS. It should not be a standalone CSS file.

    Also consider not to use a custom theme if it's not upgrade-safe.
    If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.
  • esforim
    Active Community Member
    • Jan 2020
    • 2204

    #2
    What is upgrade-safe? That mean change in the "x" part only? For example "8.1.x"

    Comment

    • yuri
      Member
      • Mar 2014
      • 8442

      #3

      1. The theme includes a CSS of some standard theme.
      2. The theme uses CSS variables.
      3. The theme may add an additional CSS.

      The standard Espo themes are based on the same CSS, mostly only variables are different. Neglect that in fact they are in separate CSS files as it's because of the build optimizer transformed include statements to a CSS code.
      If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

      Comment

      Working...