With regards to the Janitor functions... A two-click delete is great, but how about some shortcuts for escalating/ban-requesting?

If there's a way to remove a "sage" without deleting the post, it'd be nice if it was included in the delete options.

<-- I keep getting this bug
I have inline image expansion OFF, and it only seems to happen when I first load a page (i.e. before I've clicked anything)

>>226
I see that occasionally, myself

>>226
I have that problem alot; it happened with the normal extension, too. It's nothing too annoying though, so it doesn't really bother me.

Are reports and janitor posts actively updated? Or will I have to refresh the page for it to obtain an updated status check? I'm thinking that it's ajax. I just want to know for sure.

>>230
It is AJAX, and it updates itself every 5 minutes.

Failed to remove image:

HTML code: 200 and then a fuckton of HTML

aaagh, what the hell

>>234
screencap

>>236
Either your password is incorrect or someone already deleted that post before you managed to.

>>222
its on my todo list

>>224
nope, there is no way to edit a post, for mods or janitors.

>>226
my current stance on this is that its a bug in the firefox display engine, since just by clicking on the page/scrolling up and down you can usualy fix it. There is probably a way to get arround this problem though, but I have not yet found one.

>>230
Yes, it should refresh every 5 minuets.

>>234
I keep forgetting to tidy up that error, as >>237 said; you'll get it when the thing you're trying to delete has already been deleted or you are not signed in/don't have permission to delete the image.

I don't suppose a copy of the plugin could be made to be compatible with Netscape in the foreseeable future? Netscape is based off the Mozilla engine, after all, but has a bit more meat to it than Firefox.

>>241
isn't it the other way around?

But I doubt it, the extension uses quite a few things which I belive are firefox only.. It would probably be easier to rewrite the extension, which would be no quick job. unless anyone else write it I think you'll be stuck with firefox, or not using it.

it might be a nice idea to add the option for one of those annoying pop-ups (like when all downloads finish) for board status changes. i can't speak for everyone, but i know that if i'm busy surfing or working elsewhere on the computer i might not notice Yotsuba's hair turn yellow or red.

>>245
If this is incorporated into the extension, it ought to include an option to turn it off. It would get annoying for boards with lots of reports.

>>245
I agree, I had it turn yellow and the only way I noticed is I accidently glanced down there, a pop up or something you be pretty awesome.

>>246
yeah, i agree with you there. it shouldn't be a mandatory thing, but a feature we can use.

Another potential feature for the next version of the extension: allow middle-clicking the yotsuba leaves to open up the reports window in a new tab. It's easier than opening up a new tab if my currently-focused tab is important.

>>249
Right clicking already does this I believe.

>>250
Awesome, thanks! I'm a little foolish for not trying that out already.

>>249
Middle clicking works for me - I use it all the time.

>>252
It's official: I fail at life, and using this extension.

Disregard my earlier post, I suck cocks.

I keep getting this error pop up

>>268
it pops up every 5 minutes :x

>>236
I have been getting this error as well after, even after re-entering my password.

>>293
I switched back to my regular computer and everything seems to be working now. :) Nevermind!

Seeing as how Firefox 2.0 will be released tomorrow, and I fear it will fuck up all my extensions, will the janitor extension work?

Never mind, the extension appears to work fine with FF 2.0!

The extension functions, like the left-click image viewing, and the [+] to view an entire thread works on some boards (/v/,/h/,/j/), but not others (/b/,/tv/).

This is hardly a serious bug, or even a source of any great annoyance, but I thought I should mention it here, anyway. It seems that when I go into reply mode in a thread, none of the extension's buttons load, as you can see in the attached screenshot.

They will load for a particular post when I move the mouse over it, though, which is why a few of the posts in the screenshot have them but the rest don't.

Again, nothing serious, but I found it curious.

>>320
was that on a long thread? if so, then its not a bug, it doesn't add buttons to long threads becaues its slow. big stckies on /b/ can take minuets to parse, so I disable it and make them just appear on mouse over.

>>319
I've had a few janitors mention this, I'll look into it.

>>321
That might have actually been why. I didn't realize I was looking at mainly large threads at the time.

I'm getting the, already mentioned, error with a ton of raw HTML, but only when I try and do the "two-click" delete. When I'm in on the reports page, I can do everything just fine. So right now, I can't delete something like this until someone reports it.

The yotsuba just turned blue on me. I can't see them of course, but this is very weird, ban requests have never shown up on the janitor toolbar before. It just happened all of a sudden when I refreshed.

>>346
yes, it was just fixed by coda. I suppose the janitor version doesn't need to know the number of ban requests.

>>347
I'm still getting ban requests on my plugin.

>>349
Yes, of course you do, I haven't updated the extension yet!

>>351
Oh, I thought it was a server-side thing. Silly me.

well that annoying pop up seems to have ceased from appearing.

thanks?

I seem to be having a problem with the extension; when I attempt to delete a thread using the button, it pops up a message that says "Unable to Delete Post NULL. HTTP Code:200" followed by the sourcecode of the page.
This is on /v/, where I janitor-it-up.
Any ideas? x.x It used to work just peachy keen.

>>364
That happens when you're trying to delete a post that's already been deleted.

>>368
Uh huh, except that none of the ones I try to delete have already been deleted.

>>370
I think you also get it if you not signed in. I should really change that error, it was only ment to be a debug thing I think.

I think there should be a kind of rush on the updated Janitor Extention. I keep missing reports because the Yotsuba doesn't change if there're ban requests.

Uhhhhhhhh...
Can someone delete the goatse in >>>/wg/97845.html#97984 for me? Suddenly, I can't delete shit anymore.

>>425
Check to make sure you're logged in properly.

>>268
>>268
>>268

I get the same thing. HELP PLOX

>>436

olol it goes away eventually

this pops up when i start firefox. :(

>>463
edit: it only happens when i'm not logged in, of course

/reports/ redirects to www.4chan.org if you're not logged in, and i guess XHR follows it.

>>464
>>463
Yeah, I've noticed that, I'll change it to a more meaningful message.

new beta, probably broken!
http://4chan.wrathfilledhate.net/nojanitormenuhere/4chan_janitor.v0.4.5.0.BETA1.xpi

*janitor version no-longer sees ban requests and admin version has the orders changed.
*janitor version has report, escalate and ban request 2-click buttons.
*probably bug fixes
*probably more bugs
*not all of the bugs mentioned here have been fixed, I'll try and get them done soon.

admin version: check the wiki in a bit

>>498
got it. thanks, looks good so far. :)

"4chan News" link appears to be broken in the beta

http://4chan.wrathfilledhate.net/nojanitormenuhere/4chan_janitor.v0.4.5.0.BETA2.xpi

*menu links now work
*added annoying flashing red Yotsuba icon when there are more than 5 illegal reports (moot made me :( ).
*added even more annoying popup when ther are more than 10 illegal reports (moot :( ).

some things are still probably broken blah blah blah

ill update the team 4chan wiki with the admin one shortly.

I don't know if anyone has mentioned this, but would it be a stupid idea to have a button or option to hide all the extra janitor-only buttons we get? I have several friends who are all 4channers, and since we're not supposed to let people know our position, it'd be helpful. Same goes for screencaps of 4chan in general.

Again, appologies if it's a stupid or frivolous idea.

I think that there needs to be some distinction as to whether something is reported or escalated... the new version treats them both the same now. Maybe allow a color code for an escalated post but make sure it can be overridden by the color for non-escalated reports?

>>565
As far as I know, blue hasn't been used to denote escalated reports. It's been ban requests, which no longer apply to janitors/aren't displayed. Esclated posts aren't of a concern to janitors since it's the moderators who will be dealing with them. Moderators aren't going to be escalating posts for janitors to deal with.

Note: I miswrote this in the HOWTO. I updated it.

>>566
They still show up in our report list, though, with the exclamation mark, and the yotsuba leaves remain yellow while they exist. It's kind of annoying trying to find out if any new reports come in if there's an escalated post keeping the leaves on yellow.

>>567
coda is going to modify the reports system to remove a report that has been escalated from the queue. Whenever he does this change this won't happen any longer. He's busy with other stuff though so give him a few days/weeks/MONTHS!

>>551

just go to the 'janitor' submenu of the plugin and uncheck the 'add delete buttons' and 'add toolbox' as needed.

just a suggestion.

>>574
That does not seem to remove the new ban request and escalate post buttons, though.

>>577
I've been lazy and havn't added a config option for that, I plan to add one at some point.