Open HavardPede opened 4 years ago
The master branch is not php 7 compatible without changes to code (is a temporary patch file in the build directory). Not sure about the MySQL issues, but might also be related to versioning (changes in what default values are accepted).
As of now I would personally recommend running the docker setup from master, or docker-compose PR/branch, as that will eliminate much of the variations/debugging needed to getting a basic version up an running. These also have the most recent setup instructions.
I'm quite new to the project, so might be others with better help for your specific issues without changing to the docker approach?
I'm running the prod
branch with no major issues on PHP 7.2 and MySQL 5.7 in my testing environment. From my experience it is mostly PHP 7.3 and beyond that breaks some stuff.
By the way, i edited your post and enclosed the logs in code tags.
I am currently running the master branch on php 7.2 and MySQL 5.7, and am currently getting those issues. @Atriusftw is MySQL not throwing errors for you with default timestamps set to "0000-00-00" etc? I will try setting it up with prod instead of master and let you know
Seems to be the mysql server who are not happy about the entry seems like strict mode or sql_mode are interupting what you are doing. I got this fixed.
Currently trying to set up Wannabe, following your setup guide. We are running it with php7, and MySql version 5.7 however. As I'm setting up, I am noticing that MySql is throwing a lot of errors due to default TIMESTAMP and datetime values being set to '0000-00-00 00:00:00'. Upon doing research, I realize that these two types ony accept values from '1970-01-02 00:00:00' and upwards, which renders 0000-00-00 incorrect. I changed all the default values in the intial migration file to this timestamp, and which allowed me to call
sh migrate.sh
for the first time without the database throwing errors.However, when I now try to run
cake event
, the following occours:Do you have any solution for this?