@epriestley Can I write and submit a patch for this?

This request doesn't describe a root problem and we don't seem to be making progress toward one, so we can't move forward on it.

@jhurwitz I use conduit to fetch wiki pages and format them with conduit to get a html syntax. I do that to add Wiki-Pages to a Frontend-Styleguide. Then i just add the required phabricator css and everything looks fine.
So i think you can write your own simple script to do everything over conduit, right?

@cburroughs: thank you

See also T3301, T8594, & T4558

I understand that my description is not a root problem, but I don't know how I could make it clearer.

"Feature doesn't exist" or "We'd use it" isn't to us a description of a root problem. Let's say for sake of argument, we'll never build that solution into Phabricator. Can you describe what problem you are having using Phabricator and let us determine how to solve it in a way that benefits the most users.

Thank you again, I try to describe the situation more clearly.

Thanks for the feature request! This feature request doesn't have the information we need to move forward, so I'd like to start by trying to understand why it doesn't. Specifically, it does not describe the root problem you are facing, and instead asks for a specific feature.

We don't have a secret internal Phabricator full of juicy status updates: if we make progress, we'll update this task. See Planning for details.

Any progress here? What about setting the hierachy limit in the wiki document itself? So you can say "show X levels in the document hierachy of this page" where X is inherited and has a default value of 2?

You’re missing soo much good stuff with new projects.

In T10307#158056, @chad wrote:

Rule #1 of bug reporting:

• Update your install.

I can reproduce this. Not sure this should happen "by default" but at least a checkbox seems reasonable to also rename child slugs.

You are welcome to reproduce on a Phacility test instance if you are unable to update, but as a rule we only take bug reports at HEAD.

Rule #1 of bug reporting:

FWIW, I'm running 2015 week 43.

Agreed with @activars - if we can get phab to allow just iframe embedding from google docs, this will be very useful.

Is it currently possible to configure number of levels to be displayed for wiki document hierarchy in Phriction? The current default seems to be equal to '2'. I have seen {D8061}, which is not resolved. Perhaps, I have missed other relevant info.

You can now add links to wiki pages, conpherences, etc., to the sidebar.

I agree that we should have a single wiki page set as "Project Wiki Home" or the like, set from Projects (with appropriate edit permissions), not from Phriction. Then, if someone wants a page to be "associated" with a project, but not the homepage, they simply add it beneath that main page (or link to it on the main page). That should resolve any confusion about what it means to 'associate a page'.

I believe this was fixed by D14511.

2 is such a surprising limit, it misleads you. You look at your wiki and you think, "I was sure I wrote a page on X, but no, I guess I'll start a new one".

Confirming that removing the apostrophe from the slug in the db did resolve. Thanks.

I did indeed update across those 3 revisions you listed; I was previously at October 11.

It's intentional that we normalize the slugs to try to make typing URLs a little more forgiving: For example, if you go to any of these links:

I think I see the issue.

There were some changes to slugs about 6 weeks ago (D14260, D14261, D14287) but I don't think they would have affected this.

We just did a visual refresh, but this didn't touch anything mechanical about Phriction. Not sure how it might have gotten in that state.

Since we can't reproduce this, I'm not sure how we could fix it.

I too cannot recreate it.

Steps to reproduce would be helpful. I tried to reproduce the error naturally and am unable to. I tried:

Oh, this was already fixed at HEAD (rP06aa3a0a1b). I pushed this server, should be good now.

Thanks, I'll look into this.

Works well now. Thanks a lot @chad

Thanks a lot @chad .

I think I found one here:

D14390 introduces "ApplicationEditor", which includes more race-resistant controls for editing things like projects and subscribers. In effect, this should merge edits of these fields correctly in all cases where there are no conflicts. Here's an example:

Projects are "tags" in Phabricator, they are general purpose containers for describing groups of things including Projects, Tags, Teams, Buckets, Whatever.

In T9622#141931, @rhkeeler wrote:

Tagging with projects would be great too, but we were really thinking of arbitrary tags not limited to the set of projects. (One example might be an "onboarding" tag; it's a word that's used in a few different contexts, so it would be pretty valuable to easily narrow in on just a subset -- e.g. pages intending to help new engineers onboard onto the team, which doesn't have an associated project.)

Tagging with projects would be great too, but we were really thinking of arbitrary tags not limited to the set of projects. (One example might be an "onboarding" tag; it's a word that's used in a few different contexts, so it would be pretty valuable to easily narrow in on just a subset -- e.g. pages intending to help new engineers onboard onto the team, which doesn't have an associated project.)