Jump to content

ICT:VisualEditor

From Costa Sano MediaWiki
Revision as of 10:26, 27 December 2025 by Mngr (talk | contribs) (Nieuwe pagina aangemaakt met '= VisualEditor – Operator Summary = This page provides a short operational overview of how VisualEditor works on this MediaWiki installation. It is intended for day‑to‑day administrators who need a quick reference without reading the full technical documentation. == Status == * VisualEditor is '''enabled and fully functional'''. * No special reverse‑proxy rules are required. * No Parsoid service is running externally; MediaWiki uses its built‑in…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

VisualEditor – Operator Summary

This page provides a short operational overview of how VisualEditor works on this MediaWiki installation. It is intended for day‑to‑day administrators who need a quick reference without reading the full technical documentation.

Status

  • VisualEditor is enabled and fully functional.
  • No special reverse‑proxy rules are required.
  • No Parsoid service is running externally; MediaWiki uses its built‑in REST interface.
  • If MediaWiki works with clean URLs, VisualEditor works as well.

Key Files

  • All configuration lives in: LocalSettings.php
  • The VisualEditor block is clearly marked between:
 * #---VisualEditor -----------  
 * #---end VisualEditor --------------

What to Check After Upgrades

  • /rest.php loads without errors.
  • /api.php loads normally.
  • Editing a page opens VisualEditor.
  • Saving works without warnings.
  • Browser console shows no REST or CORS errors.

If all of the above succeed, VisualEditor is healthy.

When Problems Occur

  • VisualEditor stuck on loading:
 Check browser console → REST errors usually indicate /rest.php not reachable.
  • 403/404 errors:
 Check Apache vhost and SELinux (if enforcing).
  • Mixed content warnings:
 Ensure $wgServer uses https://mwiki.costasano.club.

Where to Find Full Documentation

See: ICT:VisualEditor installation for the complete explanation, configuration snippet, and troubleshooting details.