• The site has now migrated to Xenforo 2. If you see any issues with the forum operation, please post them in the feedback thread.
  • Due to issues with external spam filters, QQ is currently unable to send any mail to Microsoft E-mail addresses. This includes any account at live.com, hotmail.com or msn.com. Signing up to the forum with one of these addresses will result in your verification E-mail never arriving. For best results, please use a different E-mail provider for your QQ address.
  • For prospective new members, a word of warning: don't use common names like Dennis, Simon, or Kenny if you decide to create an account. Spammers have used them all before you and gotten those names flagged in the anti-spam databases. Your account registration will be rejected because of it.
  • Since it has happened MULTIPLE times now, I want to be very clear about this. You do not get to abandon an account and create a new one. You do not get to pass an account to someone else and create a new one. If you do so anyway, you will be banned for creating sockpuppets.
  • Due to the actions of particularly persistent spammers and trolls, we will be banning disposable email addresses from today onward.
  • The rules regarding NSFW links have been updated. See here for details.

Can't rearrange threadmarks

NOTTHISWAY

NOTTHISWAY

Indebted Capitalist
Joined
Oct 31, 2017
Messages
11,043
Likes received
214,322
Recently, in my compilation thread, I deleted a whole bunch of threadmarks from a story that had been moved to its own thread, and ever since I did that, I've been totally unable to edit the threadmarks' position. Whenever I try to edit display order, it gets stuck in a permanent "loading" screen. Every single other thread works, the intex tab works, it's just the threadmark tab when I click edit display order that gets stuck like that, like this:

mxqsmRo.png
 
Thank you for checking, hopefully they'll be able to fix whatever it is.

Might be worth testing out deleting a large amount of threadmarks in a row, and seeing if it reproduces the issue? Not sure how it works on the back end to be honest.
 
Don't really wanna be an annoyance now but, this issue still seems to persist.
 
I can confirm I've got the same problem in that thread. This looks like the annoying kind of bug.

I'll have to wait until I'm back at a real computer to look into this, hopefully tomorrow.
 
You must log in or register to reply here.

Users who are viewing this thread

Total: 1 (members: 0, guests: 1)
Back
Top