ExtensionFlow Platform Changelog

Security 1

• Blocked downloadsource entries that point back to the current platform domain so fallback sources remain real external mirrors instead of redundant self-references.

Fixed 2

• Fixed public UI spacing and translation edge cases on extension lists, release pages and the platform status panel, including compact status alignment, percentage spacing and translated extension type labels.
• Separated translated UI labels from export labels so Russian admin headings no longer leak into generated Markdown or Joomla XML output.

Language 1

• Completed a Russian localization pass across public catalog pages, release detail pages, status pages, admin registries, roadmap screens and release forms, including lifecycle warnings such as Joomla/PHP/database EOL and security-only states.

Added 5

• Exposed stored SHA256, SHA384, SHA512 and MD5 checksums on release artifacts with copy actions in both public release pages and admin artifact metadata panels.
• Added Joomla downloadsource fallback URL management so update XML can publish external mirror URLs after the primary downloadurl, with URL normalization and one-line XML output.
• Extended release artifact handling beyond ZIP so the platform can accept ZIP, TAR, TAR.GZ/TGZ, TAR.BZ2/TBZ2 and TAR.ZST/TZST files while rendering Joomla-compatible format values such as zip, gz and bz2.
• Introduced release_download_artifacts so a single release can expose multiple active archive variants as separate Joomla downloadurl entries, each with its own UUID, format, size, status, priority, primary flag and checksums.
• Added cross-group drag-and-drop for changelog items and roadmap cards, plus Markdown export/download workflows for roadmap data alongside changelog Markdown, Joomla XML and HTML previews.

Changed 6

• Changed release archive storage to writable/uploads/releases/<extension-alias>/<release-version>/ so all archive variants for one extension release live together in a predictable directory layout.
• Removed duplicated release detail metadata by making the download variants block the single source of truth for artifact format, size, download actions and checksums, with checksum rows hidden inside accordions.
• Refined the admin release artifact form: metadata now sits under each archive, download/copy/delete actions moved to the artifact header, new archive rows use server-side Auto format detection and primary selection is only available after an artifact is saved.
• Polished admin controls with styled switches, custom select dropdowns, improved dropdown width calculation, custom scrollbars, safer inline-code spacing, compact checksum rows and a top-bar language switcher.
• Refined Changelog Builder cards, placeholders, import panel styling, enable switches, copy/download actions and sample Markdown downloads while keeping exported Markdown/Joomla XML section names canonical.
• Refined Roadmap Builder layout, filters, item headers, public switches, toolbar actions and translations while keeping exported Markdown lanes canonical as Now, Next, Later and Backlog.

Added 4

• Added public and admin system-status pages with health checks, platform metrics, incident history, scheduled maintenance events and availability summaries.
• Added AJAX filtering for admin extension, release and database-version registries while keeping normal GET fallback URLs.
• Introduced a Joomla ↔ PHP compatibility matrix so selecting Joomla lines can preselect the appropriate PHP range and remove stale PHP selections when Joomla support changes.
• Added a compatibility baseline seed so fresh installs immediately receive current Joomla, PHP, database and changelog registry defaults.

Changed 3

• Refined the public catalog, extension pages, release tables and documentation hub with cleaner navigation, compact filters and AJAX search flows.
• Reworked release and extension edit forms into compact sections with sticky save actions, read-only artifact metadata and clearer private/archived release behavior.
• Normalized database compatibility around product lines and lifecycle states: Supported, Extended support, EOL, Future and Inactive. SQL Server now uses major product lines instead of build numbers.

Added 1

• Expanded public documentation into wiki-style sections with admin release fields, extension fields and compatibility registry guides.

Changed 3

• Polished the database compatibility registry so engines and version rows remain readable, filterable and sorted with newest practical product lines first.
• Added distinct Joomla and PHP compatibility badge colors to make supported target lines easier to scan on public product, release and documentation pages.
• Made public platform and extension changelog timelines more compact by replacing oversized count/detail blocks with small meta pills and inline detail links.

Added 1

• Added platform-level documentation file rendering on the documentation hub for platform ADRs, architecture notes, API references and internal seed notes.

Changed 1

• Separated platform documentation from product documentation: ExtensionFlow ADRs, ERDs, API notes and seed/migration files now belong to platform docs instead of extension docs.

Changed 1

• Reset extension and release documentation pages to a simple placeholder while keeping platform documentation unchanged. Product-specific documentation references and CTA-specific seeded guides are disabled until a cleaner model is reintroduced.

Added 1

• Added documentation references so ADRs, PDFs, architecture notes and internal docs files can be attached to an extension documentation page without registering them as extension artifacts.

Added 1

• Added a public portal field and button reference that explains the catalog, extension overview, documentation, changelog, roadmap, status and download actions.

Added 5

• Rebuilt the Changelog Builder around individual items with enable/disable state, sorting, drag handles, Markdown import, clear-all workflow and live previews.
• Added Joomla-compatible <changelogurl> XML endpoints with security, fix, language, addition, change, remove and note nodes generated from enabled changelog items.
• Added an extension-level Roadmap Builder with lanes, status, priority, target version, target date, Markdown import and public roadmap pages.
• Added seed migrations for Baby in Brazil CTA 1.0.9 through 1.0.13, Baby in Brazil Stats 1.0.0 through 1.0.2, and their separated language packs.
• Converted the global ExtensionFlow changelog from static view content into a seeded, database-driven platform changelog.

Changed 3

• Changed public changelog pages into timeline views with left-side navigation, version cards and HTML-rendered Markdown instead of raw Markdown text.
• Public roadmaps now use the same navigation principle as changelogs: left-side table of contents, right-side roadmap cards with descriptions and metadata.
• Compact relationship manager now uses collapsed child cards and a full-policy Add Child modal for staging multiple artifacts before saving.

Security 1

• Centralized public-access checks so private extensions cannot be opened, downloaded or exposed through update XML by direct URL.

Added 4

• Added child artifact relationships for libraries, plugins, language packs, optional add-ons and dependent add-ons.
• Language packs can now be hidden from the top-level catalog while still appearing inside the parent extension with their own detail page, changelog, download and update feed policy.
• Added database engine/version management and normalized supported_databases data for Joomla update XML.
• Seeded multiple historical Joomla extensions, packages, templates, modules, plugins, libraries and translation packs with checksums and real ZIP payloads.

Changed 2

• Changed the public catalog from a flat list of Joomla technical records into a product-level catalog that highlights packages and standalone extensions.
• Archived extensions and releases remain viewable as historical records, but downloads and update-feed delivery are blocked.

Security 1

• Removed CDN dependencies from public, admin and auth layouts so the strict Content Security Policy can stay enabled in production.

Fixed 1

• Aligned the application package with CodeIgniter 4.7.3 runtime behavior, including required filter aliases, controller property compatibility and cache-safe throttling keys.

Added 3

• Completed authentication, password reset, remember-me sessions and role-based access control workflows for Super Administrator, Administrator, Editor and Viewer roles.
• Implemented secure release ZIP storage under writable, controlled download routing, checksum generation and download tracking.
• Added production seed migrations for the first Joomla extension releases, including Baby in Brazil CTA release history.