It's the maximum execution time. Removing it can cause serious problems.
Please tell me the structure of the post.

Post has been edited 1 time(s), last time on Aug 19 2010, 11:05 pm by Devourer.

The fact that it's timing out in the first place is alarming (should not ever happen unless something screwed up). I suspect it's part of the code responsible for not giving minerals for quotes in a post.

Here's one of the posts in question:
http://www.staredit.net/253082/

fixed it:

First and most importantly, I may/probably-will take a (hopefully short) break from coding the site due to emotional stress. I will return to coding for SEN -- and again, hopefully soon -- and when I do I'll get right back on my to-do list. I just can't summon up the mental energy for it right now. D:

Also, another list of known bugs (that I can actually work on) will be made in the v5.1 topic soon. I like having these things publicly viewable; it proves that I'm aware of bugs (so people know when they're being heard and when they're not), and it makes me accountable if I take too long to fix them. I'll be adding the bugs below to the list. I wonder, though, if I shouldn't start doing those posts here? (I do multiple posts (rather than just having one and editing only it) just so that if I lose a link to a to-do post, I can just go to the last post in a topic and backtrack, without having to dig through a ton of posts.)

And finally, the new bugs themselves, and my requests for more information. More, I say! MOAR!

Odd, I fixed and tested it on Chrome. What version do you have? Maybe yours is out of date, or maybe an update re-broke the BBCode Console.

Browser, version, and OS please. I'm betting Chrome or Safari, but I need confirmation so I know what to test.

In any case, I haven't gotten around to editing topic HTML yet, so that's another item for the ever-lengthening to-do list.

Something else for the to-do list.

Oh, wait, there's one last thing.

BUG for Devourer. When quoting using the Multiquote feature, some special characters are escaped even when they weren't in the original post. Or maybe people just prefer typing out ' instead of '.

Firefox 3.6.8, Windows 7 x64. Dev already fixed it though.


I MENTIONED IT FIRST DAMMIT

Forgot you mentioned the Search thing, but it was already on my todo list anyway.

When I made this post, payne had won the raffle three times in a row. He read this post afterwards. Now he only wins the raffle every other time.

I think we should still double-check the raffle code. He's probably exploiting the same glitch I mentioned. Ban payne from the raffle in the meantime; that mini moose guy also seems pretty suspicious .

Also, shoutbox: "/m" should be made to have the same functionality as "/w".

Saved shouts do not reproduce "/me". Saved whispers are able to be viewed publicly. Saved shouts also do not have timestamps.

Here's a bug and some tips for Devourer regarding the HTML of the Magic Boxes.

Bug. After you've picked a box, you can see who picked what box by hovering over the links that show how many minerals were earned. However, the links lead to "#", so clicking them forcibly scrolls to the top. If you want, I can add a "fake link" code to the CSS that allows you to make any element (including an A with no href) look exactly like a hyperlink; then, you can simply remove the href attribute.

Feature request. If you put an ID on the Magic Box table, it will be possible for skins to style it via CSS. Then, I could implement the below recommendations myself.

Feature request. You can make an entire cell clickable (rather than just the link) if you put an ID on the Magic Box table and then apply the following CSS. For the purposes of demonstration, I'll use the ID "sen-magic-boxes-table" in the code.

As a bonus, you can hover any part of a box to see who bought that box. (Basically, it expands the A inside of the table cell to cover the entire table cell. The line-height declaration keeps the text vertically centered (by setting the line-height to the same height as the entire element).)

This code will make the cursor turn into a help cursor when someone hovers over an already-opened box. Makes it somewhat more obvious that hovering reveals information.

why are only the first and 3rd quotes dark?

Because the alternating backgrounds for quote nests are hardcoded, ofc .

Probably fix that too.

Also, double-clicking "report" reports a post twice. Similarly, triple/quadruple/etc. clicks send identical reports. Kill the dialog on click rather on report sent.

I thought you were joking about me exploiting a glitch... but it seems like you really are thinking such a thing.
Ah, people and their Conspiracy Theory, nostalgia!

EDIT: I'd also -love- to know where you took from that information stating the glitch is about "taking the last ticket". I'm actually 99% of the time part of the two first to buy a ticket.

Can't, not with CSS. There's no way to do alternation by parent, and CSS3 is needed to do alternation by siblings. Here's what the skin does now, basically:

quote { background: black }
quote quote { background: grey }
quote quote quote { background: black }
quote quote quote quote { background: grey }
quote quote quote quote quote { background: black }

We'd have to keep adding more and more bits like that to support deeper nesting levels, as CSS doesn't have this kind of alternation-by-nesting functionality built-in. (Kind of stupid that it doesn't, but meh.)

That's a client-side problem, I'll move that to my v5.1 to-do list (though this would really affect all skins). Simple matter of making it a single-instance modeless dialog.

You can do the alternating with PHP + alternating in-line CSS. Or you can copy/paste ten times.

Write CSS classes to every other level of nesting? That sounds like a good solution.
no

Post has been edited 1 time(s), last time on Aug 22 2010, 1:34 am by NudeRaider. Reason: keep cool

The chance of payne winning the raffle this many times by chance is less than 1/15120, or 0.0066138%.

I still think something is glitched.

I agree...

He just has luck.
For every bought ticket a new entry in the database is made (only one! there is no way that someone can have two or more tickets). When the drawing time arrived, a random number between 1 and the number of tickets in the database is chosen (see code). Thus, he simply has luck, else the PHP random command is buggy, which is highly doubtable.

Finally convinced you all that he just got luck?

No, I want diagrams and pie charts!

This code snippet proves nothing. Even without understanding the commands I already see several other possible causes for a glitch even when the code you quoted is working as intended.
You were wrong too many times when you said "That's impossible" when I told you that something is buggy, so your bold statement bears no weight for me.

To be fair, the PHP rand() function can be relatively predictable. It'd be better to at least seed it first (with srand()), or replace it with the Mersenne Twister Randomization function (mt_rand()) which and also be seeded with srand (mt_srand()).

Assuming none of this is done already, and that's not pseudo code.