Skip to content

Saving and persistence

Change and save in one place

  • Per-section save – Each section usually has its own Save (or Apply) action. Change options in the panel and click Save. The request is sent to the FleekDash backend (e.g. REST API); success toast or message confirms. Unsaved changes may be lost if you switch section without saving (depending on implementation).

  • Validation – Required fields or invalid values may block save and show inline or toast errors. Fix the values and save again.

  • Persistence – Saved settings are stored by the backend (WordPress options or FleekDash API). They persist across sessions. Refreshing the page or reopening the section loads the saved values.

  • License – License Activation has its own flow: enter key → Activate; Deactivate or Refresh to update status. License state is used for plan and feature access across FleekDash.

Benefit: Change and save in one place; no hunting for "where did I save that?"