aboutsummaryrefslogtreecommitdiffstats
path: root/mod/cloud.php
Commit message (Collapse)AuthorAgeFilesLines
* module updatesredmatrix2016-04-181-104/+0
|
* static Appredmatrix2016-03-311-3/+3
|
* deprecate $a->get_baseurl()redmatrix2016-03-301-1/+1
|
* finish up the storage moveredmatrix2016-02-191-1/+1
|
* move storage assets to zotlabs/storageredmatrix2016-02-191-7/+7
|
* don't spit out sabre xml on permission denied exceptions, just provide a 401redmatrix2015-12-101-30/+12
|
* issue #50 - cloud listings produce white screen for unauthenticated viewerredmatrix2015-09-211-18/+20
|
* start to partition the davredmatrix2015-06-101-27/+4
|
* Merge branch 'master' of https://github.com/redmatrix/redmatrixredmatrix2015-05-171-1/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: include/bb2diaspora.php include/diaspora.php include/enotify.php mod/admin.php mod/cloud.php mod/dav.php mod/home.php mod/invite.php mod/like.php mod/mitem.php mod/p.php mod/pubsites.php mod/setup.php mod/siteinfo.php util/messages.po
| * more work isolating the projectname from core.redmatrix2015-05-171-1/+1
| |
* | second pass name changeredmatrix2015-05-051-1/+1
| |
* | first pass name changeredmatrix2015-05-051-3/+3
|/
* local_user => local_channelfriendica2015-01-281-1/+1
|
* revert recent 3.0 changes to mod/cloud so we can work on this completely in ↵friendica2015-01-131-30/+19
| | | | another branch and not destabilise core
* theme toggle issue when viewing mod/cloud of another channelfriendica2015-01-121-9/+0
|
* that was not intended to be merged with master yet. Put it under a definefriendica2015-01-111-2/+36
|
* begin the grand unification for 3.0. Start by splitting DAV into a web ↵friendica2015-01-061-27/+3
| | | | accessible component and a DAV accessible component so that we can eliminate the http-auth prompts for web-accessed resources.
* A fix, but I have no case to verify.Klaus2014-10-121-2/+2
| | | I could not find out under which conditions this is relevant and therefore have no test case, but it must be of instance RedDAV\RedFile.
* Moved classes from reddav.php into own files.Klaus Weidenbach2014-10-121-2/+2
| | | | | | Finished moving classes out from include/reddav.php into own files. Also continued with namespace for RedDAV. Improved some docs and added some todos and fixmes.
* dav issuefriendica2014-10-081-1/+0
|
* Moved RedBrowser class from reddav.php to it's own file.Klaus Weidenbach2014-10-061-12/+18
| | | | | | | | | First step on cleaning up ReadDAV classes and restructuring it bit in preparation for adding some more DAV features, photo access, CalDAV, etc. and hopefully also some PHPunits. Add a PHP5.3 namespace for RedDAV classes. Any objections against this or the vendor namespace? Add some more documentation for RedBrowser.
* Some documentation for include/reddav.php and a bit code cleanup.Klaus Weidenbach2014-10-051-42/+44
| | | | | Removed some duplicate code in RedBasicAuth and restructured a bit. Still work in progress.
* derivative themes not loading parent theme includes when visiting /cloudfriendica2014-07-281-0/+11
|
* provide os_mkdir to workaround permission issues with php mkdirfriendica2014-07-161-1/+1
|
* Return a correct timestamp when a folder is empty.Klaus Weidenbach2014-06-291-27/+27
| | | | | If a folder was empty a zero timestamp was returned. Now it will return the timestamp of the folder itself.
* Display quota and translatable stringsPaolo Tacconi2014-06-251-0/+1
|
* strip hard-wired zids from posted links as they will have the wrong identity ↵friendica2014-02-161-2/+2
| | | | when somebody tries to view the link
* The final piece of the DAV authentication puzzle. Provide a directory view ↵friendica2014-01-261-5/+9
| | | | to an un-auth'd person (without asking for a password) by adding a query parameter 'davguest=1'. This is a bit of a hack, but there was no response on the official forum about how to do this correctly so it will have to do. On the downside, if permission is denied, it won't ask for a password - but we're talking about unauthenticated folks who didn't go through magic auth so chances are even if they authenticate, permission will still be denied.
* don't prompt guests for a password if they're accessing an embedded public file.friendica2014-01-261-2/+22
|
* seems you can't easily have a blank password for DAV guests, so the guest ↵friendica2014-01-211-2/+4
| | | | password is now +++
* create store directory if it's missing before initialising DAVfriendica2014-01-211-1/+4
|
* catch auth exceptionsfriendica2014-01-201-2/+7
|
* strip zid= from REQUEST_URI as well as QUERY_STRING - sabre uses bothfriendica2014-01-191-0/+3
|
* kill the ummagumma effectfriendica2014-01-161-2/+4
|
* prevent zid's from reaching the DAV core code.friendica2014-01-161-0/+3
|
* directory creation error, display localtimes on cloud webpage, doc updatesfriendica2014-01-101-0/+2
|
* add cloud link to profile_tabs and Comanchify the suckerfriendica2014-01-091-0/+15
|
* disable web browser post inputs if no storage write permissionfriendica2014-01-051-78/+6
|
* reddav - basic mkdir support - needs more work to be robustfriendica2014-01-051-0/+2
|
* the web browser interface for DAV has now got zotfriendica2014-01-051-1/+23
|
* more dav workfriendica2014-01-031-1/+1
|
* basic browsing and file retrieval for webdav working - uploads not yet. A ↵friendica2014-01-021-1/+1
| | | | lot of permissions stuff is in place so it's marginally (but probably not completely) permission controlled
* some DAV tweaks before the next round of heavy liftingfriendica2014-01-021-5/+3
|
* return to working on red-dav; This is a bit of a slog at the moment and the ↵friendica2014-01-011-3/+21
| | | | basic framework isn't even close to working. This does break the working test we did have (which was never connected to the Red backend). Now we're starting to connect Red and DAV together intimately. There will probably be some twists and turns along the way as we get the information we need into all the class objects that need them. But the important part is that the RedDirectory and RedFile classes are loading without throwing white screens and from here we can use logging to figure out what the DAV front end is trying to do and what it is passing to the backend and hopefully figure out what it expects to do with the results. Unless you're a competent developer with a strong background in OOP and are helping develop this code, you should keep it an arm's length away from any production site and don't even think of enabling it. By default it is turned off.
* move killme inside module function so that typo worksfriendica2013-10-221-2/+2
|
* very early cloud demo code - READ THE FRICKIN NOTES and also THE CODE in ↵friendica2013-10-221-0/+107
mod/cloud.php - there is no other documentation. Use at your own risk. Send all bug reports to nobody@nowhere.com.