aboutsummaryrefslogtreecommitdiffstats
path: root/boot.php
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'dev' of https://github.com/redmatrix/hubzilla into xdev_mergezotlabs2017-04-261-1/+1
|\
| * database support for client side e2ee for private mailzotlabs2017-04-251-1/+1
| |
* | include attach.php here (boot.php) instead of each file that uses it. ↵zotlabs2017-04-171-0/+1
| | | | | | | | Eventually this needs to move to an autoloader.
* | Merge branch 'dev' of https://github.com/redmatrix/hubzilla into xdev_mergezotlabs2017-04-171-1/+0
|\|
| * bump versionMario Vavti2017-04-131-1/+1
| |
| * Merge pull request #715 from zotlabs/cppgit-marijus2017-04-131-1/+1
| |\ | | | | | | backend infrastructure for 'channel protection password'; which will …
| | * backend infrastructure for 'channel protection password'; which will be used ↵zotlabs2017-04-121-1/+1
| | | | | | | | | | | | to optionally encrypt export files and resolve channel/identity ownership/hijacking disputes
| * | correct the mastodon "boost" (aka 'share') author attribution by checking ↵zotlabs2017-04-121-0/+1
| |/ | | | | | | for share activities and pulling the original author info from the activity:object
| * crypto updateszotlabs2017-04-021-3/+0
| |
* | backend infrastructure for 'channel protection password'; which will be used ↵zotlabs2017-04-121-1/+1
| | | | | | | | to optionally encrypt export files and resolve channel/identity ownership/hijacking disputes
* | correct the mastodon "boost" (aka 'share') author attribution by checking ↵zotlabs2017-04-111-0/+1
| | | | | | | | for share activities and pulling the original author info from the activity:object
* | use aes-ctr which is slightly/arguably better than a poke in the eye and ↵zotlabs2017-04-011-7/+0
| | | | | | | | don't restrict the crypto algorithm by server role.
* | Merge branch 'dev' of https://github.com/redmatrix/hubzilla into xdev_mergezotlabs2017-03-311-1/+3
|\|
| * version bumpMario Vavti2017-03-311-1/+1
| |
| * fix a couple more instances where we were still calling mail() directly for ↵zotlabs2017-03-311-27/+27
| | | | | | | | site critical messages
| * get rid of some more deprecated uses of $azotlabs2017-03-311-7/+5
| |
| * remove obsolete app argument from load_pdlzotlabs2017-03-311-1/+1
| |
| * get rid of get_app()zotlabs2017-03-311-12/+0
| |
| * move db_upgrade to zlibzotlabs2017-03-311-87/+3
| |
* | Merge branch 'dev' of https://github.com/redmatrix/hubzilla into xdev_mergezotlabs2017-03-291-1/+3
|\|
| * remove hubzilla.site from directory fallback servers until further noticeMario Vavti2017-03-291-1/+1
| |
| * bump versionMario Vavti2017-03-291-1/+1
| |
| * get rid of some cruft in boot.phpzotlabs2017-03-291-62/+17
| |
| * code_allowed is a real mess. Start the cleanup by remving the account level ↵zotlabs2017-03-291-1/+0
| | | | | | | | code allow and limiting to specific channels only. This reduces the possibility of cross channel security issues coming into play. Then provide a single function for checking the code permission. This is only partially done as we often need to check against the observer or logged in channel as well as the resource owner to ensure that this only returns true for local channels which also own the requested resource.
* | fix a couple more instances where we were still calling mail() directly for ↵zotlabs2017-03-281-27/+27
| | | | | | | | site critical messages
* | get rid of some more deprecated uses of $azotlabs2017-03-281-7/+5
| |
* | remove obsolete app argument from load_pdlzotlabs2017-03-281-1/+1
| |
* | get rid of get_app()zotlabs2017-03-281-12/+0
| |
* | Merge branch 'dev' of https://github.com/redmatrix/hubzilla into xdev_mergezotlabs2017-03-251-0/+1
|\|
| * bump versionsMario Vavti2017-03-231-1/+1
| |
* | move db_upgrade to zlibzotlabs2017-03-231-87/+3
| |
* | rev updatezotlabs2017-03-231-1/+1
| |
* | get rid of some cruft in boot.phpzotlabs2017-03-141-62/+17
| |
* | code_allowed is a real mess. Start the cleanup by remving the account level ↵zotlabs2017-03-131-1/+0
| | | | | | | | code allow and limiting to specific channels only. This reduces the possibility of cross channel security issues coming into play. Then provide a single function for checking the code permission. This is only partially done as we often need to check against the observer or logged in channel as well as the resource owner to ensure that this only returns true for local channels which also own the requested resource.
* | more cleanupzotlabs2017-03-121-29/+35
| |
* | update std_versionzotlabs2017-03-121-1/+1
| |
* | one role.zotlabs2017-03-091-45/+2
| |
* | more cleanupzotlabs2017-03-091-2/+2
|/
* bump versionMario Vavti2017-02-251-1/+1
|
* move some functions to more appropriate placeszotlabs2017-02-231-0/+18
|
* fix several places where head_add_(css|js) functions have been used ↵zotlabs2017-02-191-3/+6
| | | | | | | | | | | incorrectly. It appears that mistakes were made going back a long time and propagated. Here's the way it should work: - if there is no preceding / character, we look for the file within all the appropriate theme directories. - otherwise the file should have a preceding /, which means use this path relative to the hubzilla basedir - files beginning with // are considered to be schemeless URLs. Therefore 'foo.css' means find the best theme-able representation of foo.css. '/library/foo.css' means only use the version of foo.css that is in /library.
* change primary directory per requestzotlabs2017-02-181-2/+1
|
* fix immediate issue with multiple login forms until I can figure out an ↵zotlabs2017-02-081-2/+2
| | | | elegant way to "popup" the modal login form already on the page. We still may need this fix for the actual login module which should always be callable and present a login form even if the nav is completely borked.
* move opensearch to pluginszotlabs2017-02-021-1/+8
|
* tested extensible permissions by adding wiki permissions. Discovered a ↵zotlabs2017-02-011-7/+9
| | | | couple of issues that needed attention in the process.
* fix a few style issues with nav login panelzotlabs2017-02-011-1/+2
|
* consolidate hubloc storagezotlabs2017-01-301-0/+1
|
* Alter the queue so that each queue item stores the scheduled time of the ↵zotlabs2017-01-291-1/+1
| | | | | | | | next delivery. This keeps the query for queued items simple. We no longer group by posturl; as the queue update function will only keep one item per destination scheduled for shorter term processing. Others (multiple queued items for a single destination) will be scheduled for delivery far into the future and only delivered if the hub responds to the "active" or short term queue item.
* provide lowlevel xchan storage function to ensure that all non-null rows are ↵zotlabs2017-01-281-0/+1
| | | | initialised
* nwiki updatesHubzilla2017-01-181-0/+1
|