[Owncloud] Owncloud on apache servers

2012-12-02 Thread Brijesh Kothari
Hi, I am installing OwnCloud on a server running as apache webserver. Now OwnCloud requires the owner of the /data directory to be "apache" but my username is soft and I am unable to change the owner of the data directory to apache. I have provided writeable permissions to the data directory i.e.

[Owncloud] Adding another cloud to Owncloud

2012-12-02 Thread Tharindu Dhananjaya Galappaththi
Hi, I'm trying to develop some features for owncloud for a university project of mine. Is there a way of configuring 2 or more clouds to owncloud? e.g :- like configuring 2 mail accounts to thunderbird Thank you ___ Owncloud mailing list Owncloud@kde.org

Re: [Owncloud] endless 4.5.3 setup loop (was:upgrade from 4.0.7 to 4.5.3 without config files?)

2012-12-02 Thread Ditmar Unger
Hi, (Thanks Michael; before importing the saved old db tables ) I tried to install a fresh 4.5.3 oc but the mysql db never gets populated and oc loops for the initial setup page. I deleted all users, files and the db via phpmyadmin and started from scratch (apt.get install owncloud) but no succ

[Owncloud] Warnings on write/modify/remove files

2012-12-02 Thread George Ruinelli
Hi all I am trying to write an App which can write/modify/remove files. I was now able to do this with the following code, but get some warnings: - CODE - $root = "Notes"; $user = OCP\USER::getUser(); OC_Filesystem::init($root, '/' . $user . '/'); OC_Filesy

Re: [Owncloud] Documentation Repo Howto

2012-12-02 Thread Michael Grosser
I like the new documentation, but I dislike the different design usage for the client docs. We really should stick to one style. (probably in the works, but I just wanted to point that out) Cheers Michael On Sun, Dec 2, 2012 at 1:03 PM, Daniel Molkentin wrote: > > On 30.11.2012, at 08:45, Qing

Re: [Owncloud] Documentation Repo Howto

2012-12-02 Thread Daniel Molkentin
On 30.11.2012, at 08:45, Qingping Hou wrote: > On Thu, Nov 29, 2012 at 6:12 AM, Bernhard Posselt > wrote: >> Maybe this should also be worked into the documentation >> >> so we have documentation about the how to produce the documentation in >> the documentation :) >> > > Yes, totally agree