Skip to content
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

Improve TYPO3 Exception 1436717322 or restore original text and improve this? #103

Open
sypets opened this issue Apr 3, 2023 · 2 comments

Comments

@sypets
Copy link
Contributor

sypets commented Apr 3, 2023

https://docs.typo3.org/typo3cms/exceptions/main/en-us/Exceptions/1436717322.html

This exception text provides misleading information:


Also, I noticed the original text contained more context which had been removed, see: https://github.com/TYPO3-Documentation/TYPO3CMS-Exceptions/blame/d23df932963463949139656542de5f17a212d712/Documentation/Exceptions/1436717322.rst

The context might have been helpful here, it shows that it is a very specific suggestion for one specific usecase.

@brotkrueml
Copy link
Contributor

dotenv-connector is not the only one. One can also use symfony/dotenv or vlucas/phpdotenv. But I agree, this should be made more clear.

Additionally, it is config.yaml, not config.xml.

@DavidBruchmann
Copy link

Concerning the deleted comment:
I suppose that backslashes in any URL are certainly a bad idea in general.
Nevertheless it leads to the config.yaml as source of a problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants