Troubleshooting Common Issues in Eschelbacher Enterprises WebEditor

Troubleshooting Common Issues in Eschelbacher Enterprises WebEditor

Keeping your site running smoothly with Eschelbacher Enterprises WebEditor requires knowing how to diagnose and fix common problems quickly. This guide covers frequent issues, step-by-step troubleshooting, and preventive tips.

1. Editor won’t load or is blank

• Possible causes: network issues, browser cache conflicts, incompatible extensions, or service outages.
• Steps to fix:
  1. Reload the page (Ctrl/Cmd+R).
  2. Clear browser cache for the site and reload.
  3. Open in Incognito/Private mode to rule out extensions.
  4. Try a different browser (Chrome, Firefox, Edge).
  5. Check service status (status page or admin console) for outages.
  6. If the problem persists, capture console errors (F12 → Console) and contact support with the error messages.

2. Changes not saving or revert after publish

• Possible causes: session timeout, permission conflicts, server-side validation errors, or concurrent edits.
• Steps to fix:
  1. Confirm user permissions for the page/resource.
  2. Save drafts frequently; use explicit “Save” before “Publish.”
  3. Check for validation errors shown in the editor and address them.
  4. Look for concurrent edits: coordinate with other users or use versioning features.
  5. Verify server timeouts and extend session duration if necessary.
  6. Review logs for failed save requests (network tab in DevTools).

3. Media (images/videos) fail to upload or display

• Possible causes: file size/type restrictions, CDN issues, wrong file paths, or permissions.
• Steps to fix:
  1. Confirm allowed file types and max size; resize or convert files if needed.
  2. Upload via the media manager rather than drag-and-drop to surface errors.
  3. Check file URLs in the rendered HTML and ensure they point to the correct CDN or storage.
  4. Verify CDN/storage credentials and permissions.
  5. Clear CDN cache after replacing media.
  6. Inspect network requests to the media endpoint for error codes (403, 404, 413).

4. Formatting/CSS changes not appearing on site

• Possible causes: caching, stylesheet order, or selector specificity.
• Steps to fix:
  1. Hard-refresh the page (Ctrl/Cmd+Shift+R) to bypass browser cache.
  2. Clear server/CDN caches and any caching plugins.
  3. Inspect computed styles in DevTools to see which rule overrides yours.
  4. Ensure stylesheet is loaded after theme defaults or increase selector specificity.
  5. Use versioned asset filenames (e.g., style.v2.css) to force updates.

5. Broken links or routing errors

• Possible causes: moved pages, incorrect slugs, or rewrite rules.
• Steps to fix:
  1. Run a link checker to list broken links.
  2. Verify page slugs/paths in the page settings.
  3. Check routing rules or .htaccess/nginx configs for recent changes.
  4. Implement 301 redirects for moved pages and update internal links.

6. Slow editor performance

• Possible causes: large pages, many plugins/widgets, slow network, or client machine limits.
• Steps to fix:
  1. Close unnecessary tabs/apps and try again.
  2. Break large pages into smaller sections or lazy-load widgets.
  3. Disable nonessential plugins/widgets temporarily.