aboutsummaryrefslogtreecommitdiffstats
path: root/include/Contact.php
Commit message (Collapse)AuthorAgeFilesLines
* improvements in duplicate like detection, especially w/r/t event participationfriendica2015-02-101-1/+1
|
* fix random profilesfriendica2015-01-301-2/+3
|
* local_user => local_channelfriendica2015-01-281-3/+3
|
* more heavy lifting on poco repfriendica2015-01-151-0/+1
|
* syncing connections issue, incorrect return_url after deleting connectionfriendica2015-01-071-0/+2
|
* direct messages in api have some issues, not properly ported from friendica ↵friendica2014-12-221-1/+2
| | | | | | originally. Here's a start. I think at best they may return encrypted gibberish currently, but let's work through them one at a time.
* Option to check that a random profile works before returning itStefan Parviainen2014-12-221-6/+23
|
* small changeChristian Vogeley2014-12-071-1/+1
|
* Remove channel cloud files from file system whenChristian Vogeley2014-12-071-0/+36
| | | | the channel is removed
* Whitespace. Stupid £#@£@$ editor.Thomas Willingham2014-11-291-5/+5
|
* Fix abook_toggle_flag from postgres stuffThomas Willingham2014-11-291-5/+7
|
* PostgreSQL support initial commitHabeas Codice2014-11-131-26/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* when removing a channel, check to see if there are any valid hublocs ↵friendica2014-10-211-4/+17
| | | | | | remaining before marking the xchan deleted. Issue #657
* implement a "powered-by" but leave it turned off until somebody with a good ↵friendica2014-09-291-0/+13
| | | | eye for layout can figure out where best to put it.
* diaspora connections being marked orphan on directory serversfriendica2014-09-091-1/+1
|
* feed removal issuefriendica2014-09-021-1/+1
|
* use feed icon as default avatar for rss connectionsfriendica2014-09-011-1/+1
|
* take off the kid glovesfriendica2014-08-261-7/+7
|
* Account deletionChristian Vogeley2014-08-151-0/+2
| | | | fix multi user deletion, add confirmation message
* Some work on account deletionChristian Vogeley2014-08-141-4/+9
|
* clone sync of "unfriend" actionsfriendica2014-08-051-67/+0
|
* reset timestamps when unarchiving a connectionfriendica2014-06-181-0/+13
|
* add a few days of slop to the orphan finder to account for any lags in dir ↵friendica2014-06-011-1/+1
| | | | syncing.
* this is an important bit - only mark dead hubs on directory servers. They ↵friendica2014-05-291-0/+4
| | | | shouldn't matter anywhere else.
* cleanup dead directory entries. This was a real b#tch, so keep your eye out ↵friendica2014-05-281-18/+66
| | | | for issues - which you shouldn't see until next weekend when this is scheduled to run. We're only setting flags, so if anything goes wrong we should be able to recover without too much pain.
* filter randprof results to avoid channels that are known to be deceased.friendica2014-05-251-1/+1
|
* Hope I have repaired the channel admin page.sasiflo2014-04-061-1/+1
| | | | | | | | | | Channel blocking and deleting was copied from user actions. This was not done to an end. Hope what I do is enough to enable channel blocking and deleting the correct way. On deletion all entities that belong to the channel are deleted. But the channel itself is just marked as deleted. Do not really understand why it is done this way.
* small changes to a couple of lookup functions which we need to use a bit morefriendica2014-02-201-3/+6
|
* vsprintf error on updatefriendica2014-02-201-2/+2
|
* use profile photo on vcard before reverting to xchan photofriendica2014-02-111-1/+1
|
* remove a couple of mysql reserved words from being used as table or row ↵friendica2013-12-221-1/+1
| | | | names. For this round we're getting 'group' and 'desc'. Warning: potentially destabilising as this touches a lot of code.
* more comanchefriendica2013-12-191-1/+5
|
* prepare for Comanchification of mod_photosfriendica2013-12-131-0/+13
|
* refactor magic-authfriendica2013-12-021-79/+0
|
* removeme sort of works for a single channel - lots of loose ends to deal ↵friendica2013-11-121-22/+36
| | | | with but it's a start
* more work on channel removal - it might sort of work now but I'm expecting ↵friendica2013-11-051-4/+22
| | | | lots of issues. Hence there is still no code in chanman to start the process rolling and make it happen. Will need a barrage of test cases.
* implement republish permission for use in sourced channelsfriendica2013-09-301-1/+2
|
* Pieces we'll need to tie together chanman and account/channel deletion and ↵friendica2013-09-171-15/+44
| | | | | | | | directory sync. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. OK? Understood?
* premium/restricted channel connections implemented, configure at ↵friendica2013-08-211-1/+8
| | | | yoursite/channel/nickname - this basically redirects "follow" requests to a premium channel's sell page if it has one configured. You can still click through and create a connection request (introduction), but this provides a means for the channel owner to state their terms. If you don't abide by the terms, you will likely be blocked or the channel deleted. This facility is extensible in a number of ways.
* don't include archived contacts in public posts, unless specifically requestedfriendica2013-08-151-2/+2
|
* debugging issue #58 - seems to work but needs (more) themingfriendica2013-08-131-3/+10
|
* untested patch for issue #58 - will require theming if it worksfriendica2013-08-131-0/+18
|
* enotify: localize things we know how to translatefriendica2013-08-051-1/+1
|
* progress on unfriendingfriendica2013-08-041-15/+19
|
* basic *account* removal, but the channel removal which it calls still needs ↵friendica2013-08-041-0/+43
| | | | (lots of) work. Oh and the intro table is no longer used and won't be - so it's gone.
* provide a controlling user for theme settings, not necessarily local_user() ↵friendica2013-07-161-0/+5
| | | | - can't test on my test site so moving into production and I'll debug it there.
* more nomadic clone syncfriendica2013-06-261-0/+3
|
* sql error on contact removalfriendica2013-04-191-1/+1
|
* randprof sorta workingfriendica2013-03-061-2/+2
|
* start formatting for Doxygenfriendica2013-02-251-1/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-30 10:40:17 +0000