Talk:OwnCloud

From SME Server
Revision as of 02:55, 31 December 2013 by Mmccarn (talk | contribs)
Jump to navigationJump to search

Mmccarn (talk) 17:55, 30 December 2013 (MST)

Note: Despite the supposed dependancy of OwnCloud 6 on PHP v5.3.8, I was able to install Owncloud 6.0a without problems on SME8 using the OwnCloud 'web installer'.


Mmccarn 08:14, 2 December 2012 (MST)

Notes: Installing from a git clone generated a blank screen during installation, with the following error in /var/log/messages:

httpd: PHP Fatal error:  Cannot access protected property MDB2_Driver_mysql::$varchar_max_length in /home/e-smith/files/ibays/owncloud/html/3rdparty/MDB2/Driver/Datatype/mysql.php on line 156

This was reported to owncloud and determined to be "not a bug": http://bugs.owncloud.org/thebuggenie/owncloud/issues/oc-1583

However, I suspect that it's related to this change in PEAR: http://pear.php.net/bugs/bug.php?id=19582

As reported, downloaded releases (v4.5.3 and v4.5.4) installed fine.

webtatic-el5

The solution proposed as you can see below is to upgrade your php version with the webtatic repository
Warning.png Warning:
if you update php with the webtatic repository, you can experience some problems with contribs such as phpmyadmin which need php53 dependencies. see bug 7613c12


first we need to install the webtatic repository, see the relevant wiki page

/sbin/e-smith/db yum_repositories set webtatic repository \
Name 'webtatic - EL5' \
MirrorList 'http://mirror.webtatic.com/yum/centos/5/$basearch/mirrorlist' \
EnableGroups no \
GPGCheck yes \
GPGKey http://repo.webtatic.com/yum/RPM-GPG-KEY-webtatic-andy \
Visible no \
status disabled

After adding it to the database updating the configuration file is required:

signal-event yum-modify

check your php version

[root@sme8dev-3 ~]# rpm -q php
php-5.3.3-13.el5.sme.2

upgrade your php version

[root@sme8dev-3 ~]# yum update --enablerepo=webtatic php

verify your php version

[root@sme8dev-3 ~]# rpm -q php
php-5.3.27-2.w5

and reconfigure your server

signal-event post-upgrade; signal-event reboot

After that you can continue the HowTo