-
Notifications
You must be signed in to change notification settings - Fork 292
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
Baikal PHP Error #701
Comments
Same here. Im on a freshly installed machine with Apache 2.4 and PHP 7.0 (Debian9). Baikal is on 0.4.6. Before my migration from an old machine (with PHP5) my installation ie. my configs worked well. Is this a PHP7 issue? Did I forgot to install additional php packages? Thanks in advance. |
Okay, I digged deeper into it. Turns out I missed a dependency: |
Hi, So, my question is: @1977er How did you install this missing dependency? And why was a webserver restart necessary? Did you follow one of these ways here? http://sabre.io/dav/install/ Did you install composer first? Sorry for dumb questions - I'm not that deep into PHP... |
Ah! OK. It was not missing php-sabre-dav - This is already inside the baikal ZIP! In my case I could get rid of the error by installing these debian packages for Baikal: @maintainers: would it be possible that you list the PHP7 dependencies on your installtion pages? |
Editing the wiki pages is open for everyone: Feel free to add these information. |
Indeed, Baikal needs the XML extension to work! |
Hi, I have some problems using Baikal. My admin area works well, but not the main area, like dav.php, card.php and cal.php.
If I go to domain/dav.php I get:
Error: Class 'DOMDocument' not found in /mnt/are/www/dav/vendor/sabre/dav/lib/DAV/Server.php:256
Stack trace:
#0 /mnt/are/www/dav/Core/Frameworks/Baikal/Core/Server.php(123): Sabre\DAV\Server->exec()
#1 /mnt/are/www/dav/html/dav.php(61): Baikal\Core\Server->start()
#2 {main}
If you want, I can upload my nginx configuration file.
What's the problem? PHP? Nginx? Or Baikal itself?
I have php 7.0.
Thanks! :)
The text was updated successfully, but these errors were encountered: