What was quite literally my #1 development issue on the forum is now a working feature!

If your front page sidebar doesn't look like this:

Then you need to force reload the page a couple times (hold Shift while reloading).

Note that filters will *not* filter an event that you've RSVP'd for (those are always visible).

Enjoy. :)

- No text -

What was quite literally my #1 development issue on the forum is now a working feature!

If your front page sidebar doesn't look like this:

Then you need to force reload the page a couple times (hold Shift while reloading).

Enjoy. :)

I saw the check-boxes and was like :O

and then you made them all fancy toggle switches and I was like :D

Any way to have your settings persist?

You. Are. Awesome. Now I don't have to look at events from inferior consoles!

Thanks!!!!

- No text -

Any way to have your settings persist?

Already there. As long as you have JavaScript enabled (which is usually the default for everyone), those settings will persist across logins and browsers. Whereas the RSVP settings are stored in the current session (and seem to be quickly forgotten), the Filter stuff is actually saved to the database, so it follows you whenever you're logged-in. I'm planning some changes to the RSVP system in the future (and actually laid some foundations for that with this update), so we'll be moving that stuff into the permanent-storage database at a later date. :)

- No text -

- No text -

Any way to have your settings persist?

Already there. As long as you have JavaScript enabled (which is usually the default for everyone), those settings will persist across logins and browsers.

Weird. I have Javascript enabled in Chrome, but my settings get reset every time I refresh.

- No text -

Javascript enabled (at least according to this). Using Chrome 42.0.2311.135

- No text -

It's working here on all browsers.

Checking things… Stand by…

It's working here on all browsers.

Checking things… Stand by…

Yeah, not working here at all. Using Chrome, as well (MacOSX, Version 42.0.2311.152 (64-bit) )

I cleared cache data, loaded the forum, saw the new buttons. Good.

Unclicked the PS options; only Xbox items left. Good.

Clicked 'DBO Forums' link at the top of the page - all four platforms visible again.

- No text -

It's working here on all browsers.

Checking things… Stand by…

Yeah, not working here at all. Using Chrome, as well (MacOSX, Version 42.0.2311.152 (64-bit) )

I cleared cache data, loaded the forum, saw the new buttons. Good.

Unclicked the PS options; only Xbox items left. Good.

Clicked 'DBO Forums' link at the top of the page - all four platforms visible again.

Just tried Safari.

Click forum bookmark. Shows new interface. Good.

Unclick PS options: shows only Xbox. Good.

Hit Command-R (to reload the forum): all four platforms visible.

- No text -

Same on Chrome in Windows.

Maybe you forgot to comment the "IF (user!=Beorn): saveflag=False" line?

- No text -

Nah, it's clearly a local reference issue: SaveStateTo: "/Volumes/Beorn'sHD" else FailSpectacularly

He always knows how to fix these things.

;-)

I think there has been only one ever.

Nice feature, Beorn. I don't need it myself, but I can see the need for others.

- No text -

- No text -

- No text -

- No text -

- No text -

- No text -

- No text -

- No text -

Have I told you lately that I love you?

;p

I honestly wouldn't be surprised

No prob.

Notice how Bungie has taken a number of my suggestions and made them real, for instance, removing the damage upgrade / defense upgrade nodes on gear.

Where's my check guys?

How about this one:

Players drop their heavy ammo when they die, but only if they are killed by a primary or special weapon. Think about it!

Okay, so… Cody was right. That little hiccup was an issue with "not enough testing" on my end before publishing. For those who even care about such things, here's the skinny…

There is a "FTB settings" table in the database exclusively for storing information related to your FTB preferences. Right now it only contains the filtering options, but later it will hold RSVP info and, maybe, other things.

Here's the rub… the system only creates a database row for you only if you've bothered to set any preferences at all. If you don't have preferences, it returns a null data set with empty placeholders for various options. This is how the rest of the code knows whether or not you've set preferences or not. The first time you do set a preference, it's supposed to create a new row for you that's populated with data instead of null values, and the code reacts accordingly.

Only that whole "return the empty placeholders" thing wasn't actually working for everybody else but me. Because I tested the system immediately after publishing, there were no rows in the database before me and everything worked as planned. But when everyone else tried to set preferences, the database was returning my account's preferences instead of a blank row. This meant that the database thought it didn't need to insert a record, so it was attempting to run UPDATE operations on rows that didn't exist. Thus, no data got saved.

Turns out I forgot to insert two characters (a = and a 0, in that order) at the proper place in the SQL query. After I finally tracked down what was happening, the fix was easy.

I really like explanations like this. I also am very familiar with similar order of mistakes. They happen ALL the time. Don't worry, Beorn, we don't hate you.

...yet.

- No text -