Jump to content

Simon

Administrators
  • Posts

    14,358
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by Simon

  1. It's forum-wide. Options are moderation, suspension of posting rights (they can still read) or banning from the site. Each can be timed or permanent.
  2. That's more like it, I suppose. Nolgroth is going to be in a bit of a time-out until next February.
  3. Please refresh your memory of the rules of this thread -- while I'd like to test out some of the new moderation abilities in the site software, I'd just as soon wait for a better opportunity.
  4. Closing the browser entirely changes things -- that's dependent on the system and browser. Most will clear out all session data...and the days of having a "backdoor" cookie that gets you through the authentication are justifiably gone. Some browsers will hold onto session data when shutdown/restarted. This will apply for the duration of the session (30 minutes, typically...and in the case of this site). Close your system and go to bed, you'll have to login again in the morning. Other browsers will delete session data during their shutdown process -- when restarted, you'll need to login again. The "remember me" functionality in this case will apply to your user ID. The password will need to come from your browser's built-in password storage (which is more secure than the alternative). Hope this helps!
  5. Does Waikiki really have some of the worst traffic in the nation? As a recovered Chicago resident, I'm honestly curious... (currently loving a bad rush hour occurring when turkeys/deer/geese/ducks decide to cross the road and take their sweet time doing it...resulting in a 5 minute delay. Worst we've had is the horror of getting stuck behind a tractor as they're switching fields....and they tend to mount big pointy things on the front to discourage folks from getting too obstinate...or pick up hay rounds, never could tell which)
  6. It remains. The barrier itself is the effect of using the power -- just like the damage from a Blast remaining after you switch your MP to a different slot. Edit: Doh! I'm just realizing this is the 6E rules questions forum...I apparently need to get used to some of the new ways to browse posts. My apologies to Steve...and I hope I answered well ;-)
  7. More likely someone being stubborn and dismissing the browser dialog rather than making a selection...
  8. Within the thread listing for a forum, if you click on the small dot/star on the left of the thread title you'll be taken to the first unread post in that thread. The same applies when at the top level of the forums and looking at the fluid view, when looking at the activity feed, or any other area where threads are listed. Not sure if this is what you were after...but hopefully it helps.
  9. I'm curious how closely opinions on DST track with one's latitude. Up here in the Great White Nort (ok...I'm not _that_ far north), it's rather nice when daylight savings rolls around in the fall -- I'm no longer getting up before the break of dawn. There's a definite mental advantage there.
  10. Likely a browser issue (in that it's been working well for me on multiple systems and browsers). Check on cookie settings in particular -- that's what the site will be using for any functionality that spans browser sessions. There are some security checks in place on the admin side - it doesn't like changing an IP address during a session, so there's the possibility that there's a lower level of that kind of check on the user side of things...but that would only come into play with a change (or changes) in your IP address. If you're not seeing the "remember me" functionality working from the same location, then browser settings (particularly in regards to cookie handling) are your best bet.
  11. Round and round we go. You are not listening. So I'll save us both time and frustration: this "conversation" is over. You can either read through my responses and take the advice that I gave you, ignore what I've said and simply deal with it, or go away in a huff.
  12. I'm telling you that it has almost nothing to do with this site. The dialog that you're seeing is not generated by this site -- it is generated by your browser.
  13. Ye gods yes. Now that we're on a dedicated server, there are no more roadblocks to keeping up to date with the software (CPU or otherwise). That and the resolution of the issues with the rather large upgrade from our EoL version of the software to the current should make for quick, easy, and seamless updates going forward. There's a minor update/patch available now, but I'm waiting for the background tasks to complete from the current upgrade before applying it. I don't think there will be any downtime when applying the patch, beyond possibly a minute or two when folks are unable to access the forums. There's a minor version upgrade due out at the beginning of next year, purportedly adding to and enhancing the additional features from the current -- while that may take slightly longer to apply than the patches, it should still be a "one and done" process.
  14. Yup! It had been set to insert a new paragraph on enter...I've changed that to insert a newline.
  15. It is not -- the "issue" is within your browser configuration. Again, it is only peripherally related to the site at all -- the site is coded to utilize HTML5 notifications, so your browser will ask for your approval. That's as far as the site's code/functionality goes, the rest is on your end. I have received the notification on many sites. On this one, I allowed it, on others I declined...and that was the end of it. This has been the behavior across multiple platforms and multiple browsers.
  16. If you opted to turn them off prior to the upgrade, you're going to want to look in your preferences again -- there are a LOT of new ones, which will have been set to defaults. If you opted to turn off email notifications after the upgrade, check to ensure that all post notifications are correct in your preferences...and then wait a few days. It's likely just a matter of the background tasks completing. They're currently churning through the 2.5 million archived posts -- that process takes a couple of days on its own and needs to complete before things like "rebuilding profile fields" takes place.
  17. A couple of things on this: 1. The notifications dialog that you're referring to is common to most modern social/content-driven sites. It's a way for the site to alert you outside of the context of the browser window (e.g. notification center, browser badge, etc.) when there are notifications that you've selected to receive. It is not really a setting on the site so much as simply modern browser and HTML5 functionality. 2. Selecting "no" should dismiss the dialog and cause it not to reappear for this site for some time. Typically about a year. If it comes up repeatedly, you'll need to look to your browser settings. There should be settings regarding notification behavior (e.g. ask ever time, always yes, always no, etc.) as well as settings which would affect the persistence of your selection if that setting has not been altered. That's unfortunately about as far down that particular rabbit hole as I can go -- the rest is on you to handle within your system.
  18. The software that drives the site is a packaged solution from Invision -- not something that I've coded. What you're asking is akin to asking the IT head at your office "Microsoft Word asks if I'm sure I want to overwrite a file when I select "Save As..." and specify an existing filename -- can you add a checkbox to remove that?" (assuming you don't work for Microsoft)
  19. Not sure...given that I'm not seeing that when I click on a forum with unread posts, I'll assume that it's a setting somewhere in the software...will keep an eye out for it.
  20. Look around and test things out -- there's a LOT of new functionality added in. The mobile side has most of it, though some is a bit hard to spot. Make sure you try both mobile and desktop to see what's available.
  21. Continuing to test through things -- all looking suspiciously good so far. Which means I can take a moment, crack a celebratory beer, and explain the past year or so: We were on a shared server with Host Gator (after I got out of the hosting business -- it became _insane_ in both time commitment and price). This was great in terms of price, but Host Gator started putting limits on our CPU utilization -- shutting down the site when it got too high. This was a problem for several reasons: Our CPU utilization would routinely spike during "attacks". Some of these attacks were simple DoS (some joker pounding the search function for an hour or so), some more complex DDoS (as I started to block the simple ones). The only way to combat these was to limit the CPU load that the site would allow and disable a number of features that were either being abused or causing the CPU to spike through normal use. A new major version upgrade to the site software required a pretty significant change to the database that the site uses. Since the database has grown to be quite large over the years, these changes caused the CPU usage to rise beyond the levels that Host Gator would tolerate from us, causing them to terminate the process. Enter the frustration phase, as getting through those changes and upgrades would allow us to reduce the overall load that the site caused...but whatever. Normal usage of the site goes through surges. During prime usage times, the CPU load would increase to just shy of our limit...making the attacks noted in (1) much more successful despite my best efforts. So we opted to setup a dedicated (non-shared) server with Host Gator. While expensive (making me very briefly reconsider getting out of the hosting business), it would allow us to do all of the maintenance that we needed and go through the upgrades....and (hopefully) to re-enable a bunch of functionality that had been turned off. The new server was stood up in April of this year. After going through a fair bit of configuration and setup, I ran a test transfer and upgrade on the site...which is where all hell broke loose. Very little worked. Lots of errors in the upgrade. After a lot of back and forth with Invision (the makers of the software that drive the site), we finally managed to track down the major issue to a failing drive in the brand new RAID array on the server. So Host Gator rebuilt the whole thing. And I reconfigured it....and then continued to run into issues with the upgrade process. After a LONG period of back and forth with Invision (in which I tweaked out the configuration on the server within an inch of its life in the mistaken belief that it was the cause of the problems), we finally came to the conclusion that it was a problem with the upgrade process itself. This required MANY attempts at said upgrade (each of which would take up most of a day) and multiple escalations within Invision's support until I was talking directly with the developers. So then we started experimenting with fixes. It was a non-trivial issue (to say the least). We were losing all files from the Downloads section and from the Store (which means that while order history was showing up, no file downloads were possible or visible). Many of the attempts required allowing the background processes (which are currently running) to complete -- making any given attempt take approximately 4-5 days before we figured out what worked and what didn't. About two weeks ago, we finally got a custom build that gave us access to all files in the Downloads as well as all files in the Store (after Jason made some edits on the old site). There was some missing information in the background (things like tax rates, payment method definitions, and shipping methods/rates), but those were things that we (meaning Jason) could fill in while I worked through all of the software configuration settings....which is where we are now. Everything seems to be checking out, meaning I can finally breathe a sigh of relief, close out the longest support ticket in Invision's history, and monitor the background processes before applying a final update to bring us to the most recent release of the software (that'll happen in a few days' time).
  22. Pretty much. It went smoothly...but has taken a bit over six months to prepare for -- there were a number of "unique to our setup" bugs in the upgrade process which we had to work out. I'm sure that there's going to be a kink or two to work out, so test away.
  23. I think that the site upgrade is more or less complete at this point. There are still a number of background tasks to complete -- some manual, some automated. The manual tasks include updating shipping methods for the store and verifying that everything is functioning normally. This should be done before the end of the day. The automated background tasks are going to be running for the next few days and may result in some slowness. A few features on the site will not be available until the background tasks complete (some searching, etc.). Other than that, look around, have fun, play nice, and let us know if anything looks odd/out of place.
  24. Let me be clear: "cannot access the jar file" means you are running the command from a directory that does not have the jar file...or as an account that cannot see/access the jar file. It's pretty simple...and has nothing whatsoever to do with HD.
  25. Make sure you run from a directory that contains the HD6.jar file and which you have full read/write access to.
×
×
  • Create New...