aboutsummaryrefslogtreecommitdiffstats
path: root/include/api.php
Commit message (Collapse)AuthorAgeFilesLines
...
| * api extenesions for file migrationredmatrix2015-10-131-4/+5
| |
* | port of file detail api callredmatrix2015-10-121-3/+1
| |
* | Merge https://github.com/redmatrix/redmatrix into pending_mergeredmatrix2015-10-121-0/+24
|\|
| * file detail api call (will not work for huge files)redmatrix2015-10-121-0/+24
| |
* | Merge https://github.com/redmatrix/redmatrix into pending_mergeredmatrix2015-10-121-0/+8
|\| | | | | | | | | Conflicts: include/attach.php
| * attach_list_files had some problems - wasn't used until now apparentlyredmatrix2015-10-121-0/+8
| |
* | preserve code blocks on item import if channel has code rights. When ↵redmatrix2015-09-081-0/+49
| | | | | | | | | | | | importing the channel itself, turn code access off unless this is the admin.
* | Merge https://github.com/redmatrix/redmatrix into pending_mergeredmatrix2015-08-261-1/+1
|\|
| * use extended export format for items in api photo_detailredmatrix2015-08-261-1/+1
| |
* | Merge https://github.com/redmatrix/redmatrix into pending_mergeredmatrix2015-08-261-1/+21
|\|
| * add item info to photo detail in apiredmatrix2015-08-261-1/+21
| |
* | Merge https://github.com/redmatrix/redmatrix into pending_mergeredmatrix2015-08-191-50/+71
|\| | | | | | | | | Conflicts: include/api.php
| * add photo_detail api callredmatrix2015-08-181-68/+89
| |
* | item flag fixes discovered after a few mergesredmatrix2015-06-231-10/+7
| |
* | convert the abook fieldsredmatrix2015-06-141-7/+7
| |
* | more work on item table optimisationredmatrix2015-06-101-13/+26
| |
* | Merge branch 'master' of https://github.com/redmatrix/redmatrixredmatrix2015-05-271-0/+32
|\| | | | | | | | | Conflicts: mod/impel.php
| * some high-level stuff we may need for shareable menus. Also make the client ↵redmatrix2015-05-271-11/+1
| | | | | | | | register function do the right thing even though I refuse to make it work. If **you** want service federation with things like pumpio and openid connect, it's time for **you** to put your own skin in the game and quit treating project volunteers like excrement just because you can't get up off your lazy buttocks.
| * Update api.phpjeroenpraat2015-05-261-1/+1
| | | | | | one comma to much
| * placeholder for dynamic regoredmatrix2015-05-251-2/+2
| |
| * slow but forward progress on dynamic client registrationredmatrix2015-05-251-0/+42
| |
* | Merge branch 'master' into tresredmatrix2015-05-171-1/+4
|\ \
| * | Merge branch 'master' of https://github.com/redmatrix/redmatrixredmatrix2015-05-171-1/+4
| |\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| | * Implement permission checking for OAuth clients using the xperm table. ↵redmatrix2015-05-171-1/+4
| | | | | | | | | | | | Currently 'all' permissions are applied to OAuth clients which gives them the same rights as the channel owner and full access to API functions as the channel owner. However, individual permissions can now be created. These mirror the permission names from the normal permission table (although it isn't required that they do so). Lack of an xp_perm entry for the specified permission and lack of an 'all' override indicates permission denied.
* | | Merge branch 'master' into tresredmatrix2015-05-141-2/+2
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: include/Import/refimport.php include/activities.php include/attach.php include/event.php include/externals.php include/identity.php include/items.php include/notifier.php include/photos.php include/taxonomy.php include/zot.php mod/channel.php mod/connedit.php mod/events.php mod/item.php mod/like.php mod/manage.php mod/mood.php mod/ping.php mod/poke.php mod/subthread.php mod/tagger.php mod/thing.php
| * | Merge branch 'master' of https://github.com/redmatrix/redmatrixredmatrix2015-05-131-1/+1
| |\| | | | | | | | | | | | | | | | | | | Conflicts: boot.php include/api.php include/enotify.php
| | * product was a bad string to use because we may require it for e-commerce, ↵redmatrix2015-05-131-1/+1
| | | | | | | | | | | | and RED_PLATFORM is equally problematic for other reasons.
| * | convert ITEM_WALL from bitfield to standaloneredmatrix2015-05-061-3/+2
| | |
| * | first pass name changeredmatrix2015-05-051-1/+1
| |/
* | Merge branch 'master' into tresfriendica2015-04-231-93/+264
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: include/Contact.php include/ItemObject.php include/api.php include/attach.php include/diaspora.php include/dir_fns.php include/enotify.php include/event.php include/expire.php include/items.php include/notifier.php include/notify.php include/photos.php include/taxonomy.php include/text.php include/widgets.php include/zot.php mod/admin.php mod/channel.php mod/dirsearch.php mod/display.php mod/editwebpage.php mod/events.php mod/home.php mod/item.php mod/manage.php mod/mood.php mod/network.php mod/page.php mod/photos.php mod/ping.php mod/post.php mod/thing.php mod/viewsrc.php view/css/mod_events.css
| * doco updatesfriendica2015-04-191-3/+0
| |
| * add favorites/create and destroy to apifriendica2015-04-191-36/+137
| |
| * api performance enhancerfriendica2015-04-191-5/+2
| |
| * assorted fixes to api direct messagesfriendica2015-04-191-31/+35
| |
| * some api cleanupfriendica2015-04-191-11/+15
| |
| * api - unobscure mailfriendica2015-04-191-4/+4
| |
| * log this since we may need it to track down failuresfriendica2015-04-181-2/+3
| |
| * remove failed experimentfriendica2015-04-171-2/+0
| |
| * add last post to api/account/verify_credentialsfriendica2015-04-171-5/+60
| |
| * limit notification detail queries for items and eventsfriendica2015-03-231-1/+5
| |
| * operation snakebite, cont.friendica2015-03-221-0/+10
| |
| * also update the api to matchfriendica2015-03-161-2/+2
| |
| * remove superfluous non-boolean booleanHabeas Codice2015-02-161-2/+2
| |
| * provide relief to sites that are severely impacted by the slow ITEM_UNSEEN ↵friendica2015-02-121-4/+1
| | | | | | | | searches. This does not incorporate any other flag optimisations as that will require a major DB update and possibly involve significant downtime. This is just to bite off a little chunk now and provide some much needed relief.
* | Merge branch 'master' into tresfriendica2015-01-291-2/+2
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: include/group.php include/text.php mod/acl.php mod/channel.php mod/connections.php mod/display.php mod/group.php mod/item.php mod/locs.php mod/network.php mod/photos.php mod/ping.php mod/starred.php mod/viewsrc.php
| * local_user => local_channelfriendica2015-01-281-2/+2
| |
* | heavy lifting converting item flag bitsfriendica2015-01-221-11/+6
|/
* some improvements in api direct messagesfriendica2014-12-221-4/+9
|
* direct messages in api have some issues, not properly ported from friendica ↵friendica2014-12-221-9/+10
| | | | | | originally. Here's a start. I think at best they may return encrypted gibberish currently, but let's work through them one at a time.
* PostgreSQL support initial commitHabeas Codice2014-11-131-14/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)