How QCUL Quarantines Email and Scheduled Task Side Effects
QCUL quarantines common copied-site side effects so the production-derived laboratory is far less likely to send real mail or run autonomous Joomla scheduled work while you test updates.
Current quarantine
- Sets laboratory mail delivery offline/disabled and reinforces mail isolation at runtime.
- Disables copied Joomla Scheduled Task rows.
- Disables Scheduler/lazy-scheduler system behavior in the lab database.
- Clears copied sessions and remember-me tokens.
- Redirects supported production-origin links/forms/browser requests back into the laboratory.
Why quarantine is not universal sandboxing
A custom extension can call an external API directly outside Joomla mail/Scheduler or generate an encoded remote URL QCUL does not recognize. Avoid irreversible real-world actions and inspect integrations during human review.
Do not re-enable production side effects casually
If a feature needs outbound mail or scheduled execution to test, design a controlled test method rather than turning the copied production automations back on wholesale.
Defense-in-depth principle
How QCUL Quarantines Email and Scheduled Task Side Effects is one layer in QCUL’s security model. Keep Joomla ACL, CSRF tokens, private gate/storage, laboratory identity, runtime authorization, side-effect quarantine, production Super User checks, and careful handling of production-derived evidence together rather than weakening another control to make one workflow more convenient.
Community Discussion
Want to compare update-testing workflows, share practical tips, or discuss how you use this QCUL feature? Visit the QC Update Laboratory Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.