fix: make TYPO3 nginx config work with TYPO3 v12, fixes #7299, for #7230#7301
Conversation
|
@mabolek would appreciate your review here as well, thanks! |
|
Download the artifacts for this pull request:
See Testing a PR. |
|
i havent seen your PR, randy only asked it would be good to have a quickstart for v12. i'Ve created one #7302 adding tabs for v13 and v12 plus bats test for each. i then ran into a failing test for the login on v12 ^^, a good proof that it works. i then downloaded the artifact from this PR and with that the tests passed. i just realized you are adding tests for v12 in this PR as well. i wonder would it make sense to drop the test from this one and use the test from the other. for one the creation for the first install file is only necessary for installs in the web ui for install using typo3 setup it is not necessary plus i did a one or two more asserts. you may take a look. or we might update the test in here? either way would be ok for me. |
|
i've also tested the artifact with v11 there i run into a 500 error on |
|
@rpkoller, let's keep your PR open. I thought I was logged in and probably tested it on a version where it "worked". But testing again today on a fresh head, I get a 500 error after login on TYPO3 v13. |
9d0b9ee to
f38f77f
Compare
|
@rpkoller, I think it's better to pull my PR first and then rebase yours. (I looked at your PR, and I think we still need a quickstart without I changed the nginx conditions, now it should work better. |
|
the one thing i dont understand, @opi99 mentioned in the corresponding thread that your previous approach wouldnt work, but i wonder why it then worked for me when i tested locally? i downloaded the artifact and and ran the test from my own PR with it. they passed, after switching back to HEAD they failed again. would have my testes have to be extended? and i am not sure why a quickstart for older versions would be necessary? those are only informal nothing is tested, they are only instructions for users how to setup a specific version? but i am fully on board to add another test, one without a quickstart like for typo3 v14? |
|
I think the problem was that the login worked but nothing from there on. We can always hope to make more sophisticated quickstart tests... |
|
I re-ran the quickstart tests as they failed on shopware6 of all things! |
Correct.
@rpkoller, the reason why the previous change in #7230 worked for the current TYPO3 is because TYPO3 v13 already deprecated // Legacy wrapper for typo3/index.php
// @deprecated will be removed in TYPO3 v14, /index.php entrypoint should be used directlyI think it would not make any difference if I just replaced In case of TYPO3 v12, it uses a different approach in And that's why we need to test TYPO3 v12. |
|
I'm removing the TYPO3 v12 test from this PR. It'll be changed anyway in #7302, and I want to avoid PR conflicts. |
f38f77f to
f9873e2
Compare
rfay
left a comment
There was a problem hiding this comment.
Yay!
I tested in v11, v12, v13, v14, and also tested with alternate BE path /admin for v14. All worked great.
The Issue
Culprit:
How This PR Solves The Issue
Uses a different nginx technique. Spent long hours with ChatGPT.
Manual Testing Instructions
Try TYPO3 quickstart for v11, v12, v13, v14 (full install with login)
https://ddev.readthedocs.io/en/stable/users/quickstart/#typo3
v14:
v13:
v12:
v11:
Automated Testing Overview
Release/Deployment Notes