aboutsummaryrefslogtreecommitdiffstats
path: root/mod/mail.php
Commit message (Collapse)AuthorAgeFilesLines
* timeago() works best with iso format. fix #118Mario Vavti2015-11-031-1/+1
|
* mail sync debuggingredmatrix2015-10-151-0/+9
|
* Merge https://github.com/redmatrix/redmatrix into pending_mergeredmatrix2015-10-151-1/+4
|\ | | | | | | | | Conflicts: install/update.php
* | bring single message view to inbox/outbox viewMario Vavti2015-10-041-1/+8
| |
* | cleanup some unused variablesMario Vavti2015-10-041-12/+0
| |
* | private mail: if receiver is not in abook provide only his webbie to the formMario Vavti2015-10-041-29/+14
| |
* | private mail: $preid should be abook_xchan not abook_idMario Vavti2015-10-021-4/+4
| |
* | private mail compositor changesMario Vavti2015-10-021-8/+6
| |
* | add delivery reports to mail (not backported to redmatrix)redmatrix2015-09-301-0/+2
| |
* | private mail: bring additional inbox/outbox views and ajaxify single message ↵Mario Vavti2015-09-281-15/+29
| | | | | | | | drop
* | private mail: some work on conversations viewMario Vavti2015-09-251-3/+3
| |
* | some heavy private mail restructuring - work in progressMario Vavti2015-09-241-94/+105
| |
* | quickfix for private messages - needs a lot more workMario Vavti2015-09-171-4/+1
| |
* | more work on mail flagsredmatrix2015-06-231-3/+2
|/
* local_user => local_channelfriendica2015-01-281-16/+16
|
* Allow tags in mail, many profile fields, and admin infoStefan Parviainen2015-01-131-0/+3
|
* private mail buttonsfriendica2014-11-181-2/+6
|
* PostgreSQL support initial commitHabeas Codice2014-11-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* rev updatefriendica2014-10-031-1/+4
|
* This is long overdue - use a symblic constant NULL_DATE instead of the ↵friendica2014-09-081-1/+1
| | | | easily mis-typed sequence '0000-00-00 00:00:00'
* Some more buttons. Not ready yet. Changed in private message -submit- to ↵Jeroen2014-08-091-1/+1
| | | | -send-. Confusing in other language(s).
* Brain fart. Should really wait until the first cuppa kicks in.friendica2014-07-141-1/+1
|
* issue #536 - move a line so it doesn't interferefriendica2014-07-141-1/+1
|
* issue #536friendica2014-07-141-0/+13
|
* rule of snakes #1, kill the snake.friendica2014-06-281-10/+7
| | | | | | tinymce is gone. if you want a visual editor, figure out what you want and make it happen. If you don't want a visual editor, do nothing. This is in the community's hands. I don't need a visual editor.
* change the way jot tools are displayed/hiddenmarijus2014-04-081-4/+4
|
* oopsfriendica2013-12-231-0/+349
|
* front pageMike Macgirvin2010-08-031-85/+0
|
* add mail moduleMike Macgirvin2010-07-221-0/+85