aboutsummaryrefslogtreecommitdiffstats
path: root/include/RedDAV
Commit message (Collapse)AuthorAgeFilesLines
* more file/photo merge workredmatrix2015-06-142-17/+51
|
* isolate the os_storage flagredmatrix2015-06-132-6/+6
|
* Merge branch 'master' of https://github.com/redmatrix/redmatrixredmatrix2015-06-131-2/+10
|\ | | | | | | | | Conflicts: util/messages.po
* | make cloud work againredmatrix2015-06-114-5/+5
| |
* | first pass name changeredmatrix2015-05-054-5/+5
|/
* missed oneHabeas Codice2015-04-071-1/+1
|
* "PHP Strict Standards: Only variables should be passed by reference"Habeas Codice2015-04-071-3/+4
|
* fix os_mkdirfriendica2015-03-292-0/+3
|
* RedDAV: fix renaming files.Klaus2015-03-061-1/+2
| | | | How can no one have spot this bug yet?!? Is no one using WebDAV? Took me 2 days to figure out it was not my RedDAV rewrite, but that this should have never worked. :-!
* local_user => local_channelfriendica2015-01-281-1/+1
|
* show shared button only to local usermarijus2015-01-281-1/+2
|
* move userReadableSize() and getIconFromType() from ↵marijus2015-01-271-88/+7
| | | | /include/RedDAV/RedBrowser.php to include/text.php and add template for mod/sharedwithme
* add some mimetypesmarijus2015-01-221-2/+5
|
* Merge https://github.com/friendica/red into pending_mergefriendica2015-01-181-5/+6
|\
| * fix postgres escapingHabeas Codice2015-01-181-5/+6
| |
* | typofriendica2015-01-181-2/+2
|/
* remove all hardwired references to 'cloud' in the files interfaces and ↵friendica2015-01-181-7/+11
| | | | replace with $a->module. It's OK to leave them in the RedBrowser component because this will remain under /cloud. All the DAV bits need to be abstracted as they will eventually end up under /dav. $a->module will contain the correct string to use.
* basic proof of concept file activity support - will send activity via the ↵marijus2015-01-182-2/+5
| | | | filestorage module and via attach_delete()
* uninitialised theme parent in mod/cloudfriendica2015-01-121-1/+1
|
* theme toggle issue when viewing mod/cloud of another channelfriendica2015-01-121-0/+9
|
* design fixes for photos, files and random fixesmarijus2014-12-301-0/+6
|
* some more mime-type -> icon for filebrowsermarijus2014-12-271-2/+13
|
* more work on filesmarijus2014-12-271-0/+41
|
* files: make mod/filestorage.php load via ajax and some design work. work in ↵marijus2014-12-211-10/+14
| | | | progress...
* Add security logger to RedDAV.Klaus Weidenbach2014-12-142-6/+10
| | | | Some smaller clean ups whitepsaces and tabs, use PHP_EOL, Doxygen, etc.
* PostgreSQL support initial commitHabeas Codice2014-11-132-13/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There were 11 main types of changes: - UPDATE's and DELETE's sometimes had LIMIT 1 at the end of them. This is not only non-compliant but it would certainly not do what whoever wrote it thought it would. It is likely this mistake was just copied from Friendica. All of these instances, the LIMIT 1 was simply removed. - Bitwise operations (and even some non-zero int checks) erroneously rely on MySQL implicit integer-boolean conversion in the WHERE clauses. This is non-compliant (and bad programming practice to boot). Proper explicit boolean conversions were added. New queries should use proper conventions. - MySQL has a different operator for bitwise XOR than postgres. Rather than add yet another dba_ func, I converted them to "& ~" ("AND NOT") when turning off, and "|" ("OR") when turning on. There were no true toggles (XOR). New queries should refrain from using XOR when not necessary. - There are several fields which the schema has marked as NOT NULL, but the inserts don't specify them. The reason this works is because mysql totally ignores the constraint and adds an empty text default automatically. Again, non-compliant, obviously. In these cases a default of empty text was added. - Several statements rely on a non-standard MySQL feature (http://dev.mysql.com/doc/refman/5.5/en/group-by-handling.html). These queries can all be rewritten to be standards compliant. Interestingly enough, the newly rewritten standards compliant queries run a zillion times faster, even on MySQL. - A couple of function/operator name translations were needed (RAND/RANDOM, GROUP_CONCAT/STRING_AGG, UTC_NOW, REGEXP/~, ^/#) -- assist functions added in the dba_ - INTERVALs: postgres requires quotes around the value, mysql requires that there are not quotes around the value -- assist functions added in the dba_ - NULL_DATE's -- Postgres does not allow the invalid date '0000-00-00 00:00:00' (there is no such thing as year 0 or month 0 or day 0). We use '0001-01-01 00:00:00' for postgres. Conversions are handled in Zot/item packets automagically by quoting all dates with dbescdate(). - char(##) specifications in the schema creates fields with blank spaces that aren't trimmed in the code. MySQL apparently treats char(##) as varchar(##), again, non-compliant. Since postgres works better with text fields anyway, this ball of bugs was simply side-stepped by using 'text' datatype for all text fields in the postgres schema. varchar was used in a couple of places where it actually seemed appropriate (size constraint), but without rigorously vetting that all of the PHP code actually validates data, new bugs might come out from under the rug. - postgres doesn't store nul bytes and a few other non-printables in text fields, even when quoted. bytea fields were used when storing binary data (photo.data, attach.data). A new dbescbin() function was added to handle this transparently. - postgres does not support LIMIT #,# syntax. All databases support LIMIT # OFFSET # syntax. Statements were updated to be standard. These changes require corresponding changes in the coding standards. Please review those before adding any code going forward. Still on my TODO list: - remove quotes from non-reserved identifiers and make reserved identifiers use dba func for quoting - Rewrite search queries for better results (both MySQL and Postgres)
* move all theme initialisation to one place - just after calling module_init. ↵friendica2014-10-201-0/+1
| | | | Revert if there are serious issues, but please note the issues in as much detail as possible so we can work through them.
* When you delete something in /cloud stay in the right folder.Klaus Weidenbach2014-10-144-56/+70
| | | | | | | When you deleted a file in /cloud you was always jumped back to /cloud/[channel], now you will stay in the parent folder. Some more doxygen documentation. Removed duplicate data from logging output and reduced logging in RedDAV in general.
* Moved classes from reddav.php into own files.Klaus Weidenbach2014-10-124-7/+954
| | | | | | 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.
* change parent constructor per discussionfriendica2014-10-081-1/+1
|
* dav issuefriendica2014-10-081-1/+1
|
* Moved RedBrowser class from reddav.php to it's own file.Klaus Weidenbach2014-10-061-0/+361
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.