Clearing The Browser Cache

If your Zegeba Dashboard or Designer doesn’t show the latest features after an update, the page may be served from your browser’s cache.
Start with a hard reload (does not delete local data). If needed, clear per-site data for your Zegeba server. Avoid a full browser data wipe unless necessary.

Steps

1) Try a Hard Reload (quickest)

• Windows/Linux (Chrome, Edge, Firefox): Press Ctrl+F5 (or Shift+F5).
• macOS (Chrome, Edge, Firefox): Press Cmd+Shift+R.
• Safari (macOS): Press Cmd+Option+R to Reload Page from Origin. Alternatively, enable the Develop menu (Safari ▸ Settings ▸ Advanced ▸ “Show features for web developers”) and use Develop ▸ Empty Caches (Opt+Cmd+E).

Open the Zegeba Dashboard or Designer and check if the newest UI appears. If not, continue.

2) Clear Per-Site Data (recommended)

Google Chrome (desktop)

1. Open: chrome://settings/content/all.
2. In Search sites, type your Zegeba server (e.g., demo).
3. If only your Zegeba site is listed, click Clear displayed data.
4. If multiple sites appear, click the › next to your Zegeba site → Clear data.
5. Reload the Dashboard/Designer and sign in again if prompted.

Alternative (broader): Settings ▸ Privacy and security ▸ Clear browsing data ▸ Cached images and files (time range All time). This affects all sites and may sign you out elsewhere; use only if per-site clearing didn’t help.

Microsoft Edge (desktop)

1. Open: edge://settings/siteData.
2. Search for your Zegeba server.
3. Click the bin icon for the matching site, or open it and choose Clear.
4. Reload Zegeba Dashboard/Designer.

Mozilla Firefox (desktop)

Per-site via Settings

1. Settings/Preferences ▸ Privacy & Security ▸ Cookies and Site Data ▸ Manage Data…
2. Search your Zegeba server → Remove Selected → Save Changes → Remove.
3. Reload Zegeba.

Per-site via the padlock

1. Visit your Zegeba site.
2. Click the padlock in the address bar → Clear cookies and site data… → Remove.

Apple Safari (macOS)

1. Safari ▸ Settings (Preferences) ▸ Privacy ▸ Manage Website Data…
2. Search your Zegeba server → select it → Remove → Done.
3. Reload Zegeba. If the Develop menu is enabled, you can also use Develop ▸ Empty Caches (Opt+Cmd+E).

3) Validate

• Open Dashboard and Designer; confirm latest UI loads.
• If your org shows a release/version badge in the app, verify it matches the expected version.
• If still stale, try an Incognito/Private window, then repeat per-site clearing.

4) Next

• If issues persist, capture a short screen recording and contact your Zegeba admin/support with your browser, OS, Zegeba URL, and the time you tested.

FAQs

Why start with a hard reload?
It requests assets from the server, bypassing cached files without deleting site data. It’s fast and safe.

Will clearing site data delete my work?
It can delete unsent local data stored by the browser. Ensure captures are sent and Designer changes are saved first.

Should I clear all browsing data?
Prefer per-site clearing. A global wipe logs you out of many sites and removes unrelated caches.

Do I need to clear cookies as well?
Usually no—per-site data removal for your Zegeba domain is sufficient. If login/session issues persist, include cookies for that site.

What if hard reload + per-site clear didn’t help?
Try an Incognito/Private window. If it works there, an extension or stored credential may conflict, disable extensions for a test and clear per-site data again.

Does mobile work differently?
Yes, on mobile the App is used, so shutting down the App and restarting it, may solve the issues.

Article ID: 272