after some further testing and using of ./bin/policy unlock of all relevant files this may not be the exact cause: I am certain though that creating such a file results in logged out users from seeing only a broken file while logged in I see it just fine.

@fzhan try bin/cache purge --purge-remarkup first?

Perfect, thanks!

Just tested this. Looks like this has been fixed.

@tagra123 is a co-worker of mine.

I think Diviner is meant for these scenarios. Basically because

That sounds like another great solution option for this problem :)

This is a related wishlist-y thing but it would be really cool if:

• The wiki was a repo
• It could be mirrored in a minimal read-only way (which could mean a lot of things, maybe it renders remarkup but otherwise just links everything?) but sync with the 'main' instance somehow (master with a repo mirror?). Honestly just the raw markup in a repo would probably be good enough to make me switch.

Well thanks !
But it still shows a problem : this solution is not present in the documentation : https://secure.phabricator.com/book/phabricator/article/remarkup/
Or is it just me ?

This seems like a small issue, but since there's absolutely no workaround and it's impossible to post any documentation that makes use of non-trivial tables, I think this is a pretty big deal.

You can do this:

1. Some
# Item

I think fixing this is basically removing the unique constraint on the "slugs" table in Phriction, and then using application logic to make sure that there can be only one active page with a given slug at any time.

I can't seem to reproduce this. See this test page here...

In T8530#120488, @epriestley wrote:

Assuming this is a misfire on "wiki", not an actual Wikimedia request.

I had the same feeling about the "View Options" drop-down in differential; I was thinking maybe we can have just the icons from the actions on the outside, for "advanced users" that know what they mean - sort of like this, but not done with Paint:

This keeps being a problem for Wikimedia. Situations when the probability of clashes include someone sends an email to wikitech-l (more than 1000 subscribers), one team or more are working on something specific on a specific day, or, like this weekend, we organize a hackathon with 200 developers around.

T8011 is at least superficially the same as this, and probably the same at the root.

...fixes the immediate issue, but then we hit something deeper down:

After T5378, most links should be external (because internal links would be converted into Remarkup objects).

Can you go into more detail on the problem you are having with Phabricator, specifically? It's unclear to me what problem this actually solves. It provides information, yes, but do you take actions different based on that information? https://secure.phabricator.com/book/phabcontrib/article/feature_requests/#describe-problems

Yeah, I think you have to write a bit of JS since every other menu we have either gets generated via JS or has at least one item in it that needs JS.

10 minutes of poking and realized this seems to include writing JavaScript. Unless I'm wrong. A little more than I can handle today.

I gotta eat lunch, etc. so feel free to yoink this back in the next 30 minutes or so if you wanted to do it @chad...! :D

I should be able to do this (convert). I thnk. Mybe.

I think the root cause for this is a bit complicated to explain, but basically we try to match this as a move:

That'd be nice. That or:

This would be very useful for the use-case described in T6004#107054.

Hmm. Yes, for this particular use-case, T7638 would probably be a preferable solution, as there does tend to accumulate a fair amount of links over time in those wiki docs. I seem to think that there were redirects to handle moved wiki pages, but if that is not the case, then that could be a problem.

T7638 might be another approach -- roughly, a checkbox like:

Having started to close down and archive our first projects in Phabricator, we find this would be a very, very useful feature.

This should probably just be a phuix dropdown instead of a CSS workaround. It bothers me I can't dismiss the menu without re-clicking Actions. lol.

This is fixed by D12360.