Streams/streams
Streams/streams
1
0
Fork 0
mirror of https://codeberg.org/streams/streams.git synced 2024-09-20 09:55:15 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
streams/include/identity.php

1595 lines
45 KiB
PHP
Raw Normal View History

start formatting for Doxygen
2013-02-26 01:09:40 +00:00
<?php /** @file */
get_item_elements (json version)
2012-07-30 05:43:51 +00:00
basic identity creation
2012-08-24 08:14:42 +00:00
require_once('include/zot.php');
require_once('include/crypto.php');
get_item_elements (json version)
2012-07-30 05:43:51 +00:00
a few minor changes
2012-08-27 06:05:00 +00:00
more documentation work
2013-12-04 01:33:48 +00:00
/**
* @function identity_check_service_class($account_id)
* Called when creating a new channel. Checks the account's service class and number
* of current channels to determine whether creating a new channel is within the current
* service class constraints.
*
* @param int $account_id
* Account_id used for this request
*
* @returns array
* 'success' => boolean true if creating a new channel is allowed for this account
* 'message' => if success is false, optional error text
*/
a few minor changes
2012-08-27 06:05:00 +00:00
function identity_check_service_class($account_id) {
$ret = array('success' => false, $message => '');
PostgreSQL support initial commit 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)
2014-11-13 20:21:58 +00:00
$r = q("select count(channel_id) as total from channel where channel_account_id = %d and not ( channel_pageflags & %d )>0 ",
don't include deleted channels in number of channels service class checks
2014-02-16 22:48:07 +00:00
intval($account_id),
intval(PAGE_REMOVED)
a few minor changes
2012-08-27 06:05:00 +00:00
);
if(! ($r && count($r))) {
only auto-follow the site recommendations if creating the first channel for an account.
2014-10-01 22:40:19 +00:00
$ret['total_identities'] = 0;
a few minor changes
2012-08-27 06:05:00 +00:00
$ret['message'] = t('Unable to obtain identity information from database');
return $ret;
}
only auto-follow the site recommendations if creating the first channel for an account.
2014-10-01 22:40:19 +00:00
$ret['total_identities'] = intval($r[0]['total']);
a few minor changes
2012-08-27 06:05:00 +00:00
if(! service_class_allows($account_id,'total_identities',$r[0]['total'])) {
$result['message'] .= upgrade_message();
return $result;
}
$ret['success'] = true;
return $ret;
}
more documentation work
2013-12-04 01:33:48 +00:00
/**
* @function validate_channelname($name)
* Determine if the channel name is allowed when creating a new channel.
* This action is pluggable.
*
* @param string $name
*
* @returns nil return if name is valid, or string describing the error state.
*
* We're currently only checking for an empty name or one that exceeds our storage limit (255 chars).
* 255 chars is probably going to create a mess on some pages.
* Plugins can set additional policies such as full name requirements, character sets, multi-byte
* length, etc.
*
*/
provide a global way of enforcing name policy restrictions, but only enforce empty names or length > storage size. Allow plugins to set other policies. In particular, you can't have an empty channel name now, but one char is legal ;-)
2013-02-08 02:53:51 +00:00
function validate_channelname($name) {
if(! $name)
return t('Empty name');
if(strlen($name) > 255)
return t('Name too long');
$arr = array('name' => $name);
call_hooks('validate_channelname',$arr);
if(x($arr,'message'))
return $arr['message'];
return;
}
a few minor changes
2012-08-27 06:05:00 +00:00
more documentation work
2013-12-04 01:33:48 +00:00
/**
clean up sys_channel creation so it will work
2013-12-22 22:08:38 +00:00
* @function create_sys_channel()
more documentation work
2013-12-04 01:33:48 +00:00
* Create a system channel - which has no account attached
*
*/
we'll need a special system channel (not attached to any account) for directory synchronisation
2013-03-19 00:55:04 +00:00
clean up sys_channel creation so it will work
2013-12-22 22:08:38 +00:00
function create_sys_channel() {
if(get_sys_channel())
return;
create_sys_channel during setup bypasses our check when creating the first account that there is a site keypair. Esnure that a site keypair is created before any sys channels are created.
2014-03-24 01:12:32 +00:00
// Ensure that there is a host keypair.
if((! get_config('system','pubkey')) && (! get_config('system','prvkey'))) {
make sure crypto is loaded before creating a keypair
2014-03-24 01:34:17 +00:00
require_once('include/crypto.php');
create_sys_channel during setup bypasses our check when creating the first account that there is a site keypair. Esnure that a site keypair is created before any sys channels are created.
2014-03-24 01:12:32 +00:00
$hostkey = new_keypair(4096);
set_config('system','pubkey',$hostkey['pubkey']);
set_config('system','prvkey',$hostkey['prvkey']);
}
clean up sys_channel creation so it will work
2013-12-22 22:08:38 +00:00
create_identity(array(
'account_id' => 'xxx', // This will create an identity with an (integer) account_id of 0, but account_id is required
'nickname' => 'sys',
'name' => 'System',
'pageflags' => PAGE_SYSTEM,
'publish' => 0,
'xchanflags' => XCHAN_FLAGS_SYSTEM
));
}
function get_sys_channel() {
PostgreSQL support initial commit 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)
2014-11-13 20:21:58 +00:00
$r = q("select * from channel left join xchan on channel_hash = xchan_hash where (channel_pageflags & %d)>0 limit 1",
clean up sys_channel creation so it will work
2013-12-22 22:08:38 +00:00
intval(PAGE_SYSTEM)
);
if($r)
return $r[0];
return false;
}
allow zotfeed to create a firehose of a site.
2014-03-26 23:09:07 +00:00
function is_sys_channel($channel_id) {
$r = q("select channel_pageflags from channel where channel_id = %d limit 1",
intval($channel_id)
);
if(($r) && ($r[0]['channel_pageflags'] & PAGE_SYSTEM))
return true;
return false;
}
we'll need a special system channel (not attached to any account) for directory synchronisation
2013-03-19 00:55:04 +00:00
more documentation work
2013-12-04 01:33:48 +00:00
/**
* @channel_total()
don't include deleted channels in number of channels service class checks
2014-02-16 22:48:07 +00:00
* Return the total number of channels on this site. No filtering is performed except to check PAGE_REMOVED
more documentation work
2013-12-04 01:33:48 +00:00
*
* @returns int
* on error returns boolean false
*
*/
we'll need a special system channel (not attached to any account) for directory synchronisation
2013-03-19 00:55:04 +00:00
more site stats
2013-07-25 01:17:00 +00:00
function channel_total() {
PostgreSQL support initial commit 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)
2014-11-13 20:21:58 +00:00
$r = q("select channel_id from channel where not ( channel_pageflags & %d )>0",
don't include deleted channels in number of channels service class checks
2014-02-16 22:48:07 +00:00
intval(PAGE_REMOVED)
);
more site stats
2013-07-25 01:17:00 +00:00
if(is_array($r))
return count($r);
return false;
}
more documentation work
2013-12-04 01:33:48 +00:00
/**
* @function create_identity($arr)
* Create a new channel
* Also creates the related xchan, hubloc, profile, and "self" abook records, and an
* empty "Friends" group/collection for the new channel
*
* @param array $arr
* 'name' => full name of channel
* 'nickname' => "email/url-compliant" nickname
* 'account_id' => account_id to attach with this channel
* [other identity fields as desired]
*
* @returns array
* 'success' => boolean true or false
* 'message' => optional error text if success is false
* 'channel' => if successful the created channel array
*/
back to identity creation form
2012-08-24 03:00:10 +00:00
function create_identity($arr) {
now it gets hard
2012-08-28 08:55:18 +00:00
$a = get_app();
a few minor changes
2012-08-27 06:05:00 +00:00
$ret = array('success' => false);
if(! $arr['account_id']) {
$ret['message'] = t('No account identifier');
return $ret;
}
ability to pre-populate connections for new channels. e.g. "MySpace Tom"
2014-10-01 21:48:08 +00:00
$ret = identity_check_service_class($arr['account_id']);
Service class identity, follow, photo upload, att upload
2013-09-07 22:21:42 +00:00
if (!$ret['success']) {
return $ret;
}
only auto-follow the site recommendations if creating the first channel for an account.
2014-10-01 22:40:19 +00:00
// save this for auto_friending
$total_identities = $ret['total_identities'];
Don't allow channel creation with a nickname
2013-11-15 00:51:23 +00:00
several unrelated things - auto_follow wasn't working for new accounts, error returned in private mention to a collection, and added auto-completion to photo tags; though it only matches people so the hover text is now wrong. Also made the photo edit form XHTML (XML) compliant.
2014-10-28 02:21:41 +00:00
force webbies to lowercase
2013-08-28 00:19:52 +00:00
$nick = mb_strtolower(trim($arr['nickname']));
Don't allow channel creation with a nickname
2013-11-15 00:51:23 +00:00
if(! $nick) {
$ret['message'] = t('Nickname is required.');
return $ret;
}
a few minor changes
2012-08-27 06:05:00 +00:00
$name = escape_tags($arr['name']);
$pageflags = ((x($arr,'pageflags')) ? intval($arr['pageflags']) : PAGE_NORMAL);
Some sys chan stuff
2013-12-22 20:47:57 +00:00
$xchanflags = ((x($arr,'xchanflags')) ? intval($arr['xchanflags']) : XCHAN_FLAGS_NORMAL);
provide a global way of enforcing name policy restrictions, but only enforce empty names or length > storage size. Allow plugins to set other policies. In particular, you can't have an empty channel name now, but one char is legal ;-)
2013-02-08 02:53:51 +00:00
$name_error = validate_channelname($arr['name']);
if($name_error) {
$ret['message'] = $name_error;
return $ret;
}
don't allow normal channels to have the name 'sys'.
2014-03-24 01:45:42 +00:00
if($nick === 'sys' && (! ($pageflags & PAGE_SYSTEM))) {
$ret['message'] = t('Reserved nickname. Please choose another.');
return $ret;
}
begin debug zentity
2012-08-24 08:57:36 +00:00
if(check_webbie(array($nick)) !== $nick) {
basic identity creation
2012-08-24 08:14:42 +00:00
$ret['message'] = t('Nickname has unsupported characters or is already being used on this site.');
return $ret;
}
$guid = zot_new_uid($nick);
$key = new_keypair(4096);
back to identity creation form
2012-08-24 03:00:10 +00:00
add hash to channel structure for consistency/redundancy
2012-10-04 10:13:57 +00:00
$sig = base64url_encode(rsa_sign($guid,$key['prvkey']));
clean up more code duplication
2014-07-15 04:21:24 +00:00
$hash = make_xchan_hash($guid,$sig);
add hash to channel structure for consistency/redundancy
2012-10-04 10:13:57 +00:00
Whinging whining stupid fucks.
2013-02-12 10:02:35 +00:00
// Force a few things on the short term until we can provide a theme or app with choice
$publish = 1;
if(array_key_exists('publish', $arr))
$publish = intval($arr['publish']);
admittedly local magic-auth is easy so that's mostly done. Now it gets hard.
2012-12-14 00:27:58 +00:00
$primary = true;
basic identity creation
2012-08-24 08:14:42 +00:00
more groundwork for channel import
2013-02-15 01:39:16 +00:00
if(array_key_exists('primary', $arr))
$primary = intval($arr['primary']);
implement permission roles - the backend should be done except for maybe a couple of small tweaks. Now we just need to define the rest of the roles and create a chooser for them. Adam started on this some time back but I don't know where that has gone.
2014-09-18 00:59:46 +00:00
some sane permission defaults.
2013-08-19 03:20:03 +00:00
$perms_sql = '';
implement permission roles - the backend should be done except for maybe a couple of small tweaks. Now we just need to define the rest of the roles and create a chooser for them. Adam started on this some time back but I don't know where that has gone.
2014-09-18 00:59:46 +00:00
$role_permissions = null;
channel permission roles
2014-09-18 04:16:15 +00:00
$global_perms = get_perms();
implement permission roles - the backend should be done except for maybe a couple of small tweaks. Now we just need to define the rest of the roles and create a chooser for them. Adam started on this some time back but I don't know where that has gone.
2014-09-18 00:59:46 +00:00
if(array_key_exists('permissions_role',$arr) && $arr['permissions_role']) {
$role_permissions = get_role_perms($arr['permissions_role']);
channel permission roles
2014-09-18 04:16:15 +00:00
implement permission roles - the backend should be done except for maybe a couple of small tweaks. Now we just need to define the rest of the roles and create a chooser for them. Adam started on this some time back but I don't know where that has gone.
2014-09-18 00:59:46 +00:00
if($role_permissions) {
foreach($role_permissions as $p => $v) {
if(strpos($p,'channel_') !== false) {
channel permission roles
2014-09-18 04:16:15 +00:00
$perms_keys .= ', ' . $p;
implement permission roles - the backend should be done except for maybe a couple of small tweaks. Now we just need to define the rest of the roles and create a chooser for them. Adam started on this some time back but I don't know where that has gone.
2014-09-18 00:59:46 +00:00
$perms_vals .= ', ' . intval($v);
}
if($p === 'directory_publish')
$publish = intval($v);
}
}
}
else {
$defperms = site_default_perms();
foreach($defperms as $p => $v) {
$perms_keys .= ', ' . $global_perms[$p][0];
$perms_vals .= ', ' . intval($v);
}
some sane permission defaults.
2013-08-19 03:20:03 +00:00
}
more groundwork for channel import
2013-02-15 01:39:16 +00:00
channel permission roles
2014-09-18 04:16:15 +00:00
Let admins set a default expire days value.
2014-04-01 18:36:56 +00:00
$expire = get_config('system', 'default_expire_days');
$expire = (($expire===false)? '0': $expire);
channel permission roles
2014-09-18 04:16:15 +00:00
moving a lot of structure around. 'entity' is now 'channel'
2012-09-26 00:57:20 +00:00
$r = q("insert into channel ( channel_account_id, channel_primary,
add hash to channel structure for consistency/redundancy
2012-10-04 10:13:57 +00:00
channel_name, channel_address, channel_guid, channel_guid_sig,
Set timezone when creating a channel.
2014-10-02 23:57:07 +00:00
channel_hash, channel_prvkey, channel_pubkey, channel_pageflags, channel_expire_days, channel_timezone $perms_keys )
That's a string, not an integer
2014-10-03 14:16:05 +00:00
values ( %d, %d, '%s', '%s', '%s', '%s', '%s', '%s', '%s', %d, %d, '%s' $perms_vals ) ",
basic identity creation
2012-08-24 08:14:42 +00:00
a few minor changes
2012-08-27 06:05:00 +00:00
intval($arr['account_id']),
basic identity creation
2012-08-24 08:14:42 +00:00
intval($primary),
dbesc($name),
dbesc($nick),
dbesc($guid),
add hash to channel structure for consistency/redundancy
2012-10-04 10:13:57 +00:00
dbesc($sig),
dbesc($hash),
basic identity creation
2012-08-24 08:14:42 +00:00
dbesc($key['prvkey']),
dbesc($key['pubkey']),
Let admins set a default expire days value.
2014-04-01 18:36:56 +00:00
intval($pageflags),
Set timezone when creating a channel.
2014-10-02 23:57:07 +00:00
intval($expire),
dbesc($a->timezone)
basic identity creation
2012-08-24 08:14:42 +00:00
);
some sane permission defaults.
2013-08-19 03:20:03 +00:00
moving a lot of structure around. 'entity' is now 'channel'
2012-09-26 00:57:20 +00:00
$r = q("select * from channel where channel_account_id = %d
add hash to channel structure for consistency/redundancy
2012-10-04 10:13:57 +00:00
and channel_guid = '%s' limit 1",
a few minor changes
2012-08-27 06:05:00 +00:00
intval($arr['account_id']),
basic identity creation
2012-08-24 08:14:42 +00:00
dbesc($guid)
);
a few minor changes
2012-08-27 06:05:00 +00:00
Whinging whining stupid fucks.
2013-02-12 10:02:35 +00:00
if(! $r) {
basic identity creation
2012-08-24 08:14:42 +00:00
$ret['message'] = t('Unable to retrieve created identity');
return $ret;
}
a few minor changes
2012-08-27 06:05:00 +00:00
moving a lot of structure around. 'entity' is now 'channel'
2012-09-26 00:57:20 +00:00
$ret['channel'] = $r[0];
a few minor changes
2012-08-27 06:05:00 +00:00
we'll need a special system channel (not attached to any account) for directory synchronisation
2013-03-19 00:55:04 +00:00
if(intval($arr['account_id']))
set_default_login_identity($arr['account_id'],$ret['channel']['channel_id'],false);
use hash for channel id
2012-10-02 02:04:21 +00:00
a few minor changes
2012-08-27 06:05:00 +00:00
// Create a verified hub location pointing to this site.
need to accomodate different webbies on different hubs
2012-11-01 01:05:36 +00:00
$r = q("insert into hubloc ( hubloc_guid, hubloc_guid_sig, hubloc_hash, hubloc_addr, hubloc_flags,
this is the reason Diaspora forum tagging was broken
2014-10-15 01:02:34 +00:00
hubloc_url, hubloc_url_sig, hubloc_host, hubloc_callback, hubloc_sitekey, hubloc_network )
values ( '%s', '%s', '%s', '%s', %d, '%s', '%s', '%s', '%s', '%s', '%s' )",
add hash to channel structure for consistency/redundancy
2012-10-04 10:13:57 +00:00
dbesc($guid),
use hash for channel id
2012-10-02 02:04:21 +00:00
dbesc($sig),
dbesc($hash),
need to accomodate different webbies on different hubs
2012-11-01 01:05:36 +00:00
dbesc($ret['channel']['channel_address'] . '@' . get_app()->get_hostname()),
a few minor changes
2012-08-27 06:05:00 +00:00
intval(($primary) ? HUBLOC_FLAGS_PRIMARY : 0),
dbesc(z_root()),
moving a lot of structure around. 'entity' is now 'channel'
2012-09-26 00:57:20 +00:00
dbesc(base64url_encode(rsa_sign(z_root(),$ret['channel']['channel_prvkey']))),
starting on pinging the basic elements of federation and communication
2012-10-31 23:55:19 +00:00
dbesc(get_app()->get_hostname()),
a few minor changes
2012-08-27 06:05:00 +00:00
dbesc(z_root() . '/post'),
this is the reason Diaspora forum tagging was broken
2014-10-15 01:02:34 +00:00
dbesc(get_config('system','pubkey')),
dbesc('zot')
a few minor changes
2012-08-27 06:05:00 +00:00
);
if(! $r)
logger('create_identity: Unable to store hub location');
now it gets hard
2012-08-28 08:55:18 +00:00
use hash for channel id
2012-10-02 02:04:21 +00:00
moving a lot of structure around. 'entity' is now 'channel'
2012-09-26 00:57:20 +00:00
$newuid = $ret['channel']['channel_id'];
now it gets hard
2012-08-28 08:55:18 +00:00
clean up sys_channel creation so it will work
2013-12-22 22:08:38 +00:00
$r = q("insert into xchan ( xchan_hash, xchan_guid, xchan_guid_sig, xchan_pubkey, xchan_photo_l, xchan_photo_m, xchan_photo_s, xchan_addr, xchan_url, xchan_follow, xchan_connurl, xchan_name, xchan_network, xchan_photo_date, xchan_name_date, xchan_flags ) values ('%s', '%s', '%s', '%s', '%s', '%s', '%s', '%s', '%s', '%s', '%s', '%s', '%s', '%s', '%s', %d)",
use hash for channel id
2012-10-02 02:04:21 +00:00
dbesc($hash),
fixed the hash, now onward & upward
2012-11-02 07:19:04 +00:00
dbesc($guid),
use hash for channel id
2012-10-02 02:04:21 +00:00
dbesc($sig),
get profile edits working
2012-10-19 03:59:00 +00:00
dbesc($key['pubkey']),
more heavy lifting
2012-10-24 04:24:23 +00:00
dbesc($a->get_baseurl() . "/photo/profile/l/{$newuid}"),
dbesc($a->get_baseurl() . "/photo/profile/m/{$newuid}"),
dbesc($a->get_baseurl() . "/photo/profile/s/{$newuid}"),
starting on pinging the basic elements of federation and communication
2012-10-31 23:55:19 +00:00
dbesc($ret['channel']['channel_address'] . '@' . get_app()->get_hostname()),
"profile url" e.g. the wall/stream is now "channel url". "Profile URL" goes to the profile details.
2012-10-30 00:14:02 +00:00
dbesc(z_root() . '/channel/' . $ret['channel']['channel_address']),
progress on generic sellpage - is not yet linked from existing connect buttons and editing has not been completed
2013-08-22 03:05:55 +00:00
dbesc(z_root() . '/follow?f=&url=%s'),
add poco and follow to default xchan creation
2013-12-05 02:30:14 +00:00
dbesc(z_root() . '/poco/' . $ret['channel']['channel_address']),
wall posts now display - address book structure revamp started
2012-10-11 00:58:56 +00:00
dbesc($ret['channel']['channel_name']),
dbesc('zot'),
dbesc(datetime_convert()),
Some sys chan stuff
2013-12-22 20:47:57 +00:00
dbesc(datetime_convert()),
intval($xchanflags)
use hash for channel id
2012-10-02 02:04:21 +00:00
);
// Not checking return value.
// It's ok for this to fail if it's an imported channel, and therefore the hash is a duplicate
Whinging whining stupid fucks.
2013-02-12 10:02:35 +00:00
$r = q("INSERT INTO profile ( aid, uid, profile_guid, profile_name, is_default, publish, name, photo, thumb)
VALUES ( %d, %d, '%s', '%s', %d, %d, '%s', '%s', '%s') ",
moving a lot of structure around. 'entity' is now 'channel'
2012-09-26 00:57:20 +00:00
intval($ret['channel']['channel_account_id']),
set the account_id on channel creation
2012-09-03 04:24:39 +00:00
intval($newuid),
get profile edits working
2012-10-19 03:59:00 +00:00
dbesc(random_string()),
typo
2012-12-16 10:07:16 +00:00
t('Default Profile'),
now it gets hard
2012-08-28 08:55:18 +00:00
1,
Whinging whining stupid fucks.
2013-02-12 10:02:35 +00:00
$publish,
moving a lot of structure around. 'entity' is now 'channel'
2012-09-26 00:57:20 +00:00
dbesc($ret['channel']['channel_name']),
fix photo paths
2012-10-24 07:00:16 +00:00
dbesc($a->get_baseurl() . "/photo/profile/l/{$newuid}"),
dbesc($a->get_baseurl() . "/photo/profile/m/{$newuid}")
now it gets hard
2012-08-28 08:55:18 +00:00
);
implement permission roles - the backend should be done except for maybe a couple of small tweaks. Now we just need to define the rest of the roles and create a chooser for them. Adam started on this some time back but I don't know where that has gone.
2014-09-18 00:59:46 +00:00
if($role_permissions) {
$myperms = ((array_key_exists('perms_auto',$role_permissions) && $role_permissions['perms_auto']) ? intval($role_permissions['perms_accept']) : 0);
}
ok heads up - potentially destabilising change. I've tried to sort out all the default connection permissions for those who don't have a predefined (or therefore have a "custom") permissions role. Unfortunately this includes most people that were using this software more than a month ago. The real changes are that the SELF address book entry no longer holds "auto-permissions" but instead holds your "default permissions" (if you have a pre-defined role, the defaults will be pulled from the role table). The auto permissions have moved to a pconfig (uid.system.autoperms). A DB update will move these settings into their new homes. What used to be the "Auto-permissions settings" page is now the "default permissions settings" page and a checkbox therein decides whether or not to apply the permissions automatically. A link to this page will only be shown when you have the "custom" role selected. With luck nobody will notice anything wrong. But at least for the next few days, please review permissions that have been assigned to new connections (either automatically or manually) and make sure they make sense (e.g. they aren't "nothing"). You still need to take action when seeing a message "permissions have changed but not yet submitted" as we always let you review and perhaps adjust the settings _before_ a connection is established (unless you have autoperms turned on).
2014-11-05 01:11:02 +00:00
else
$myperms = PERMS_R_STREAM|PERMS_R_PROFILE|PERMS_R_PHOTOS|PERMS_R_ABOOK
|PERMS_W_STREAM|PERMS_W_WALL|PERMS_W_COMMENT|PERMS_W_MAIL|PERMS_W_CHAT
|PERMS_R_STORAGE|PERMS_R_PAGES|PERMS_W_LIKE;
implement permission roles - the backend should be done except for maybe a couple of small tweaks. Now we just need to define the rest of the roles and create a chooser for them. Adam started on this some time back but I don't know where that has gone.
2014-09-18 00:59:46 +00:00
$r = q("insert into abook ( abook_account, abook_channel, abook_xchan, abook_closeness, abook_created, abook_updated, abook_flags, abook_my_perms )
values ( %d, %d, '%s', %d, '%s', '%s', %d, %d ) ",
fixing broken things again after the latest round of ripping out the yellow slime and replacing it with red slime.
2012-10-30 03:47:56 +00:00
intval($ret['channel']['channel_account_id']),
intval($newuid),
dbesc($hash),
intval(0),
dbesc(datetime_convert()),
dbesc(datetime_convert()),
implement permission roles - the backend should be done except for maybe a couple of small tweaks. Now we just need to define the rest of the roles and create a chooser for them. Adam started on this some time back but I don't know where that has gone.
2014-09-18 00:59:46 +00:00
intval(ABOOK_FLAG_SELF),
intval($myperms)
fixing broken things again after the latest round of ripping out the yellow slime and replacing it with red slime.
2012-10-30 03:47:56 +00:00
);
we'll need a special system channel (not attached to any account) for directory synchronisation
2013-03-19 00:55:04 +00:00
if(intval($ret['channel']['channel_account_id'])) {
now it gets hard
2012-08-28 08:55:18 +00:00
implement permission roles - the backend should be done except for maybe a couple of small tweaks. Now we just need to define the rest of the roles and create a chooser for them. Adam started on this some time back but I don't know where that has gone.
2014-09-18 00:59:46 +00:00
// Save our permissions role so we can perhaps call it up and modify it later.
usability tweaks
2014-09-18 04:52:30 +00:00
if($role_permissions) {
implement permission roles - the backend should be done except for maybe a couple of small tweaks. Now we just need to define the rest of the roles and create a chooser for them. Adam started on this some time back but I don't know where that has gone.
2014-09-18 00:59:46 +00:00
set_pconfig($newuid,'system','permissions_role',$arr['permissions_role']);
usability tweaks
2014-09-18 04:52:30 +00:00
if(array_key_exists('online',$role_permissions))
Typo in regex causes runtime error
2014-09-29 02:30:47 +00:00
set_pconfig($newuid,'system','hide_presence',1-intval($role_permissions['online']));
some minor cleanup of unreported (and as yet undiscovered) issues with permissions toggling. No smoking guns and no obvious issues discovered here. Repeated and tried to duplicate zottell's issue as described without seeing any obvious problems.
2014-11-06 00:21:03 +00:00
if(array_key_exists('perms_auto',$role_permissions))
set_pconfig($newuid,'system','autoperms',(($role_permissions['perms_auto']) ? $role_permissions['perms_accept'] : 0));
usability tweaks
2014-09-18 04:52:30 +00:00
}
implement permission roles - the backend should be done except for maybe a couple of small tweaks. Now we just need to define the rest of the roles and create a chooser for them. Adam started on this some time back but I don't know where that has gone.
2014-09-18 00:59:46 +00:00
usability tweaks
2014-09-18 04:52:30 +00:00
// Create a group with yourself as a member. This allows somebody to use it
we'll need a special system channel (not attached to any account) for directory synchronisation
2013-03-19 00:55:04 +00:00
// right away as a default group for new contacts.
now it gets hard
2012-08-28 08:55:18 +00:00
we'll need a special system channel (not attached to any account) for directory synchronisation
2013-03-19 00:55:04 +00:00
require_once('include/group.php');
group_add($newuid, t('Friends'));
usability tweaks
2014-09-18 04:52:30 +00:00
group_add_member($newuid,t('Friends'),$ret['channel']['channel_hash']);
Whinging whining stupid fucks.
2013-02-12 10:02:35 +00:00
implement permission roles - the backend should be done except for maybe a couple of small tweaks. Now we just need to define the rest of the roles and create a chooser for them. Adam started on this some time back but I don't know where that has gone.
2014-09-18 00:59:46 +00:00
// if our role_permissions indicate that we're using a default collection ACL, add it.
if(is_array($role_permissions) && $role_permissions['default_collection']) {
$r = q("select hash from groups where uid = %d and name = '%s' limit 1",
intval($newuid),
dbesc( t('Friends') )
);
if($r) {
PostgreSQL support initial commit 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)
2014-11-13 20:21:58 +00:00
q("update channel set channel_default_group = '%s', channel_allow_gid = '%s' where channel_id = %d",
private forum issues
2014-10-21 23:33:35 +00:00
dbesc($r[0]['hash']),
implement permission roles - the backend should be done except for maybe a couple of small tweaks. Now we just need to define the rest of the roles and create a chooser for them. Adam started on this some time back but I don't know where that has gone.
2014-09-18 00:59:46 +00:00
dbesc('<' . $r[0]['hash'] . '>'),
intval($newuid)
);
}
}
only auto-follow the site recommendations if creating the first channel for an account.
2014-10-01 22:40:19 +00:00
// auto-follow any of the hub's pre-configured channel choices.
// Only do this if it's the first channel for this account;
// otherwise it could get annoying. Don't make this list too big
// or it will impact registration time.
ability to pre-populate connections for new channels. e.g. "MySpace Tom"
2014-10-01 21:48:08 +00:00
$accts = get_config('system','auto_follow');
only auto-follow the site recommendations if creating the first channel for an account.
2014-10-01 22:40:19 +00:00
if(($accts) && (! $total_identities)) {
several unrelated things - auto_follow wasn't working for new accounts, error returned in private mention to a collection, and added auto-completion to photo tags; though it only matches people so the hover text is now wrong. Also made the photo edit form XHTML (XML) compliant.
2014-10-28 02:21:41 +00:00
require_once('include/follow.php');
ability to pre-populate connections for new channels. e.g. "MySpace Tom"
2014-10-01 21:48:08 +00:00
if(! is_array($accts))
$accts = array($accts);
foreach($accts as $acct) {
if(trim($acct))
new_contact($newuid,trim($acct),$ret['channel'],false);
}
}
implement permission roles - the backend should be done except for maybe a couple of small tweaks. Now we just need to define the rest of the roles and create a chooser for them. Adam started on this some time back but I don't know where that has gone.
2014-09-18 00:59:46 +00:00
we'll need a special system channel (not attached to any account) for directory synchronisation
2013-03-19 00:55:04 +00:00
call_hooks('register_account', $newuid);
proc_run('php','include/directory.php', $ret['channel']['channel_id']);
}
Whinging whining stupid fucks.
2013-02-12 10:02:35 +00:00
basic identity creation
2012-08-24 08:14:42 +00:00
$ret['success'] = true;
return $ret;
back to identity creation form
2012-08-24 03:00:10 +00:00
}
more documentation work
2013-12-04 01:33:48 +00:00
/**
* @function set_default_login_identity($account_id, $channel_id, $force = true)
* Set default channel to be used on login
*
* @param int $account_id
* login account
* @param int $channel_id
* channel id to set as default for this account
* @param boolean force
* if true, set this default unconditionally
* if $force is false only do this if there is no existing default
*
* @returns nil
*/
back to identity creation form
2012-08-24 03:00:10 +00:00
moving a lot of structure around. 'entity' is now 'channel'
2012-09-26 00:57:20 +00:00
function set_default_login_identity($account_id,$channel_id,$force = true) {
$r = q("select account_default_channel from account where account_id = %d limit 1",
a few minor changes
2012-08-27 06:05:00 +00:00
intval($account_id)
);
fix default channel setting after import
2013-07-19 04:35:28 +00:00
if($r) {
if((intval($r[0]['account_default_channel']) == 0) || ($force)) {
PostgreSQL support initial commit 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)
2014-11-13 20:21:58 +00:00
$r = q("update account set account_default_channel = %d where account_id = %d",
fix default channel setting after import
2013-07-19 04:35:28 +00:00
intval($channel_id),
intval($account_id)
);
}
get_item_elements (json version)
2012-07-30 05:43:51 +00:00
}
a few minor changes
2012-08-27 06:05:00 +00:00
}
more documentation work
2013-12-04 01:33:48 +00:00
/**
optionally include wall items (posts) in import/export
2014-09-26 03:21:23 +00:00
* @function identity_basic_export($channel_id,$items = false)
more documentation work
2013-12-04 01:33:48 +00:00
* Create an array representing the important channel information
* which would be necessary to create a nomadic identity clone. This includes
* most channel resources and connection information with the exception of content.
*
* @param int $channel_id
* Channel_id to export
optionally include wall items (posts) in import/export
2014-09-26 03:21:23 +00:00
* @param boolean $items
* Include channel posts (wall items), default false
more documentation work
2013-12-04 01:33:48 +00:00
*
* @returns array
* See function for details
*
*/
channel export with items
2014-09-16 04:31:32 +00:00
function identity_basic_export($channel_id, $items = false) {
provide other ways to export the basic info
2013-01-17 05:34:36 +00:00
/*
* Red basic channel export
*/
$ret = array();
add versioning info to basic identity export, create skeleton function for import
2013-01-19 00:01:14 +00:00
begin to cut the umbilical
2013-04-15 05:24:47 +00:00
$ret['compatibility'] = array('project' => RED_PLATFORM, 'version' => RED_VERSION, 'database' => DB_UPDATE_VERSION);
add versioning info to basic identity export, create skeleton function for import
2013-01-19 00:01:14 +00:00
provide other ways to export the basic info
2013-01-17 05:34:36 +00:00
$r = q("select * from channel where channel_id = %d limit 1",
intval($channel_id)
);
if($r)
$ret['channel'] = $r[0];
$r = q("select * from profile where uid = %d",
intval($channel_id)
);
if($r)
$ret['profile'] = $r;
$xchans = array();
$r = q("select * from abook where abook_channel = %d ",
intval($channel_id)
);
if($r) {
$ret['abook'] = $r;
foreach($r as $rr)
$xchans[] = $rr['abook_xchan'];
stringify_array_elms($xchans);
}
if($xchans) {
$r = q("select * from xchan where xchan_hash in ( " . implode(',',$xchans) . " ) ");
if($r)
$ret['xchan'] = $r;
$r = q("select * from hubloc where hubloc_hash in ( " . implode(',',$xchans) . " ) ");
if($r)
$ret['hubloc'] = $r;
}
remove a couple of mysql reserved words from being used as table or row names. For this round we're getting 'group' and 'desc'. Warning: potentially destabilising as this touches a lot of code.
2013-12-23 02:37:39 +00:00
$r = q("select * from `groups` where uid = %d ",
add groups and personal configs to export/import
2013-02-22 05:18:36 +00:00
intval($channel_id)
);
if($r)
$ret['group'] = $r;
$r = q("select * from group_member where uid = %d ",
intval($channel_id)
);
if($r)
$ret['group_member'] = $r;
$r = q("select * from pconfig where uid = %d",
intval($channel_id)
);
if($r)
$ret['config'] = $r;
dang - this is almost testable. Still have to figure out the best way to deal with the profile photo. Otherwise if you're really brave you could give it a go and see what happens. The worst that could happen is that it destroys the universe. Not a big deal. More likely you could end up with a bunch of imported things that have to be cleaned up. Less likely but entirely possible is that nothing useful will happen at all and it'll white screen.
2013-02-20 03:08:04 +00:00
$r = q("select type, data from photo where scale = 4 and profile = 1 and uid = %d limit 1",
intval($channel_id)
);
if($r) {
$ret['photo'] = array('type' => $r[0]['type'], 'data' => base64url_encode($r[0]['data']));
}
issues with diaspora comment signatures on relayed comments that are relayed through a redmatrix site (parent post is redmatrix) and involve a private post.
2014-10-02 09:43:07 +00:00
// All other term types will be included in items, if requested.
$r = q("select * from term where type in (%d,%d) and uid = %d",
intval(TERM_SAVEDSEARCH),
intval(TERM_THING),
intval($channel_id)
);
if($r)
$ret['term'] = $r;
some background work for import/export of things and liked things/profiles
2014-09-27 07:14:35 +00:00
$r = q("select * from obj where obj_channel = %d",
intval($channel_id)
);
if($r)
$ret['obj'] = $r;
channel export with items
2014-09-16 04:31:32 +00:00
if(! $items)
return $ret;
some background work for import/export of things and liked things/profiles
2014-09-27 07:14:35 +00:00
$r = q("select likes.*, item.mid from likes left join item on likes.iid = item.id where likes.channel_id = %d",
intval($channel_id)
);
if($r)
$ret['likes'] = $r;
optionally include wall items (posts) in import/export
2014-09-26 03:21:23 +00:00
$r = q("select item_id.*, item.mid from item_id left join item on item_id.iid = item.id where item_id.uid = %d",
channel export with items
2014-09-16 04:31:32 +00:00
intval($channel_id)
);
if($r)
$ret['item_id'] = $r;
$key = get_config('system','prvkey');
dang - this is almost testable. Still have to figure out the best way to deal with the profile photo. Otherwise if you're really brave you could give it a go and see what happens. The worst that could happen is that it destroys the universe. Not a big deal. More likely you could end up with a bunch of imported things that have to be cleaned up. Less likely but entirely possible is that nothing useful will happen at all and it'll white screen.
2013-02-20 03:08:04 +00:00
channel export with items
2014-09-16 04:31:32 +00:00
// warning: this may run into memory limits on smaller systems
PostgreSQL support initial commit 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)
2014-11-13 20:21:58 +00:00
$r = q("select * from item where (item_flags & %d)>0 and not (item_restrict & %d)>0 and uid = %d",
channel export with items
2014-09-16 04:31:32 +00:00
intval(ITEM_WALL),
intval(ITEM_DELETED),
intval($channel_id)
);
if($r) {
use the more portable encoded_item format for exported items - but with added attributes so we can use it as a reasonably complete item backup. The encoded_item format gives us extended author and owner information in case we need to probe them to bring the entry back. It also contains taxonomy entries. Importing and/or recovering will best be accomplished in chunks. It could take some time and some memory to chew through this.
2014-09-16 10:33:48 +00:00
$ret['item'] = array();
xchan_query($r);
$r = fetch_post_tags($r,true);
foreach($r as $rr)
$ret['item'][] = encode_item($rr,true);
channel export with items
2014-09-16 04:31:32 +00:00
}
provide other ways to export the basic info
2013-01-17 05:34:36 +00:00
return $ret;
channel export with items
2014-09-16 04:31:32 +00:00
provide other ways to export the basic info
2013-01-17 05:34:36 +00:00
}
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
/**
*
more documentation work
2013-12-04 01:33:48 +00:00
* @function : profile_load(&$a, $nickname, $profile)
* Generate
* @param App $a
* @param string $nickname
* @param string $profile
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
*
more documentation work
2013-12-04 01:33:48 +00:00
* Summary: Loads a profile into the App structure.
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
* The function requires a writeable copy of the main App structure, and the nickname
more documentation work
2013-12-04 01:33:48 +00:00
* of a valid channel.
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
*
more documentation work
2013-12-04 01:33:48 +00:00
* Permissions of the current observer are checked. If a restricted profile is available
* to the current observer, that will be loaded instead of the channel default profile.
*
* The channel owner can set $profile to a valid profile_guid to preview that profile.
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
*
more documentation work
2013-12-04 01:33:48 +00:00
* The channel default theme is also selected for use, unless over-riden elsewhere.
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
*
*/
function profile_load(&$a, $nickname, $profile = '') {
logger('profile_load: ' . $nickname . (($profile) ? ' profile: ' . $profile : ''));
$user = q("select channel_id from channel where channel_address = '%s' limit 1",
dbesc($nickname)
);
if(! $user) {
logger('profile error: ' . $a->query_string, LOGGER_DEBUG);
notice( t('Requested channel is not available.') . EOL );
$a->error = 404;
return;
}
// get the current observer
$observer = $a->get_observer();
set theme for un-viewable profile
2014-02-24 22:19:21 +00:00
$can_view_profile = true;
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
// Can the observer see our profile?
require_once('include/permissions.php');
if(! perm_is_allowed($user[0]['channel_id'],$observer['xchan_hash'],'view_profile')) {
set theme for un-viewable profile
2014-02-24 22:19:21 +00:00
$can_view_profile = false;
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
}
if(! $profile) {
$r = q("SELECT abook_profile FROM abook WHERE abook_xchan = '%s' and abook_channel = '%d' limit 1",
dbesc($observer['xchan_hash']),
intval($user[0]['channel_id'])
);
if($r)
$profile = $r[0]['abook_profile'];
}
set theme for un-viewable profile
2014-02-24 22:19:21 +00:00
$p = null;
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
if($profile) {
set theme for un-viewable profile
2014-02-24 22:19:21 +00:00
$p = q("SELECT profile.uid AS profile_uid, profile.*, channel.* FROM profile
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
LEFT JOIN channel ON profile.uid = channel.channel_id
WHERE channel.channel_address = '%s' AND profile.profile_guid = '%s' LIMIT 1",
dbesc($nickname),
dbesc($profile)
);
}
set theme for un-viewable profile
2014-02-24 22:19:21 +00:00
if(! $p) {
take a p
2014-02-24 23:07:00 +00:00
$p = q("SELECT profile.uid AS profile_uid, profile.*, channel.* FROM profile
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
LEFT JOIN channel ON profile.uid = channel.channel_id
PostgreSQL support initial commit 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)
2014-11-13 20:21:58 +00:00
WHERE channel.channel_address = '%s' and not ( channel_pageflags & %d )>0
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
AND profile.is_default = 1 LIMIT 1",
dbesc($nickname),
intval(PAGE_REMOVED)
);
}
photo timestamp was missing from main profile photo url which prevents photo changes from being immediately seen there.
2014-03-31 22:04:56 +00:00
set theme for un-viewable profile
2014-02-24 22:19:21 +00:00
if(! $p) {
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
logger('profile error: ' . $a->query_string, LOGGER_DEBUG);
notice( t('Requested profile is not available.') . EOL );
$a->error = 404;
return;
}
photo timestamp was missing from main profile photo url which prevents photo changes from being immediately seen there.
2014-03-31 22:04:56 +00:00
some work on extended profile fields
2014-08-14 05:22:52 +00:00
$q = q("select * from profext where hash = '%s' and channel_id = %d",
dbesc($p[0]['profile_guid']),
intval($p[0]['profile_uid'])
);
if($q) {
$extra_fields = array();
require_once('include/identity.php');
$profile_fields_basic = get_profile_fields_basic();
$profile_fields_advanced = get_profile_fields_advanced();
$advanced = ((feature_enabled(local_user(),'advanced_profiles')) ? true : false);
if($advanced)
$fields = $profile_fields_advanced;
else
$fields = $profile_fields_basic;
foreach($q as $qq) {
foreach($fields as $k => $f) {
if($k == $qq['k']) {
$p[0][$k] = $qq['v'];
$extra_fields[] = $k;
break;
}
}
}
}
$p[0]['extra_fields'] = $extra_fields;
photo timestamp was missing from main profile photo url which prevents photo changes from being immediately seen there.
2014-03-31 22:04:56 +00:00
$z = q("select xchan_photo_date from xchan where xchan_hash = '%s' limit 1",
dbesc($p[0]['channel_hash'])
);
if($z)
$p[0]['picdate'] = $z[0]['xchan_photo_date'];
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
// fetch user tags if this isn't the default profile
set theme for un-viewable profile
2014-02-24 22:19:21 +00:00
if(! $p[0]['is_default']) {
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
$x = q("select `keywords` from `profile` where uid = %d and `is_default` = 1 limit 1",
intval($profile_uid)
);
set theme for un-viewable profile
2014-02-24 22:19:21 +00:00
if($x && $can_view_profile)
$p[0]['keywords'] = $x[0]['keywords'];
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
}
set theme for un-viewable profile
2014-02-24 22:19:21 +00:00
if($p[0]['keywords']) {
$keywords = str_replace(array('#',',',' ',',,'),array('',' ',',',','),$p[0]['keywords']);
if(strlen($keywords) && $can_view_profile)
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
$a->page['htmlhead'] .= '<meta name="keywords" content="' . htmlentities($keywords,ENT_COMPAT,'UTF-8') . '" />' . "\r\n" ;
}
Better handling of restricted /channel and /profile permissions. We will show the name, profile photo and a 'connect' button if appropriate on these pages regardless of permissions. A blank page makes it difficult for folks to figure out how to connect and if it is their real life friend 'x' or not. It also matches our overall policy (adopted from Facebook's lessons learned) that the channel name and default profile photo are always visible and can't really be blocked without messing up the usability of the entire network. This also makes sure that a connect button can be found somewhere besides the directory - where the entry could be blocked; and avoid somebody having to figure out the webbie and find the link to "follow" (another related issue).
2014-04-14 23:45:16 +00:00
$a->profile = $p[0];
$a->profile_uid = $p[0]['profile_uid'];
$a->page['title'] = $a->profile['channel_name'] . " - " . $a->profile['channel_address'] . "@" . $a->get_hostname();
$a->profile['permission_to_view'] = $can_view_profile;
set theme for un-viewable profile
2014-02-24 22:19:21 +00:00
if($can_view_profile) {
$online = get_online_status($nickname);
$a->profile['online_status'] = $online['result'];
online indication on profile sidebar
2014-01-29 01:07:25 +00:00
set theme for un-viewable profile
2014-02-24 22:19:21 +00:00
}
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
set theme for un-viewable profile
2014-02-24 22:19:21 +00:00
if(local_user()) {
$a->profile['channel_mobile_theme'] = get_pconfig(local_user(),'system', 'mobile_theme');
$_SESSION['mobile_theme'] = $a->profile['channel_mobile_theme'];
}
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
/**
* load/reload current theme info
*/
set theme for un-viewable profile
2014-02-24 22:19:21 +00:00
$_SESSION['theme'] = $p[0]['channel_theme'];
Better handling of restricted /channel and /profile permissions. We will show the name, profile photo and a 'connect' button if appropriate on these pages regardless of permissions. A blank page makes it difficult for folks to figure out how to connect and if it is their real life friend 'x' or not. It also matches our overall policy (adopted from Facebook's lessons learned) that the channel name and default profile photo are always visible and can't really be blocked without messing up the usability of the entire network. This also makes sure that a connect button can be found somewhere besides the directory - where the entry could be blocked; and avoid somebody having to figure out the webbie and find the link to "follow" (another related issue).
2014-04-14 23:45:16 +00:00
// $a->set_template_engine(); // reset the template engine to the default in case the user's theme doesn't specify one
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
Better handling of restricted /channel and /profile permissions. We will show the name, profile photo and a 'connect' button if appropriate on these pages regardless of permissions. A blank page makes it difficult for folks to figure out how to connect and if it is their real life friend 'x' or not. It also matches our overall policy (adopted from Facebook's lessons learned) that the channel name and default profile photo are always visible and can't really be blocked without messing up the usability of the entire network. This also makes sure that a connect button can be found somewhere besides the directory - where the entry could be blocked; and avoid somebody having to figure out the webbie and find the link to "follow" (another related issue).
2014-04-14 23:45:16 +00:00
// $theme_info_file = "view/theme/".current_theme()."/php/theme.php";
// if (file_exists($theme_info_file)){
// require_once($theme_info_file);
// }
set theme for un-viewable profile
2014-02-24 22:19:21 +00:00
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
return;
}
function profile_create_sidebar(&$a,$connect = true) {
$block = (((get_config('system','block_public')) && (! local_user()) && (! remote_user())) ? true : false);
$a->set_widget('profile',profile_sidebar($a->profile, $block, $connect));
return;
}
/**
*
* Function: profile_sidebar
*
* Formats a profile for display in the sidebar.
* It is very difficult to templatise the HTML completely
* because of all the conditional logic.
*
* @parameter: array $profile
*
* Returns HTML string stuitable for sidebar inclusion
* Exceptions: Returns empty string if passed $profile is wrong type or not populated
*
*/
function profile_sidebar($profile, $block = 0, $show_connect = true) {
$a = get_app();
$observer = $a->get_observer();
$o = '';
$location = false;
$address = false;
$pdesc = true;
if((! is_array($profile)) && (! count($profile)))
return $o;
head_set_icon($profile['thumb']);
$is_owner = (($profile['uid'] == local_user()) ? true : false);
$profile['picdate'] = urlencode($profile['picdate']);
call_hooks('profile_sidebar_enter', $profile);
require_once('include/Contact.php');
if($show_connect) {
// This will return an empty string if we're already connected.
$connect_url = rconnect_url($profile['uid'],get_observer_hash());
$connect = (($connect_url) ? t('Connect') : '');
if($connect_url)
$connect_url = sprintf($connect_url,urlencode($profile['channel_address'] . '@' . $a->get_hostname()));
// premium channel - over-ride
if($profile['channel_pageflags'] & PAGE_PREMIUM)
$connect_url = z_root() . '/connect/' . $profile['channel_address'];
}
// show edit profile to yourself
if($is_owner) {
$profile['menu'] = array(
'chg_photo' => t('Change profile photo'),
'entries' => array(),
);
if(feature_enabled(local_user(),'multi_profiles')) {
$profile['edit'] = array($a->get_baseurl(). '/profiles', t('Profiles'),"", t('Manage/edit profiles'));
$profile['menu']['cr_new'] = t('Create New Profile');
}
else
$profile['edit'] = array($a->get_baseurl() . '/profiles/' . $profile['id'], t('Edit Profile'),'',t('Edit Profile'));
$r = q("SELECT * FROM `profile` WHERE `uid` = %d",
local_user());
if($r) {
foreach($r as $rr) {
$profile['menu']['entries'][] = array(
'photo' => $rr['thumb'],
'id' => $rr['id'],
'alt' => t('Profile Image'),
'profile_name' => $rr['profile_name'],
'isdefault' => $rr['is_default'],
'visible_to_everybody' => t('visible to everybody'),
'edit_visibility' => t('Edit visibility'),
);
}
}
}
comanchify all the simple cases - those that only load a profile. Rework permission checks for the profile sidebar so that it is all done internally. Remove crepair which we aren't using.
2013-12-11 22:54:36 +00:00
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
if((x($profile,'address') == 1)
|| (x($profile,'locality') == 1)
|| (x($profile,'region') == 1)
|| (x($profile,'postal_code') == 1)
|| (x($profile,'country_name') == 1))
$location = t('Location:');
issue #683 - don't linkify homepage field without validating
2014-11-11 03:20:23 +00:00
$profile['homepage'] = linkify($profile['homepage']);
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
$gender = ((x($profile,'gender') == 1) ? t('Gender:') : False);
$marital = ((x($profile,'marital') == 1) ? t('Status:') : False);
$homepage = ((x($profile,'homepage') == 1) ? t('Homepage:') : False);
online indication on profile sidebar
2014-01-29 01:07:25 +00:00
$profile['online'] = (($profile['online_status'] === 'online') ? t('Online Now') : False);
logger('online: ' . $profile['online']);
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
comanchify all the simple cases - those that only load a profile. Rework permission checks for the profile sidebar so that it is all done internally. Remove crepair which we aren't using.
2013-12-11 22:54:36 +00:00
if(! perm_is_allowed($profile['uid'],((is_array($observer)) ? $observer['xchan_hash'] : ''),'view_profile')) {
$block = true;
}
Better handling of restricted /channel and /profile permissions. We will show the name, profile photo and a 'connect' button if appropriate on these pages regardless of permissions. A blank page makes it difficult for folks to figure out how to connect and if it is their real life friend 'x' or not. It also matches our overall policy (adopted from Facebook's lessons learned) that the channel name and default profile photo are always visible and can't really be blocked without messing up the usability of the entire network. This also makes sure that a connect button can be found somewhere besides the directory - where the entry could be blocked; and avoid somebody having to figure out the webbie and find the link to "follow" (another related issue).
2014-04-14 23:45:16 +00:00
if(($profile['hidewall'] && (! local_user()) && (! remote_user())) || $block ) {
online indication on profile sidebar
2014-01-29 01:07:25 +00:00
$location = $pdesc = $gender = $marital = $homepage = $online = False;
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
}
the rest of the diaspora local discovery stuff
2014-08-22 03:31:55 +00:00
$firstname = ((strpos($profile['channel_name'],' '))
? trim(substr($profile['channel_name'],0,strpos($profile['channel_name'],' '))) : $profile['channel_name']);
$lastname = (($firstname === $profile['channel_name']) ? '' : trim(substr($profile['channel_name'],strlen($firstname))));
store diaspora meta info in the item table. It has to go there or it will kill us with complex joins. We can phase out the sign table once this all checks out.
2014-09-03 12:09:43 +00:00
$diaspora = array(
'podloc' => z_root(),
'searchable' => (($block) ? 'false' : 'true'),
'nickname' => $profile['channel_address'],
'fullname' => $profile['channel_name'],
'firstname' => $firstname,
'lastname' => $lastname,
'photo300' => z_root() . '/photo/profile/300/' . $profile['uid'] . '.jpg',
'photo100' => z_root() . '/photo/profile/100/' . $profile['uid'] . '.jpg',
'photo50' => z_root() . '/photo/profile/50/' . $profile['uid'] . '.jpg',
);
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
contact_block() not being shown to unauthenticated visitors - even if perms allow. Also separate the permissions logic for this function so that we can have a mini-profile widget and a separate contact_block widget instead of always lumping them together. We probably also should move contact_block() outside of include/text.php as it doesn't really belong there. Just not sure where it belongs - perhaps contact_widgets wouold be a good place.
2014-03-14 00:13:36 +00:00
$contact_block = contact_block();
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
$channel_menu = false;
$menu = get_pconfig($profile['uid'],'system','channel_menu');
Better handling of restricted /channel and /profile permissions. We will show the name, profile photo and a 'connect' button if appropriate on these pages regardless of permissions. A blank page makes it difficult for folks to figure out how to connect and if it is their real life friend 'x' or not. It also matches our overall policy (adopted from Facebook's lessons learned) that the channel name and default profile photo are always visible and can't really be blocked without messing up the usability of the entire network. This also makes sure that a connect button can be found somewhere besides the directory - where the entry could be blocked; and avoid somebody having to figure out the webbie and find the link to "follow" (another related issue).
2014-04-14 23:45:16 +00:00
if($menu && ! $block) {
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
require_once('include/menu.php');
$m = menu_fetch($menu,$profile['uid'],$observer['xchan_hash']);
if($m)
$channel_menu = menu_render($m);
}
$menublock = get_pconfig($profile['uid'],'system','channel_menublock');
comanchify all the simple cases - those that only load a profile. Rework permission checks for the profile sidebar so that it is all done internally. Remove crepair which we aren't using.
2013-12-11 22:54:36 +00:00
if ($menublock && (! $block)) {
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
require_once('include/comanche.php');
$channel_menu .= comanche_block($menublock);
}
$tpl = get_markup_template('profile_vcard.tpl');
$o .= replace_macros($tpl, array(
'$profile' => $profile,
'$connect' => $connect,
'$connect_url' => $connect_url,
'$location' => $location,
'$gender' => $gender,
'$pdesc' => $pdesc,
'$marital' => $marital,
'$homepage' => $homepage,
'$chanmenu' => $channel_menu,
the rest of the diaspora local discovery stuff
2014-08-22 03:31:55 +00:00
'$diaspora' => $diaspora,
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
'$contact_block' => $contact_block,
));
$arr = array('profile' => &$profile, 'entry' => &$o);
call_hooks('profile_sidebar', $arr);
return $o;
}
// FIXME or remove
function get_birthdays() {
$a = get_app();
$o = '';
if(! local_user())
return $o;
$bd_format = t('g A l F d') ; // 8 AM Friday January 18
$bd_short = t('F d');
$r = q("SELECT `event`.*, `event`.`id` AS `eid`, `contact`.* FROM `event`
LEFT JOIN `contact` ON `contact`.`id` = `event`.`cid`
WHERE `event`.`uid` = %d AND `type` = 'birthday' AND `start` < '%s' AND `finish` > '%s'
ORDER BY `start` ASC ",
intval(local_user()),
dbesc(datetime_convert('UTC','UTC','now + 6 days')),
dbesc(datetime_convert('UTC','UTC','now'))
);
if($r && count($r)) {
$total = 0;
$now = strtotime('now');
$cids = array();
$istoday = false;
foreach($r as $rr) {
if(strlen($rr['name']))
$total ++;
if((strtotime($rr['start'] . ' +00:00') < $now) && (strtotime($rr['finish'] . ' +00:00') > $now))
$istoday = true;
}
$classtoday = $istoday ? ' birthday-today ' : '';
if($total) {
foreach($r as &$rr) {
if(! strlen($rr['name']))
continue;
// avoid duplicates
if(in_array($rr['cid'],$cids))
continue;
$cids[] = $rr['cid'];
$today = (((strtotime($rr['start'] . ' +00:00') < $now) && (strtotime($rr['finish'] . ' +00:00') > $now)) ? true : false);
$sparkle = '';
$url = $rr['url'];
if($rr['network'] === NETWORK_DFRN) {
$sparkle = " sparkle";
$url = $a->get_baseurl() . '/redir/' . $rr['cid'];
}
$rr['link'] = $url;
$rr['title'] = $rr['name'];
$rr['date'] = day_translate(datetime_convert('UTC', $a->timezone, $rr['start'], $rr['adjust'] ? $bd_format : $bd_short)) . (($today) ? ' ' . t('[today]') : '');
$rr['startime'] = Null;
$rr['today'] = $today;
}
}
}
$tpl = get_markup_template("birthdays_reminder.tpl");
return replace_macros($tpl, array(
'$baseurl' => $a->get_baseurl(),
'$classtoday' => $classtoday,
'$count' => $total,
'$event_reminders' => t('Birthday Reminders'),
'$event_title' => t('Birthdays this week:'),
'$events' => $r,
'$lbr' => '{', // raw brackets mess up if/endif macro processing
'$rbr' => '}'
));
}
// FIXME
function get_events() {
Ooops, replaced too many
2014-04-11 23:11:43 +00:00
require_once('include/bbcode.php');
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
$a = get_app();
if(! local_user())
return $o;
$bd_format = t('g A l F d') ; // 8 AM Friday January 18
$bd_short = t('F d');
$r = q("SELECT `event`.* FROM `event`
WHERE `event`.`uid` = %d AND `type` != 'birthday' AND `start` < '%s' AND `start` > '%s'
ORDER BY `start` ASC ",
intval(local_user()),
dbesc(datetime_convert('UTC','UTC','now + 6 days')),
dbesc(datetime_convert('UTC','UTC','now - 1 days'))
);
if($r && count($r)) {
$now = strtotime('now');
$istoday = false;
foreach($r as $rr) {
if(strlen($rr['name']))
$total ++;
$strt = datetime_convert('UTC',$rr['convert'] ? $a->timezone : 'UTC',$rr['start'],'Y-m-d');
if($strt === datetime_convert('UTC',$a->timezone,'now','Y-m-d'))
$istoday = true;
}
$classtoday = (($istoday) ? 'event-today' : '');
foreach($r as &$rr) {
if($rr['adjust'])
$md = datetime_convert('UTC',$a->timezone,$rr['start'],'Y/m');
else
$md = datetime_convert('UTC','UTC',$rr['start'],'Y/m');
$md .= "/#link-".$rr['id'];
Ooops, replaced too many
2014-04-11 23:11:43 +00:00
$title = substr(strip_tags(bbcode($rr['desc'])),0,32) . '... ';
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
if(! $title)
$title = t('[No description]');
$strt = datetime_convert('UTC',$rr['convert'] ? $a->timezone : 'UTC',$rr['start']);
$today = ((substr($strt,0,10) === datetime_convert('UTC',$a->timezone,'now','Y-m-d')) ? true : false);
$rr['link'] = $md;
$rr['title'] = $title;
$rr['date'] = day_translate(datetime_convert('UTC', $rr['adjust'] ? $a->timezone : 'UTC', $rr['start'], $bd_format)) . (($today) ? ' ' . t('[today]') : '');
$rr['startime'] = $strt;
$rr['today'] = $today;
}
}
$tpl = get_markup_template("events_reminder.tpl");
return replace_macros($tpl, array(
'$baseurl' => $a->get_baseurl(),
'$classtoday' => $classtoday,
'$count' => count($r),
'$event_reminders' => t('Event Reminders'),
'$event_title' => t('Events this week:'),
'$events' => $r,
));
}
function advanced_profile(&$a) {
Show tags in other channels profile field to make it easier to navigate to the channels
2014-12-07 15:17:45 +00:00
require_once('include/text.php');
cleanup and Comanchification of mod_profile
2013-12-11 07:27:17 +00:00
if(! perm_is_allowed($a->profile['profile_uid'],get_observer_hash(),'view_profile'))
return '';
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
$o = '';
$o .= '<h2>' . t('Profile') . '</h2>';
if($a->profile['name']) {
$tpl = get_markup_template('profile_advanced.tpl');
$profile = array();
$profile['fullname'] = array( t('Full Name:'), $a->profile['name'] ) ;
if($a->profile['gender']) $profile['gender'] = array( t('Gender:'), $a->profile['gender'] );
profile likes
2014-06-23 05:16:26 +00:00
$ob_hash = get_observer_hash();
correct the permissions on profile page
2014-07-18 05:07:23 +00:00
if($ob_hash && perm_is_allowed($a->profile['profile_uid'],$ob_hash,'post_like')) {
profile likes
2014-06-23 05:16:26 +00:00
$profile['canlike'] = true;
$profile['likethis'] = t('Like this channel');
$profile['profile_guid'] = $a->profile['profile_guid'];
}
$likers = q("select liker, xchan.* from likes left join xchan on liker = xchan_hash where channel_id = %d and target_type = '%s' and verb = '%s'",
intval($a->profile['profile_uid']),
dbesc(ACTIVITY_OBJ_PROFILE),
dbesc(ACTIVITY_LIKE)
);
$profile['likers'] = array();
$profile['like_count'] = count($likers);
$profile['like_button_label'] = tt('Like','Likes',$profile['like_count'],'noun');
if($likers) {
foreach($likers as $l)
$profile['likers'][] = array('name' => $l['xchan_name'],'url' => zid($l['xchan_url']));
}
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
if(($a->profile['dob']) && ($a->profile['dob'] != '0000-00-00')) {
allow birthdays with just a year (no month or day).
2014-05-02 01:40:00 +00:00
$val = '';
if((substr($a->profile['dob'],5,2) === '00') || (substr($a->profile['dob'],8,2) === '00'))
$val = substr($a->profile['dob'],0,4);
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
$year_bd_format = t('j F, Y');
$short_bd_format = t('j F');
allow birthdays with just a year (no month or day).
2014-05-02 01:40:00 +00:00
if(! $val) {
$val = ((intval($a->profile['dob']))
? day_translate(datetime_convert('UTC','UTC',$a->profile['dob'] . ' 00:00 +00:00',$year_bd_format))
: day_translate(datetime_convert('UTC','UTC','2001-' . substr($a->profile['dob'],5) . ' 00:00 +00:00',$short_bd_format)));
}
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
$profile['birthday'] = array( t('Birthday:'), $val);
}
if($age = age($a->profile['dob'],$a->profile['timezone'],'')) $profile['age'] = array( t('Age:'), $age );
if($a->profile['marital']) $profile['marital'] = array( t('Status:'), $a->profile['marital']);
Bring BBCode to profiles
2014-04-11 13:54:07 +00:00
if($a->profile['with']) $profile['marital']['with'] = bbcode($a->profile['with']);
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
This is long overdue - use a symblic constant NULL_DATE instead of the easily mis-typed sequence '0000-00-00 00:00:00'
2014-09-09 03:35:15 +00:00
if(strlen($a->profile['howlong']) && $a->profile['howlong'] !== NULL_DATE) {
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
$profile['howlong'] = relative_date($a->profile['howlong'], t('for %1$d %2$s'));
}
if($a->profile['sexual']) $profile['sexual'] = array( t('Sexual Preference:'), $a->profile['sexual'] );
if($a->profile['homepage']) $profile['homepage'] = array( t('Homepage:'), linkify($a->profile['homepage']) );
if($a->profile['hometown']) $profile['hometown'] = array( t('Hometown:'), linkify($a->profile['hometown']) );
if($a->profile['keywords']) $profile['keywords'] = array( t('Tags:'), $a->profile['keywords']);
if($a->profile['politic']) $profile['politic'] = array( t('Political Views:'), $a->profile['politic']);
if($a->profile['religion']) $profile['religion'] = array( t('Religion:'), $a->profile['religion']);
Revert to prepare_text, use bbcode only for with
2014-04-11 23:08:50 +00:00
if($txt = prepare_text($a->profile['about'])) $profile['about'] = array( t('About:'), $txt );
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
Revert to prepare_text, use bbcode only for with
2014-04-11 23:08:50 +00:00
if($txt = prepare_text($a->profile['interest'])) $profile['interest'] = array( t('Hobbies/Interests:'), $txt);
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
Revert to prepare_text, use bbcode only for with
2014-04-11 23:08:50 +00:00
if($txt = prepare_text($a->profile['likes'])) $profile['likes'] = array( t('Likes:'), $txt);
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
Revert to prepare_text, use bbcode only for with
2014-04-11 23:08:50 +00:00
if($txt = prepare_text($a->profile['dislikes'])) $profile['dislikes'] = array( t('Dislikes:'), $txt);
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
Revert to prepare_text, use bbcode only for with
2014-04-11 23:08:50 +00:00
if($txt = prepare_text($a->profile['contact'])) $profile['contact'] = array( t('Contact information and Social Networks:'), $txt);
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
Show tags in other channels profile field to make it easier to navigate to the channels
2014-12-07 15:17:45 +00:00
// Support tags in the other channels field (probably want to restrict it to channels only?)
$txt = $a->profile['channels'];
$matches = get_tags($txt);
$access_tag = '';
$str_tags = '';
foreach($matches as $m) {
$success = handle_tag($a, $txt, $access_tag, $str_tags, $a->profile_uid, $m); // Use uid of the profile maker
}
if($txt = prepare_text($txt)) {
$profile['channels'] = array( t('My other channels:'), $txt);
}
Missed these from git add...a year ago
2014-01-17 23:30:33 +00:00
Revert to prepare_text, use bbcode only for with
2014-04-11 23:08:50 +00:00
if($txt = prepare_text($a->profile['music'])) $profile['music'] = array( t('Musical interests:'), $txt);
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
Revert to prepare_text, use bbcode only for with
2014-04-11 23:08:50 +00:00
if($txt = prepare_text($a->profile['book'])) $profile['book'] = array( t('Books, literature:'), $txt);
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
Revert to prepare_text, use bbcode only for with
2014-04-11 23:08:50 +00:00
if($txt = prepare_text($a->profile['tv'])) $profile['tv'] = array( t('Television:'), $txt);
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
Revert to prepare_text, use bbcode only for with
2014-04-11 23:08:50 +00:00
if($txt = prepare_text($a->profile['film'])) $profile['film'] = array( t('Film/dance/culture/entertainment:'), $txt);
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
Revert to prepare_text, use bbcode only for with
2014-04-11 23:08:50 +00:00
if($txt = prepare_text($a->profile['romance'])) $profile['romance'] = array( t('Love/Romance:'), $txt);
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
Revert to prepare_text, use bbcode only for with
2014-04-11 23:08:50 +00:00
if($txt = prepare_text($a->profile['work'])) $profile['work'] = array( t('Work/employment:'), $txt);
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
Revert to prepare_text, use bbcode only for with
2014-04-11 23:08:50 +00:00
if($txt = prepare_text($a->profile['education'])) $profile['education'] = array( t('School/education:'), $txt );
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
some work on extended profile fields
2014-08-14 05:22:52 +00:00
if($a->profile['extra_fields']) {
foreach($a->profile['extra_fields'] as $f) {
$x = q("select * from profdef where field_name = '%s' limit 1",
dbesc($f)
);
if($x && $txt = prepare_text($a->profile[$f]))
$profile[$f] = array( $x[0]['field_desc'] . ':',$txt);
}
$profile['extra_fields'] = $a->profile['extra_fields'];
}
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
a bit more backend work on things
2013-12-29 01:04:23 +00:00
$things = get_things($a->profile['profile_guid'],$a->profile['profile_uid']);
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
ability to like things
2014-06-23 12:19:28 +00:00
// logger('mod_profile: things: ' . print_r($things,true), LOGGER_DATA);
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
return replace_macros($tpl, array(
'$title' => t('Profile'),
ability to like things
2014-06-23 12:19:28 +00:00
'$canlike' => (($profile['canlike'])? true : false),
'$likethis' => t('Like this thing'),
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
'$profile' => $profile,
a bit more backend work on things
2013-12-29 01:04:23 +00:00
'$things' => $things
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
));
}
return '';
}
function get_my_url() {
if(x($_SESSION,'zrl_override'))
return $_SESSION['zrl_override'];
undo
2014-03-04 23:29:27 +00:00
if(x($_SESSION,'my_url'))
return $_SESSION['my_url'];
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
return false;
}
function get_my_address() {
if(x($_SESSION,'zid_override'))
return $_SESSION['zid_override'];
if(x($_SESSION,'my_address'))
return $_SESSION['my_address'];
return false;
}
/**
* @function zid_init(&$a)
* If somebody arrives at our site using a zid, add their xchan to our DB if we don't have it already.
* And if they aren't already authenticated here, attempt reverse magic auth.
*
* @hooks 'zid_init'
* string 'zid' - their zid
* string 'url' - the destination url
*
*/
function zid_init(&$a) {
$tmp_str = get_my_address();
if(validate_email($tmp_str)) {
proc_run('php','include/gprobe.php',bin2hex($tmp_str));
$arr = array('zid' => $tmp_str, 'url' => $a->cmd);
The scenario is that you're authenticated via magic-auth on a remote hub and you change channels locally. Next time you start an auth exchange we'll look to see if your identity changed and we should start fresh if that's the case, rather than just falling through and keeping the old credentials.
2014-02-10 23:39:19 +00:00
call_hooks('zid_init',$arr);
if(! local_user()) {
prevent zid's from reaching the DAV core code.
2014-01-16 09:19:58 +00:00
$r = q("select * from hubloc where hubloc_addr = '%s' order by hubloc_connected desc limit 1",
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
dbesc($tmp_str)
);
The scenario is that you're authenticated via magic-auth on a remote hub and you change channels locally. Next time you start an auth exchange we'll look to see if your identity changed and we should start fresh if that's the case, rather than just falling through and keeping the old credentials.
2014-02-10 23:39:19 +00:00
if($r && remote_user() && remote_user() === $r[0]['hubloc_hash'])
return;
logger('zid_init: not authenticated. Invoking reverse magic-auth for ' . $tmp_str);
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
// try to avoid recursion - but send them home to do a proper magic auth
fix the fix (can't work on query if it hasn't been added to $dest yet)
2014-01-10 08:21:36 +00:00
$query = $a->query_string;
$query = str_replace(array('?zid=','&zid='),array('?rzid=','&rzid='),$query);
$dest = '/' . urlencode($query);
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
if($r && ($r[0]['hubloc_url'] != z_root()) && (! strstr($dest,'/magic')) && (! strstr($dest,'/rmagic'))) {
goaway($r[0]['hubloc_url'] . '/magic' . '?f=&rev=1&dest=' . z_root() . $dest);
}
else
logger('zid_init: no hubloc found.');
}
}
}
/**
* @function zid($s,$address = '')
* Adds a zid parameter to a url
* @param string $s
* The url to accept the zid
* @param boolean $address
* $address to use instead of session environment
* @return string
*
* @hooks 'zid'
* string url - url to accept zid
* string zid - urlencoded zid
* string result - the return string we calculated, change it if you want to return something else
*/
function zid($s,$address = '') {
if(! strlen($s) || strpos($s,'zid='))
return $s;
$has_params = ((strpos($s,'?')) ? true : false);
$num_slashes = substr_count($s,'/');
if(! $has_params)
$has_params = ((strpos($s,'&')) ? true : false);
$achar = strpos($s,'?') ? '&' : '?';
$mine = get_my_url();
$myaddr = (($address) ? $address : get_my_address());
// FIXME checking against our own channel url is no longer reliable. We may have a lot
// of urls attached to out channel. Should probably match against our site, since we
// will not need to remote authenticate on our own site anyway.
if($mine && $myaddr && (! link_compare($mine,$s)))
$zurl = $s . (($num_slashes >= 3) ? '' : '/') . $achar . 'zid=' . urlencode($myaddr);
else
$zurl = $s;
$arr = array('url' => $s, 'zid' => urlencode($myaddr), 'result' => $zurl);
call_hooks('zid', $arr);
return $arr['result'];
}
// Used from within PCSS themes to set theme parameters. If there's a
// puid request variable, that is the "page owner" and normally their theme
// settings take precedence; unless a local user sets the "always_my_theme"
// system pconfig, which means they don't want to see anybody else's theme
// settings except their own while on this site.
function get_theme_uid() {
$uid = (($_REQUEST['puid']) ? intval($_REQUEST['puid']) : 0);
if(local_user()) {
if((get_pconfig(local_user(),'system','always_my_theme')) || (! $uid))
return local_user();
}
get_theme_uid() - if no uid, look for a system channel and use that. This allows default theme/scheme tweaks at the server level.
2014-02-18 04:38:30 +00:00
if(! $uid) {
$x = get_sys_channel();
if($x)
return $x['channel_id'];
}
reorganise a few included functions - notably identity related functions
2013-12-03 23:35:13 +00:00
return $uid;
}
Must have broken that in a merge - put it back
2013-12-22 21:13:24 +00:00
/**
* @function get_default_profile_photo($size = 175)
Style
2013-12-22 21:15:13 +00:00
* Retrieves the path of the default_profile_photo for this system
* with the specified size.
Must have broken that in a merge - put it back
2013-12-22 21:13:24 +00:00
* @param int $size
Style
2013-12-22 21:15:13 +00:00
* one of (175, 80, 48)
Must have broken that in a merge - put it back
2013-12-22 21:13:24 +00:00
* @returns string
*
*/
function get_default_profile_photo($size = 175) {
Style
2013-12-22 21:15:13 +00:00
$scheme = get_config('system','default_profile_photo');
if(! $scheme)
$scheme = 'rainbow_man';
Changed default avatars to PNG as agreed with Mike here: https://redmatrix.nl/channel/jeroenpraat/?f=&mid=83603d8f0876c040efafce87755fcd252dbe8da4a75d82fdb230519e3c8dcb72@redmatrix.nl. Added a few new. You can set it like this: util/config system default_profile_photo red_avatar
2014-10-05 18:32:28 +00:00
return 'images/default_profile_photos/' . $scheme . '/' . $size . '.png';
Must have broken that in a merge - put it back
2013-12-22 21:13:24 +00:00
}
add account_level, is_foreigner and is_member functions; convert all e2ee user input and prompts to hex to avoid javascipt's lame handling of quotes. !!This breaks all prior encrypted posts.!!
2013-12-23 23:13:09 +00:00
/**
*
* @function is_foreigner($s)
* Test whether a given identity is NOT a member of the Red Matrix
* @param string $s;
* xchan_hash of the identity in question
*
* @returns boolean true or false
*
*/
function is_foreigner($s) {
snakebite, cont. magic-auth via openid is now possible, with the caveat that one needs a hand-crafted xchan at the moment to make use of it and if you wish to do so, there will be no assistance or help provided. The risk of system instability and mangled DBs now and going forward is significant if you try this.
2014-02-18 04:10:43 +00:00
return((strpbrk($s,'.:@')) ? true : false);
add account_level, is_foreigner and is_member functions; convert all e2ee user input and prompts to hex to avoid javascipt's lame handling of quotes. !!This breaks all prior encrypted posts.!!
2013-12-23 23:13:09 +00:00
}
/**
*
* @function is_member($s)
* Test whether a given identity is a member of the Red Matrix
* @param string $s;
* xchan_hash of the identity in question
*
* @returns boolean true or false
*
*/
function is_member($s) {
return((is_foreigner($s)) ? false : true);
urlencode query_string for magic auth to make sure GET params make it back to the originating server
2014-01-09 14:59:42 +00:00
}
online indication on profile sidebar
2014-01-29 01:07:25 +00:00
function get_online_status($nick) {
$ret = array('result' => false);
return the expected array
2014-02-12 23:12:42 +00:00
if(get_config('system','block_public') && ! local_user() && ! remote_user())
return $ret;
online indication on profile sidebar
2014-01-29 01:07:25 +00:00
$r = q("select channel_id, channel_hash from channel where channel_address = '%s' limit 1",
dbesc(argv(1))
);
if($r) {
$hide = get_pconfig($r[0]['channel_id'],'system','hide_online_status');
if($hide)
return $ret;
$x = q("select cp_status from chatpresence where cp_xchan = '%s' and cp_room = 0 limit 1",
dbesc($r[0]['channel_hash'])
);
if($x)
$ret['result'] = $x[0]['cp_status'];
}
return $ret;
}
online indication to the directory popup
2014-01-29 03:49:56 +00:00
function remote_online_status($webbie) {
$result = false;
$r = q("select * from hubloc where hubloc_addr = '%s' limit 1",
dbesc($webbie)
);
if(! $r)
return $result;
$url = $r[0]['hubloc_url'] . '/online/' . substr($webbie,0,strpos($webbie,'@'));
$x = z_fetch_url($url);
if($x['success']) {
$j = json_decode($x['body'],true);
if($j)
$result = (($j['result']) ? $j['result'] : false);
}
return $result;
}
code cleanup
2014-02-21 01:07:43 +00:00
function get_channel_by_nick($nick) {
$r = q("select * from channel where channel_address = '%s' limit 1",
dbesc($nick)
);
return(($r) ? $r[0] : false);
Make zid() work for observers as well as local users
2014-03-04 23:18:33 +00:00
}
provide the ability for rpost to post as another of your channels. This does not yet work, so the functionality has not been enabled.
2014-04-05 09:32:07 +00:00
function identity_selector() {
if(local_user()) {
implicit boolean, formatting
2014-11-20 12:55:01 +00:00
$r = q("select channel.*, xchan.* from channel left join xchan on channel.channel_hash = xchan.xchan_hash where channel.channel_account_id = %d and (channel_pageflags & %d) = 0 order by channel_name ",
provide the ability for rpost to post as another of your channels. This does not yet work, so the functionality has not been enabled.
2014-04-05 09:32:07 +00:00
intval(get_account_id()),
intval(PAGE_REMOVED)
);
if(count($r) > 1) {
$selected_channel = null;
$account = get_app()->get_account();
$o = replace_macros(get_markup_template('channel_id_select.tpl'),array(
'$channels' => $r,
'$selected' => local_user()
));
return $o;
}
}
return '';
Bring BBCode to profiles
2014-04-11 13:54:07 +00:00
}
visage tracking opt-in/opt-out
2014-07-04 00:26:42 +00:00
function is_public_profile() {
if(! local_user())
return false;
if(intval(get_config('system','block_public')))
return false;
$channel = get_app()->get_channel();
if($channel && $channel['channel_r_profile'] == PERMS_PUBLIC)
return true;
return false;
}
Let site admin choose what profile fields to support.
2014-08-03 06:28:51 +00:00
issue #551 provide import/export of profiles (if this feature is enabled)
2014-08-04 23:47:49 +00:00
function get_profile_fields_basic($filter = 0) {
$profile_fields_basic = (($filter == 0) ? get_config('system','profile_fields_basic') : null);
Let site admin choose what profile fields to support.
2014-08-03 06:28:51 +00:00
if(! $profile_fields_basic)
issue #551 provide import/export of profiles (if this feature is enabled)
2014-08-04 23:47:49 +00:00
$profile_fields_basic = array('name','pdesc','chandesc','gender','dob','dob_tz','address','locality','region','postal_code','country_name','marital','sexual','homepage','hometown','keywords','about','contact');
Let site admin choose what profile fields to support.
2014-08-03 06:28:51 +00:00
$x = array();
if($profile_fields_basic)
foreach($profile_fields_basic as $f)
$x[$f] = 1;
return $x;
}
issue #551 provide import/export of profiles (if this feature is enabled)
2014-08-04 23:47:49 +00:00
function get_profile_fields_advanced($filter = 0) {
$basic = get_profile_fields_basic($filter);
$profile_fields_advanced = (($filter == 0) ? get_config('system','profile_fields_advanced') : null);
Let site admin choose what profile fields to support.
2014-08-03 06:28:51 +00:00
if(! $profile_fields_advanced)
$profile_fields_advanced = array('with','howlong','politic','religion','likes','dislikes','interest','channels','music','book','film','tv','romance','work','education');
$x = array();
if($basic)
foreach($basic as $f => $v)
$x[$f] = $v;
if($profile_fields_advanced)
foreach($profile_fields_advanced as $f)
$x[$f] = 1;
return $x;
}
disable email notifications when bulk importing content.
2014-10-08 22:15:20 +00:00
/**
* @function notifications_off($channel_id)
* Clear notifyflags for a channel - most likely during bulk import of content or other activity that is likely
* to generate huge amounts of undesired notifications.
* @param int $channel_id
* The channel to disable notifications for
* @returns int
* Current notification flag value. Send this to notifications_on() to restore the channel settings when finished
* with the activity requiring notifications_off();
*/
Let site admin choose what profile fields to support.
2014-08-03 06:28:51 +00:00
disable email notifications when bulk importing content.
2014-10-08 22:15:20 +00:00
function notifications_off($channel_id) {
$r = q("select channel_notifyflags from channel where channel_id = %d limit 1",
intval($channel_id)
);
PostgreSQL support initial commit 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)
2014-11-13 20:21:58 +00:00
$x = q("update channel set channel_notifyflags = 0 where channel_id = %d",
disable email notifications when bulk importing content.
2014-10-08 22:15:20 +00:00
intval($channel_id)
);
return intval($r[0]['channel_notifyflags']);
}
function notifications_on($channel_id,$value) {
PostgreSQL support initial commit 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)
2014-11-13 20:21:58 +00:00
$x = q("update channel set channel_notifyflags = %d where channel_id = %d",
disable email notifications when bulk importing content.
2014-10-08 22:15:20 +00:00
intval($value),
intval($channel_id)
);
return $x;
ok heads up - potentially destabilising change. I've tried to sort out all the default connection permissions for those who don't have a predefined (or therefore have a "custom") permissions role. Unfortunately this includes most people that were using this software more than a month ago. The real changes are that the SELF address book entry no longer holds "auto-permissions" but instead holds your "default permissions" (if you have a pre-defined role, the defaults will be pulled from the role table). The auto permissions have moved to a pconfig (uid.system.autoperms). A DB update will move these settings into their new homes. What used to be the "Auto-permissions settings" page is now the "default permissions settings" page and a checkbox therein decides whether or not to apply the permissions automatically. A link to this page will only be shown when you have the "custom" role selected. With luck nobody will notice anything wrong. But at least for the next few days, please review permissions that have been assigned to new connections (either automatically or manually) and make sure they make sense (e.g. they aren't "nothing"). You still need to take action when seeing a message "permissions have changed but not yet submitted" as we always let you review and perhaps adjust the settings _before_ a connection is established (unless you have autoperms turned on).
2014-11-05 01:11:02 +00:00
}
function get_channel_default_perms($uid) {
implicit boolean, formatting
2014-11-20 12:55:01 +00:00
$r = q("select abook_my_perms from abook where abook_channel = %d and (abook_flags & %d) > 0 limit 1",
ok heads up - potentially destabilising change. I've tried to sort out all the default connection permissions for those who don't have a predefined (or therefore have a "custom") permissions role. Unfortunately this includes most people that were using this software more than a month ago. The real changes are that the SELF address book entry no longer holds "auto-permissions" but instead holds your "default permissions" (if you have a pre-defined role, the defaults will be pulled from the role table). The auto permissions have moved to a pconfig (uid.system.autoperms). A DB update will move these settings into their new homes. What used to be the "Auto-permissions settings" page is now the "default permissions settings" page and a checkbox therein decides whether or not to apply the permissions automatically. A link to this page will only be shown when you have the "custom" role selected. With luck nobody will notice anything wrong. But at least for the next few days, please review permissions that have been assigned to new connections (either automatically or manually) and make sure they make sense (e.g. they aren't "nothing"). You still need to take action when seeing a message "permissions have changed but not yet submitted" as we always let you review and perhaps adjust the settings _before_ a connection is established (unless you have autoperms turned on).
2014-11-05 01:11:02 +00:00
intval($uid),
intval(ABOOK_FLAG_SELF)
);
if($r)
return $r[0]['abook_my_perms'];
return 0;
Show tags in other channels profile field to make it easier to navigate to the channels
2014-12-07 15:17:45 +00:00
}
Reference in a new issue Copy permalink