2011-07-11 17:54:22 +02:00
|
|
|
<?php
|
|
|
|
|
2011-09-14 17:02:31 +02:00
|
|
|
/**
|
|
|
|
* @group phriction
|
|
|
|
*/
|
2013-01-11 20:39:22 +01:00
|
|
|
final class PhrictionDocument extends PhrictionDAO
|
|
|
|
implements PhabricatorPolicyInterface {
|
2011-07-11 17:54:22 +02:00
|
|
|
|
|
|
|
protected $id;
|
|
|
|
protected $phid;
|
|
|
|
protected $slug;
|
|
|
|
protected $depth;
|
|
|
|
protected $contentID;
|
2011-12-17 18:19:08 +01:00
|
|
|
protected $status;
|
2011-07-11 17:54:22 +02:00
|
|
|
|
2011-07-12 00:42:12 +02:00
|
|
|
private $contentObject;
|
|
|
|
|
2011-07-11 17:54:22 +02:00
|
|
|
public function getConfiguration() {
|
|
|
|
return array(
|
|
|
|
self::CONFIG_AUX_PHID => true,
|
|
|
|
self::CONFIG_TIMESTAMPS => false,
|
|
|
|
) + parent::getConfiguration();
|
|
|
|
}
|
|
|
|
|
|
|
|
public function generatePHID() {
|
|
|
|
return PhabricatorPHID::generateNewPHID(
|
|
|
|
PhabricatorPHIDConstants::PHID_TYPE_WIKI);
|
|
|
|
}
|
|
|
|
|
2011-07-12 00:06:19 +02:00
|
|
|
public static function getSlugURI($slug, $type = 'document') {
|
|
|
|
static $types = array(
|
|
|
|
'document' => '/w/',
|
|
|
|
'history' => '/phriction/history/',
|
|
|
|
);
|
|
|
|
|
|
|
|
if (empty($types[$type])) {
|
|
|
|
throw new Exception("Unknown URI type '{$type}'!");
|
|
|
|
}
|
|
|
|
|
|
|
|
$prefix = $types[$type];
|
|
|
|
|
2011-07-11 17:54:22 +02:00
|
|
|
if ($slug == '/') {
|
2011-07-12 00:06:19 +02:00
|
|
|
return $prefix;
|
2011-07-11 17:54:22 +02:00
|
|
|
} else {
|
2011-07-12 00:06:19 +02:00
|
|
|
return $prefix.$slug;
|
2011-07-11 17:54:22 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
public function setSlug($slug) {
|
2012-04-10 23:18:20 +02:00
|
|
|
$this->slug = PhabricatorSlug::normalize($slug);
|
|
|
|
$this->depth = PhabricatorSlug::getDepth($slug);
|
2011-07-11 17:54:22 +02:00
|
|
|
return $this;
|
|
|
|
}
|
|
|
|
|
2011-07-12 00:42:12 +02:00
|
|
|
public function attachContent(PhrictionContent $content) {
|
|
|
|
$this->contentObject = $content;
|
|
|
|
return $this;
|
|
|
|
}
|
|
|
|
|
|
|
|
public function getContent() {
|
|
|
|
if (!$this->contentObject) {
|
|
|
|
throw new Exception("Attach content with attachContent() first.");
|
|
|
|
}
|
|
|
|
return $this->contentObject;
|
|
|
|
}
|
|
|
|
|
Provide wiki pages for projects
Summary:
Provide tighter integration between Projects and Phriction. Partly, I have most
of a rewrite for the Projects homepage ready but it's not currently possible to
publish feed stories about a project so all the feeds are empty/boring. This
partly makes them more useful and partly just provides a tool integration point.
- When you create a project, all the wiki pages in projects/<project_name>/*
are associated with it.
- Publish updates to those pages as being related to the project so they'll
show up in project feeds.
- Show a project link on those pages.
This is very "convention over configuration" but I think it's the right
approach. We could provide some sort of, like, "@project=derp" tag to let you
associated arbitrary pages to projects later, but just letting you move pages is
probably far better.
Test Plan:
- Ran upgrade scripts against stupidly named projects ("der", " der", " der
", "der (2)", " der (2) (2)", etc). Ended up with uniquely named projects.
- Ran unit tests.
- Created /projects/ wiki documents and made sure they displayed correctly.
- Verified feed stories publish as project-related.
- Edited projects, including perfomring a name-colliding edit.
- Created projects, including performing a name-colliding create.
Reviewers: btrahan, jungejason
Reviewed By: btrahan
CC: aran, epriestley, btrahan
Maniphest Tasks: T681
Differential Revision: 1231
2011-12-17 20:58:55 +01:00
|
|
|
public static function isProjectSlug($slug) {
|
2012-04-10 23:18:20 +02:00
|
|
|
$slug = PhabricatorSlug::normalize($slug);
|
Provide wiki pages for projects
Summary:
Provide tighter integration between Projects and Phriction. Partly, I have most
of a rewrite for the Projects homepage ready but it's not currently possible to
publish feed stories about a project so all the feeds are empty/boring. This
partly makes them more useful and partly just provides a tool integration point.
- When you create a project, all the wiki pages in projects/<project_name>/*
are associated with it.
- Publish updates to those pages as being related to the project so they'll
show up in project feeds.
- Show a project link on those pages.
This is very "convention over configuration" but I think it's the right
approach. We could provide some sort of, like, "@project=derp" tag to let you
associated arbitrary pages to projects later, but just letting you move pages is
probably far better.
Test Plan:
- Ran upgrade scripts against stupidly named projects ("der", " der", " der
", "der (2)", " der (2) (2)", etc). Ended up with uniquely named projects.
- Ran unit tests.
- Created /projects/ wiki documents and made sure they displayed correctly.
- Verified feed stories publish as project-related.
- Edited projects, including perfomring a name-colliding edit.
- Created projects, including performing a name-colliding create.
Reviewers: btrahan, jungejason
Reviewed By: btrahan
CC: aran, epriestley, btrahan
Maniphest Tasks: T681
Differential Revision: 1231
2011-12-17 20:58:55 +01:00
|
|
|
$prefix = 'projects/';
|
|
|
|
if ($slug == $prefix) {
|
|
|
|
// The 'projects/' document is not itself a project slug.
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
return !strncmp($slug, $prefix, strlen($prefix));
|
|
|
|
}
|
|
|
|
|
|
|
|
public static function getProjectSlugIdentifier($slug) {
|
|
|
|
if (!self::isProjectSlug($slug)) {
|
|
|
|
throw new Exception("Slug '{$slug}' is not a project slug!");
|
|
|
|
}
|
|
|
|
|
2012-04-10 23:18:20 +02:00
|
|
|
$slug = PhabricatorSlug::normalize($slug);
|
Provide wiki pages for projects
Summary:
Provide tighter integration between Projects and Phriction. Partly, I have most
of a rewrite for the Projects homepage ready but it's not currently possible to
publish feed stories about a project so all the feeds are empty/boring. This
partly makes them more useful and partly just provides a tool integration point.
- When you create a project, all the wiki pages in projects/<project_name>/*
are associated with it.
- Publish updates to those pages as being related to the project so they'll
show up in project feeds.
- Show a project link on those pages.
This is very "convention over configuration" but I think it's the right
approach. We could provide some sort of, like, "@project=derp" tag to let you
associated arbitrary pages to projects later, but just letting you move pages is
probably far better.
Test Plan:
- Ran upgrade scripts against stupidly named projects ("der", " der", " der
", "der (2)", " der (2) (2)", etc). Ended up with uniquely named projects.
- Ran unit tests.
- Created /projects/ wiki documents and made sure they displayed correctly.
- Verified feed stories publish as project-related.
- Edited projects, including perfomring a name-colliding edit.
- Created projects, including performing a name-colliding create.
Reviewers: btrahan, jungejason
Reviewed By: btrahan
CC: aran, epriestley, btrahan
Maniphest Tasks: T681
Differential Revision: 1231
2011-12-17 20:58:55 +01:00
|
|
|
$parts = explode('/', $slug);
|
|
|
|
return $parts[1].'/';
|
|
|
|
}
|
|
|
|
|
2013-01-11 20:39:22 +01:00
|
|
|
// TODO: Customize this? Copypasta from PhabricatorPaste.
|
|
|
|
public function getCapabilities() {
|
|
|
|
return array(
|
|
|
|
PhabricatorPolicyCapability::CAN_VIEW,
|
|
|
|
PhabricatorPolicyCapability::CAN_EDIT,
|
|
|
|
);
|
|
|
|
}
|
|
|
|
|
|
|
|
public function getPolicy($capability) {
|
|
|
|
return PhabricatorPolicies::POLICY_USER;
|
|
|
|
}
|
|
|
|
|
|
|
|
public function hasAutomaticCapability($capability, PhabricatorUser $user) {
|
|
|
|
return false;
|
|
|
|
}
|
2011-07-11 17:54:22 +02:00
|
|
|
}
|