aboutsummaryrefslogtreecommitdiffstats
path: root/mod/settings.php
Commit message (Collapse)AuthorAgeFilesLines
* The other half of 'any theme for any device'. Closes #71Thomas Willingham2014-11-301-6/+11
|
* allow members to set the per-item "show more" height (separately for network ↵friendica2014-11-171-0/+11
| | | | and matrix, display and search are system pages and therefore set at 400)
* blog/list mode display settingsfriendica2014-11-161-0/+10
|
* Merge remote-tracking branch 'upstream/master'Habeas Codice2014-11-131-1/+54
|\ | | | | | | | | | | | | | | | | | | | | | | 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 minor cleanup of unreported (and as yet undiscovered) issues with ↵friendica2014-11-051-0/+1
| | | | | | | | 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.
| * changed notification descriptionfriendica2014-11-041-1/+1
| |
| * configurable visual alerts/notificationsfriendica2014-11-041-1/+53
| |
* | PostgreSQL support initial commitHabeas Codice2014-11-131-11/+11
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* couple of other places where we need to reset stuff completely if the role ↵friendica2014-10-261-6/+11
| | | | changes
* reset ACL just in case it was custom already.friendica2014-10-261-1/+1
|
* put privacy role selector in settings page. Change visibility of various ↵friendica2014-10-261-117/+107
| | | | permissions items accordingly.
* Merge https://github.com/friendica/red into pending_mergefriendica2014-09-181-1/+1
|\
| * Catch the settings tooThomas Willingham2014-09-181-1/+1
| |
* | repeated content collapse on update from display page under rare conditions ↵friendica2014-09-181-0/+6
|/ | | | (when the conversation hasn't changed)
* Made link post titles to source optional in display settings. Hopefully I ↵Jeroen2014-09-141-1/+7
| | | | did a right.
* Fixed. Thanks to Thomas.Jeroen2014-09-121-4/+3
|
* Addon count on addon settings page (featured) doesnt work (always 0). ↵Jeroen2014-09-121-2/+3
| | | | Commented out.
* Add account deletion to the UIChristian Vogeley2014-08-161-0/+1
|
* provide an expert option to opt out from user zoom on mobile devicesmarijus2014-08-131-1/+7
|
* block channel removal for 48 hours after changing the account password, ↵friendica2014-07-291-1/+2
| | | | 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-5/+5
| | | | bookmark permission), also remove the unused 'unconnected contacts' view for now.
* Remove Remove Account link from account settingsChristian Vogeley2014-06-291-1/+3
| | | | | because it doesn’t remove the account. Move channel removal link to channel page
* Implements a new permission level PERMS_PENDINGAlexandre Hannud Abdo2014-06-191-1/+2
| | | | | | | | | | | | | | | | 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.
* only show jotnets when posting conversation itemsfriendica2014-06-141-1/+1
|
* fix the intermittent theme previewfriendica2014-05-251-3/+1
|
* add randprof app and do away with the universally hated chanview-iframe ↵friendica2014-05-231-4/+3
| | | | mode. It's gone. Please do not try and bring it back. We are not Diaspora and we have no desire to be like them. ("And they're all made out of ticky-tacky and they all look just the same"). Our profiles do not have to look the same and they won't anyway. We don't have to sugar coat the fact that some of the content in the matrix doesn't look like the rest of the content in the matrix.
* clarify location - issue #392friendica2014-04-021-1/+1
|
* change wording of new connection request notification settingfriendica2014-03-271-2/+2
|
* add expire setting, take out unknown mailers and max friend requests per day ↵friendica2014-03-191-0/+1
| | | | which aren't implemented
* add pdl editor to settings/displayfriendica2014-03-041-0/+1
|
* allow personalised page layouts for modules.friendica2014-02-251-1/+0
|
* believe i found the issue which was causing hundreds/thousands of identical ↵friendica2014-02-201-1/+1
| | | | hublocs to be created
* Merge pull request #324 from tonybaldwin/masterfriendica2014-02-201-1/+1
|\ | | | | Do not view remote profiles in frames. (changed description for display->settings), in ALL relevant files
| * s/View remote profiles as webpages/Do not view remote profiles intony baldwin2014-02-191-1/+1
| | | | | | | | frames/g
* | use a "fullscreen" icon for chanview full screen mode; add channel_menu ↵friendica2014-02-191-3/+17
|/ | | | selection and setting to the settings page.
* introduce a new privacy level "PERMS_AUTHED" to indicate somebody that is ↵friendica2014-02-181-1/+2
| | | | able to successfully authenticate (but is not necessarily in this network).
* several things were not working correctly w/r/t community tagging. The ↵friendica2014-02-161-0/+1
| | | | preference vanished from settings at some point, and we also weren't updating the original post timestamp so that the changed taxonomy would propagate correctly as an edit.
* This makes advanced privacy settings adjustable in expert mode only. Also ↵marijus2014-02-131-0/+2
| | | | they are hidden behind a button. This is a design hotfix should probably come up with something better someday...
* fix a mysql error which popped up in the dbfail logfriendica2014-02-111-1/+1
|
* add chanview mode to settingsfriendica2014-02-101-1/+5
|
* bookmark permissionsfriendica2014-02-041-1/+5
|
* more wordsmithingfriendica2014-02-021-1/+1
|
* wordsmithingfriendica2014-02-021-4/+4
|
* don't draw attention to advanced permissions and their corresponding ↵friendica2014-02-021-4/+6
| | | | complexity and clearly mark the simple permissions which people are encouraged to use.
* fix sql query and provide setting to hide online statusfriendica2014-01-281-0/+7
|
* allow site defaults for enabled featuresfriendica2014-01-261-1/+1
|
* more comanche migrationfriendica2013-12-191-105/+3
|
* split off mod_connections into mod_connections & mod_connedit - lots of ↵friendica2013-12-181-1/+1
| | | | links to fix
* a couple more comanche conversionsfriendica2013-12-141-2/+2
|
* some code cleanup - gad I forgot what a mess the "other" notifications tabs ↵friendica2013-12-061-64/+0
| | | | (everything but system) were in. Maybe I'll just remove them so we can start over.