Changes between Initial Version and Version 1 of Ticket #65395, comment 8
- Timestamp:
- 07/07/2026 10:54:56 AM (6 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #65395, comment 8
initial v1 1 I tested this on a local WordPress 7.0 installation with OPcache enabled via php.ini. After restarting the web server, phpinfo() reported Zend OPcache as "Up and Running," and WordPress Site Health correctly displayed "Opcode cache is enabled." I was not able to reproduce the reported issue in my local environment. The issue may be specific to certain shared hosting environments where OPcache management functions are restricted.1 I tested this on a local WordPress 7.0 installation with OPcache enabled through php.ini. After restarting the web server, phpinfo() confirmed that Zend OPcache was Up and Running, and WordPress Site Health correctly reported that Opcode cache is enabled. I was able to reproduce the reported behavior in my local environment. Based on my testing, this issue may be specific to certain shared hosting environments where OPcache management functions are restricted or unavailable.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)