aboutsummaryrefslogtreecommitdiffstats
path: root/include/enotify.php
Commit message (Collapse)AuthorAgeFilesLines
* product was a bad string to use because we may require it for e-commerce, ↵redmatrix2015-05-131-1/+1
| | | | and RED_PLATFORM is equally problematic for other reasons.
* Correcting reported Doxygen syntax warnings.Klaus Weidenbach2015-03-291-90/+106
| | | | | | | Fixed wrong Doxygen syntax and add some of the available FIXME to Doxygen documentation. Updated Doxygen configuration to add also all capital letter tags. Adding some more Doxygen documentation.
* superblock enhancementsfriendica2015-01-261-0/+1
|
* backend for mailhost addonfriendica2015-01-151-0/+8
|
* Make showing wall posts, intros and private messages under Notices optionalStefan Parviainen2014-12-301-2/+15
|
* 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)
* bring back some friendica crypto stuff including all the key mangling and ↵friendica2014-08-151-0/+9
| | | | translation functions. Also add ability to completely supress email notifications for actitivies with private contents. We'll still pass private mail notifications because often the email notification is the only way infrequently used channels get alerted to these.
* in HTML email notifications, angle brackets in posts were unescaped - ↵friendica2014-08-141-1/+1
| | | | including those in code blocks.
* put an indicator (*) in the message subject line for notification emails ↵friendica2014-08-141-0/+1
| | | | when the message body has been suppressed
* prevent obscured email notificationsfriendica2014-08-091-1/+1
|
* obscured message showing up in email notificationfriendica2014-08-071-1/+1
|
* notify tweaksfriendica2014-06-091-0/+2
|
* prevent follows of and notifications to deceased channelsfriendica2014-04-071-2/+3
|
* use parent_mid in the parent query for enotify instead of of the parent id. ↵friendica2014-04-061-8/+9
| | | | This should fix the issue with encrypted content in the notification messages (for locally posted replies). The fix was a bit harder than anticipated because we store the parent id as an int in the notify table so this had to be modified to char storage as well.
* new connection notificationfriendica2014-03-271-3/+3
|
* mail notification goes to old linkfriendica2014-03-161-1/+1
|
* I'll have to fix this someday.friendica2014-02-251-0/+6
|
* simplify permalink selection logicfriendica2014-01-091-1/+3
|
* split private messages into two modules - "message" is just for message ↵friendica2013-12-211-2/+2
| | | | lists, "mail" is for reading and writing conversations. This is so we can Comanchify it cleanly.
* if somebody tagged you in a private post, the tag email notification ↵friendica2013-12-191-3/+2
| | | | contained the obscured message. Clear it.
* generate a small amount of entropy to avoid duplicate notifications from ↵friendica2013-12-041-0/+4
| | | | essentially simultaneous deliveries.
* add recipient name to the rest of the notification emailsfriendica2013-11-241-37/+47
|
* add recipient name to some of the notification emails for those who have a ↵friendica2013-11-211-3/+3
| | | | lot of channels and it isn't always obvious which channel is getting the notification. If this works out we should probably add this to the rest of them.
* add aid to notifiy table which we may need to supress duplicate notify ↵friendica2013-11-201-3/+5
| | | | | | emails across your channels also try to handle the wretched mess of broken and duplicated hublocs that fred.cepheus.uberspace.de typically reports
* change product name on notification emails to lowercasefriendica2013-11-151-1/+1
|
* tag notifications for private posts contain obscured data - they should be blankfriendica2013-11-041-1/+1
|
* don't send email notifications for likes (as comment notifications). We'll ↵friendica2013-09-241-1/+6
| | | | need a separate preference for whether you want notifications for likes.
* The triple linebreaks in notification emails finally bothered me enough to ↵friendica2013-09-021-4/+2
| | | | do something about it.
* we've been storing json_encoded structures on disk in several places because ↵friendica2013-08-061-1/+2
| | | | it's a lot easier to parse than xml - but OMG do they get mangled - stored as single quoted strings when escaped as if double quoted. We need to use my new function json_decode_plus() wherever we need to parse one of these babies to make sure we get it right. Maybe we should've just used serialize().
* enotify: localize things we know how to translatefriendica2013-08-051-3/+13
|
* better mail obscuringfriendica2013-07-311-2/+15
|
* undo comment policy override - there are a handful of stored posts from the ↵friendica2013-06-181-0/+3
| | | | 17th-June with a broken policy (which won't have a comment box) but it seems to be working for both recent and older posts.
* another try on zidified notifications - this time it actually seems to workfriendica2013-06-171-1/+3
|
* one of those days...friendica2013-06-171-2/+2
|
* zidify bodies of notification emailsfriendica2013-06-171-1/+15
|
* missed a few zrl/zmg conversions, like for translate_item and enotify messagesfriendica2013-06-121-1/+1
|
* also strip title from notification of private messages - it leaks ↵friendica2013-05-101-1/+1
| | | | potentially sensitive message info. Note: there is still information leakage of sender but this is difficult to avoid completely. "You've got an email from (we're sorry, we can't tell you...)"
* get search page working with live-update and endless scroll, still not ↵friendica2013-05-091-0/+7
| | | | perfect - there may be duplicated content and possibly unauthorised content and 'timeago' not working correctly - will deal with those later, but at least you can see results.
* email notification content privacy by default (unless it's public content)friendica2013-05-051-0/+24
|
* turn all Red links into zrls (not the old zrls, the new bbcode zrl which ↵friendica2013-04-151-19/+19
| | | | means we can zidify them)
* begin to cut the umbilicalfriendica2013-04-141-1/+1
|
* start formatting for Doxygenfriendica2013-02-251-1/+1
|
* recursion and typo in rmagic with zidfriendica2013-02-131-35/+0
|
* catch typosfriendica2013-02-061-1/+1
|
* massive notification revisionfriendica2013-02-061-29/+31
|
* lots of notification tweaksfriendica2013-01-081-3/+3
|
* fix notification uidfriendica2013-01-051-5/+11
|
* tweak notifications so they store correctlyfriendica2013-01-051-7/+7
|
* start rewrite of notification system delivery backendfriendica2013-01-051-46/+66
|
* fix register_policy globallyfriendica2013-01-031-3/+3
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-12 20:55:22 +0000