aboutsummaryrefslogtreecommitdiffstats
path: root/include/apps.php
Commit message (Collapse)AuthorAgeFilesLines
* Sync the current list of system apps with the built-in name translation ↵redmatrix2016-05-031-3/+8
| | | | table. Some of the names were changed in the past without the translation table being updated to reflect it.
* more background work for app management - give every member a copy of all ↵redmatrix2016-05-031-13/+60
| | | | the system apps so that they can edit and delete them to taste/preference. This needs further work to pick up changes in system apps (additions, edits, deletions, etc.). Currently this is done once and never attempted again.
* some preliminary structural work for app organisationredmatrix2016-05-031-2/+7
|
* static Appredmatrix2016-03-311-5/+5
|
* turn relative links in app_render() into absolute links, without affecting ↵redmatrix2015-10-211-3/+8
| | | | the install.
* change name of matrix appredmatrix2015-10-141-1/+1
|
* app syncredmatrix2015-09-021-2/+21
|
* add timestamps for syncing appsredmatrix2015-09-021-3/+10
|
* initial work on obj import, rename import_profile_photo to ↵redmatrix2015-09-011-2/+2
| | | | import_xchan_photo to more accurately state its purpose.
* remote_user => remote_channelfriendica2015-01-281-1/+1
|
* local_user => local_channelfriendica2015-01-281-12/+12
|
* Fix feature check in apps (missing parenthesis), allow multiple requires ↵Stefan Parviainen2014-12-221-54/+59
| | | | (comma separated)
* PostgreSQL support initial commitHabeas Codice2014-11-131-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* allow a site to over-ride the system app list without causing git issuesfriendica2014-10-091-1/+4
|
* provide a config option to prevent wall uploads (photos and files) from ↵friendica2014-09-021-30/+0
| | | | being set to the same ACL as the containing post, and instead are uploaded with public visibility (no ACL). This is to prevent folks on other networks from seeing prohibited signs for things uploaded into a private conversation. It is primarily useful when posting to collections that have mixed folks from red and other networks and an otherwise public (typical) profile. Consequently, these uploads will match your chosen default visibility for photos and storage and not that of the containing conversation item (and is only useful if the default visibility is public). This choice must be explained adequately because it represents a complex series of tradeoffs and side effects. It will reduce complaints from other networks about blocked content, but essentially forces you to use another method (dav or the photos page) if you wish to upload protected files/media.
* Ability to close comments at a certain date/time - needed for loom.io ↵friendica2014-08-281-1/+1
| | | | emulation (and many other uses)
* begin embeddable/shareable design elements (blocks, webpages, layouts, ↵friendica2014-08-271-1/+33
| | | | menus, etc.)
* Added some missing translation strings. Fixed to scalable for a few font sizes.Jeroen2014-08-141-1/+7
|
* visage tracking opt-in/opt-outfriendica2014-07-031-0/+9
|
* issue #433friendica2014-06-101-1/+1
|
* merge the app menusfriendica2014-06-101-3/+13
|
* syntax errorfriendica2014-06-101-1/+1
|
* should really wait until after the first cuppafriendica2014-06-101-4/+5
|
* remote install app (untested)friendica2014-06-101-1/+14
|
* suggest appfriendica2014-06-031-1/+3
|
* give the cloud file list a bit of paddingfriendica2014-05-271-22/+24
|
* fix search to use in appfriendica2014-05-221-1/+2
|
* more appsfriendica2014-05-221-0/+2
|
* implement 'requires' on personal appsfriendica2014-05-221-6/+43
|
* sort by app name and not by apd filenamefriendica2014-05-221-1/+4
|
* Add the admin appfriendica2014-05-211-0/+5
|
* more app workfriendica2014-05-211-3/+16
|
* make it possible to edit/delete apps via /apps/personal/editfriendica2014-05-211-0/+3
|
* add zids to all the personal app linksfriendica2014-05-201-0/+5
|
* more app workfriendica2014-05-201-8/+29
|
* most of the remaining apps basic infrastructure except a form to create the ↵friendica2014-05-201-4/+50
| | | | things. Don't let this fool you - there is still a lot of work, but there isn't a whole lot of work to create a demo; in fact you can demo it now.
* more app backend workfriendica2014-05-191-4/+41
|
* apps: fix encoding/decoding and chunk splittingfriendica2014-05-181-2/+2
|
* start to build out the appsfriendica2014-05-181-6/+56
|
* more app workfriendica2014-05-181-0/+44
|
* more app infrastructurefriendica2014-05-181-4/+49
|
* the help appfriendica2014-05-161-1/+1
|
* add hover tips - except we need a way to translate the thingsfriendica2014-05-151-0/+5
|
* login appfriendica2014-05-151-0/+4
|
* add directoryfriendica2014-05-151-1/+1
|
* more base appsfriendica2014-05-151-1/+1
|
* the app menu takes formfriendica2014-05-151-3/+43
|
* apps: provide a default photo if none was set. For now it's the default ↵friendica2014-05-151-1/+14
| | | | profile photo until we have a default app photo
* some backend stuff for appsfriendica2014-05-151-0/+53