IPS Management
  • Content count

  • Joined

  • Last visited

About Matt

  • Rank
    Chief Software Architect

Contact Methods

IPS Marketplace

  • Resources Contributor
    Total file submissions: 1

Profile Information

  • Gender
  • Location
    Cambs, UK!
  • Interests

Recent Profile Visitors

219,620 profile views
  1. Thanks all! We do work really hard on the product and try to balance new cool stuff with stability.
  2. Those that are having trouble, can you check to make sure the member_id and pass_hash cookies are actually being set in your devices?
  3. Did you choose to use 'Remember Me' cookies when logging into the PC? I've just tried those exact same steps, and I stay logged in just fine on my Mac.
  4. For those affected, are you checking the "Remember Me" checkbox to save log in cookies?
  5. I am not opposed to this.
  6. Hi Jack, I've just replied to your ticket, but as you posted this publicly, I feel it's worth replying here too. I was just asking for more information so I could make the correct fix. I wasn't trying to be difficult. In either case, you'll have a fix this morning.
  7. Hi all, Thanks for pitching in, we do appreciate your input. Our aim here isn't to cripple anyone's enthusiasm for helping us out by reporting bugs, neither is to try and diminish the importance of the bug tracker. What we're trying to do is find a way to streamline things a bit. During the course of a day, we probably fix a good few legitimate bugs reported via tickets. This means that while it looks like the tracker is sitting dormant, it is possible and indeed likely that many things are fixed but via tickets rather than the bug report. What we tend to do is work in cycles. We always try and find a balance between stabilising things and adding cool new things. When we do a stabilisation cycle, we will go through the tracker, which we're currently doing now if you took a look. You'll see we've created a few new categories to help key staff members order issues they will be responsible for. We've moved a lot of more complex engineering bugs that require significant work to our internal tracker so we can discuss how and when to resolve these issues. Of course, if it was a critical issue, then it would have been fixed by now because show stopping bugs tend to get our attention. As always, if you have a critical issue then a ticket is always the first port of call. That's what you're paying support for. I'm currently managing our top support tier and I'm committing bug fixes daily. So, to recap: we appreciate all your input. We love that you are enthusiastic and want to help us and we're not trying to diminish the importance of a tracker.
  8. "Sunset" I think we decided?
  9. Actually, it's a whole new system to highlight specific groups' posts and comments which is configurable per theme via the theme settings.
  10. As IPS 4.1 matures, we'll be switching gears to devoting more time in the bug tracker. One must keep in mind that we make dozens of bug fixes and changes a day based on tickets sent to us, so please don't think that we're neglecting the software.
  11. You can via editing the CSS, yes.
  12. Yep, @Mark Hhas a very busy 3.x forum that he upgrades as part of the QA procedure.
  13. I would do this: 1) Submit a bug report. Note it is a dev site. 2) If the developer working the report wants a ticket, submit a ticket quoting the bug report ID in the title of the ticket and re-iterate in the body of the support request that developer Z (Andy, Matt, etc) requested you submit a ticket. 3) Reply to the bug report saying that you've submitted a ticket and add the ticket number.
  14. I'm going to go ahead and lock this. RPG, we often butt heads in the bug tracker, and I don't think arguing semantics is really helping anyone. Feel free to contact me via a support ticket or PM if you want to talk or push for a code change because of feedback you wish to give.
  15. The best solution I can think of right now is that if you encounter a bug on a dev copy of your site, go and file that bug report and note it's a dev install. A developer will triage the report and if it requires more investigation, they'll ask for a ticket for access to that dev installation (assuming access is possible, otherwise this whole discussion is moot). We've done this a lot in the past. I consider a bug report different from a support request. We appreciate people taking the time to test and report issues, so we'll happily look at your dev installs if it fixes an issue we can't reproduce and has great impact on the suite.