Page MenuHomeMiraheze

WikiForum broken on All The Tropes
Closed, InvalidPublic

Description

The WikiForum extension used by All The Tropes seems to have been disrupted in some manner -- the Special:WikiForum page displays "No such special page - You have requested an invalid special page." instead of linking to the forum directory. As far as we can tell, the extension is still live and supported, there are no issues resembling it reported for it, and it appears all the admin management options are still working. As far as we can tell, that means there must be a backend issue somewhere, possibly caused by the recent update.

Could someone please look into this? Thank you.

Event Timeline

Unknown Object (User) added a comment.Dec 1 2022, 20:27

I have meant to make this widely known (through ManageWiki note) for a while, so I am very sorry it was not. WikiForum has been disabled due to security vulnerabilities.

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.

Unknown Object (User) closed this task as Invalid.Dec 3 2022, 23:14
Unknown Object (User) claimed this task.

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 understand, unfortunately our priority in the matter is security, and since a patch at this time is unknown, we can not re-enable, nor have any ETA for it.

Due to this depending on upstream, closing as invalid, but we will work to restore it as soon as possible.

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 understand, unfortunately our priority in the matter is security, and since a patch at this time is unknown, we can not re-enable, nor have any ETA for it.

Due to this depending on upstream, closing as invalid, but we will work to restore it as soon as possible.

Can a task be filed upstream with the identified security issues?

Unknown Object (User) added a comment.Dec 4 2022, 20:19

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 understand, unfortunately our priority in the matter is security, and since a patch at this time is unknown, we can not re-enable, nor have any ETA for it.

Due to this depending on upstream, closing as invalid, but we will work to restore it as soon as possible.

Can a task be filed upstream with the identified security issues?

There is one,

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

For later reference, however, could the filed issue with upstream be linked here?

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 understand, unfortunately our priority in the matter is security, and since a patch at this time is unknown, we can not re-enable, nor have any ETA for it.

Due to this depending on upstream, closing as invalid, but we will work to restore it as soon as possible.

Can a task be filed upstream with the identified security issues?

There is one,

do you have the link?