Closed ulrikkold closed 9 years ago
I can't reproduce this. I did a fresh build of a box this morning without any issues.
I have seen this happen when re-running composer on a site with an existing database. In this case it may help to remove both the database and the web files for that site. Then re-deploy.
I'll try that when I find the time.
søn. 19. apr. 2015 10.27 skrev Michiel Roos notifications@github.com:
I have seen this happen when re-running composer on a site with an existing database. In this case it may help to remove both the database and the web files for that site. Then re-deploy.
— Reply to this email directly or view it on GitHub https://github.com/Tuurlijk/TYPO3.Homestead/issues/13#issuecomment-94251507 .
Please re-open if this is still an issue ;-)
Is this supposed to happen? I'm guessing there should have been an SQL-file with a set of standard users, which should have been imported before warming up the cache? Or is the typo3_console feature not complete yet?