jmiller
f5bcc7c457
Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || github.ref_name }}) (push) Successful in 17s
fix(css): reliably load component stylesheets (progress bar was unstyled) The full-screen backup progress bar lost all styling after the CSS moved to the Web Asset Manager: this component's WAM style assets do not emit a <link> on the admin document. The asset resolves without error (Joomla lazily registers media/com_mokosuitebackup/joomla.asset.json, so useStyle does not throw) yet no stylesheet tag is rendered — and the same was already silently true of com_mokosuitebackup.admin (it was just cosmetic, so unnoticed). Confirmed live: neither runbackup.css nor admin.css loads, body stays white, the bar has no track/fill. Attach the external media stylesheets directly to the document (addStyleSheet), which renders reliably via <jdoc:include type="styles">. The joomla.asset.json + useStyle calls are kept so the WAM path resumes automatically if/when it starts emitting. Fixes both runbackup and the profile edit screen. Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i @
Contributing to MokoSuiteBackup
Thank you for your interest in contributing to MokoSuiteBackup.
Getting Started
- Fork the repository on MokoGitea
- Create a feature branch from
dev(feature/your-feature) - Make your changes following the coding standards below
- Submit a pull request targeting
dev
Branch Strategy
main— stable releases onlydev— active developmentfeature/*— new features (targetdev)fix/*— bug fixes (targetdev)hotfix/*— urgent fixes (targetdevormain)
Coding Standards
- PHP 8.1+ required
- Follow Joomla coding standards
- SPDX license headers on all PHP files
- Use
SubscriberInterfacefor event subscription - Use
bind() -> check() -> store()for Table operations
Reporting Issues
Report bugs and feature requests via Issues.
License
By contributing, you agree that your contributions will be licensed under GPL-3.0-or-later.