aboutsummaryrefslogtreecommitdiffstats
path: root/install/update.php
Commit message (Collapse)AuthorAgeFilesLines
* add site_dead flag to prevent delivery to dead sites. Allow sys channel ↵redmatrix2015-06-081-1/+12
| | | | webpages to be viewed even if site is configured "block public".
* add menu_created, menu_edited fields to DBredmatrix2015-05-281-1/+23
|
* provide default permissions ('all') for existing and newly created OAuth app ↵redmatrix2015-05-141-2/+23
| | | | clients, which will be extended in the future to allow specific permissions.
* add channel_lastpost timestamp to help optimise some outrageously expensive ↵friendica2015-03-261-1/+15
| | | | queries.
* add queue priorityfriendica2015-03-041-1/+10
|
* finish converting "delete" to trash icons for consistency. The 'x' was left ↵friendica2015-02-261-2/+6
| | | | in a couple of places like the group list widget and saved search term widget and ignoring friend suggestions where it was more appropriate to leave it.
* require access token to view, query, or join directories in private realms, ↵friendica2015-02-241-1/+9
| | | | if the realm is so configured.
* make sql work on both db typesHabeas Codice2015-02-131-1/+1
|
* provide relief to sites that are severely impacted by the slow ITEM_UNSEEN ↵friendica2015-02-121-1/+11
| | | | 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.
* make update 1133 work in PHP < 5.5zottel2015-02-101-1/+1
|
* Merge branch 'master' of https://github.com/friendica/redHabeas Codice2015-02-051-2/+9
|\
| * admin/dbsync not reporting failed updatesfriendica2015-02-011-1/+1
| |
| * two tracks proceeding in parallel - first adding the ability to store a ↵friendica2015-02-011-1/+8
| | | | | | | | digital signature with ratings so that directories can pass them around, second provide some directory registration functions so we can obtain a list of directories from somewhere (to pass ratings around between them). This gives the primary directory role some value as that is where you register your directory.
* | typo/cleanup pg onlyHabeas Codice2015-02-051-4/+5
|/
* postgres does not support the , syntax. a ; would work, if it weren't ↵Habeas Codice2015-01-281-1/+3
| | | | | | | statement-locked. FWIW, the exact same queries listed for postgres are perfectly valid and equivalent on mysql. no need for separate statements.
* provide storage for directory based reputation in the xlink table by setting ↵friendica2015-01-261-1/+12
| | | | xlink_static = 1, so that xlink_static = 0 is traditional poco linkages
* unmatched parensHabeas Codice2015-01-231-1/+1
|
* typo in postgres db update, remove redmatrix.nl from directory servers since ↵friendica2015-01-201-1/+1
| | | | it isn't a directory server any more.
* oauth permissions tablefriendica2015-01-191-2/+32
|
* fix update 1131 for postgres databasesHabeas Codice2015-01-181-1/+14
|
* more backend work on poco ratingfriendica2015-01-151-1/+11
|
* ok heads up - potentially destabilising change. I've tried to sort out all ↵friendica2014-11-041-1/+21
| | | | | | | | | | the default connection permissions for those who don't have a predefined (or therefore have a "custom") permissions role. Unfortunately this includes most people that were using this software more than a month ago. The real changes are that the SELF address book entry no longer holds "auto-permissions" but instead holds your "default permissions" (if you have a pre-defined role, the defaults will be pulled from the role table). The auto permissions have moved to a pconfig (uid.system.autoperms). A DB update will move these settings into their new homes. What used to be the "Auto-permissions settings" page is now the "default permissions settings" page and a checkbox therein decides whether or not to apply the permissions automatically. A link to this page will only be shown when you have the "custom" role selected. With luck nobody will notice anything wrong. But at least for the next few days, please review permissions that have been assigned to new connections (either automatically or manually) and make sure they make sense (e.g. they aren't "nothing"). You still need to take action when seeing a message "permissions have changed but not yet submitted" as we always let you review and perhaps adjust the settings _before_ a connection is established (unless you have autoperms turned on).
* missing quotefriendica2014-10-141-1/+1
|
* this is the reason Diaspora forum tagging was brokenfriendica2014-10-141-1/+8
|
* store diaspora meta info in the item table. It has to go there or it will ↵friendica2014-09-031-1/+10
| | | | kill us with complex joins. We can phase out the sign table once this all checks out.
* Ability to close comments at a certain date/time - needed for loom.io ↵friendica2014-08-281-1/+9
| | | | emulation (and many other uses)
* mind numbing drudgery continued...friendica2014-08-271-1/+11
|
* place to store multiple choice and select items for extensible profilesfriendica2014-08-261-1/+10
|
* more hard workfriendica2014-08-261-1/+33
|
* We really can't do this without a hubloc. I was hoping we could, but ↵friendica2014-08-221-1/+13
| | | | notifier is setup to take hublocs, not xchans.
* some more work on realmsfriendica2014-08-171-1/+9
|
* provide backend storage and declaration of directory realmfriendica2014-08-161-1/+10
|
* item table upgrade for storing post visibilityfriendica2014-08-061-1/+10
|
* db tables for extensible profile fieldsfriendica2014-08-021-1/+29
|
* block channel removal for 48 hours after changing the account password, ↵friendica2014-07-291-1/+10
| | | | since the password is required to remove a channel. Somebody looking at an open session on somebody else's computer can simply change the password and then proceed to maliciously remove the channel. This change gives the owner 2 days to discover that something is wrong and recover his/her password and potentially save their channel from getting erased by the vandal. This is most likely to happen if a relationship has gone bad, or something incriminating was found in your private messages when you left your computer briefly unattended.
* provide a specific permission for liking profiles (reuse the obsolete ↵friendica2014-07-171-2/+12
| | | | bookmark permission), also remove the unused 'unconnected contacts' view for now.
* provide os_mkdir to workaround permission issues with php mkdirfriendica2014-07-161-2/+2
|
* move smarty compiled files to store/[data]/smarty3 - which puts all ↵friendica2014-07-101-3/+8
| | | | writeable areas of the server except the config file and logs under the "store" directory. We'll do logs at a future time.
* finish implementing email verification. Currently it only applies if ↵friendica2014-07-091-1/+9
| | | | REGISTER_OPEN is in effect.
* ability to like thingsfriendica2014-06-231-1/+9
|
* honour the admin censored flag in the directory, and some slow progress on ↵friendica2014-06-221-1/+11
| | | | extended likes
* likes table for liking things besides posts and commentsfriendica2014-06-221-1/+23
|
* implement 'requires' on personal appsfriendica2014-05-221-1/+8
|
* try to recover from bad updatefriendica2014-05-201-1/+13
|
* more app backend workfriendica2014-05-191-2/+9
|
* support commerical appsfriendica2014-05-181-1/+12
|
* app DB structurefriendica2014-05-171-1/+26
|
* use parent_mid in the parent query for enotify instead of of the parent id. ↵friendica2014-04-061-1/+8
| | | | This should fix the issue with encrypted content in the notification messages (for locally posted replies). The fix was a bit harder than anticipated because we store the parent id as an int in the notify table so this had to be modified to char storage as well.
* more efficient public feed fetchingfriendica2014-04-021-1/+10
|
* finish up the source route storage so we can prevent messages from flowing ↵friendica2014-03-311-1/+8
| | | | upstream in complicated delivery chains
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-22 17:52:53 +0000