Issue Opcode cache Issue

[anthonydclark]

Server operating system version

Debian 11

Plesk version and microupdate number

18.0.77 #5

Please could you bear with me as I have limited knowledge here and currently pulling my hair out on things.

In Wordpress a message has appeared about Opcode Cache not being enabled.
I have checked the PHP version of the website that is 8.3.31.

I have logged into Plesk that confirms the PHP version as being 8.3.31 and under the 8.3.31 FPM application the Opcache is enabled!
In the PHP Settings in Plesk it is stating that Opcache is turned on and enabled with verison 8.3.31 PHP support.
Could anyone shed any light why indeed that Wordpress thinks it is not enabled?

The website is currently on a VPS Server on its own and I am wondering if it is down to the settings disable_functions and that is should show BLANK as opposed to apache get_status (default)?

Wordpress was updated to 7.0 recently and the website was prevfious on a shared platform many years ago but is now sat on its own server?

I don't want to start messing around with settings here causing the site to crash and appreciate some assitance.

I have spoken to the website hosts and they are clueless in what to suggest here if this is the reason for it

 

[anthonydclark]

Could anyone advise? I am not sure if apache get_status (default) such be removed from disbaled_functions? Am I correct? If so it is just a matter of typing "none" OR "blanking it" out? As I unsure on scripting and if I can just Empty the "disable_functions" field in plesk?

 

[Sebahat.hadzhi]

Hi, @anthonydclark . Apologies for the delayed response. This appears to be a bug and judging by the last message in the report you already found it:

• https://core.trac.wordpress.org/ticket/64707

It looks like they provided a patch.

 

[Kaspar]

Additionally, it's worth noting that opcache_get_status is disabled by default on Plesk as a security measure. As the function can disclose information about other websites hosted on the same server. However having this particular PHP function disabled does not disable or restrict opcache itself. It just limits applications (like Wordpress) to check if opcache is enabled. It's a bit of a catch 22 I suppose: opcache is enabled and available for use, but the default method to check if it's available is disabled.

Because of this you can safely ignore the reported health issue about Opcode in Wordpress. But if it bothers you, you can indeed remove opcache_get_status from the disabled_functions text field in Plesk, making the text field completely empty. This will enable the opcache_get_status function, allowing Wordpress to correctly check and report Opcache is running.