大家好，
我的 aaPanel 生產環境目前正在運行 PHP 7.2.33，主要用來支撐一套 maccms v10 影片網站系統。
我的網站依賴了以下幾個關鍵的外掛與組件：
- SourceGuardian (SG11) 加密解密擴充
- Redis 快取擴充
因為我的主機商無法提供伺服器層級的快照（Snapshot），一旦透過編譯更新 PHP 失敗或外掛報錯，將很難做到一鍵完美還原。想請教各位前輩，有沒有人已經成功升級 aapanel 這個修補版的 PHP 7.2.35，並且確認像 SG11 這種商業擴充都沒有受到影響的？
另外，在這次的安全性更新中，PHP 7.2 的編譯過程有沒有常見的報錯或相容性坑需要特別注意？
在正式對生產環境動手之前，希望能聽聽大家的實際經驗與建議，謝謝！
Hi,
I am currently running PHP 7.2.33 on my aaPanel production server, powering a maccms v10 video website system.
My setup relies on several essential extensions and components:
SourceGuardian (SG11) loader for encrypted scripts
Redis extension for caching
Because my hosting provider does not support server-level snapshots, I don't have a simple 1-click rollback if something goes wrong during a compiler-based PHP update.
Specifically, I am looking at the aaPanel-patched PHP 7.2.35 build (which is an unofficial backported security update provided by aaPanel, rather than an official release from the PHP team).
Has anyone here successfully updated to this patched 7.2.35 version without breaking third-party commercial extensions like SG11? Also, are there any known compilation errors or compatibility issues on this specific build?
Any feedback or shared experiences would be greatly appreciated before I take the risk on a live production server!
