What to Check If the BESSER Web Modeling Editor Does Not Work as Expected

Updated

Start with the basics: this is a browser-based, JavaScript-driven web application, so most failures trace back to the browser, the network, or a stale cached session. Work through the checks below in order — browser and JavaScript first, then connectivity, then cache and reload, and finally the site's own help or feedback channel if the problem persists. The steps are ordered from fastest to slowest to rule out.

1. Confirm your browser and JavaScript

Because the editor runs entirely in the browser, it depends on a modern browser with JavaScript enabled. If the page loads but nothing is interactive — no canvas, no toolbar response, no menus — JavaScript is the first suspect.

  • Use a current version of a mainstream browser (Chrome, Firefox, Edge, Safari).
  • Check that JavaScript is not blocked: browser settings, an extension such as NoScript, or a corporate policy can disable it.
  • Try a private/incognito window with extensions disabled. If the editor works there, an extension or a conflicting setting is the cause.

Expected result: the editor interface renders and responds to clicks. If it stays blank or static, continue to the next check.

2. Check your network connection

The BESSER Web Modeling Editor is an online tool, so an unstable or filtered connection can break loading, saving, or model operations mid-session.

  • Reload the page on a stable connection and watch whether assets finish loading.
  • If you are on a corporate, campus, or restricted network, a proxy or firewall may block required resources.
  • Try a different network (for example, a mobile hotspot) to isolate the cause.

Expected result: the page and its resources load completely without hanging. If it only fails on one network, the network — not the editor — is the problem.

3. Refresh, then clear cache and reload

A stale cached version of the app is a common cause of odd behavior after an update.

  1. Do a hard refresh first (Ctrl+Shift+R on Windows/Linux, Cmd+Shift+R on macOS).
  2. If that does not help, clear the browser cache and site data for this domain, then reopen the editor.
  3. Sign in again if the session was reset.

Expected result: the editor loads the current version cleanly. If the problem disappears, it was a caching issue.

4. If it still fails, use the site's help or feedback channel

When browser, network, and cache checks all pass and the problem remains, the issue is likely on the service side or specific to your account or model. Look for a help, documentation, or contact/feedback link on the site and report:

  • What you were doing when it failed (which modeling action or view).
  • The exact error message or behavior.
  • Your browser and version, and your operating system.
  • Whether the problem is reproducible in a private window.

Quick triage table

Symptom First check Likely cause
Page loads but nothing is interactive JavaScript enabled, extensions JS blocked or extension conflict
Blank page or assets never finish Network stability, proxy/firewall Connectivity or filtering
Worked before, now behaves oddly Hard refresh, clear cache Stale cached version
Fails only for you, not others Account/session, report to site Session or service-side issue

Key points to remember

  • Rule out the browser and JavaScript before anything else — it is the fastest check.
  • Treat connectivity as a first-class cause, since the editor is online-only.
  • A hard refresh or cache clear resolves many "it suddenly broke" cases.
  • If all local checks pass, report the issue through the site's help or feedback channel with concrete details.