aboutsummaryrefslogtreecommitdiffstats
path: root/view/en
Commit message (Collapse)AuthorAgeFilesLines
* remove redundant untranslated htconfig templates and add the ↵Mario2023-03-171-0/+6
| | | | db_skip_locked_supported config option
* update htconfig.tplMario2022-09-301-14/+14
|
* invite: fix variable name in template and do not substitute the Â@ in the ↵Mario2021-10-221-3/+3
| | | | webfinger address with @+
* register: fix language issue and add additional info to the infobox if email ↵Mario2021-05-071-3/+3
| | | | verification is configured
* register: more ui/uxMario2021-04-081-6/+5
|
* at end of day, some files probably without conflicts so farHilmar R2021-01-237-2/+58
|
* port db update improvements from zapMario Vavti2019-05-031-6/+15
|
* Issue with configurable site age limit, vagueness when informing about email ↵zotlabs2018-01-261-1/+6
| | | | 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.
* remove server role from language configszotlabs2017-05-291-9/+0
|
* string updatezotlabs2016-10-301-2/+2
|
* Provide better explanation of server_roles in the config templatezotlabs2016-10-091-2/+3
|
* use config system.server_role and deprecate 'UNO'redmatrix2016-08-071-2/+8
|
* consolidate all the sys_boot functionality that is common between the web ↵redmatrix2016-05-261-1/+1
| | | | server and the cli daemon manager. Get rid of yet another global variable ($default_timezone) whilst doing so.
* log if the session handler fails and surface the ssl_cookie config settingredmatrix2016-04-081-0/+1
|
* static Appredmatrix2016-03-311-15/+15
|
* Added Link to TOS to EMail templates targeting membersTobias Luther2016-03-063-0/+13
|
* duplicated lines in en config fileredmatrix2016-02-081-10/+0
|
* make yet another recommended security header optional - this time because of ↵redmatrix2016-02-081-0/+17
| | | | piwik. Personally I think if you want to track people you really don't understand this project and its history, but whatever....
* initial uno configredmatrix2016-02-041-0/+2
|
* no trailing slashJeroen van Riet Paap2016-01-271-1/+1
|
* change text "Red developers" in update failed emailredmatrix2015-12-051-1/+1
|
* document that you probably shouldn't set a primary directory server in ↵redmatrix2015-11-251-1/+1
| | | | somebody else's realm.
* second pass name changeredmatrix2015-05-052-2/+2
|
* first pass name changeredmatrix2015-05-051-2/+2
|
* automated warning after a few days if poller is deadfriendica2015-03-021-0/+17
|
* here's the email templatefriendica2015-03-011-0/+20
|
* queue management actions. Still needs further work such as indication of ↵friendica2015-03-011-1/+0
| | | | last successful connection or indication that the hub was marked offline, but these are potentially expensive queries.
* PostgreSQL support initial commitHabeas Codice2014-11-131-1/+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)
* remove unused email template fileszottel2014-10-104-75/+0
|
* make verify_email the default for new installs (at least English installs), ↵friendica2014-09-101-0/+5
| | | | and provide a setting on the admin page for it.
* some initial work towards email address verificationfriendica2014-07-031-0/+25
|
* Clean up legacy smarty3Thomas Willingham2014-04-1910-301/+0
|
* removed default maximagesize - it can be set in the admin pages.friendica2014-04-021-4/+0
|
* This should be a slight improvement in setting ciphers - we'll punt on ↵friendica2014-03-251-7/+0
| | | | RedHat but open up the list just for openssl distros which seem to have all the problems at the moment.
* ssl ciphers - be liberal in what we accept, conservative in what we generatefriendica2014-03-241-0/+7
|
* notification bug - don't use $r, we already set it to something else that we ↵friendica2014-02-061-1/+2
| | | | need further on.
* INSTALL for dummies - step 1: ensure that we throw an ugly error message in ↵friendica2013-11-051-0/+11
| | | | | | | their face if there's an ugly error when we first try to install. DON'T white screen until after they've got it running.
* add "tiered" access policy, add tagcloud to directory pagesfriendica2013-09-181-2/+8
|
* if changing primary hub during an import operation - remove the old xchan ↵friendica2013-08-191-1/+1
| | | | and create a fresh xchan pointing at this instance. Also a minor edit to increase the default photo upload limit for new sites. There aren't many cameras left that will take photos < 800k in size.
* Add a site access policy (to determine if this is really a public site or ↵friendica2013-08-061-0/+14
| | | | just an open site) and add an orphan flag to xchans in case all their hublocs go away. Get rid of a couple of DO NOT EDIT template messages which were still lurking in the tree.
* convert all the remaining email templates to smartyfriendica2013-05-168-51/+53
|
* update email template to smarty (several more to go)friendica2013-05-151-5/+5
|
* fix intltext templates - maybefriendica2013-05-151-10/+10
|
* add port settings to setupfriendica2013-05-151-0/+1
|
* Sort out registrations requiring approvalfriendica2013-02-114-12/+12
|
* add soapbox settingsfriendica2013-02-102-8/+28
|
* perhaps REGISTER_VERIFY will work now. I'll test it and make certain it ↵friendica2013-02-082-2/+2
| | | | works some day. But not today.
* add newline at end of headerZach Prezkuta2013-01-1110-2/+12
|
* add warning messae about automatically generated templatesZach Prezkuta2013-01-1110-10/+50
|
* add Smarty templates for international templatesZach Prezkuta2013-01-1010-0/+241
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-27 23:43:28 +0000