aboutsummaryrefslogtreecommitdiffstats
path: root/boot.php
Commit message (Collapse)AuthorAgeFilesLines
* provide compatibility functions so code breakage with customised setups or ↵friendica2015-01-281-0/+12
| | | | work in progress should be minor
* remote_user => remote_channelfriendica2015-01-281-1/+1
|
* local_user => local_channelfriendica2015-01-281-8/+8
|
* provide storage for directory based reputation in the xlink table by setting ↵friendica2015-01-261-1/+1
| | | | xlink_static = 1, so that xlink_static = 0 is traditional poco linkages
* Merge branch 'master' of https://github.com/friendica/redmarijus2015-01-221-1/+2
|\
| * added redmatrix.nl back as a directory server. this was not the issue with ↵Jeroen2015-01-221-1/+2
| | | | | | | | the performance problems
* | change mod/sharedwithme backend to use activity object - this is not ↵marijus2015-01-221-1/+1
|/ | | | backwards compatible
* add my.federated.social as directory serverfriendica2015-01-201-0/+1
|
* typo in postgres db update, remove redmatrix.nl from directory servers since ↵friendica2015-01-201-1/+0
| | | | it isn't a directory server any more.
* oauth permissions tablefriendica2015-01-191-1/+1
|
* fix update 1131 for postgres databasesHabeas Codice2015-01-181-1/+1
|
* more backend work on poco ratingfriendica2015-01-151-1/+1
|
* some back-end code to support location activity objects. Work in progress.friendica2015-01-141-0/+1
|
* federate consensus items (in network only). Work in progress.friendica2015-01-141-1/+1
|
* provide a setting to control ALLOWCODE permissions at the channel level - it ↵friendica2015-01-131-1/+1
| | | | isn't always appropriate to apply this to all channels in an account.
* basic backend work for creating consensus itemsfriendica2015-01-111-0/+4
|
* basic changes for file activitymarijus2015-01-091-0/+1
|
* syncing connections issue, incorrect return_url after deleting connectionfriendica2015-01-071-1/+1
|
* don't allow admin to delete the sys channel from the channel manage pagefriendica2015-01-061-1/+1
|
* Sorting of autocompleteStefan Parviainen2015-01-041-0/+16
|\
| * no newline at end of filefriendica2015-01-021-1/+1
| |
| * syntax issues (with some php versions?), unchecked intvalfriendica2015-01-011-0/+16
| |
* | Autocmplete suggestions for non-local users, also suggest from visited ↵Stefan Parviainen2015-01-041-0/+1
|/ | | | channel's connections
* filter posts you author from unseen notifications - note there are other ↵friendica2014-12-281-0/+2
| | | | ways to do this, but involve some code complexity. This is easier to implement but may have a slight impact on the ping query performance. It's not horrid, just mentioning for the record.
* doc updatefriendica2014-12-261-1/+1
|
* provide last successful poll run time (using relative time) in siteinfo so ↵friendica2014-12-211-0/+10
| | | | that we can tell folks that have no idea what we're talking about that their poller definitely isn't running and this is probably why nothing works correctly.
* Add security logger to RedDAV.Klaus Weidenbach2014-12-141-1/+10
| | | | Some smaller clean ups whitepsaces and tabs, use PHP_EOL, Doxygen, etc.
* Fix WSOD on loginThomas Willingham2014-12-121-3/+5
|
* Some Doxygen comments and small cleanups.Klaus Weidenbach2014-12-071-50/+138
|
* Put dir back - the fat lady didn't sing afterall.Thomas Willingham2014-12-041-1/+2
|
* Update dir fallbacks.Thomas Willingham2014-11-251-1/+0
|
* some poller optimisations and a fix for undefined (empty) dbtype which shows ↵friendica2014-11-161-1/+2
| | | | up as a mysql error that 'rand' isn't found.
* Merge pull request #691 from dawnbreak/masterRedMatrix2014-11-141-19/+24
|\ | | | | Changed two strange looking places in boot.php.
| * Fixed a variable conflict in mod/xchan.php.Klaus Weidenbach2014-11-141-1/+1
| | | | | | | | | | A variable $rr inside the foreachs was used twice. Add translation to mod/xchan.php.
| * Changed two strange looking places in boot.php.Klaus Weidenbach2014-11-131-19/+24
| | | | | | | | | | There have been two places that looked wrong, but I don't know how I can test them. So please review and test if I am not wrong.
* | Merge remote-tracking branch 'upstream/master'Habeas Codice2014-11-131-169/+186
|\| | | | | | | | | | | | | | | | | | | | | | | Conflicts: boot.php include/dba/dba_driver.php include/diaspora.php include/follow.php include/session.php include/zot.php mod/photos.php mod/ping.php
| * Some Doxygen documentation.Klaus Weidenbach2014-11-131-162/+162
| | | | | | | | | | Add some more Doxygen formating for boot.php and dba_driver.php. Cleaning a bit up, too.
| * slow progress on sys publishing, making sure all the data we need is in the ↵friendica2014-11-111-2/+2
| | | | | | | | places we need it but validate it anyway
| * add public forum identification to libzot. No attempt is made to identify ↵friendica2014-11-101-0/+1
| | | | | | | | other types of forums or weird custom channel permissions. If the channel is auto-accept and taggable, it's a public forum.
| * include self in load_contact_links so you don't get a connect menu entry for ↵friendica2014-11-061-3/+2
| | | | | | | | yourself
| * Provide a way to mark photos as adult and hide them from the default album ↵friendica2014-11-061-0/+1
| | | | | | | | view. Still need a button or setting to enable "unsafe viewing". This has no effect anywhere but in the album views. They can still be viewed by flipping through the individual photos with 'prev' and 'next'. We probably need a comprehensive strategy for how to deal with n-s-f-w photos in albums so consider this a band-aid which requires additional work and integration with other facilities which access these photos. It is entirely optional.
| * ok heads up - potentially destabilising change. I've tried to sort out all ↵friendica2014-11-041-1/+1
| | | | | | | | | | | | | | | | | | | | 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).
| * configurable visual alerts/notificationsfriendica2014-11-041-0/+16
| |
| * Pixelbit restored. Going forwards, we probably want to add a checkThomas Willingham2014-11-021-0/+1
| | | | | | | | | | | | that a directory is returning something in find_upstream_directory() since this was spotted by a new install who thought *they* were broken.
| * Remove pixelbits from directory fallback - blocked public searches provideThomas Willingham2014-11-021-1/+0
| | | | | | | | no results.
* | PostgreSQL support initial commitHabeas Codice2014-11-131-5/+7
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-6/+10
| | | | Revert if there are serious issues, but please note the issues in as much detail as possible so we can work through them.
* mark signature forgeriesfriendica2014-10-161-0/+1
|
* this is the reason Diaspora forum tagging was brokenfriendica2014-10-141-1/+1
|
* allow custom role permissions and fix site timezone.friendica2014-09-291-4/+2
|