aboutsummaryrefslogtreecommitdiffstats
path: root/include/permissions.php
Commit message (Collapse)AuthorAgeFilesLines
* Some Doxygen comments and small cleanups.Klaus Weidenbach2014-12-071-68/+98
|
* minor photo flag issue - and some more whitespace editsfriendica2014-11-191-1/+1
|
* Merge remote-tracking branch 'upstream/master'Habeas Codice2014-11-131-3/+3
|\ | | | | | | | | | | | | | | | | | | | | | | 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
| * set channel_w_stream to 0 for forum roleszottel2014-11-101-3/+3
| |
* | 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)
* add "repository" permissions role and make sure we have a sane "accept" ↵friendica2014-10-271-2/+45
| | | | default for the custom role.
* put privacy role selector in settings page. Change visibility of various ↵friendica2014-10-261-0/+4
| | | | permissions items accordingly.
* allow custom role permissions and fix site timezone.friendica2014-09-291-0/+5
|
* closing tagfriendica2014-09-191-1/+1
|
* usability tweaksfriendica2014-09-171-0/+9
|
* channel permission rolesfriendica2014-09-171-1/+26
|
* defined several permission roles - these will probably require some review ↵friendica2014-09-171-0/+245
| | | | | | | | | | | | | | and adjustment. social social_restricted social_private forum forum_restricted forum_private feed feed_restricted soapbox
* implement permission roles - the backend should be done except for maybe a ↵friendica2014-09-171-4/+7
| | | | couple of small tweaks. Now we just need to define the rest of the roles and create a chooser for them. Adam started on this some time back but I don't know where that has gone.
* beginning of permission role settingsfriendica2014-08-171-0/+60
|
* Added some missing translation strings. Fixed to scalable for a few font sizes.Jeroen2014-08-141-1/+1
|
* a bit more cleanup and a bug fix or two for the new private post security modelfriendica2014-08-071-9/+9
|
* provide a specific permission for liking profiles (reuse the obsolete ↵friendica2014-07-171-1/+4
| | | | bookmark permission), also remove the unused 'unconnected contacts' view for now.
* add 'block_public' checking to get_all_perms() and perm_is_allowed() so we ↵friendica2014-07-031-0/+12
| | | | have everything related to allowing or denying something in one place. Currently this check is done separately in a huge number of places. Now we can start to remove all the extra checks. A couple of them are still necessary, but most are now redundant.
* Implements a new permission level PERMS_PENDINGAlexandre Hannud Abdo2014-06-191-17/+23
| | | | | | | | | | | | | | | | With this a user can allow some action to any user which connects to them, even before they've connected back. Ref. https://mobiliza.org.br/display/478d9e71eaf55748dc646d3990651d6d34cfb7db5c38360538ec730ca3ccf908@zothub.com Also some code cleanup and an alternative logic for handling notifications of permission changes in zot.php. This assumes that private posts are still restricted to people in your addressbook. Regardless of your global permissions, a pending channel won't get private posts, even if the post only has a deny clause not matching the pending channel.
* Remove automatic bookmarking - it was a bad idea and just leads to menu ↵friendica2014-04-301-1/+1
| | | | clutter. Bookmarks can always be saved manually if desired.
* 'anybody in this network' permissions were not being allowed for ↵friendica2014-04-091-6/+22
| | | | non-connected channels.
* introduce a new privacy level "PERMS_AUTHED" to indicate somebody that is ↵friendica2014-02-181-0/+8
| | | | able to successfully authenticate (but is not necessarily in this network).
* more snakebite stufffriendica2014-02-171-6/+7
|
* bookmarkingfriendica2014-02-041-1/+1
|
* bookmark permissionsfriendica2014-02-041-0/+1
|
* remove the text "requires compatible chat plugin"friendica2014-02-021-1/+1
|
* implement republish permission for use in sourced channelsfriendica2013-09-301-0/+1
|
* some sane permission defaults.friendica2013-08-181-0/+35
|
* more diagnosticsfriendica2013-07-151-1/+1
|
* fix "new connection has less permissions than public"friendica2013-06-151-4/+12
|
* by default pending connections have no rightsfriendica2013-06-061-2/+2
|
* more permissions descriptive text to lessen confusionfriendica2013-05-211-1/+1
|
* doc update plus fix the "only to those in my address book" permissionfriendica2013-05-181-0/+5
|
* start formatting for Doxygenfriendica2013-02-251-1/+1
|
* permission plugin hooksfriendica2013-02-191-2/+23
|
* why oh why is poco_load not getting called? oh - that's why.friendica2013-01-241-16/+16
|
* auto permissions (such as for forums or whatever) - untested but might just workfriendica2013-01-231-4/+6
|
* read/write "pages" permissions and fiddly bits - per Thomasfriendica2013-01-141-0/+2
|
* syntax errorfriendica2013-01-131-1/+1
|
* this should make tag delivery (e.g. forums) work - but not yet fully testedfriendica2013-01-131-1/+11
|
* add permission controls to "storage" objects such as attachments or other ↵friendica2012-12-221-0/+3
| | | | stored files
* revamp permissions, blocking a contact takes priority over all other ↵friendica2012-12-101-51/+65
| | | | permission settings, such as "allow anybody in network to do xyz". If they're blocked they can't do it.
* Allow forum/account delegation by anybody? On any site? But of course...friendica2012-12-101-0/+1
|
* finish basic item encoding, add plugin compatibility tag, notes on improving ↵friendica2012-11-161-0/+6
| | | | $global_perms for edge cases
* got zotfriendica2012-11-121-2/+2
|
* permissions and contact permissions are now stickyfriendica2012-11-081-11/+11
|
* change permission settings from radio buttons to select boxesfriendica2012-11-051-11/+11
|
* slightly better wording of permission choicesfriendica2012-11-021-4/+4
|
* consolidate permission arraysfriendica2012-11-021-36/+11
|
* grrr... hashes aren't matching.friendica2012-11-011-17/+26
|