Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | that was not intended to be merged with master yet. Put it under a define | friendica | 2015-01-11 | 1 | -2/+36 |
| | |||||
* | begin the grand unification for 3.0. Start by splitting DAV into a web ↵ | friendica | 2015-01-06 | 1 | -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. | Klaus | 2014-10-12 | 1 | -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 Weidenbach | 2014-10-12 | 1 | -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 issue | friendica | 2014-10-08 | 1 | -1/+0 |
| | |||||
* | Moved RedBrowser class from reddav.php to it's own file. | Klaus Weidenbach | 2014-10-06 | 1 | -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 Weidenbach | 2014-10-05 | 1 | -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 /cloud | friendica | 2014-07-28 | 1 | -0/+11 |
| | |||||
* | provide os_mkdir to workaround permission issues with php mkdir | friendica | 2014-07-16 | 1 | -1/+1 |
| | |||||
* | Return a correct timestamp when a folder is empty. | Klaus Weidenbach | 2014-06-29 | 1 | -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 strings | Paolo Tacconi | 2014-06-25 | 1 | -0/+1 |
| | |||||
* | strip hard-wired zids from posted links as they will have the wrong identity ↵ | friendica | 2014-02-16 | 1 | -2/+2 |
| | | | | when somebody tries to view the link | ||||
* | The final piece of the DAV authentication puzzle. Provide a directory view ↵ | friendica | 2014-01-26 | 1 | -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. | friendica | 2014-01-26 | 1 | -2/+22 |
| | |||||
* | seems you can't easily have a blank password for DAV guests, so the guest ↵ | friendica | 2014-01-21 | 1 | -2/+4 |
| | | | | password is now +++ | ||||
* | create store directory if it's missing before initialising DAV | friendica | 2014-01-21 | 1 | -1/+4 |
| | |||||
* | catch auth exceptions | friendica | 2014-01-20 | 1 | -2/+7 |
| | |||||
* | strip zid= from REQUEST_URI as well as QUERY_STRING - sabre uses both | friendica | 2014-01-19 | 1 | -0/+3 |
| | |||||
* | kill the ummagumma effect | friendica | 2014-01-16 | 1 | -2/+4 |
| | |||||
* | prevent zid's from reaching the DAV core code. | friendica | 2014-01-16 | 1 | -0/+3 |
| | |||||
* | directory creation error, display localtimes on cloud webpage, doc updates | friendica | 2014-01-10 | 1 | -0/+2 |
| | |||||
* | add cloud link to profile_tabs and Comanchify the sucker | friendica | 2014-01-09 | 1 | -0/+15 |
| | |||||
* | disable web browser post inputs if no storage write permission | friendica | 2014-01-05 | 1 | -78/+6 |
| | |||||
* | reddav - basic mkdir support - needs more work to be robust | friendica | 2014-01-05 | 1 | -0/+2 |
| | |||||
* | the web browser interface for DAV has now got zot | friendica | 2014-01-05 | 1 | -1/+23 |
| | |||||
* | more dav work | friendica | 2014-01-03 | 1 | -1/+1 |
| | |||||
* | basic browsing and file retrieval for webdav working - uploads not yet. A ↵ | friendica | 2014-01-02 | 1 | -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 lifting | friendica | 2014-01-02 | 1 | -5/+3 |
| | |||||
* | return to working on red-dav; This is a bit of a slog at the moment and the ↵ | friendica | 2014-01-01 | 1 | -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 works | friendica | 2013-10-22 | 1 | -2/+2 |
| | |||||
* | very early cloud demo code - READ THE FRICKIN NOTES and also THE CODE in ↵ | friendica | 2013-10-22 | 1 | -0/+107 |
mod/cloud.php - there is no other documentation. Use at your own risk. Send all bug reports to nobody@nowhere.com. |