aboutsummaryrefslogtreecommitdiffstats
path: root/mod/setup.php
Commit message (Collapse)AuthorAgeFilesLines
* module updatesredmatrix2016-04-181-744/+0
|
* static Appredmatrix2016-03-311-20/+20
|
* deprecate $a->get_baseurl()redmatrix2016-03-301-5/+5
|
* I haven't investigated 'why', but the addition of the router class in ↵redmatrix2016-02-271-0/+3
| | | | https://github.com/redmatrix/hubzilla/commit/1db3409f36f408bfc49816e1fab3df4b53b8f19e resulted in the setup global variable $install_wizard_pass to not get initiated at the global level when the setup module file was included. This corrects the situation and makes install work but without explaining why the variable wasn't instantiated in the first place. This may be important - if any other modules use global variables internally. I don't believe that any do, but the behaviour needs to be resolved or documented.
* guest photo upload failing when js_upload is in use due to non-existent acl ↵redmatrix2016-02-111-1/+1
| | | | parameters
* uno stuffredmatrix2016-02-051-3/+5
|
* initial uno configredmatrix2016-02-041-10/+11
|
* generalise the site black|white allow lists, also add a channel black|white ↵redmatrix2015-11-291-1/+1
| | | | list for future use
* change setup defaults to 127.0.0.1 instead of localhost for DB server, add ↵redmatrix2015-10-161-3/+3
| | | | documentation to the INSTALL.txt explaining the choice.
* Merge https://github.com/redmatrix/redmatrix into pending_mergeredmatrix2015-08-121-0/+4
| | | | | | Conflicts: view/es/htconfig.tpl view/es/update_fail_eml.tpl
* coverup and ignore the illegal string offset message that some sites have ↵redmatrix2015-07-141-1/+1
| | | | been reporting. This does not fix it. A fix would be to examine the data that has been received and find out why it is mangled and trace this back to where it was mangled.
* Add PHP's xml module check and upload limits to setup.Klaus Weidenbach2015-05-241-189/+255
| | | | And some documentation.
* more work isolating the projectname from core.redmatrix2015-05-171-2/+2
|
* mysql schema typo, do the install check for store before chcking smarty, as ↵friendica2015-03-151-2/+2
| | | | that is where the dir is created, change install doc to point to install/schema_xxxxx.sql instead of database.sql
* INSTALL: 'store' is created during setup but not 'store/[data]/smarty3' and ↵friendica2015-02-191-1/+1
| | | | we explicitly check for the latter and report that it isn't there or isn't writable. Doh.
* remove extraneous debug file left over from postgres work.friendica2015-01-111-1/+0
|
* Use grouped select field for timezone selectionStefan Parviainen2015-01-011-1/+1
|
* PostgreSQL support initial commitHabeas Codice2014-11-131-12/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* convert application strings to en-USfriendica2014-07-311-1/+1
|
* provide os_mkdir to workaround permission issues with php mkdirfriendica2014-07-161-1/+1
|
* move smarty compiled files to store/[data]/smarty3 - which puts all ↵friendica2014-07-101-4/+4
| | | | writeable areas of the server except the config file and logs under the "store" directory. We'll do logs at a future time.
* issue #479 - tag escaping not needed here.friendica2014-06-021-8/+8
|
* issue #476friendica2014-05-311-1/+1
|
* setup: check for open https port with an invalid cert, even if configured to ↵friendica2014-05-061-11/+25
| | | | use http. Also a bit more word-smithing on the resultant error text but it's still not perfect.
* Added some more details about why browser-valid SSL certificates must besasiflo2014-04-101-1/+8
| | | | | | | used when SSL is used at all. It is now in the check failure message in the installation routine, the installation readme and in the documentation pages.
* This should be a slight improvement in setting ciphers - we'll punt on ↵friendica2014-03-251-0/+19
| | | | RedHat but open up the list just for openssl distros which seem to have all the problems at the moment.
* report curl errors during install when they are most neededfriendica2014-03-231-0/+3
|
* Actually create syschan during installThomas Willingham2014-03-071-0/+3
|
* some windows fixesfriendica2014-02-021-1/+4
|
* add store directory write check to install checksfriendica2014-01-081-0/+20
|
* install redbasic during setup so that at least one theme is registered. ↵friendica2013-12-161-0/+2
| | | | Otherwise none of the display settings seem to work very well.
* issue #240 - we were using htmlentities instead of htmlspecialchars in ↵friendica2013-12-111-1/+1
| | | | several places, and this was a bit greedy in the set of characters which were converted from utf-8 to HTML entities. Also brought mail attachments up to date so they are rendered identically to item attachments.
* INSTALL for dummies - step 1: ensure that we throw an ugly error message in ↵friendica2013-11-051-0/+19
| | | | | | | 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.
* Issue #181Thomas Willingham2013-10-141-2/+2
|
* fix include pathsdsp19862013-09-171-1/+1
|
* if somebody changes the site url during setup - check if we can connect to ↵friendica2013-05-161-0/+12
| | | | the new url e.g. it has a valid cert.
* fix intltext template driverfriendica2013-05-151-0/+9
|
* another typofriendica2013-05-151-1/+1
|
* more setup workfriendica2013-05-151-3/+3
|
* typofriendica2013-05-151-1/+1
|
* add port settings to setupfriendica2013-05-151-2/+9
|
* add certificate check to setupfriendica2013-05-151-0/+9
|
* disable pcss when installing since modules don't yet work and pcss uses the ↵friendica2013-05-141-1/+1
| | | | view module, plus weekly doc update
* add db_port to setup and cli_startup - still need to set the port in mod/setupfriendica2013-05-101-3/+3
|
* db abstraction layerfriendica2013-04-221-12/+12
|
* xss attack vector in bbcode.php - check for proc_open being disabled for ↵friendica2013-02-261-0/+6
| | | | security reasons in install
* make sure old fetch_url calls (and those that provided their own curl ↵friendica2013-02-251-2/+2
| | | | wrapper) go through z_fetch_url
* check for mcrypt during install, allow admin email account to be admin *if* ↵friendica2013-01-271-0/+5
| | | | it's the first account.
* add Smarty templates for international templatesZach Prezkuta2013-01-101-4/+0
|
* bypass smarty for intletext templatesfriendica2013-01-071-0/+4
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 07:09:39 +0000