aboutsummaryrefslogtreecommitdiffstats
path: root/include/account.php
Commit message (Collapse)AuthorAgeFilesLines
* several email validation issueszotlabs2018-02-281-1/+1
|
* typo from previous checkin and partial fix to hubzilla #965 - show any ↵zotlabs2018-01-261-1/+1
| | | | connection without comment permission as archived in contact_block().
* Issue with configurable site age limit, vagueness when informing about email ↵zotlabs2018-01-261-11/+33
| | | | validation policy; added email validation resend ability and the option to input a verification code at a webpage though both require additional work to provide these abilities.
* create account_store_lowlevel()zotlabs2017-05-291-34/+58
|
* start deprecation of server_rolezotlabs2017-05-291-8/+2
|
* consolidate email validation checkszotlabs2017-05-111-1/+1
|
* remove more backquoteszotlabs2016-10-091-4/+4
|
* Unify the various mail sending instance to enotify::send() and z_mail(). ↵redmatrix2016-10-011-22/+30
| | | | Both take the same arguments. z_mail() is text only, enotify::send() provides html and text. Both are pluggable using the enotfy_send hook.
* null_date conversion; phase 1redmatrix2016-09-251-2/+2
|
* pro: add system techlevel to new accountsredmatrix2016-09-021-4/+6
|
* provide techlevels in the pro server role. Should have no visible effect on ↵redmatrix2016-08-311-0/+27
| | | | other roles.
* use config system.server_role and deprecate 'UNO'redmatrix2016-08-071-2/+2
|
* sort out some of the authentication mess - with luck this may fix the DAV ↵redmatrix2016-07-201-1/+1
| | | | auth issue which I simply could not duplicate or find a reason for.
* add letsencrypt x3 intermediate cert and new cert file, improve UX of new ↵redmatrix2016-06-271-1/+17
| | | | registrations
* more removal of reserved words from DB schemasredmatrix2016-05-311-3/+3
|
* code cleanupredmatrix2016-05-241-1/+2
|
* renamed include files identity.php (channel.php) and Contact.php ↵redmatrix2016-05-221-1/+1
| | | | (connections.php)
* allow engineering units (e.g. 400M, 1G) as service class limitsredmatrix2016-04-281-0/+3
|
* static Appredmatrix2016-03-311-4/+4
|
* ensure auto_channel_create() is executed for all workflows when UNO is set.redmatrix2016-02-191-2/+2
|
* 'auto channel creation' - if the corresponding config variable is set, ↵redmatrix2016-01-121-5/+17
| | | | | | create a channel when an account is created. Plugins can provide the necessary channel details (probably from an extended registration form). If no details are provided, a social (mostly public) channel will be created using the LHS of the email address and you will be directed to your channel page (unless email verification is required, in which case this step will be delayed until successful validation and login). If the reddress is already assigned a random name(1000-9999) reddress will be assigned.
* Fix #109.jeroenpraat2015-12-091-2/+2
|
* notification changes to support testdriveredmatrix2015-10-011-0/+2
|
* Correcting reported Doxygen syntax warnings.Klaus Weidenbach2015-03-291-46/+45
| | | | | | | 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.
* Documentation and remove duplicate code.Klaus Weidenbach2015-03-161-72/+79
| | | | | Add a bit Doxygen documentation and remove some duplicate code from account.php.
* Some documentation, fix chatroom service class lookup.Klaus Weidenbach2015-03-141-13/+38
| | | | | Add some Doxygen documentation and fixing a service class lookup for chatroom_create().
* local_user => local_channelfriendica2015-01-281-2/+2
|
* Fix for issue #763 Error creating new channel within the limits of theChristian Vogeley2015-01-111-0/+26
| | | | subscription plan
* PostgreSQL support initial commitHabeas Codice2014-11-131-15/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* honour service class restrictions for total_identities, total_channels ↵friendica2014-09-151-0/+23
| | | | ("friends") and total_feeds both when importing channels and subsequently when syncing clones. Limits are based on the local system - additional entries are silently dropped.
* argument order reversed in downgrade_accountsfriendica2014-09-091-2/+2
|
* This is long overdue - use a symblic constant NULL_DATE instead of the ↵friendica2014-09-081-3/+4
| | | | easily mis-typed sequence '0000-00-00 00:00:00'
* implement service class for feed polling frequenecy, fixed a service class ↵friendica2014-09-031-0/+88
| | | | bug, moved service class stuff from plugin to account.php where it belongs and load that by default instead of on demand
* more diaspora heavy liftingfriendica2014-08-251-1/+1
|
* finish implementing email verification. Currently it only applies if ↵friendica2014-07-091-1/+8
| | | | REGISTER_OPEN is in effect.
* some initial work towards email address verificationfriendica2014-07-031-0/+84
|
* some more snakebite and fix up include/account - forgot about that inline ↵friendica2014-02-181-3/+6
| | | | array stuff
* service class downgrade to the default service class on account expiration ↵friendica2014-02-181-0/+52
| | | | if using a non-default service class and account has expired.
* fix the admin interface to pending registrationsfriendica2014-01-211-2/+2
|
* more work on dav - deletion and a bit more progress on OS storagefriendica2014-01-071-0/+1
|
* Missing include for new_keypairThomas Willingham2013-08-101-0/+1
|
* move sitekey creation to the account creation function instead of during ↵friendica2013-08-091-0/+7
| | | | channel creation. Channel import bypassed sitekey creation completely. We should do it during install, but it's possible somebody might have to install manually and the sitekey would never get created. This is the best compromise I can come up with. Looks like the doc tree was also updated in this checkin
* fix registration email (sitename)friendica2013-07-181-1/+1
|
* fix setting account_roles for admin accountfriendica2013-05-151-1/+1
|
* photo driver issue when updating contact photos - old class structure used ↵friendica2013-05-051-1/+1
| | | | instead of photo_factory()
* fix admin assignfriendica2013-05-051-2/+2
|
* minor fixes related to postgres developmentfriendica2013-05-051-1/+2
|
* start formatting for Doxygenfriendica2013-02-251-1/+1
|
* Whinging whining stupid fucks.friendica2013-02-121-8/+0
|
* Sort out registrations requiring approvalfriendica2013-02-111-3/+9
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-18 13:01:42 +0000