I removed it from Turtle. If someone else didn't remove it from the other skins, then it never left.

I'm using Turtle.

And the event handler is still here?

Change to another skin, view the Forum Index, change back, view it again, tell me if the handler is still there afterward.

Increased Image-Size-Limit to 700 pixels width and 400 pixels height.

Post has been edited 1 time(s), last time on Apr 27 2011, 10:42 pm by DevliN. Reason: Fixed.

It is

Well, I'm retarded. I removed the Forum Index one, not the one(s) shown in the forums themselves.

Here's how to remove the onmouseover and onmouseout event handlers without losing functionality:

• Remove the handlers from the HTML.
  
• Add this to the forum's CSS: #content table.subforum-listing tr td:first-child+td+td:hover{background-color:#001111}
  

(The handlers were used for changing the cell's background color on hover; CSS :hover is now capable of doing that more effectively.)

Removing the onclick handler is easy, but if you just remove it, people will actually have to click directly on the link instead of just clicking anywhere on that table cell. Retaining that functionality without the use of JavaScript would require more... involved... changes to the HTML and CSS. That said, it shouldn't be a problem if people don't mind being less lazy.

Forgot to say we can't stack them neither.

Auto-resizing still trims signature images that are larger than 400 pixels in width, even though it is not supposed to happen. This completely destroys signatures with transparency. I would appreciate it if this was fixed.

EDIT> Please stop editing my posts if they do not break the forum rules, DevliN. Also, test:





Also, it looks like the modal that lets you insert images when you click on the "img" button when editing a post is ignoring your input; regardless of what numbers you type, it will substitute 700 and 450 into the BBCode that is inserted after you click "OK".

Post has been edited 4 time(s), last time on May 20 2011, 11:12 pm by Aristocrat.

At first I edited out everything related to the deleted posts. The second time was because you decided to say I deleted all your posts so you'll post it again (even though I left the important part to begin with). I didn't outright delete it because the last part of the post was relevant, once I understood you were referring to your signature (which was not stated in your original post). Next time, try not to claim I'm censoring you because I'm wrong as opposed to just deleting the unnecessary posts and leaving the one that actually gets to what you're talking about. Theoretically I could have cited "Do not undermine the staff's authority with actions such as reposting a post that a moderator just deleted" and left it at that.

The "ignoring input" is due to the javascript code that Devourer didn't care to change, as you can manually put in the numbers again anyway.







Yeah, interesting. I don't remember the gray border being there when he changed this and we tested it in the staff forum. Oh well.

Post has been edited 4 time(s), last time on May 20 2011, 11:29 pm by DevliN.

Gray border is a result of the added bbcode CSS class. When you specify the size of an image ([img=url|width|height]), the image is given the click-to-expand functionality and that class (to make it more obvious that the image can be clicked to expand), even if you're not scaling it down or even changing its size at all. Server doesn't check for unchanged/larger width and height values.

Well, with all of that aside, it remains a fact that my signature really should not be forcibly resized; even when the image is clearly under the size limitation, the resizing still occurs. It should not matter whether or not it is handled by JavaScript; most likely the fix is as simple as replacing a single number, if not in multiple places.

Being forced to upload signatures as many different images is an unnecessary inconvenience; please attempt to correct this in the near future. Just because something can be circumvented doesn't mean the problem deserves to be there; if it can be fixed, fix it. There is no reason to force users to suck up the hassle of doing things that should not be necessary because the developer can't be bothered to solve a trivial problem.

Click.

Try and go back to the first page on that.

ERROR.

Fix.

(Short and sweet =D)

Tikels, for a manual fix, change the /1/ at the end or the URL to &s=1, or whichever page you're trying to reach.

(i.e. http://www.staredit.net/?p=store&area=logs&s=1)

I suspended tikels for 0 hours and 1 severity for offensive language in the shoutbox, and it suspended him for 168 hours instead of 0.

I believe not specifying a time (i.e. putting 0) makes it automatically go to the default, which is one week.

Ah. I merely wanted to give 1 severity without a suspension.

If non-integer values are allowed, then typing something like 0.1 could work. This is assuming that values are not rounded after being entered. (It sounds like the server runs a simple check for a falsy value, so any near-zero truthy value should result in a near-zero-length suspension with severity.)

You can do that under his admin page.

I used his admin page to add the severity, but I can't see a way to add it without also adding a suspension. Hence why I tried to give him a 0 hour suspension. Incidentally can someone with the power to do so remove his suspension?