-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
easyname hosting issues with symlinks via php #583
Comments
What's the problem? The Contao Manager reports that |
Hello,
thank you for getting back to me so quickly.
We were able to fix this issue but ran into the next error:
[cid:image001.png@01D67BC4.74080F20]
It’s not like the tool asked me whether it should install in another folder, it’s complaining about itself 😃
Other than that I think we’re on the right way.
I’m looking forward to your reply.
Regards
Philipp Au
easyname Support
Von: Yanick Witschi <notifications@github.com>
Gesendet: Mittwoch, 26. August 2020 15:21
An: contao/contao-manager <contao-manager@noreply.github.com>
Cc: Philipp Au (EXT) <pa@easyname.at>; Author <author@noreply.github.com>
Betreff: Re: [contao/contao-manager] easyname hosting issues with symlinks via php (#583)
What's the problem? The Contao Manager reports that symlink() is missing on the CLI, not the web process. It has to be enabled in both SAPIs.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#583 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQYDBOWJM6L65QPWCM5C7LDSCUDZ7ANCNFSM4QLZF4NQ>.
|
@peasyname you need to upload screenshots directly on GitHub, it does not work with email replies to comments ;) Presumably you mean that the Contao Manager is complaining about a non empty directory? |
I see, here is the error message from the screenshot. The setup tool complains that it is in its own folder, but does not offer the possibility to use another folder instead: ERROR 500 Unbekannter Installationsstatus
Edit: here's a machine translation of the message as well: ERROR 500 Unknown installation status |
As explained in the documentation, you need to create an empty folder called |
the only contents of my folder are the contao-manager.phar.php and the additional contao-manager folder the setup tool created. Can I configure another folder by changing the script? |
Which folder exactly?
No, the |
I have two test cases now, one with a folder /html/contao-manager/(contao-manager.phar.php) and the other with /html/contao-manager/web/(contao-manager.phar.php) and its the same error: ERROR 500 Unbekannter Installationsstatus
|
Can you provide access to this test case? The first test case is definitely wrong, as the contao-manager.phar.php needs to be within the |
user and pass are the same as in my previous post above the one in the webfolder is reachable under https://contao-web.easynametest.com the one in the contao-manager folder is still under https://contao.easynametest.com if you need further access (ie. FTP) please email me under pa@easyname.at |
Did you set the DocumentRoot of https://contao-web.easynametest.com/ correctly to |
I assume this has been solved, and it does not look like a bug but rather a question. |
@aschempp the bug could be, that the installation does not work, if the target directory happens to be named |
That wouldn't really make sense to me. The Contao Manager only checks if the current directory is names |
hello,
until recently we had actually disabled the php function symlink(). Now we have a new experimental setup where this function is no longer disabled. however, the issue with the web install tool / contao manager remains the same. you can check the php info via https://contao.easynametest.com/phpnf0.php
You can also try running the tool yourself under https://contao.easynametest.com/contao-manager.phar.php
user: easynamesupport
pass: fDq3LbNf9im2FRL
We would like to be able to offer an automatised setup for contao in the future, but will not be able to as long as this problem persists.
thank you for getting back to us.
regards
the easyname Support Team
The text was updated successfully, but these errors were encountered: