Opcode cache Issue

  • shedmasteruk

    (@shedmasteruk)


    3 days, 6 hours ago

    I have also message this on the PLESK FORUM but everything that is being advised to me that there is a yet another bug with WordPress 7.0 that has yet to be addressed or resolved https://wordpress.org/support/topic/opcode-cache-is-not-enabled/ and https://core.trac.wordpress.org/ticket/64707

    The plesk web hosting control is stating that the Opcode cache is indeed enabled on the correct version with the PHP 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 only issue I can see is the settings disbaled_functions in Plesk site stating apache get_status (default) that WordPress is getting mixed up with.

    Is this indeed the reason that WordPress 7.0 is advising of a false negative? Or should i remove disbaled_functions in Plesk to BLANK.

    My hosting providers and also plesk are failing to understand this issue with WordPress 7.0?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter shedmasteruk

    (@shedmasteruk)

    3 days, 6 hours ago

    Wordpess admin page is stating that Opcode cache is not enabled when clearly it is?

    hupe13

    (@hupe13)

    2 days, 5 hours ago

    There are different types of Opcache: shared memory cache or file cache. If it is a file cache, there is the bug.

    Thread Starter shedmasteruk

    (@shedmasteruk)

    1 day, 3 hours ago

    I am getting contradicting information here as apparently PLESK are stating that there is indeed a BUG on WordPress on this matter https://talk.plesk.com/threads/opcode-cache-issue.394531/

    The suggestion has been to IGNORE the error being reported by WordPress 7.0 but it does not resolve the issue.

    opcache_get_status  is disabled by default by Plesk as a security measure! So why is WordPress reporting it has an issue?

    “Additionally, it’s worth noting that opcache_get_status is disabled by default by 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 does limit 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 if Opcache is running.”

    Thread Starter shedmasteruk

    (@shedmasteruk)

    1 day, 3 hours ago

    I have gone with what PLESK has advised but this does not resolve the issue! At least the annoying message has gone

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.