If you need to use Phabricator for personal reasons or any reason unrelated to Miraheze, or something that cannot be shared to Security, use your own instance. We are not hosting Phabricator. If you're looking for one, use Phacility

Why can't project creation be open? What's the point of the restriction?

You should not restrict project creation to admins, so that all users can create their personal timelines

If you do not want me to have private Maniphest tasks, create a project for me like you and NDK have

@Pauliusk you can apply for bureaucrat rights at the Stewards' noticeboard.

@Pauliusk if you are a bureaucrat on that wiki, you can go to Special:ManageWiki on the wiki and check the "private" checkbox

The task is a tracking task for me to track issues on Miraheze platforms that cannot be immediately managed by Miraheze. I noticed that many users have personal calendar projects for such tracking, such as revi and NDKilla, but I do not have permission to create such a project for myself.

Foreground is now enabled. Timeless has passed security review but is still pending installation

Great! Now, where would you change the config so that on WikiCanada the managewiki userright is restricted to the "founder" group? I'd assume overrides, but I'm just being sure

So does this mean that managewiki-restricted will no longer be required to change public/private settings?

This is legacy and it's currently undecided if this is a smart idea. It is up for discussion but it has been brought up that people can unintentionally (or intentionally) make their wiki public and then blame and put liability on Miraheze.

@John Currently I've noticed the following:

Fixed for now

Closing this task as invalid (self-withdrawal) per opposition above

First of all, if a wiki founder has committed abuse or other disruptive behavior, blocking them on their own wiki is not the way to go, as that could be seen as an abuse of sysadmin/steward global rights.

This isn't a feature request nor an extension review as SocialProfile is already installed and running - this is just a request to add a new setting to it

The Foreground Skin has been requested and should be enabled soon. The Timeless skin needs a security review per T1702 and therefore cannot be enabled at this time.

I cannot help you becasue I don't understand the language of your wiki. However, this appears to be a bug with the Flow extension to me.

This requires a wiki creator to change the wiki settings and make it public @Void @Reception123

The CreateBox extension is no longer in use, and has been superseded by the InputBox extension. InputBox is already enabled globally on all Miraheze wikis, so there's nothing more to do with this task. See here for more information on how to use the extension.

My initial change has been reverted by @John and I am not sure why. I'll let him handle it so that I don't interfere with anything.

Done

Done

This is high priority as an attempted usurp of a wiki. Also, please do not assign users to tasks unless they have been actively involved.

Unfortunately this extension is not compatible with Miraheze. Similar to the Wikimedia Foundation, Miraheze uses a central login system called CentralAuth, which means that all accounts that exist on one wiki automatically exist on all other wikis with one visit. Therefore, it is not possible for individual wikis to confirm user account requests.

I can handle the two extensions. Regarding the pages, were they pages that were created manually, or were they imported via Special:Import? In the former case you can use Special:Nuke to delete them, but in the latter case a sysadmin needs to delete them with a maintenance script

@DeMat VisualEditor has been requested and should be enabled soon

I think so. In any circumstance the extension still needs review

@Tansaku unfortunately Miraheze does not accept any banners or other advertisements

@Reception123 declined my attempt to do this, so I'll let them handle it from here

I tried to triage this task as normal priority and discovered that I do not have permission to. Why?

Seems like a MediaWiki bug to me

@Tansaku this extension needs a security review. However, you can just use MediaWiki:Sitenotice to display a message across the top of every page

This requires a wiki creator to change the settings of the wiki to make it public @Void

I believe they are enabled. There isn't any problem that I'm aware of, and therefore I'm dropping my assignment. A sysadmin may need to look at this @John @Reception123

Back to resolved - I was right the first time.

@DrewBiebs the New WikiText editor appears to already be enabled

VisualEditor has been requested. I don't know what the other extension is.

I think that Reception will handle it from here

Oops, I didn't see it in the config, but maybe I just wasn't looking closely

This requires a wiki creator to change the settings of the wiki @Void @Reception123

Sorry, I didn't realize that Hovercards was the same thing as Popups, which is installed. I'll request it now