aboutsummaryrefslogtreecommitdiffstats
path: root/mod/acl.php
Commit message (Collapse)AuthorAgeFilesLines
* taganyone wasn't workingfriendica2015-02-151-2/+5
|
* remote_user => remote_channelfriendica2015-01-281-1/+1
|
* local_user => local_channelfriendica2015-01-281-8/+8
|
* allow RSS connections in the type 'a' autocomplete results as that is used ↵friendica2015-01-271-3/+7
| | | | for channel sources. Without it a feed cannot be selected as a channel source.
* Honor requested count in navbar searchStefan Parviainen2015-01-081-1/+2
|
* Return results from acl.php in standard formStefan Parviainen2015-01-071-20/+0
|
* Make nav search use textcompleteStefan Parviainen2015-01-071-14/+14
|
* the last checkin removed hostname from the address for autocomplete ↵friendica2015-01-041-1/+1
| | | | searches. This one allows it if explicitly added with a '@'. So 'mike' will find all mikes. 'mike@z' will find mike@zothub but not mike@popcorn.
* only check the LHS of xchan_addr for autocomplete, don't match on the hostname.friendica2015-01-041-1/+1
|
* TypoStefan Parviainen2015-01-041-3/+3
|
* Sorting of autocompleteStefan Parviainen2015-01-041-4/+27
|\
| * Sort acl results according to match position (only type='c' for now)Stefan Parviainen2015-01-021-2/+5
| |
* | Autocmplete suggestions for non-local users, also suggest from visited ↵Stefan Parviainen2015-01-041-75/+52
|/ | | | channel's connections
* PostgreSQL support initial commitHabeas Codice2014-11-131-14/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* several unrelated things - auto_follow wasn't working for new accounts, ↵friendica2014-10-271-4/+4
| | | | error returned in private mention to a collection, and added auto-completion to photo tags; though it only matches people so the hover text is now wrong. Also made the photo edit form XHTML (XML) compliant.
* don't offer forum (@name+) completion in comments, since it won't do anything.friendica2014-10-231-2/+2
|
* remove feed items from ACL selector - there's nothing we can do with them ↵friendica2014-09-031-0/+5
| | | | and if we were to try we'd have to binary pack all the hashes
* Set a default directory server from a hard-wired list if one was not ↵friendica2014-04-251-7/+1
| | | | previously chosen.
* tag anyonefriendica2014-04-151-1/+20
|
* only show forum tags on contact autocomplete, not in the ACL selectorfriendica2014-04-131-1/+1
|
* this is looking better, call the forum version of a tag "foobar network", ↵friendica2014-04-121-3/+5
| | | | besides altering the icon
* use icons for identificationfriendica2014-04-111-2/+2
|
* not quite right but I need to check it in so I can switch branchesfriendica2014-04-111-2/+2
|
* the auto-complete partfriendica2014-04-111-1/+14
|
* add "self" to access control lists with special marking to indicate it's ↵friendica2014-01-061-4/+4
| | | | special (for instance you can't really deny access to yourself). But this lets us make something private to our eyes only; whatever it may be.
* don't include deleted folks in acl popupfriendica2013-12-251-10/+21
|
* remove a couple of mysql reserved words from being used as table or row ↵friendica2013-12-221-7/+7
| | | | names. For this round we're getting 'group' and 'desc'. Warning: potentially destabilising as this touches a lot of code.
* oups... should not do that...marijus2013-11-091-1/+1
|
* fix directory leaking to ppl which aint got zot in searchbar-autocomplete if ↵marijus2013-11-091-1/+5
| | | | block_public is enabled
* bring back mail list and cleanup some issues which popped out with full PHP ↵friendica2013-08-271-2/+2
| | | | warnings
* more loose endsfriendica2013-08-271-3/+2
|
* populate initial suggestions (ultimately we want to do this at install time ↵friendica2013-08-051-1/+1
| | | | as well as from the poller so that new sites have friend suggestions when they create their first channel).
* mail completion issuefriendica2013-07-211-1/+1
|
* fix some issues that showed up in the logs.friendica2013-07-151-8/+9
|
* flag taggable connections in acl selectorfriendica2013-06-161-9/+11
|
* Another missing includeThomas Willingham2013-06-091-0/+1
|
* make @tags half-ass workfriendica2013-01-231-2/+2
|
* directory services cleanupfriendica2013-01-191-14/+3
|
* distributed directory search from the navbarfriendica2013-01-191-11/+89
|
* progress on the acl selector - it should mostly work, but the returned data ↵friendica2012-12-071-2/+4
| | | | isn't yet parsed correctly in mod_item
* Fixing the acl widget is going to be hard. Here's a start.friendica2012-12-061-21/+19
|
* check permissions for mail to non-connected people, reject if no permission ↵friendica2012-12-051-4/+11
| | | | - but you can try and send mail to any webbie. We probably should check for this before you send the message but perhaps we can find another way to let you know if it's allowed or not without an expensive probe. Like mod_follow, a webbie without an @ is treated as a local address.
* DB: do the mail table again. Mail almost working onsite, still needs to zot ↵friendica2012-12-041-10/+6
| | | | though
* more progress on notifier cleanup and encoding items for transit.friendica2012-11-151-1/+1
|
* usability improvementsfriendica2012-11-131-17/+17
|
* more structural stufffriendica2012-10-291-1/+1
|
* more ui cleanupfriendica2012-10-241-2/+1
|
* Give the UI a little love after all the backend modsfriendica2012-10-241-4/+17
|
* contacts search autocompletefriendica2012-06-051-2/+24
|
* rev updatefriendica2012-05-301-1/+1
|