Introduction and New Server for Forums!

[Guest Mr. Flamegoat]

Howdy, all!

 

Quick intro: my name is MrFlamegoat aka Matt. Some of you know me, many of you won't and that's okay. I'm stepping in to help out with the forums a bit more.

 

Firstly, we've moved the forums to a new server and there were a few hiccups along the way. Everything seems to be in order now though, and hopefully everything is moving quickly for everyone.

 

Secondly, if you notice anything out of place, broken, or that just seems wonky PLEASE POST HERE. I'd love to know and I'll be working over the next couple of weeks to update, polish, clean, and optimize.

 

I think that's it. Hopefully this move didn't affect anyone too negatively.

 

Look forward to the feedback, thanks everyone!

 

Update: Email Issues Resolved!

We're now utilizing a 3rd party MTA (sparkpost) to handle all outbound emails from the forums. This should be much more reliable than default PHP methods, as well as being faster and validated. Emails should make it to your inboxes more often while avoiding the doom and gloom of the Spam folder.

 

Emails will now appear as forums@minecraftforge[dot]net via a sparkpost hostname.  Apologies to anyone that had the previous address filtered!

 

Update: Code Highlighter

Added a code highlighter that I can modify and change. It should be forward compatible (I'm removing things that are not, as well as anything that changes core files to an unpatchable state).

 

Let me know what you guys think about it.

 

Update: Forums upgraded and theme has been updated a bit.

I've patched the forums to the latest available (2.0.11) and made some rather large changes to the current theme to bring it a little closer to the modern age. It's still a long way from where I'd like it, but hopefully everything feels a bit more professional.

 

I've removed a few things (team page, various little bits) until I can update them to all fit coherently together. If you guys have any thoughts or opinions on the style and direction, please let me know!

 

If you just don't really care, that's fine too!

 

Update: Code Highlighting mostly fixed!

Automatic detection of language is not terribly easy - sometimes your code snippet may default to a language other than Java. If that happens, you can specify from changing the code tag from "code" to "code=java" or other supported language.

 

I've added gradle/groovy as supported languages and can add others as required.

[Guest Mr. Flamegoat]

It should get quite a bit faster, too! Well, technically speaking. Might not notice it - but I'm doing my best.

 

We should be updating to the latest SMF in the next day or two. That should help quite a bit with some of the few hiccups left that I haven't been able to work out.

 

Feel free to yell in my general direction if anything is out of place, missing, or broken

[Guest Mr. Flamegoat]

Very likely, but not directly

 

I've fixed quite a few errors that may have been preventing other JS events from firing.

[Guest Mr. Flamegoat]

I was actually afraid people would get mad. It's not perfect, but it's the best I can offer at the moment.

 

I'm having to move modules around and get it prepared for the upgrade It's forward compatible, so it's on the list!

[SuperGeniusZeb]

Liking the new changes so far! (Especially the code syntax highlighting!)

[loordgek]

i like the speed 

it is so much faster now  :) :) :) :) :) :)

 

offtopic http://nl.urbandictionary.com/define.php?term=Flamegoat

[shadowfacts]

There's a slight bug with the syntax highlighter:

 

// Tools (After Enum it's; Harvest Level, Durability/Uses

 

The highlighter thinks everything after the ' is in a string, but it's not because the line is commented.

[Guest Mr. Flamegoat]

There's a slight bug with the syntax highlighter:

 

// Tools (After Enum it's; Harvest Level, Durability/Uses

 

The highlighter thinks everything after the ' is in a string, but it's not because the line is commented.

 

Yea I've got some work to do on the highlighter. Some of the themes don't have appropriate language syntax. Will update soon!

[Guest Mr. Flamegoat]

i like the speed 

it is so much faster now  :) :) :) :) :) :)

 

offtopic http://nl.urbandictionary.com/define.php?term=Flamegoat

 

Haha yea, that's me.

[Velken Iakov]

The Wiki button at files.minecraftforge.net is leading to 404 page (obviously because it is keeping the files. at the begining), I would suggest to fix it.

[Bektor]

If you post a log here in the forums the editor begins to lag after you pasted it in.

I don't know how long the log needs to be to let the editor lag, but I had the problems with a 500 lines log in a spoiler.

 

Besides that, nice forum update.

Finally something better then before with this forum. For me the old one had really long loading times compared to other websites...

Keep up the good work.

[Guest Mr. Flamegoat]

The Wiki button at files.minecraftforge.net is leading to 404 page (obviously because it is keeping the files. at the begining), I would suggest to fix it.

 

Hrm, I don't have access to files currently - but I will definitely pass that along!

 

If you post a log here in the forums the editor begins to lag after you pasted it in.

I don't know how long the log needs to be to let the editor lag, but I had the problems with a 500 lines log in a spoiler.

 

Besides that, nice forum update.

Finally something better then before with this forum. For me the old one had really long loading times compared to other websites...

Keep up the good work.

 

I will look into this ASAP. Not sure how much JS is running to process the text box at the moment, but it's probably due to that. I'll see if there's anything I can fix or improve!

[SuperGeniusZeb]

Found a bug (not sure if it was there before or not):

 

When typing a post, if you try to expand the editor box by dragging the double-lined bar at the bottom, it won't work. The double-diagonal line in the corner does work, however. Not really that big of an issue, but I thought I'd let you know anyway.

[Guest Mr. Flamegoat]

Found a bug (not sure if it was there before or not):

 

When typing a post, if you try to expand the editor box by dragging the double-lined bar at the bottom, it won't work. The double-diagonal line in the corner does work, however. Not really that big of an issue, but I thought I'd let you know anyway.

 

Released another major update to the theme. Tried to figure this one out but it appears it's been around a while.

 

No fix available at the moment without digging into the SMF editor and well, it's not good lol.

 

Might see if I can just hide it, that way at least it's not a visible broken feature.

[larsgerrits]

The "new" markers on the individual forum pages are broken. It seems like if there is at least one "new" thread, all of them have the marker.

I think it is. I just read a few threads in Modder Support, and when one of them got a new reply, every thread showed the "new" label. When I read the new reply, went back to Modder Support and refreshed the page, the "new" markers dissappeared.

 

EDIT: If you click the "new" button on a post without a new reply, it goes to another thread which does have a new reply.

[Velken Iakov]

As they say: fix a bug, now you have 99 more :v

The only thing that I found (which may be on my side only, cause I have shit pc and internet), is that when you click the + to expand at Forum History (at the Statistics Center), the Loading that pops up on the top, sometimes, flicks a lot, and may cause problems to people who suffer from epilepsy.

[Draco18s]

The "new" markers on the individual forum pages are broken. It seems like if there is at least one "new" thread, all of them have the marker.

I think it is. I just read a few threads in Modder Support, and when one of them got a new reply, every thread showed the "new" label. When I read the new reply, went back to Modder Support and refreshed the page, the "new" markers dissappeared.

 

EDIT: If you click the "new" button on a post without a new reply, it goes to another thread which does have a new reply.

 

This is annoying the fuck out of me.

As soon as I noticed it my immediate thought was, "What'd we do downgrade our forum software?"

 

 

But Larsgerrits is correct, the new button doesn't even apply to the thread it's next to:

 

[Guest Mr. Flamegoat]

Woo! Man, I made a mess of that.

 

I'm working on a fix ASAP!

[Guest Mr. Flamegoat]

The "new" markers on the individual forum pages are broken. It seems like if there is at least one "new" thread, all of them have the marker.

I think it is. I just read a few threads in Modder Support, and when one of them got a new reply, every thread showed the "new" label. When I read the new reply, went back to Modder Support and refreshed the page, the "new" markers dissappeared.

 

EDIT: If you click the "new" button on a post without a new reply, it goes to another thread which does have a new reply.

 

Got that fixed up. This forum software was written back in 2006, so the bulk of it is very difficult to wade through. It wasn't great when it was written, but by today's standards it's atrocious.

 

I've fixed more than 300 issues so far that consisted of mostly poor performance issues with a heavy peppering of security holes and issues.

 

The load time on server has been reduced from 0.280ms average (with several second spikes) to an average of 0.03ms. So hopefully that's noticeable and helpful to you guys.

 

Trying my best to test thoroughly, as I've finally got it to a point I can work on it offline and push updates appropriately.

 

Sorry for any issues that causes anyone, though. Please continue to let me know any issues that arise.

 

As they say: fix a bug, now you have 99 more :v

The only thing that I found (which may be on my side only, cause I have shit pc and internet), is that when you click the + to expand at Forum History (at the Statistics Center), the Loading that pops up on the top, sometimes, flicks a lot, and may cause problems to people who suffer from epilepsy.

 

Hrm, I haven't seen this just yet, but I'll keep testing and see if I can fix this up.

[Draco18s]

Got that fixed up. This forum software was written back in 2006, so the bulk of it is very difficult to wade through. It wasn't great when it was written, but by today's standards it's atrocious.

 

Glad you fixed it.  And I hear you on wading through 10 year old code.  Hell, some of my code from only three years ago I take a look at and go "thank god there aren't bugs in there, because fixing them will require a total rewrite."

[Velken Iakov]

the redirect "NEW LOCATION HERE" on the Mods board leads to a 404

 

 

 

 

 

 

 

 

[Bektor]

This forum software was written back in 2006, so the bulk of it is very difficult to wade through. It wasn't great when it was written, but by today's standards it's atrocious.

 

The load time on server has been reduced from 0.280ms average (with several second spikes) to an average of 0.03ms. So hopefully that's noticeable and helpful to you guys.

This with the load time is really the best change. The first thing I noticed, the second thing were the changes made to the theme.

 

If the forum software was written in 2006 and if it is so bad, why not changing to a more modern one and a good one? Wouldn't that help alot?

[LexManos]

If the forum software was written in 2006 and if it is so bad, why not changing to a more modern one and a good one? Wouldn't that help alot?

Once the transfer is fully done and everything is stable. The plan is to re-evaluate all of the systems we use and look into better solutions. But the important part is to make sure everything is stable/cleaned up so we can get a full lay of the land.

[LexManos]

If the forum software was written in 2006 and if it is so bad, why not changing to a more modern one and a good one? Wouldn't that help alot?

Once the transfer is fully done and everything is stable. The plan is to re-evaluate all of the systems we use and look into better solutions. But the important part is to make sure everything is stable/cleaned up so we can get a full lay of the land.

[Guest Mr. Flamegoat]

If the forum software was written in 2006 and if it is so bad, why not changing to a more modern one and a good one? Wouldn't that help alot?

Once the transfer is fully done and everything is stable. The plan is to re-evaluate all of the systems we use and look into better solutions. But the important part is to make sure everything is stable/cleaned up so we can get a full lay of the land.

 

This. The reality is, the more I can clean it up and smooth things out now, the easier it will be if and when we decide to migrate to something else. I'm just the guy cranking the cogs right now, so I don't want to speak out of place.

 

I echo Lex, I want it to be clean, stable, and secure for you guys. I'll keep doing my best to make sure that's how it goes