Something went wrong
Unexpected error: Zend OPcache can’t be temporary enabled (it may be only disabled till the end of request) in Unknown on line 0
Please report error at https://discourse.theturninggate.net
Something went wrong
Unexpected error: Zend OPcache can’t be temporary enabled (it may be only disabled till the end of request) in Unknown on line 0
Please report error at https://discourse.theturninggate.net
Hi @dbfoto, that looks like an issue with your host’s PHP configuration. Are you able to login to the Backlight admin? Do you have an option to change the PHP version? It’s likely that whatever’s broken is specific to one version on your host.
I can get into Backlight as admin but get this message. I didn’t change anything… how and where should I change a PHP-version?
PHP version is 8.2.29 but there is 8.3.24 in the drop down list.
Just select and save that or is there more to it?
FPM application served by Apache
Hi @dbfoto, you should be able to just select and save it. There’s a page in the Backlight Admin to check the version that is running. Backlight > Special Links > phpinfo
Hi Ben,
The hosting provider has had no changes… so where to look now? I can edit text pages. But publishing, both new albums as well as publishing images, is not possible
Yes, no change and the provider asked me to switch back as that would be most likely to help. So I am in between two fires now…
There is something seriously wrong. I cannot see the photos in my albums anymore in one browser though I do in another. The error message appears here and there in an instable manner. Then it does then it doesn’t.
What occurs to me is that Safari and Brave show the error message in albums while Firefox and Chrome do not! Newer: no not consistently… pffff
That being said Lightroom still can’t initiate a new album nor can it publish new images.
New: I can upload images directly (without Lightroom) though Backlight tells me that this is not possible it still does.
Hi @dbfoto, is it the same error that you’re seeing? Line 0 implies that the error is occurring before Backlight is even reached. There may be a way to have Backlight suppress the message, which in turn may solve the issue. Can you provide me with a Backlight admin login and if possible FTP access? The best way is by clicking my profile name followed by ‘Message’.
Hi @dbfoto, thanks for the access. I have set your site to suppress startup errors and added that particular error to the errors that are ignored when that setting is enabled. The message is no longer showing up on your site.
Does that solve the issues you’ve been having?
Ha it seems that your magic did it!
My first test published a photo and my second did initiate a new album with a photo.
So… the symptom has gone but you somehow managed to get publishing on its feet again.
Many thanks!
I have the exact same issue here with both my domains on the same PLESK server. Although I can select which PHPVersion to use for each domain, it doesn’t make any difference for any domain whether I choose PHP version v8.1.33 or v8.2.29 or v8.3.25 or v8.4.12.
The error message in both the Backlight admin console and Lightroom (latest version) is:
Zend OPcache can’t be temporary enabled.
It seems that both the LR Publisher as wel as the Admin console loads the ZendOP-module again instead of CHECKING whether it is running or not?
I’ve requested access to the different PHP options from my provider, but I’d rather see some code adjustments, since I’m running out of options here.
Hi @RCBakker54, Backlight doesn’t try to load this module. The ‘line 0’ suggests that the server is attempting to load the module twice before Backlight executes. In my experience this can happen from both the php.ini loading the module and the extensions config directory also trying to load the same module. I don’t know if that’s the case here.
You may well be hosting with the same company as @dbfoto?
The workaround in Backlight is to copy the file backlight/env.php.skel
to backlight/env.php
, edit the file and remove the leading //
from the line with SUPPRESS_STARTUP_ERRORS
.
Hi @RCBakker54, the above fix requires the latest versions of Backlight 5 or Backlight 6. Specifically, visit the Backlight Modules page and reinstall the entry for module-framework.
Hello Ben (and others reading this thread),
Below is the fix that did the trick for me:
I simply reinstalled the module-framework on the Backlight Modules page as suggested by Ben.
I didn’t change anything else (as mentioned in the posts before), I didn’t change any settings on my providers’ side nor did I change any configuration of PHP on my server.
For the record: I am running the latest version of Backlight 6 on a PLESK-server with the latest PHP-version 8.4.12.
Conclusion: problem solved thanks to the tips of @Ben !