We at ATT understand the problems mentioned and can wait, this is not a super high priority at present.

I see. Given we were using it actively, it would be desirable to have it restored as soon as this is passed. We do have some fallback forums for use in the meantime, but restoration of that is preferred whenever possible.

I see. Then for now, consider the plan to replace Flow on indefinite hold. I wasn't sure if this would cause problems, hence my asking, and this sounds like the cure will be far worse than the disease.

That is good to hear. We just want to make sure Flow is depreciated for all but our Reviews namespace while the current discussions are archived to preserve history.

All The Tropes has enabled this extension as well and have similar issues, more here:

That would be preferred.

Reverted it all manually, so concur.

If need be, I'll scrape a list of specific titles for reversion, just all edits made for the period of July 13 need reverted if the last edit was by Gethbot.

That I did not know. Guess this should be tabled until that changes then.

Userboards and Friend/Foe Displays are (but seem to have no effect the Add a Friend/Foe options being available, all they do at best is hide the friends and foe lists from public view), and the UserThreshold setting to deter spammers is not available via that setting.

Re opening just make sure these settings are set like this, noticed the User boards were not enabled and a few other things were not set properly. Also added the last setting as a spammer deterrent, we've had a few try to use the SocialProfile to spam, this should deter that. Not sure if you want this to be standard for all wikis using SP, but it's a very attractive extension to let spammers spam more, hence the last option.

I already thought of a fallback solution, going to just try to disable the options via some CSS tweaks. Let me know if anything changes.

I just rechecked. Apparently, once I flushed my cache, only the friending feature remains in play. We just wanted the "foe" feature removed and confirmation it's been disabled because we had some people use it to spite other users in the past, and we wanted that aspect of SocialProfile completely excised from use to prevent further such incidences.

Upon further review, most of this can be done on our end, but one item does need done on Miraheze's end:

Hate to reopen this again, but the download keeps stalling after 400 or so MB.

Thanks, will do. I'm going to get this ASAP.

Thanks. Please keep me posted.

I'm reopening this to say I'm going to ask for temporary admin status so I can attempt to get a copy for myself then. If that isn't possible, I'm going to have to ask Miraheze to place it on Archive.org. I'll update this to report whether the server will, on my end of things, let me grab such a large archive or I need Miraheze Staff to do the needful.

I'm not an admin anymore, so could it be provided on archive.org (the image dump)

That's fine by me.

That's understandable. You can cull the deleted images from the final result if you like to bring the file size down when they are ready. Until then, I'll be patient.

Much obliged. Images to go with it would be wonderful as well, but I can wait on that.

a full current revision only dump of all of ATT is fine.

current revision only would be fine, full histories are not required for CC BY SA.

Just wanted to confirm I backed this request and LK has my authorization to request it. We cannot edit this feature since it requires specific PHP setting edits.

Still getting issues in Brave browser for some reason, but it's cleared up in all others for all items mentioned.

I am still having issues logging into Miraheze by any means, on any browser.

On MediaWiki, and I confirmed it's my legit username and password prior:

That will be more than sufficient. Thank you.

A current revision only dump would be more than fine, I simply need a recent copy of the data.

I tried to reassign groups, nothing is working.

It works, much obliged.

Once that's fixed, we would appreciate having our RelatedPages issue looked into.

Getting a bizarre error message when I try to edit setting in Special:ManageWiki

We are also in need of an interwiki link to Wikilivres/Biblio Wiki

Since this cannot be set via Special:ManageWiki, we would like the RelatedPages feature to be whitelisted for every skin in use by ATT that is available on Miraheze.

One last thing, could you check to see if this is enabled?

I see, I'm glad to hear that.

Just asking for an update on this, could really use that CirrusSearch change for reasons given in above comment.

We still need Related Articles to work on ATT. They show up on the Minerva skin, but not Vector.

It does us little good currently, so pull the plug.

Well, just making sure on the mobile request, we got some complaints our site is hard to read on mobile, glad to know that's addressed.

Also,please add this feature for MobileFrontend and the accompanying skin if we don't have it already.

We still need the rest of the features from this request.

In T2710#53964, @CnocBride wrote:

QuizGame has been removed and RandomSelection has been re-instated. Apologies @Arcane21 for my mistake. Task closed.

Well, could you look into why RandomSelection is down? Our front page seems pretty broken and I noticed it vanished around the time those changes were made.

Regrettably, going to have to ask QuizGame be disabled for now.

In T2710#50976, @MacFan4000 wrote:

Perr T895: Review RandomUsersWithAvatars RandomUsersWithAvatars is declined.

Yes, it is.

Thanks. Have fixed it.

Well, please take your time and compress it as much as is needed to conserve space and bandwidth, no need to rush this on my account.

I don;t believe it's a major concern anymore, so feel free to drop this part of this support ticket if you deem it appropriate.

Sounds prudent to me.

That's a relief. An image backup still would not be a bad idea as well when you do so, but it is a relief to see the 2014 backup is not the only one.

If performance issues are that pressing, then please do what you consider best @labster.

Wait, it seems to work, but the Special:EditProfile page remains unlisted.

Can't remove local profile comments from those spam accounts.

Still get

Well, as long as it can be restricted so the average spammer can't abuse it I'm happy, and I need those spam profiles flushed if you guys can do so.

In T1691#32365, @Amanda wrote:

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.

The way to go is to have a wiki creator or sysadmin "close" their wiki so that nobody can edit it, and if the abuse continues on Meta or elsewhere, perhaps lock their global account and send an email.

In any sense, blocking the founder of the wiki should never be done unless authorized by that founder themselves.

I'd like to oppose this for reasons of security. A wiki founder should not be exempt from being blocked if they have committed offenses that have disrupted Miraheze's operations and have caused trouble severe enough that their blocking would be justified under Miraheze policy. Granting this would effectively hamstring the police powers of the Miraheze staff and allow a troublemaker to continue to wreak havoc.

In T1739#32356, @Amanda wrote:

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

Can confirm.

Then scratch this idea.

Good points on NewSignupPage, I'd belay that until it was made more wiki agnostic.

I see. If possible, install it as an option and if it works, we'll see how it works before considering switcing to using it as our default skin.

For now, this request is officially declined. If it can be made to work without issue, someone link me to it working as it was intended to work on Miraheze before all the issues I noticed and I'll reconsider opening this request again at another time

Discovered the issue.

Yeesh, that is a bad thing.

It would be used on the main page only.

I see. I got the skin working just fine by downloading the latest version through the extension downloader on MediaWiki.org, and it seems to work just fine.

Make sure the Mobile Frontend extension is completely disabled, this will cause issues with Refreshed working at all.