2 Commits

Author	SHA1	Message	Date
johnnyq	172cd4933e	Turn cron on by default for new installs so adding the cron job is the only step - database 3.6.2 changes the default of settings.config_enable_cron to 1 and nothing else, so an existing install keeps its setting on or off, and setup/seed_data.php sets it for both setup paths; Get started's cron step is now Add the cron job with a line for hosting control panels such as Jabali, HestiaCP and cPanel, and shows Turn cron back on only when someone has switched it off; the setup page and setup_cli no longer say cron ships off, CONTRIBUTING's master switch section explains the new default, changelog updated	2026-11-06 14:26:50 -05:00
johnnyq	58e502ad38	Add Get started, a guided walk through what is left to set up after installing (cron, email, backups, billing, support, the team, starter content and a first client), each step a short form of its own with Skip for now and ticked off from the settings themselves, shown to the first admin to sign in on a new install and as a Finish setting up card on the dashboard until done, skipped or dismissed, and in Admin > Get started any time; database 3.4.7 adds settings.config_getting_started (on for a new install, off for an updated one), config_getting_started_skipped and config_getting_started_opened_at; the mail server check moves to settingsMailServerCheck() for Admin > Mail and the Email step, app.js only starts DataTables where it is loaded, and setup's finish step points at Get started	2026-10-25 14:28:17 -04:00