Added information on updating php-mapi if upgraded php to version 5.3
Line 121:
Line 121:
here is one workaround http://forums.zarafa.com/viewtopic.php?f=9&t=3263&p=18753#p18753
here is one workaround http://forums.zarafa.com/viewtopic.php?f=9&t=3263&p=18753#p18753
−
I found with the mapi error that I was getting was caused by my upgrade, PHP wouldn't start as the file libvmime.so.0 was missing or something rather (log no longer has the message). How I fixed my issue was I deleted the symlink in the /usr/lib/libvmime.so.0 which pointed to ...libvmime.0.7.1.so which is deleted when you upgrade the packages for version 7. I then "reinstalled" libvmime-0.9.2+... and restarted the httpd damaen and all was right with the world. -- Garth Kirkwood (girkers)
+
I found with the mapi error that I was getting was caused by my upgrade, PHP wouldn't start as the file libvmime.so.0 was missing or something rather (log no longer has the message). How I fixed my issue was I deleted the symlink in the /usr/lib/libvmime.so.0 which pointed to ...libvmime.0.7.1.so which is deleted when you upgrade the packages for version 7. I then "reinstalled" libvmime-0.9.2+... and restarted the httpd damaen and all was right with the world. -- girkers
+
+
==== php 5.3 ====
+
If you update your system against the testing repo, it will update php to version 5.3 and thus break things again. To fix the mapi error this time, I uninstalled php-mapi that was included with zarafa (I was using 7.0.1.28479 that was included with zarafa) and this also removes the two dependencies of zarafa-webaccess and zarafa-webaccess-mobile (if they are installed). I then downloaded an updated php-mapi, installed it and then reinstalled the webaccess rpms and restarted the httpd and all good again. - Girkers