aboutsummaryrefslogtreecommitdiffstats
path: root/util
Commit message (Collapse)AuthorAgeFilesLines
* We've passed the deadline for allowing unsigned zot finger tokens. It is now ↵zotlabs2017-02-241-3034/+3039
| | | | a protocol requirement.
* string updatezotlabs2017-02-171-405/+415
|
* util/pconfig - don't enumerate empty arrays, mod_acl - add more commentszotlabs2017-02-131-2/+4
|
* Create virtual privacy groups for private profile member listszotlabs2017-02-121-899/+914
|
* string updatezotlabs2017-02-031-1996/+1965
|
* string updatezotlabs2017-01-271-1278/+1352
|
* js errors with raw message-id, string updateHubzilla2017-01-201-695/+857
|
* native wiki stuffzotlabs2017-01-171-2/+4
|
* string updatezotlabs2017-01-131-561/+586
|
* stringszotlabs2017-01-061-2783/+2819
|
* issue with post signatures if posted from api and logged in locally with a ↵zotlabs2016-12-241-3362/+3403
| | | | different identity.
* update util/hz to use zot api instead of the (now optional) twitter apizotlabs2016-12-211-1/+1
|
* string updatezotlabs2016-12-161-929/+959
|
* Drop on switch for notificationsilu332016-12-151-5/+2
|
* Configuring email notifications per channelilu332016-12-151-0/+56
|
* superblock issue + string updatezotlabs2016-12-091-103/+107
|
* Providing more frequent string updates at the momentzotlabs2016-12-051-244/+261
|
* string updatezotlabs2016-12-021-3619/+3609
|
* connedit prev/next: sort in the db.zotlabs2016-11-261-671/+686
|
* string updatezotlabs2016-11-181-2773/+2827
|
* don't send notification for posts/comments on old conversations that were ↵zotlabs2016-11-121-205/+221
| | | | refetched after having expired. We'll accomplish this by limiting notifications to items posted within the last month.
* Some minor tweaks to zotsh.py, document that it needs the twitter_api plugin ↵zotlabs2016-11-105-3/+5
| | | | on the first hop since we no longer provide the twitter api by default
* provide /locs link on settings page if there is more than one hubloc for ↵zotlabs2016-11-051-272/+273
| | | | this channnel *that isn't deleted*.
* command line connect utility.zotlabs2016-11-011-0/+64
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Usage: util/connect uid|nick channel uid|nick must be a local channel. The target channel can be any channel. If a nick is supplied as a target it is assumed to refer to a channel on the localhost unless @host is provided. RSS feeds and remote networks can also be connected, assuming the appropriate protocols are already enabled for the local channel. If the target channel is a non-forum on the local system and you wish bi-directional communication to be enabled you will probably need to use a second connnect command with the source and target reversed. Examples: util/connect bob marketing Connects bob to the marketing channel util/connect marketing bob Connects the marketing channel to bob. util/connect 6 channelone@macgirvin.com Connects the channel with channel_id 6 to the Channel One public forum. util/connect bob https://mysite.foo/feed.rss Connects bob to an RSS feed if RSS feeds are allowed as connections on this site util/connect bob jb@diasp.org Connects bob to a diaspora account on diap.org (both the site and Bob's channel must previously have the Diaspora Protocol enabled).
* string updatezotlabs2016-10-301-494/+546
|
* string updatezotlabs2016-10-211-3031/+3032
|
* more fixes to addons doc, include project addons in string extraction for ↵zotlabs2016-10-182-4457/+7488
| | | | translations, fix the string extractor which was looking in the old places for version info
* permissions issuezotlabs2016-10-141-4669/+4688
|
* [TASK] Update Doxyfile and fix Doxygen errors.Klaus Weidenbach2016-10-131-2/+4
| | | | | | Updated Doxyfile to include new folders. Add a list for @hooks tags. Fixed some parsing problems for Doxygen.
* don't expire posts before 2001zotlabs2016-10-101-2/+2
|
* Unify the various mail sending instance to enotify::send() and z_mail(). ↵redmatrix2016-10-011-4070/+4079
| | | | Both take the same arguments. z_mail() is text only, enotify::send() provides html and text. Both are pluggable using the enotfy_send hook.
* issue #531 - util/config and postgresredmatrix2016-09-231-1/+1
|
* attach sql issueredmatrix2016-09-231-3638/+3640
|
* some changes merged from wrong branch... new function channel_reddress() ↵redmatrix2016-09-173-3480/+3491
| | | | instead of hardwired generation and which fixes case-sensitivity; allow dot notation in config and pconfig utils, updated string file
* issue #511, postgres schema issuesredmatrix2016-09-091-4248/+4297
|
* turn Settings page into sub-modulesredmatrix2016-09-061-2/+2
|
* move the rest of mod_admin to sub modulesredmatrix2016-09-051-0/+7
|
* empty schemaredmatrix2016-09-021-3680/+3763
|
* - implemented but untested: duplicate detection for photo 'move to another ↵redmatrix2016-08-261-4321/+4318
| | | | | | folder' - weekly string update
* string updateredmatrix2016-08-191-3697/+3724
|
* remove insecure repository warning.redmatrix2016-08-183-30/+30
|
* string updateredmatrix2016-08-121-3625/+3619
|
* strings updateredmatrix2016-08-051-2270/+2333
|
* make guest access tokens work with PERMS_NETWORK, PERMS_SITE, PERMS_PENDING, ↵redmatrix2016-07-311-3184/+3114
| | | | and PERMS_CONTACTS; or everything but PERMS_SPECIFIC. PERMS_SITE could be contentious, but we're currently denying them as they are a guest and don't actually have a channel on this site. We can't easily make PERMS_SPECIFIC work without providing an abook entry for the guest since we would need to set specific permissions for the guest login, but unfortunately this could be the most desirable setting to use in many cases. There is also an update of hmessages.po in this commit.
* github didn't accept the last push. Touching the files to force a git revisionredmatrix2016-07-271-1/+0
|
* fix italian strings (messed up by rtl variable); and finish removing openid ↵redmatrix2016-07-271-1/+2
| | | | from core
* string update and some minor comment editsredmatrix2016-07-241-1489/+1567
|
* sort out some of the authentication mess - with luck this may fix the DAV ↵redmatrix2016-07-201-2/+5
| | | | auth issue which I simply could not duplicate or find a reason for.
* add service class restrictions to access_tokensredmatrix2016-07-151-1/+1
|
* enforce non-empty name and token/password on access tokens until better ↵redmatrix2016-07-151-1803/+1820
| | | | checks are instituted.