You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 29, 2020. It is now read-only.
I am trying to use pawtucket but am not getting much success because I am getting the following error in the log; 2017/02/17 20:54:32 [error] 5635#5635: *1755 FastCGI sent in stderr: "PHP message: PHP Fatal error: Cannot declare class Error, because the name is already in use in /opt/pawtucket-1.4/app/lib/core/Error.php on line 46" while reading response header from upstream, client: 192.168.0.7, server: blah.com, request: "GET /pwt/ HTTP/2.0", upstream: "fastcgi://unix:/var/run/php/php7.0-fpm.sock:", host: "blah.com"
A look around and I find this nugget;
If after PHP upgrade you're getting error "PHP Fatal error: Cannot declare class error, because the name is already in use ...", you will have to rename your "error" class.
Since PHP 7 classname "Error" is predefined and used internally.
The text was updated successfully, but these errors were encountered:
The Pawtucket master branch is not compatible with php7 at the moment. Try using Pawtucket2, or if you must use this older Pawtucket try the "develop" branch.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am trying to use pawtucket but am not getting much success because I am getting the following error in the log;
2017/02/17 20:54:32 [error] 5635#5635: *1755 FastCGI sent in stderr: "PHP message: PHP Fatal error: Cannot declare class Error, because the name is already in use in /opt/pawtucket-1.4/app/lib/core/Error.php on line 46" while reading response header from upstream, client: 192.168.0.7, server: blah.com, request: "GET /pwt/ HTTP/2.0", upstream: "fastcgi://unix:/var/run/php/php7.0-fpm.sock:", host: "blah.com"
A look around and I find this nugget;
The text was updated successfully, but these errors were encountered: