aboutsummaryrefslogtreecommitdiffstats
path: root/include/config.php
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'dev' into permsredmatrix2016-07-131-3/+2
|\
| * let abconfig specify a familyredmatrix2016-07-131-2/+2
| |
* | more permissions workredmatrix2016-07-091-1/+1
|/
* change AbConfig to use channel_id instead of channel_hash; which was a ↵redmatrix2016-06-231-8/+8
| | | | mistake in retrospect
* iconfig sharing not set correctlyredmatrix2016-06-101-1/+1
|
* Finish the config familyredmatrix2016-06-071-368/+18
|
* move pconfig to static classredmatrix2016-06-051-174/+6
|
* begin moving config to zotlabs. Leave procedural stubs for backward ↵redmatrix2016-05-301-144/+17
| | | | comaptibility
* code cleanupredmatrix2016-05-241-11/+3
|
* Add space between project name and server typeredmatrix2016-05-241-1/+1
|
* move iconfig functions to include/config.php with all the rest of the ↵redmatrix2016-04-261-0/+157
| | | | configs, fix an issue with singleton discovery and start work on singleton delivery
* static Appredmatrix2016-03-311-73/+73
|
* issue #319 - NOTE: this does not fix the issue, it only reports it and ↵redmatrix2016-03-301-0/+11
| | | | continues. We need to examine any logger statements that contain 'stack:' as a result of reporting this issue and find and fix the original problem - which is that set_pconfig is being called without a valid $uid. I'm worried that since we will now continue on without throwing a PHP error that nobody will ever notice or find the problem that is causing this.
* abconfigredmatrix2016-02-291-1/+65
|
* "aconfig" or account configuration storage, needed for some upcoming work. ↵redmatrix2016-01-111-0/+19
| | | | Built on top of xconfig.
* Correcting reported Doxygen syntax warnings.Klaus Weidenbach2015-03-291-11/+18
| | | | | | | Fixed wrong Doxygen syntax and add some of the available FIXME to Doxygen documentation. Updated Doxygen configuration to add also all capital letter tags. Adding some more Doxygen documentation.
* local_user => local_channelfriendica2015-01-281-1/+1
|
* hide online presence maps to DNTfriendica2014-11-241-3/+3
|
* PostgreSQL support initial commitHabeas Codice2014-11-131-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* Silence insanely noisy log - should probably stick this in a dloggerThomas Willingham2014-09-291-1/+1
| | | | if we need it - we're getting literally hundreds of thousands of these.
* Some documentation of include/config.php.Klaus Weidenbach2014-09-261-105/+269
| | | | | I hope my guesses are not completely wrong, anyway please take look not that I tell complete bullshit.
* file had wrong extensionfriendica2014-03-111-9/+0
|
* config: don't try to unserialise an arrayfriendica2014-02-011-4/+4
|
* The check for f*cked database (which otherwise sends out zillions of update ↵friendica2013-10-041-3/+3
| | | | failed emails) interferes with install. So what else can we do about f*cked databases which open successfully but don't actually read/write data? It would of course be nice if we didn't have to deal with them, but apparently we do. For now we're not doing anything until I can figure out how to take the site offline when it happens without affecting install.
* suppress creating the directory update record for profile updates which are ↵friendica2013-09-251-0/+9
| | | | part of the normal import_xchan sequence - otherwise we get two for every change. Create it normally if we are called with a profile_update message and don't go through the whole import_xchan thing.
* load_pconfig had some issues when given a familyfriendica2013-07-291-26/+10
|
* begin code to sync channel changes across all channel clones.friendica2013-06-251-0/+21
|
* fix some anomolies in config functionsfriendica2013-06-211-47/+69
|
* fix mod-display when not logged in.friendica2013-06-181-0/+6
|
* much more efficient config functions. This will save potentially hundreds of ↵friendica2013-06-171-97/+60
| | | | DB lookups - still need to update the xconfig but want to give the others a good workout as it has been one of those days.
* silence a pointless warningfriendica2013-06-151-1/+1
|
* push refresh messages, performance work on conversations and configs, doc ↵friendica2013-06-141-9/+25
| | | | updates
* small updatesfriendica2013-05-081-2/+2
|
* add xconfig table and functions, update strings and docofriendica2013-03-151-11/+123
|
* initial docofriendica2013-02-261-16/+15
|
* start formatting for Doxygenfriendica2013-02-251-1/+1
|
* rev updatefriendica2012-09-021-2/+2
|
* rev updatefriendica2012-06-161-3/+3
|
* Check if $rr existsHauke Zuehl2012-06-161-4/+2
|
* Doing negative caching for config values, special logfile for database ↵Michael Vogel2012-05-261-2/+22
| | | | optmisations
* Merge remote branch 'upstream/master'Michael Vogel2012-05-251-3/+1
|\
| * fix setting array values to config itemsTobias Diekershoff2012-05-221-3/+1
| |
* | Performance testsMichael Vogel2012-05-201-1/+1
|/
* Another bunch of executable permission removalVasudev Kamath2012-04-141-0/+0
|
* revert config changes, we're getting duplicate keysfriendica2012-04-061-151/+147
|
* Merge branch 'master' of https://github.com/friendica/friendicaAlexander Kampmann2012-04-051-4/+7
|\ | | | | | | | | | | Conflicts: include/config.php update.php
| * fix config storage of booleansfriendica2012-04-041-0/+1
| |
* | added index to config and pconfig tableAlexander Kampmann2012-04-051-152/+154
|/ | | | changed config.php to use REPLACE instead of INSERT, this removes one db hit.
* Wrong variable nameroot2012-02-261-1/+1
|
* add remove_user hook (it looks like dreamhost changed all my file ↵friendica2012-01-181-0/+0
| | | | permissions, this will make a nasty commit)