aboutsummaryrefslogtreecommitdiffstats
path: root/mod/lostpass.php
Commit message (Collapse)AuthorAgeFilesLines
* A few minor tweaks in schemas + link to login form in lostpassjeroenpraat2016-01-211-1/+1
|
* set email verified if lost password workflow is completed to avoid the ↵redmatrix2015-08-141-2/+3
| | | | situation where they can reset the password but still not be able to login because the original email verification was lost.
* 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)
* lostpass fixes and login/logout flow if authenticated but no default channel ↵friendica2013-01-271-9/+9
| | | | exists
* maybe 'lostpass' will work now, maybe not. Didn't try it, but theoretically ↵friendica2013-01-271-39/+42
| | | | it's updated.
* add Smarty templates for international templatesZach Prezkuta2013-01-101-11/+0
|
* bypass smarty for intletext templatesfriendica2013-01-071-0/+11
|
* Merge branch 'master' of https://github.com/friendica/friendicaAlexander Kampmann2012-04-051-0/+0
| | | | | | Conflicts: include/config.php update.php
* bug #339 - lostpass sending to username, not emailfriendica2012-03-201-4/+5
|
* add remove_user hook (it looks like dreamhost changed all my file ↵friendica2012-01-181-0/+0
| | | | permissions, this will make a nasty commit)
* some more zot changes migrating back to f9a mainlineFriendika2011-08-011-4/+4
|
* don't allow blocked/unverified users to reset their password.Friendika2011-06-291-2/+6
|
* add info() function. Works like notice() but show messages in a div with ↵Fabio Comuni2011-05-231-3/+3
| | | | | | | class info-message. update code to use info() instead of notice() when appropriate (non-error message) add info-message class style in themes
* deprecate load_view_fileFriendika2011-05-111-4/+4
|
* don't use load_view_file() except in email templates and install of htconfig ↵Friendika2011-05-101-2/+2
| | | | - to avoid getting wrong file when package is updated by copying over an older version.
* set utf-8 on all emailsFriendika2011-04-141-2/+9
|
* the rest of the english html templates except for htconfigFriendika2011-04-071-0/+7
|
* more templatesFriendika2011-04-061-4/+9
|
* update source stringsfabrixxm2011-03-111-1/+1
|
* lintFriendika2010-11-071-3/+2
|
* celebrity/group/community pages about 75% implementedMike Macgirvin2010-10-171-1/+2
|
* localisation path for all view templatesMike Macgirvin2010-09-221-4/+4
|
* password resetMike Macgirvin2010-07-181-0/+104