Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


 Content Type 



IPS4 Providers

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog



Everything posted by Biker.GA

  1. Yup. We're in the same boat. With the existing state of the 3.x version of IPB, it will be a cold day in Hades before we upgrade.
  2. This. I hate posting in a new forum and then being inundated with spam because I was automatically subscribed to the thread.
  3. The options are there, though. A "Super Moderator" has always been site wide, regardless of the software package used. If you want to limit what your moderators do, you should make them a forum moderator and adjust their permissions accordingly.
  4. However, that 240kb isn't just used once. Every single thread view by members and guests will raise that consumption by quite a bit. And that's IF the limit is 20k for an image.
  5. For tech support issues, especially those that are being driven by a regional issue, this type of feature would be a godsend. I don't know how many times I've seen a thread resurrected when the original issue was solved ages ago.
  6. What research? I wasn't asked and I didn't see anything in the forums asking feedback. We DO use this feature, and arbitrarily removing it does a HUGE disservice to those that did. Make it an option. And this mindset of "just modify your site" is getting old. I've been there, done that. Have the t-shirt, bumper sticker and baseball cap. I will not spend hour after hour redoing things after an upgrade any more. And if "just modify your site" is going to be the response after arbitrarily removing something that affects a lot of users, you can be rest assured we'll start looking elsewhere.
  7. I've often wished for this feature so members who are at work and get an email notification can respond via email as well, especially for those in environments where the business has blocked forum access.
  8. What do I think of it? I think it stinks. Features that I use were arbitrarily removed, the skin design stinks to high heaven, and I shouldn't have to heavily modify something "out of the box" when it's installed. Unless certain features are put back in, skiing will be a favorite pastime in Hades before 3.2 appears on my site.
  9. I have to agree with this. The common consensus seems to be if something was removed that you want, get a modification to get it back. That isn't the point. I don't want to spend hours upon hours redoing my site whenever I do an upgrade. I did that with the early versions of vBulletin and it got old in a hurry. Removing features that are redundant is a good thing. Arbitrarily removing features that many of us use is not a good thing. It's extremely unlikely I will upgrade to 3.2. And if further releases continue down this avenue, I'll be forced yet again to explore my options for a different software solution for my site. I don't know what the decision process was for 3.2, but from a customer standpoint, it wasn't much of a process if we, the customers, weren't asked about what we use and what we don't use.
  10. So? Why should users be told to go "Google it", when there was a nice tool available that they could use that did it for them. You're thinking like the old System Administrator who wants to keep the magic in the box. Make it easy for the users, not more difficult.
  11. I'm on the fence with this one. While I can see where it would be something that many could use, I think I'd like it to be optional as to whether it's shown or not. Just because it's shared across hundreds of accounts doesn't necessarily make the item newsworthy nor does it lend credence to the validity of the subject. Not to mention. I'm starting to get pretty sick of seeing +1 all over the place. Reminds me of previous fads that got old in a hurry.
  12. Why not? If a new customer can't decide on their own whether the software is good for them or not, hiding the "bad" posts won't make it any more popular. Some companies already do this on their website and as a result, it will be a cold day in hell before I use their products or recommend them to someone else. If your product is so weak that you have to delete/lock the posts that criticize it, your product most likely wasn't that good to begin with.
  13. If the recipient likes the PM, they can reply in kind. People are getting too hung up on the bloody like feature and it's being over used as it is.
  14. And there lies the rub. Small adjustment? It has taken a YEAR for my users to get fairly comfortable with the change from vBulletin to IPB. These are not "small" changes, nor would I expect these kind of changes in a minor revision release. And before Charles jumps in about "not getting hung up on version numbers", I'd suggest looking at virtually every other software company out there and what is usually considered minor version releases vs major releases and the changes that occur with them. This was not a minor update. This was a major revision I would expect from a major upgrade (ie, 3.x to 4.x). You want specifics? I'll give you specifics. The default skin is STILL geared towards "younger eyes". It's difficult to find things, and one shouldn't have to rely on something to "magically appear" in order to perform a function. What did you guys do? Go look at Xenforo, go "ooooooooooh SHINY!" and copy some stuff? If we had been that impressed with the stuff Kier was doing, we'd have gone with that package. Bah. You do what you need to do. However, if the software continues on in the current direction that it's taking, I suspect I won't be the only one looking for a different solution.
  15. Because that default skin needs to sell. While you may have the time and knowledge to sit down and redesign your site, there are many who do not. I should not have to buy a software package and be told to redesign it when I buy it. There are many here with that mind set, and that mind set is what gets companies into trouble. I should not have to redesign anything "out of the box". It should be visually appealing and usable as soon as it's brought on line. As far as I'm concerned, this was lost with 3.2.
  16. If 3.5 gives me the same feel that I have with 3.2, I'll know that this software is heading in a direction I will not wish to follow and will be looking for an alternative.
  17. I'm not sure I'll be updating right away, either. There's just far too much about the new style that I dislike. The package no longer has that polished feel "out of the box" and many of the style changes are not going to be popular with my users. I'm sorry. While I can understand the need to change and innovate, there's such a thing as taking it too far and trying to cram too much into one version change. And, IMO, in doing so, the product has taken a step backward in usability as well as not being visually friendly at all.
  18. Back to the topic at hand.... I mentioned this nearly a week ago. To me, the new style doesn't have that polished look that 3.1 has. I really don't like it at all.
  19. **sigh** I really have to wonder who's dreaming up the location of some of this stuff. Putting something like that at the bottom of the page is efficient? Lovely, another bloody edit I'm going to have to do.
  20. My mistake. Sorry. I had VNC on the brain when I read this. Saw View Topic and brain said View New Content. >.<
  21. What does viewing existing topics have to do with creating a new one? And bring it back? I just checked my site and it's not an option in 3.1.4, either.
  22. If one wants this, one should create an addon. This is something I would even contemplate adding to my site.
  23. Agreed. Color scheme should be consistent throughout the entire product.
  24. Where did it go? If it went on walkabout, it needs to be found and put back!
  • Create New...