MokoConsulting/mokoplatform
1
0
Fork 0
Code Issues 9 Pull Requests Releases 8 Wiki Activity

feat(validate): add check_client_theme.php + update client detection #68

New Issue
Closed
opened 2026-05-23 23:12:59 +00:00 by jmiller · 0 comments
jmiller commented 2026-05-23 23:12:59 +00:00
Owner
Copy Link
Copy Source

Summary

PR #67 on dev adds support for client WaaS theme packages (Joomla type="file").

New: validate/check_client_theme.php

Validator for client theme packages:

  • Manifest: required elements (name, element, version), type="file", method="upgrade", XX.YY.ZZ version format
  • Required files: light.custom.css, dark.custom.css
  • PHP syntax check on script.php
  • CSS brace balance + BOM detection
  • Version consistency (manifest vs updates.xml vs CHANGELOG)
  • Image size warnings (>1MB)

Updated: validate/auto_detect_platform.php

Client detection now recognises type="file" manifests in src/templateDetails.xml as client repos (theme packages), alongside legacy sftp-config/monitoring detection.

Context

Client repos (client-waas-*) now use Joomla file packages instead of raw site deployments. The CI workflow (ci-client.yml) calls check_client_theme.php for validation. Already deployed to:

  • OptainFunding/client-waas-optainfunding
  • ClarksvilleFurs/client-waas-clarksvillefurs
  • MokoConsulting/Template-Client-WaaS

PR

PR #67 is ready to merge when dev is free.

Generated with Claude Code

## Summary PR #67 on dev adds support for client WaaS theme packages (Joomla `type="file"`). ### New: `validate/check_client_theme.php` Validator for client theme packages: - Manifest: required elements (`name`, `element`, `version`), `type="file"`, `method="upgrade"`, XX.YY.ZZ version format - Required files: `light.custom.css`, `dark.custom.css` - PHP syntax check on `script.php` - CSS brace balance + BOM detection - Version consistency (manifest vs `updates.xml` vs CHANGELOG) - Image size warnings (>1MB) ### Updated: `validate/auto_detect_platform.php` Client detection now recognises `type="file"` manifests in `src/templateDetails.xml` as client repos (theme packages), alongside legacy sftp-config/monitoring detection. ### Context Client repos (`client-waas-*`) now use Joomla file packages instead of raw site deployments. The CI workflow (`ci-client.yml`) calls `check_client_theme.php` for validation. Already deployed to: - `OptainFunding/client-waas-optainfunding` - `ClarksvilleFurs/client-waas-clarksvillefurs` - `MokoConsulting/Template-Client-WaaS` ### PR PR #67 is ready to merge when dev is free. Generated with Claude Code
Sign in to join this conversation.
Labels
Clear labels
automation
Automated processes or scripts
 breaking-change
Breaking API or functionality change
 build
Build system changes
 ci-cd
CI/CD pipeline changes
 config
Configuration file changes
 css
CSS/styling changes
 dependencies
Dependency updates
 deploy-failure
Automated deploy failure tracking
 docker
Docker configuration changes
 documentation
Documentation changes
 dolibarr
Dolibarr module or extension
 generic
Generic project or library
 good first issue
Good for newcomers
 health-check
Repository health check results
 health: excellent
Health score 90-100
 health: fair
Health score 50-69
 health: good
Health score 70-89
 health: poor
Health score below 50
 help wanted
Extra attention needed
 html
HTML template changes
 javascript
JavaScript code changes
 joomla
Joomla extension or component
 mokostandards
MokoStandards compliance
 needs-review
Awaiting code review
 php
PHP code changes
 push-failure
File push failure requiring attention
 python
Python code changes
 security
Security-related changes
 size/l
Large change (101-300 lines)
 size/m
Medium change (31-100 lines)
 size/s
Small change (11-30 lines)
 size/xl
Extra large change (301-1000 lines)
 size/xs
Extra small change (1-10 lines)
 size/xxl
Extremely large change (1000+ lines)
 standards-drift
Repository drifted from MokoStandards
 standards-update
MokoStandards sync update
 sync-failure
Bulk sync failure requiring attention
 sync-report
Bulk sync run report
 template-validation-failure
Template workflow validation failure
 tests
Test suite changes
 type: bug
Something isn't working
 type: chore
Maintenance tasks
 type: enhancement
Enhancement to existing feature
 type: feature
New feature or request
 type: refactor
Code refactoring
 type: version
Version-related change
 typescript
TypeScript code changes
 version
Version bump or release
 version-drift
Version mismatch detected
 work-in-progress
Work in progress, not ready for merge
No labels
Priority Medium
Type Feature
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/mokoplatform#68
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?