-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DDEV initializsation #43
Comments
It seems the "Initialization" of my_site_package is not executed. I must admit I don't know how/if I can manually import this through the CLI or so? |
It seems that "my_site_package" has a site config with:
however in my base config/sites/main/config.yaml this was created:
|
SetupCommand.php at line 627 receives "no" as the URL for the Site... |
It seems if I run this:
it works. |
(I cannot pick "pagets__Default" from the list, it always reverts to the empty option, which leads to a malformed backend layout) |
Ah, somehow the site configuration did not have the "my-site-package" set as a dependency?! I had to manually add this. |
The fact that the set up command did not work is I think a core bug: https://forge.typo3.org/issues/105871 |
The backend layout issue is waiting to be merged to be fixed: TYPO3/get.typo3.org#480 Benji is probably on vacation |
The rest of the problems is probably caused by the site that you created so that site config etc did not match anymore? In all my trials the additional.php was created automatically without a ddev restart. Mac issue? |
@garvinhicking do these commits resolve your issues? can we close this issue? |
Yes, looks good! |
Readme states to do a "ddev start && make install".
However, the process needs some tuning. After a "composer install" ddev needs to be restarted.
Probalby tweak:
into:
Untested yet. I fixed this myself by restarting DDEV and then running setup again.
However I still run into the issue that the typo3 console setup fails with:
Unsure if this is a bug with TYPO3 v13?! I have an empty site tree after this and could log into TYPO3
The text was updated successfully, but these errors were encountered: