Select the types of activity you want to include in your feed.
@recaptime-dev's working patches + fork for Phorge, a community fork of Phabricator. (Upstream dev and stable branches are at upstream/main and upstream/stable respectively.)
hq.recaptime.dev/wiki/Phorge
···88 }
991010 public function getMethodDescription() {
1111- return pht('Update an existing conpherence thread.');
1111+ return pht('Update an existing conpherence room.');
1212 }
13131414 protected function defineParamTypes() {
···28282929 protected function defineErrorTypes() {
3030 return array(
3131- 'ERR_USAGE_NO_THREAD_ID' => pht(
3232- 'You must specify a thread id or thread phid to query transactions '.
3131+ 'ERR_USAGE_NO_ROOM_ID' => pht(
3232+ 'You must specify a room id or room phid to query transactions '.
3333 'from.'),
3434- 'ERR_USAGE_THREAD_NOT_FOUND' => pht(
3535- 'Thread does not exist or logged in user can not see it.'),
3434+ 'ERR_USAGE_ROOM_NOT_FOUND' => pht(
3535+ 'room does not exist or logged in user can not see it.'),
3636 'ERR_USAGE_ONLY_SELF_REMOVE' => pht(
3737- 'Only a user can remove themselves from a thread.'),
3737+ 'Only a user can remove themselves from a room.'),
3838 'ERR_USAGE_NO_UPDATES' => pht(
3939 'You must specify data that actually updates the conpherence.'),
4040 );
···5252 } else if ($phid) {
5353 $query->withPHIDs(array($phid));
5454 } else {
5555- throw new ConduitException('ERR_USAGE_NO_THREAD_ID');
5555+ throw new ConduitException('ERR_USAGE_NO_ROOM_ID');
5656 }
5757 $conpherence = $query->executeOne();
5858 if (!$conpherence) {
5959- throw new ConduitException('ERR_USAGE_THREAD_NOT_FOUND');
5959+ throw new ConduitException('ERR_USAGE_ROOM_NOT_FOUND');
6060 }
61616262 $source = PhabricatorContentSource::newFromConduitRequest($request);
···88 }
991010 public function getObjectPolicyName() {
1111- return pht('Thread Members');
1111+ return pht('Room Participants');
1212 }
13131414 public function getPolicyExplanation() {
1515- return pht('Members of this thread can take this action.');
1515+ return pht('Participants in this room can take this action.');
1616 }
17171818 public function getRuleDescription() {
1919- return pht('thread members');
1919+ return pht('room participants');
2020+ }
2121+2222+ public function getObjectPolicyIcon() {
2323+ return 'fa-comments';
2024 }
21252226 public function canApplyToObject(PhabricatorPolicyInterface $object) {
···167167168168..to "/etc/php.d/apc.ini" or the "php.ini" file indicated by "php -i".
169169170170-= Updating Phabricator =
171171-172172-Since Phabricator is under active development, you should update frequently. To
173173-update Phabricator:
174174-175175- - Stop the webserver (including `php-fpm`, if you use it).
176176- - Run `git pull` in `libphutil/`, `arcanist/` and `phabricator/`.
177177- - Run `phabricator/bin/storage upgrade`.
178178- - Restart the webserver (and `php-fpm`, if you stopped it earlier).
179179-180180-For more details, see @{article:Configuration Guide}. You can use a script
181181-similar to this one to automate the process:
182182-183183-http://www.phabricator.com/rsrc/install/update_phabricator.sh
184184-185170= Next Steps =
186171187172Continue by:
188173189189- - configuring Phabricator with the @{article:Configuration Guide}.
174174+ - configuring Phabricator with the @{article:Configuration Guide}; or
175175+ - learning how to keep Phabricator up to date with
176176+ @{article:Upgrading Phabricator}.
+130
src/docs/user/upgrading.diviner
···11+@title Upgrading Phabricator
22+@group intro
33+44+This document contains instructions for keeping Phabricator up to date.
55+66+Overview
77+========
88+99+Phabricator is under active development, and new features are released
1010+continuously. Staying up to date will keep your install secure.
1111+1212+We recommend installs upgrade regularly (every 1-2 weeks). Upgrades usually go
1313+smoothly and complete in a few minutes. If you put off upgrades for a long
1414+time, it may take a lot more work to bring things up to date if you want access
1515+to a useful new feature or an important security change.
1616+1717+1818+Staying On Top of Changes
1919+=========================
2020+2121+We release a weekly [[https://secure.phabricator.com/w/changelog | Changelog]],
2222+which describes changes in the previous week. You can look at the changelogs
2323+for an idea of what new features are available, upcoming changes, security
2424+information, and warnings about compatibility issues or migrations.
2525+2626+2727+Stable Branch
2828+=============
2929+3030+You can either run the `master` or `stable` branch of Phabricator. The `stable`
3131+branch is run in the [[ https://phacility.com | Phacility Cluster ]], and lags
3232+about a week behind `master`.
3333+3434+The `stable` branch is a little more stable than `master`, and may be helpful
3535+if you administrate a larger install.
3636+3737+We promote `master` to `stable` about once a week, then publish the changelog
3838+and deploy the cluster. During the week, major bugfixes are cherry-picked to
3939+the `stable` branch. The changelog lists the `stable` hashes for that week,
4040+as well as any fixes which were cherry-picked.
4141+4242+To switch to `stable`, check the branch out in each working copy:
4343+4444+ phabricator/ $ git checkout stable
4545+ arcanist/ $ git checkout stable
4646+ libphutil/ $ git checkout stable
4747+4848+You can now follow the upgrade process normally.
4949+5050+5151+Upgrade Process
5252+===============
5353+5454+IMPORTANT: You **MUST** restart Apache or PHP-FPM after upgrading.
5555+5656+Phabricator runs on many different systems, with many different webservers.
5757+Given this diversity, we don't currently maintain a comprehensive upgrade
5858+script which can work on any system. However, the general steps are the same
5959+on every system:
6060+6161+ - Stop the webserver (including `php-fpm`, if you use it).
6262+ - Stop the daemons, with `phabricator/bin/phd stop`.
6363+ - Run `git pull` in `libphutil/`, `arcanist/` and `phabricator/`.
6464+ - Run `phabricator/bin/storage upgrade`.
6565+ - Start the daemons, with `phabricator/bin/phd start`.
6666+ - Restart the webserver (and `php-fpm`, if you stopped it earlier).
6767+6868+For some more discussion details, see @{article:Configuration Guide}.
6969+7070+This template script roughly outlines the steps required to upgrade Phabricator.
7171+You'll need to adjust paths and commands a bit for your particular system:
7272+7373+```lang=sh
7474+#!/bin/sh
7575+7676+set -e
7777+set -x
7878+7979+# This is an example script for updating Phabricator, similar to the one used to
8080+# update <https://secure.phabricator.com/>. It might not work perfectly on your
8181+# system, but hopefully it should be easy to adapt. This script is not intended
8282+# to work without modifications.
8383+8484+# NOTE: This script assumes you are running it from a directory which contains
8585+# arcanist/, libphutil/, and phabricator/.
8686+8787+ROOT=`pwd` # You can hard-code the path here instead.
8888+8989+### UPDATE WORKING COPIES ######################################################
9090+9191+cd $ROOT/libphutil
9292+git pull
9393+9494+cd $ROOT/arcanist
9595+git pull
9696+9797+cd $ROOT/phabricator
9898+git pull
9999+100100+101101+### CYCLE WEB SERVER AND DAEMONS ###############################################
102102+103103+# Stop daemons.
104104+$ROOT/phabricator/bin/phd stop
105105+106106+# If running the notification server, stop it.
107107+# $ROOT/phabricator/bin/aphlict stop
108108+109109+# Stop the webserver (apache, nginx, lighttpd, etc). This command will differ
110110+# depending on which system and webserver you are running: replace it with an
111111+# appropriate command for your system.
112112+# NOTE: If you're running php-fpm, you should stop it here too.
113113+114114+sudo /etc/init.d/httpd stop
115115+116116+117117+# Upgrade the database schema. You may want to add the "--force" flag to allow
118118+# this script to run noninteractively.
119119+$ROOT/phabricator/bin/storage upgrade
120120+121121+# Restart the webserver. As above, this depends on your system and webserver.
122122+# NOTE: If you're running php-fpm, restart it here too.
123123+sudo /etc/init.d/httpd start
124124+125125+# Restart daemons.
126126+$ROOT/phabricator/bin/phd start
127127+128128+# If running the notification server, start it.
129129+# $ROOT/phabricator/bin/aphlict start
130130+```
···321321 });
322322 }
323323 });
324324+324325 threadManager.syncWorkflow(workflow, 'submit');
325326 }
326327 );
···331332 function (e) {
332333 var href = config.widgetBaseUpdateURI + _loadedWidgetsID + '/';
333334 var data = e.getNodeData('remove-person');
334334- // we end up re-directing to conpherence home
335335+336336+ // While the user is removing themselves, disable the notification
337337+ // update behavior. If we don't do this, the user can get an error
338338+ // when they remove themselves about permissions as the notification
339339+ // code tries to load what jist happened.
340340+ var threadManager = JX.ConpherenceThreadManager.getInstance();
341341+ var loadedPhid = threadManager.getLoadedThreadPHID();
342342+ threadManager.setLoadedThreadPHID(null);
343343+335344 new JX.Workflow(href, data)
336336- .start();
345345+ .setCloseHandler(function() {
346346+ threadManager.setLoadedThreadPHID(loadedPhid);
347347+ })
348348+ // we re-direct to conpherence home so the thread manager will
349349+ // fix itself there
350350+ .setHandler(function(r) {
351351+ JX.$U(r.href).go();
352352+ })
353353+ .start();
337354 }
338355 );
339356