Baikal 0.2.7 to 0.4.6

[ghost]

Hello,

is it possible to get help for my problem with updating Baikal 0.2.7 to 0.4.6?
After having done all neccessary steps 1-5 from
http://sabre.io/baikal/upgrade/
I got this error message when calling the administration panel the first time after having overwritten all files:

ErrorException: The each() function is deprecated. This message will be suppressed on further calls in /var/www/web72/htdocs/baikal/Core/Frameworks/Flake/Core/Render/Container.php:62
Stack trace:
#0 [internal function]: Baikal\Framework::exception_error_handler(8192, 'The each() func...', '/var/www/web72/...', 62, Array)
#1 /var/www/web72/htdocs/baikal/Core/Frameworks/Flake/Core/Render/Container.php(62): each(Array)
#2 /var/www/web72/htdocs/baikal/Core/Frameworks/Flake/Controller/Page.php(83): Flake\Core\Render\Container->execute()
#3 /var/www/web72/htdocs/baikal/html/admin/index.php(92): Flake\Controller\Page->render()
#4 {main}

For your information I had to update PHP from 5.4(?) to PHP 7 because the installer asked for a higher PHP. So I updated PHP on the server (with LiveConfig).
Maybe this could be a problem that Baikal 0.2.7 run on PHP 5.4(?) and I have changed it to PHP 7 while installing Baikal 0.4.6?

Thank you so much in advance for helping me.

[shrank]

Hi I'm running Baikal 0.4.6 on PHP 7.0.26 without problems. The deprecated message you get is "just" informal. It tells you, that you should take action, because the function will be removed in future versions of PHP. This usually takes years. The "each()" function"has been /DEPRECATED/ as of PHP 7.2.0. Relying on this function is highly discouraged." But it is still save to use it. You should turn off the embedded log messages on production systems. Better write all errors to a logfile. http://php.net/manual/en/errorfunc.configuration.php#ini.display-errors regards, Michael Am 05.12.2017 um 01:05 schrieb donatje:

…

Hello, is it possible to get help for my problem with updating Baikal 0.2.7 to 0.4.6? After having done all neccessary steps 1-5 from http://sabre.io/baikal/upgrade/ I got this error message when calling the administration panel the first time after having overwritten all files: ErrorException: The each() function is deprecated. This message will be suppressed on further calls in /var/www/web72/htdocs/baikal/Core/Frameworks/Flake/Core/Render/Container.php:62 Stack trace: #0 [internal function]: Baikal\Framework::exception_error_handler(8192, 'The each() func...', '/var/www/web72/...', 62, Array) #1 <#1> /var/www/web72/htdocs/baikal/Core/Frameworks/Flake/Core/Render/Container.php(62): each(Array) #2 <#2> /var/www/web72/htdocs/baikal/Core/Frameworks/Flake/Controller/Page.php(83): Flake\Core\Render\Container->execute() #3 <#3> /var/www/web72/htdocs/baikal/html/admin/index.php(92): Flake\Controller\Page->render() #4 <#4> {main} For your information I had to update PHP from 5.4(?) to PHP 7 because the installer asked for a higher PHP. So I updated PHP on the server (with LiveConfig). Maybe this could be a problem that Baikal 0.2.7 run on PHP 5.4(?) and I have changed it to PHP 7 while installing Baikal 0.4.6? Thank you so much in advance for helping me. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#720>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACik2sK5o-_Mn0pP-qPjW-lFc4OQ8KiQks5s9IitgaJpZM4Q1hbT>.

[marcelbrueckner]

I use macOS Sierra 10.12.6, too, together with Baikal 0.4.5. You should use dav.php instead of card.php. In my account settings, the server path looks like ../dav.php/principals/USERNAME/

[shrank]

maybe your webserver logfile can tell you if you got the url right.

For testing, you can enter the URL in your webbrowser. You should get a Login prompt and finally a list of nodes in your addressbook.

It could be a problem with the .htaccess file settings.

• make sure you got the new .htaccess file in /html/
  -> should look like this: .htaccess
• make sure your apache server is using the settings from the file
• try the settings from issue Contacts on MacOS High Sierra #714

[zachow]

Hi experts,

I needed to upgrade from 0.2.7 to 0.4.6 because PHP 5.x is no longer supported by my provider.
I did the upgrade according to http://sabre.io/baikal/upgrade/ but received errors, which I found out here were related to the timeout problem. After fixing this I still receive the following error:

Upgrading Baïkal from version 0.2.7 to version 0.4.6

Errors
Uncaught exception during upgrade: PDOException: SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'calendarchanges' already exists in /mnt/web418/a3/03/5498703/htdocs/baikal/Core/Frameworks/BaikalAdmin/Controller/Install/VersionUpgrade.php:116 Stack trace: #0 /mnt/web418/a3/03/5498703/htdocs/baikal/Core/Frameworks/BaikalAdmin/Controller/Install/VersionUpgrade.php(116): PDO->exec('\n ...') #1 /mnt/web418/a3/03/5498703/htdocs/baikal/Core/Frameworks/BaikalAdmin/Controller/Install/VersionUpgrade.php(61): BaikalAdmin\Controller\Install\VersionUpgrade->upgrade('0.2.7', '0.4.6') #2 /mnt/web418/a3/03/5498703/htdocs/baikal/Core/Frameworks/Flake/Core/Render/Container.php(71): BaikalAdmin\Controller\Install\VersionUpgrade->render() #3 /mnt/web418/a3/03/5498703/htdocs/baikal/Core/Frameworks/Flake/Controller/Page.php(85): Flake\Core\Render\Container->renderBlocks() #4 /mnt/web418/a3/03/5498703/htdocs/baikal/html/admin/install/index.php(83): Flake\Controller\Page->render() #5 {main}

Successful operations
synctoken was added to calendars
ctag was removed from calendars

Error Baïkal has not been upgraded. See the section 'Errors' for details.

In fact, I tried several times, always restoring the database backup before. Now I don't know whether the backup itself is my problem or any mismatch in my configuration. Reverting back to 0.2.7 runs as before with the database backup, however, without having the opportunity to access the administrative web interface anymore.

Any help is highly appreciated.

Thanks

[derStephan]

@zachow: Did you try any of the solutions given in #716 or #708 or #683 or #665 or #573?

[evert]

We've been pretty quiet because the project hasn't had an active maintainer for a while. There's recently been a new release that might solve some of these problems.

It's been a while since your message so I assume you either moved on or solved it. If not, give the latest version a shot and comment here if you're running into problems.