aboutsummaryrefslogtreecommitdiffstats
path: root/.htaccess
diff options
context:
space:
mode:
authorfriendica <info@friendica.com>2014-01-01 16:07:36 -0800
committerfriendica <info@friendica.com>2014-01-01 16:07:36 -0800
commit057d885baf670467443dea0da0797b9289b919b4 (patch)
tree33efb6306a7fefc80b8bd962c33500e41259967f /.htaccess
parentca8bf551d1684966d377e9d316c00fd40bd08e6e (diff)
downloadvolse-hubzilla-057d885baf670467443dea0da0797b9289b919b4.tar.gz
volse-hubzilla-057d885baf670467443dea0da0797b9289b919b4.tar.bz2
volse-hubzilla-057d885baf670467443dea0da0797b9289b919b4.zip
return to working on red-dav; This is a bit of a slog at the moment and the 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.
Diffstat (limited to '.htaccess')
0 files changed, 0 insertions, 0 deletions