aboutsummaryrefslogtreecommitdiffstats
path: root/include
Commit message (Collapse)AuthorAgeFilesLines
* Merge remote-tracking branch 'upstream/master'Habeas Codice2014-11-182-0/+29
|\
| * place holderfriendica2014-11-171-0/+5
| |
| * Merge https://github.com/friendica/red into pending_mergefriendica2014-11-171-17/+28
| |\
| * | add unseen count and way to mark unseen to list mode. Also fix automatic ↵friendica2014-11-171-0/+24
| | | | | | | | | | | | mark of unseen so as to work with list mode.
* | | postgres fixesHabeas Codice2014-11-181-3/+3
| |/ |/|
* | Merge pull request #695 from pafcu/masterRedMatrix2014-11-181-17/+28
|\ \ | |/ |/| Switch to a better datetime picker widget
| * Switch to a better datetime picker widgetStefan Parviainen2014-11-161-17/+28
| |
* | remove old timersfriendica2014-11-161-20/+2
| |
* | speed things up a wee bitfriendica2014-11-162-7/+16
| |
* | "list mode" (forum and blog mode, no comments or comment boxes displayed on ↵friendica2014-11-161-2/+3
| | | | | | | | the summary page)
* | some poller optimisations and a fix for undefined (empty) dbtype which shows ↵friendica2014-11-163-26/+39
|/ | | | up as a mysql error that 'rand' isn't found.
* minor changes to support forum modefriendica2014-11-152-21/+7
|
* Merge pull request #693 from habeascodice/masterRedMatrix2014-11-141-0/+4
|\ | | | | Add bitwise xor to db_getfunc()
| * Add bitwise xor to db_getfunc()Habeas Codice2014-11-131-0/+4
| |
* | mysql driver - in debug mode for statements that return true/false report ↵friendica2014-11-131-1/+1
| | | | | | | | the sql along with the result so we can match it to an offending statement. This has bugged me for some time but never got around to fixing it until now.
* | put timeout code in place but don't turn it on.friendica2014-11-131-6/+7
|/
* Merge remote-tracking branch 'upstream/master'Habeas Codice2014-11-1321-129/+750
|\ | | | | | | | | | | | | | | | | | | | | | | 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-44/+128
| | | | | | | | | | Add some more Doxygen formating for boot.php and dba_driver.php. Cleaning a bit up, too.
| * make search and advanced search use the same input formmarijus2014-11-121-2/+1
| |
| * cleanupfriendica2014-11-112-2/+9
| |
| * slow progress on sys publishing, making sure all the data we need is in the ↵friendica2014-11-112-2/+2
| | | | | | | | places we need it but validate it anyway
| * a couple of places where we need to look for a sys channel euid.friendica2014-11-111-0/+7
| |
| * and urlencode that.friendica2014-11-111-2/+2
| |
| * Most directory searches are POST. get_query_args() only handles GET so that ↵friendica2014-11-111-1/+9
| | | | | | | | had to be fixed or page 2 of directory search results wouldn't match the search.
| * the code is a bit crufty, but this should fix issue #687friendica2014-11-111-3/+10
| |
| * Merge https://github.com/friendica/red into pending_mergefriendica2014-11-101-3/+3
| |\
| | * Merge pull request #685 from zzottel/masterRedMatrix2014-11-111-3/+3
| | |\ | | | | | | | | set channel_w_stream to 0 for forum roles
| | | * set channel_w_stream to 0 for forum roleszottel2014-11-101-3/+3
| | | |
| * | | issue #683 - don't linkify homepage field without validatingfriendica2014-11-101-0/+2
| |/ /
| * | indicate public forums in directory results (there will be some [possibly ↵friendica2014-11-101-4/+5
| | | | | | | | | | | | considerable] lag time before existing forums are correctly tagged).
| * | add public forum identification to libzot. No attempt is made to identify ↵friendica2014-11-101-2/+6
| |/ | | | | | | other types of forums or weird custom channel permissions. If the channel is auto-accept and taggable, it's a public forum.
| * Use consistent terminology for channel directoryStefan Parviainen2014-11-091-1/+1
| |
| * tgroup_check - decrypt if obscured before checking body text for resharesfriendica2014-11-071-1/+9
| |
| * revert that bitfriendica2014-11-071-7/+1
| |
| * visible flag reversedfriendica2014-11-061-1/+1
| |
| * Provide a way to mark photos as adult and hide them from the default album ↵friendica2014-11-061-4/+10
| | | | | | | | 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.
| * don't overwrite $x (contains import_xchan result) with role permissionszottel2014-11-061-3/+3
| |
| * make sure the "tagcloud" actually shows hashtags. So we don't confuse folks ↵friendica2014-11-061-1/+1
| | | | | | | | with categories.
| * category tagblockfriendica2014-11-062-0/+33
| |
| * logging changes, untranslated stringfriendica2014-11-052-4/+4
| |
| * some minor cleanup of unreported (and as yet undiscovered) issues with ↵friendica2014-11-052-2/+5
| | | | | | | | permissions toggling. No smoking guns and no obvious issues discovered here. Repeated and tried to duplicate zottell's issue as described without seeing any obvious problems.
| * ok heads up - potentially destabilising change. I've tried to sort out all ↵friendica2014-11-045-29/+37
| | | | | | | | | | | | | | | | | | | | 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).
| * Merge https://github.com/friendica/red into pending_mergefriendica2014-11-031-2/+3
| |\
| | * innodb issueThomas Willingham2014-11-031-2/+3
| | |
| * | various UI issues related to having an enormous number of entries in the ↵friendica2014-11-032-4/+20
| |/ | | | | | | posted_date selector including years/months that had no posts
| * provide example import scriptfriendica2014-11-032-0/+376
| |
| * php warningsfriendica2014-11-021-23/+23
| |
| * I'm going to try again with the conversation request packets. I've looked ↵friendica2014-11-022-13/+60
| | | | | | | | this over and tested a lot of edge cases, and thought about from every angle I can think of to prevent looping. I don't *think* this can loop. I also doubt that this is the problem at friendicared.de, but I don't know for sure what that problem might be.
| * add some more safety checks before turning the conversation request messages ↵friendica2014-11-022-4/+6
| | | | | | | | back on
* | PostgreSQL support initial commitHabeas Codice2014-11-1351-403/+696
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)