aboutsummaryrefslogtreecommitdiffstats
path: root/mod/register.php
Commit message (Collapse)AuthorAgeFilesLines
* More clarification about privacy of private content. Changed Channel Name to ↵jeroenpraat2016-02-171-1/+1
| | | | simply Name when registering/creating an account or channel. First time when people see this they get confused (by experience on my hubs). This will even be more with UNO.
* allow redirection to site workflow page even if auto channel create is appliedredmatrix2016-02-161-3/+4
|
* @hubdomain also for auto-create-channel + adding css wrapper (ongoing work)jeroenpraat2016-02-161-0/+1
|
* change register workflow if uno is setredmatrix2016-02-071-1/+1
|
* more uno groundworkredmatrix2016-02-051-2/+2
|
* more work on auto channel creation during registerredmatrix2016-01-131-1/+24
|
* 'auto channel creation' - if the corresponding config variable is set, ↵redmatrix2016-01-121-12/+27
| | | | | | 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.
* some notifier optimisations. Also put a fixme on the invite total ↵redmatrix2015-12-161-1/+3
| | | | generations for new accounts, which is incorrect and now commented out.
* PostgreSQL support initial commitHabeas Codice2014-11-131-3/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* allow bbcode in register_textfriendica2014-09-111-2/+2
|
* implement service class for feed polling frequenecy, fixed a service class ↵friendica2014-09-031-1/+0
| | | | bug, moved service class stuff from plugin to account.php where it belongs and load that by default instead of on demand
* make sure we don't block new folks if there's a different register policy ↵friendica2014-07-091-1/+1
| | | | and the hub admin turns on email verify
* finish implementing email verification. Currently it only applies if ↵friendica2014-07-091-4/+19
| | | | REGISTER_OPEN is in effect.
* improve the register text until the new register page is finishedfriendica2013-12-251-0/+11
|
* one step closer to merging register and pubsites pagesfriendica2013-12-221-2/+2
|
* Protocol: now set data['alg'] on all encapsulated encrypted packets, so that ↵friendica2013-11-201-0/+8
| | | | we can more easily retire 'aes256cbc' once it is no longer viable.
* issue #107friendica2013-09-041-0/+6
|
* more register_approve stuff - like the admin page. Hopefully this won't ↵friendica2013-02-081-1/+1
| | | | conflict with Thomas's admin page "list users" changes
* update friends in common tool now that poco is workingfriendica2013-01-311-2/+2
|
* fix register_policy globallyfriendica2013-01-031-1/+1
|
* Fix register policyThomas Willingham2013-01-031-1/+1
|
* zchannel rename to new_channelfriendica2012-10-291-1/+1
|
* comments sort of working again but now need to fix the threading which was ↵friendica2012-10-251-201/+118
| | | | ported when it was only half working
* updatesfriendica2012-09-091-0/+2
|
* simplifyfriendica2012-07-211-16/+5
|
* registration issue after re-factorfriendica2012-06-011-1/+6
|
* turn registration code into a standalone function for re-usefriendica2012-05-311-310/+23
|
* Create a "potential default group" called "Friends" on registration.friendica2012-05-301-0/+5
|
* rev updatefriendica2012-05-201-29/+8
|
* Remove Gravatar from core and add new hook avatar_lookup.Klaus Weidenbach2012-04-091-9/+5
| | | | | This patch removes all occurances of Gravatar from friendica's core and adds a new hook "avatar_lookup" inside the function avatar_img($email) where the new *avatar-plugins should hook in. I haven't touched the language files yet. Are they updated automatically somehow?
* Rename gravatar_img() more generic to avatar_img().Klaus Weidenbach2012-04-091-2/+2
| | | | | I would like to extend the Gravatar support to also use Libravatar, a decentralized avatar service. First step to extract Gravatar from core and put it into its own plugin. Later the Libravatar plugin can be done, too as a plugin.
* Merge branch 'master' of https://github.com/friendica/friendicaAlexander Kampmann2012-04-051-2/+9
|\ | | | | | | | | | | Conflicts: include/config.php update.php
| * ensure all new users get a timezone. We'll use UTC until they choose otherwise.friendica2012-03-311-2/+2
| |
| * register hooks for a COPA pluginfriendica2012-03-311-0/+7
|/
* prevent re-registrations using a deleted username - not an issue with ↵friendica2012-03-221-0/+10
| | | | Friendica but could create a serious privacy issue with federated platforms
* add closeness attributefriendica2012-01-311-2/+2
|
* add remove_user hook (it looks like dreamhost changed all my file ↵friendica2012-01-181-0/+0
| | | | permissions, this will make a nasty commit)
* implement max daily registrationsfriendica2011-12-201-0/+19
|
* cannot register at all when multiple_pages is not allowedfriendica2011-12-091-1/+6
|
* more social graph stuffFriendika2011-11-011-3/+5
|
* .Friendika2011-09-241-2/+1
|
* cleanupFriendika2011-08-161-1/+1
|
* guid functionsFriendika2011-08-071-1/+1
|
* some more zot changes migrating back to f9a mainlineFriendika2011-08-011-3/+3
|
* register hookFriendika2011-07-191-0/+2
|
* basic diaspora discoveryFriendika2011-07-181-2/+3
|
* invite systemFriendika2011-07-171-0/+32
|
* input the admin email address during install/setup.Friendika2011-07-071-3/+8
|
* collapse multiple spaces in usernamesFriendika2011-06-291-0/+3
|
* bug #85Friendika2011-05-231-2/+17
|