Jump to content
Invision Community


  • Content count

  • Joined

  • Last visited

  1. Support is useless !!!

    As your team works so closely with the code on a daily basis, they might not realize that the documentation they write may make sense to some of the audience but not all. The documentation you have provided in support of IPS Connect and other products most certainly could benefit from some additional details and examples. You don't necessarily have to start from scratch, sometimes clarity can be provided by simply rephrasing a couple of sentences. It might be beneficial to provide your customers with a better understanding of the use cases where IPS Connect might be appropriate (or not) as it might allay misunderstandings and frustration on both sides. Your SSO Service package could also benefit from a better explanation as to what additional functionality your value add-service provides over that of IPS Connect. When people have a better understanding of the complexity of implementing a well executed SSO, they will appreciate the "value" it could bring to their community and be more amenable to the cost of your consulting service.
  2. Minimum characters in post

    Instead of resorting to "software" engineering to solve this issue I would recommend that you engage your community in a little "social" engineering instead. Encourage them to communicate more eloquently and express something "meaningful" each time they comment. You might consider reaching out to a handful of members that show a natural talent for communication and work with them to come up with an innovative approach to engaging your entire community around addressing this issue.
  3. Why have you forsaken blogs?

    The collective information technology experience shared amongst all of IPB’s clientele would be compelling if we all shared our backgrounds with each other. We all have a vested interest in IPB being a success for the long term and some of us would actually jump at the chance to be of service to the community in some fashion or another if we were simply asked. The product(s) could exponentially leapfrog ahead with the help of a select group of customers helping out with targeted bug detection, documentation, product demonstration pages, forum support, etc.
  4. Why have you forsaken blogs?

    I am one of the non-vocal customers who has purchased all of the IPB products and has been paying renewal fees for years in the hope that one day IPB would address the many shortcomings of the products and I wouldn't have to spend a fortune on developers to meet my needs which might not be all that unique. Great strides have been made on all of the other products, but the Gallery and the Blog need additional features before I could actually use them and neither product seem to get much development resources allocated to them. Every time IPB has released a new version I check the release notes to see if either of the products has received any kind of attention and invariably they don’t. What I find interesting is that I have never once received any kind of inquiry from IPB asking for my feedback via any means about any of their products and I’ve been a customer for a long time. I would welcome a better approach going forward to engage your customers in determining how your products should evolve (or not). If IPB does decide to slow down development, eliminate a product, or refuse to add some particular feature, a better mechanism should be implemented to allow the developer community to step in (in timely fashion) and provide a solution if customer demand warrants it. I think there is “customer demand”, for further development of both the Gallery and Blog, maybe not overwhelming but there all the same. How can IPB better meet the needs of this portion of their client base?
  5. Testing IPB 4.0 Blogs

    Why isn't the "Blogs" hosted on this website being populated with customer blogs to help beta test the product and to allow your customers to see how the product has matured since the 3.x version?
  6. Feature Plan

  7. Documentation Is Hard to Find

    The more features that IPB adds to their software suite and the more configuration options they add the more complex the product becomes. People interested in hosting a IPB site typically have a limited amount of time each day they can devote towards operating their site and have little time to spare to try to intuit their way to being able to understand how to setup their site correctly and to deal with various issues that crop up. I would strongly urge IPB to take a small break after they release v4 to work with the user and developer community to determine what areas could benefit from some documentation and then launch a community based documentation project who would work with the IPB developers to answer specific questions that crop up during the documentation process. If this project was broken down into small bit sized pieces the user community is more apt to be willing to lend a hand and a lot of useful content might end up being generated in a short span of time and IPB could then go back to devoting their time coming up with new features to dazzle us with.