NeoFrag Reborn 1.2.13

Added

• The error log, in the administration (System → Monitoring → Error log). No more need for FTP or server access to know what failed: the site's errors, grouped, from most recent to oldest, sorted by severity, filterable by period or by word. The installation path, passwords, keys and tokens are masked on screen, email and IP addresses partly; the file can be downloaded and emptied (the old one is kept alongside). Monitoring flags errors from the last 24 hours, and a logs/ folder the site can no longer write to.
• Diagnostic tools are turned on from the administration (Monitoring → Diagnostics), for one hour, without editing config/neofrag.php over FTP:
  • debug mode — what it displays, the bar at the bottom of the page and error details, is now shown only to logged-in administrators; when on, it was displayed to all visitors, queries and visit data included;
  • the page trace, which can finally be read in the administration: the latest pages served, their queries and their duration, with sensitive values masked;
  • the translation check, with the list of missing texts per language and per extension; the flag it adds in front of translated texts is now shown only to administrators.
• The administration organized into nine sections: Content, Community, Activities, Gaming, Knowledge, Media, Outreach, Support, Monetization (and System). The previous six mixed the calendar with media or the Bugtracker with community, and thirteen modules ended up in "Other modules".
• The live editor's "Navigation" menu follows the same sections, as collapsible submenus, with a search; it lined up more than forty pages one after another.
• The site address can be corrected from the administration (Monitoring → Site address). After a domain change, email links still led to the old one until you edited config/url.php over FTP.
• A reference for every error. A visitor who hits an error reads an eight-character reference; the administrator searches for it in the log and lands on the right line.
• Times in everyone's own time zone. A member chooses their time zone in their profile; failing that, the site uses their browser's, and failing that the site's, a new setting in Settings → General Preferences. Times entered in forms are understood in the time zone of whoever enters them. The time zone list is grouped by region, with cities named in the site language.

Fixed

• Times are no longer off. The site displayed them in server time — universal time — for everyone: two hours behind for a visitor in France in summer. The member profile's time zone, for its part, applied only on profile pages, and shifted the dates that member saved. The calendar, the wiki, the Bugtracker, archived conversations and the file manager wrote their times without conversion; the web radio's "live" show was read in server time.
• The calendar: the start and end of an event are chosen in a date picker, and no longer in a text field in "YYYY-MM-DD HH:MM:SS" format; an accented title no longer shows as "journée"; the formatted description no longer shows its markup; the calendar export receives clean text.
• Lists with search say "No results" in the site language, not "No results found".
• The live editor now offers to lay out the Forum, Galleries, Teams, Contact and Awards pages: its menu left them out, as it did not recognize their home page.
• A page that crashes says "An error occurred" (500), with its reference, instead of "Page not found", which suggested a wrong address.
• No more blank pages. A fatal error, or an error raised outside a page, displays an error page in the visitor's language. So does an unreachable database (503), instead of a raw English message, and the outage is finally recorded in the log.
• A failing action says so: a dialog that does not open, a rejected submission, a server that no longer responds display a message, with the error reference — instead of a button left grayed out without a word. Monitoring, when it fails to refresh, stops its hourglass.
• Backup and update tell the truth. They announced "Backup saved" or "Update completed successfully" even after a failure; they now announce success only if the server confirms it, and otherwise say what failed. The backup also checks that it actually wrote its archive: in a non-writable folder or on a full disk, it reported success — and the update, which relies on it to roll back, would have had nothing to restore.
• A form field's error is shown under the field, and no longer only when hovering over a small icon.
• Two internal errors no longer leave a trace in the log: a form submitted without one of its fields, and a database query that returns nothing to read — the latter crashed the page.
• The debug bar displays again: a numeric value crashed it since the code started checking its types strictly, and its timeline was wrong.
• The update announcement is visible again. It had shrunk to a colorless "1.2.x" in the top bar: a cleanup of the administration styles had swept away its own. It gets back a box under the logo — "Update available · NeoFrag X.Y.Z" — and a readable badge in the top bar.
• The update window showed an empty block and left a warning in the log: it now says which version is coming, that the site is backed up before starting and returns to its previous state on failure, with a link to what the version brings.

Removed

• NEOFRAG_LOGS_DB, which nothing read: new installations no longer write it to config/neofrag.php. An existing installation can keep it; it has no effect.