aboutsummaryrefslogtreecommitdiffstats
path: root/include/group.php
Commit message (Collapse)AuthorAgeFilesLines
* first cut on restructuring the previously called network tabsMario Vavti2018-05-301-1/+1
|
* If one has system.network_page_default set to a different sort order use ↵zotlabs2018-05-061-1/+1
| | | | that order on the 'All Channels' selection of the Collections (privacy group) widget.
* issue with group_rmvzotlabs2017-11-131-6/+2
|
* hubzilla issue #832zotlabs2017-07-191-1/+2
|
* Create virtual privacy groups for private profile member listszotlabs2017-02-121-11/+57
|
* sql: limit 1 for UPDATE and DELETE is not supported by the SQL standard and ↵Florian Steinel2016-10-271-1/+1
| | | | | | postgresql (see: https://www.postgresql.org/message-id/flat/1291109101.26137.35.camel%40pcd12478 )
* even more backslashesredmatrix2016-10-031-20/+20
|
* Don't use count() to check DB resultsredmatrix2016-06-191-9/+9
|
* more db column renamesredmatrix2016-05-311-10/+10
|
* fix #328 by using a seperate query instead of group_concatMario Vavti2016-03-201-0/+16
|
* revert f62ec4132ed571288737423de386054a4cc8b0d5 - allow one self to be added ↵Mario Vavti2016-02-251-1/+1
| | | | to a privacy group.
* rename collections to privacy groupsredmatrix2016-01-261-5/+5
|
* use consistent terminologyredmatrix2015-08-191-1/+1
|
* convert the abook fieldsredmatrix2015-06-141-4/+2
|
* consensus items not working correctly and make the collections widget abide ↵redmatrix2015-05-181-1/+1
| | | | by the corresponding feature setting. This needs to be backported as it is borken in redmatrix. Also provide the ability to change the number of most recent expanded comments to conversations on a site-wide basis, increase it to 3 by default. We may also want this as a personal setting.
* Merge branch 'master' into tresfriendica2015-04-231-2/+2
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: include/Contact.php include/ItemObject.php include/api.php include/attach.php include/diaspora.php include/dir_fns.php include/enotify.php include/event.php include/expire.php include/items.php include/notifier.php include/notify.php include/photos.php include/taxonomy.php include/text.php include/widgets.php include/zot.php mod/admin.php mod/channel.php mod/dirsearch.php mod/display.php mod/editwebpage.php mod/events.php mod/home.php mod/item.php mod/manage.php mod/mood.php mod/network.php mod/page.php mod/photos.php mod/ping.php mod/post.php mod/thing.php mod/viewsrc.php view/css/mod_events.css
| * revert iconic change to collection list widgetfriendica2015-04-011-1/+1
| |
| * change "create new collection" to iconic, document the account tablefriendica2015-03-301-1/+1
| |
| * Explicitly force link for 'All Collections' on the network page to gid=0 so ↵friendica2015-03-191-1/+1
| | | | | | | | it can be used with a default page over-ride for gid.
* | Merge branch 'master' into tresfriendica2015-01-291-4/+4
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: include/group.php include/text.php mod/acl.php mod/channel.php mod/connections.php mod/display.php mod/group.php mod/item.php mod/locs.php mod/network.php mod/photos.php mod/ping.php mod/starred.php mod/viewsrc.php
| * local_user => local_channelfriendica2015-01-281-4/+4
| |
* | working through the xchan table to remove bitfields, mostly complete except ↵friendica2015-01-201-2/+1
|/ | | | for updating the updater
* PostgreSQL support initial commitHabeas Codice2014-11-131-5/+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)
* issue #588 can't add feeds to collections using connedit page group sidebar ↵friendica2014-09-111-0/+1
| | | | widget
* the sending side of clone syncing of collection/privacy_group information. ↵friendica2014-07-141-0/+11
| | | | The receiving side is not yet implemented.
* let oneself be added to a collection in exchange for deleted contactsmarijus2014-02-071-2/+2
|
* make network tabs regard selected group (collection) and vice versamarijus2014-01-221-1/+1
|
* remove a couple of mysql reserved words from being used as table or row ↵friendica2013-12-221-12/+12
| | | | names. For this round we're getting 'group' and 'desc'. Warning: potentially destabilising as this touches a lot of code.
* comanchify connedit, groupfriendica2013-12-191-1/+1
|
* starting on the journey to comanche everywhere - beginning with widget ↵friendica2013-12-081-2/+2
| | | | conversions. There are approximately 20 which need to be wrapped for accessibility to comanche.
* white screenfriendica2013-11-211-3/+3
|
* fix private group deliveryfriendica2013-11-051-3/+4
|
* Add public visibility setting to privacy groups (collections). This doesn't ↵friendica2013-08-071-3/+4
| | | | yet make them visible, but allows them to be visible (like a Cc: instead of a Bcc:)
* issue #55 (number 2)friendica2013-05-281-4/+6
|
* members_of_group() output not entirely correctfriendica2013-05-021-1/+2
|
* add new connections to default group (if any)friendica2013-03-271-9/+25
|
* fix timeago (again), webfinger new spec implemented, some theme workfriendica2013-03-041-1/+1
|
* start formatting for Doxygenfriendica2013-02-251-1/+1
|
* clean up some sql errors from the logsfriendica2013-02-081-1/+1
|
* fixed contactgroup editorfriendica2013-01-221-2/+1
|
* Stringify groups before implodingOlaf Conradi2012-12-251-2/+1
|
* db query looping without bounds if group table wasn't manually updated to ↵friendica2012-12-141-1/+1
| | | | add the 'hash' column.
* Fixing the acl widget is going to be hard. Here's a start.friendica2012-12-061-2/+14
|
* add pending check on group queriesfriendica2012-11-291-2/+3
|
* make the visual group editor work again in the new worldfriendica2012-11-141-4/+6
|
* groups now take xchans, so you can have groups containing channels that you ↵friendica2012-11-141-45/+30
| | | | aren't connected with
* a lot more changes of terminologyfriendica2012-11-031-6/+6
|
* contact group is now 'channel group'friendica2012-10-271-4/+4
|
* here's where the heavy lifting begins - everything is likely to be broken ↵friendica2012-10-011-2/+33
| | | | for quite some time as we add location and db independence to items and conversations and work through the rest of the permissions and how to federate the buggers.
* convert all network search params to get requests (no url path args)friendica2012-07-231-1/+1
|