Balázs Dura-Kovács
Balázs Dura-Kovács
So it seems that the error message is coming from the server itself. Could you check the error log on the server too? Should be under storage/logs
Yes please. The call stack might reveal what is causing the issue.
@IamAhmedly Are you using SQL server as well?
You're probably right, rewriting it would be a big task and we lost momentum a long time ago. Nice to see some progress again!
I abolutely agree with you. Starting again from scratch is often much easier than making a huge refactor (which is very much needed). I think we should drop backward compatibility....
Maybe we should use git-flow? For handling stable/dev/bugfix branches
It's not an answer to your question but the very core (crud and related stuff) could be a facade. Then api functions could be called from the entire system (including...
Very well done, lot of work you have already done as I can see. :+1: Maybe the hardest thing is to start somewhere... And it looks really good quality code...
One last thing: > `"laravel/framework": "^5.2"` Since 5.1 is an LTS release, we should support it as well. So we can't rely on new functions in 5.2 But you may...
I see. Ok then