Table of Contents

  1. Introduction

  2. Why Display Issues Occur After an Update

  3. Common Types of Display Problems

  4. Preparing for Updates: Prevention is Better Than Cure

  5. First Steps in Diagnosing UI Problems

  6. Clearing Cache and Browser Data

  7. Theme Compatibility and CSS Conflicts

  8. Broken Menus, Buttons, or Layouts

  9. JavaScript Errors and How to Spot Them

  10. Module Conflicts and Legacy Code

  11. Reverting to a Stable Interface Temporarily

  12. When CustomizeInterface or Oblyon Breaks

  13. Using the Developer Tools in Your Browser

  14. Fixing Language File Issues and Labels

  15. Reporting Issues to the Dolibarr Community

  16. Best Practices for Long-Term Interface Stability

1. Introduction

Dolibarr ERP/CRM evolves rapidly. With each new version come enhancements, fixes, and architectural changes. While this ensures constant improvement, it sometimes leads to display issues—especially if customizations, outdated modules, or browser caches are involved. This article provides a full roadmap to identifying and resolving display issues after updating your Dolibarr instance.

2. Why Display Issues Occur After an Update

Some of the most frequent causes include:

  • CSS or JavaScript changes in core files

  • Old themes or modules no longer compatible

  • Browser cache holding outdated assets

  • Custom code conflicts with new DOM structures

  • Language or translation files missing new strings

These problems are common in open-source ERP platforms where modularity and customization are strong features.

3. Common Types of Display Problems

Here are typical UI problems after updates:

  • Missing menus or items in the sidebar

  • Overlapping buttons or broken layouts

  • Fields not displaying properly

  • Tabs not responding to clicks

  • Blank sections in forms or dashboards

  • Unexpected colors, icons, or fonts

4. Preparing for Updates: Prevention is Better Than Cure

Before upgrading:

  • Backup the full database and file system

  • Deactivate third-party modules temporarily

  • Document any custom themes or CSS

  • Note previous version number and changelogs

  • Test in a staging environment first

Doing these steps reduces your risk and recovery time.

5. First Steps in Diagnosing UI Problems

After updating, if display issues appear:

  1. Open Dolibarr in a private/incognito window

  2. Switch to the default theme (e.g., Eldy)

  3. Compare admin vs regular user screens

  4. Enable the debug mode in conf.php

This helps you isolate whether it’s a cache issue, theme problem, or deeper bug.

6. Clearing Cache and Browser Data

A critical first step:

  • Clear browser cache (CTRL+SHIFT+DEL)

  • Delete Dolibarr’s cache folder: documents/temp/

  • Remove any cached CSS/JS files in theme/

  • Restart the web server (especially after PHP changes)

Many UI problems disappear after cache clearing.

7. Theme Compatibility and CSS Conflicts

If using Oblyon or another custom theme:

  • Ensure it supports the new Dolibarr version

  • Check changelogs for deprecated selectors or classes

  • Restore to Eldy theme and test again

  • Look for overridden .tpl.php or .css files

CSS selectors or template changes in Dolibarr core can silently break visual layouts.

8. Broken Menus, Buttons, or Layouts

Often caused by:

  • Changes in core JavaScript libraries

  • Modified menu positions no longer supported

  • HTML structure updates (like added wrappers)

Solutions:

  • Inspect HTML with browser dev tools

  • Reapply CSS overrides based on the new layout

  • Reset menu positions in module settings

9. JavaScript Errors and How to Spot Them

Use your browser’s developer console (F12 > Console tab):

  • Look for red error messages (e.g., Uncaught ReferenceError)

  • Check which file they originate from (theme, module, or core)

  • Disable plugins one by one to test which causes it

JS errors can stop dropdowns, modals, or AJAX updates from working.

10. Module Conflicts and Legacy Code

After updating Dolibarr, some older modules may:

  • Load outdated jQuery versions

  • Use deprecated hooks or triggers

  • Add broken tabs or actions

Check each third-party module:

  • Deactivate one by one

  • Look for error logs

  • Contact developers for updates

11. Reverting to a Stable Interface Temporarily

To stabilize the system:

  • Use the Eldy theme temporarily

  • Disable all optional modules

  • Reassign permissions from scratch if menus are missing

This lets you work while debugging deeper issues.

12. When CustomizeInterface or Oblyon Breaks

Both modules rely on core UI structures.

  • Check if the new version of Dolibarr altered HTML structure

  • Visit Dolistore for the latest module updates

  • Comment out problematic CSS temporarily

  • Use the module’s debug mode if available

13. Using the Developer Tools in Your Browser

To inspect display issues:

  • Right-click on a broken element > Inspect

  • Check applied styles and inherited rules

  • Test changes live in the browser to fix CSS

  • Review network tab for missing assets (404s)

This is your best ally in resolving front-end problems.

14. Fixing Language File Issues and Labels

After updates, you may notice:

  • Missing translations

  • Old labels not appearing

Fixes:

  • Clear language cache (admin/tools.php?action=clear_langcache)

  • Update your language packs manually if needed

  • Check for file overrides in langs/custom/

15. Reporting Issues to the Dolibarr Community

If all else fails:

The community is active and responsive.

16. Best Practices for Long-Term Interface Stability

  • Avoid modifying core files—use hooks and overrides

  • Keep themes and modules up-to-date

  • Use staging environments to test updates

  • Document any customization done to the UI

  • Join Dolibarr community to follow UI-related updates