Support Request Support[phpBB Debug] PHP Warning

Support Section
Previous topicNext topic
User avatar

Topic Author
YellowFlash
Users
Users
Posts: 8
Joined: 10 years ago
Status: Offline
User theme: Dark
    Windows 7 Chrome

[phpBB Debug] PHP Warning

Post by YellowFlash »

Your phpBB Version: 3.2.2
Your phpBB Type: Standard phpBB
Extensions installed: Yes
Your knowledge: Basic Knowledge

PHP Version: 5.5.6

What have you done before the problem was there?
Nothing

What have you already tried to solve the problem?
Trying to set the cache permissions to 777, also the production too

Description and Message
[phpBB Debug] PHP Warning: in file [ROOT]/phpbb/di/container_builder.php on line 146: require(./cache/production/autoload_4335734bbdd20f586549a504dff5f80c.php): failed to open stream: No such file or directory
[phpBB Debug] PHP Warning: in file [ROOT]/phpbb/di/container_builder.php on line 146: require(./cache/production/autoload_4335734bbdd20f586549a504dff5f80c.php): failed to open stream: No such file or directory

User avatar

Topic Author
YellowFlash
Users
Users
Posts: 8
Joined: 10 years ago
Status: Offline
User theme: Dark
    Windows 7 Chrome

Re: [phpBB Debug] PHP Warning

Post by YellowFlash »

Solved it

User avatar

Posey
Users
Users
Posts: 84
Joined: 10 years ago
Status: Offline
User theme: Dark
    Windows 10 Chrome

Re: [phpBB Debug] PHP Warning

Post by Posey »

I'll reply nevertheless, for people having the same issue.
This is a 'cache' issue, which aren't really issues.
Most of the time it can already be resolved by a 'force refresh', which can be done by Ctrl + F5.
Otherwise delete the files starting with container_ in your <root>/cache/production/-folder.

Image
''I'm pretty sure there's a lot more to life than being really, really, ridiculously good looking.
And I plan on finding out what that is.''

posey

User avatar

Jester
Users
Users
Posts: 24
Joined: 8 years ago
Status: Offline
User theme: Dark
    Windows 7 Chrome

Re: [phpBB Debug] PHP Warning

Post by Jester »

Posey wrote: 8 years ago I'll reply nevertheless, for people having the same issue.
This is a 'cache' issue, which aren't really issues.
Most of the time it can already be resolved by a 'force refresh', which can be done by Ctrl + F5.
Otherwise delete the files starting with container_ in your <root>/cache/production/-folder.

Image
----------------------
+1 :tumbsyes:

Previous topicNext topic