• Content count

  • Joined

  • Last visited

  1. IP.Content is little complicated and not friendly using

    IP.Content is great for pages and records, but is nothing close to a usable wiki. No name-based links means hyperlinks are just too painful to bother adding. The category/record organization is very inflexible and not useful for most applications. My users just won't use it, and keep asking for MediaWiki. Unfortunately, the guy who wrote a bridge disappears every 6 months, so good luck with support for that.,
  2. Show pre-coupon subtotal

    When purchasing multiple products and using a coupon, if you show a bigger price and then a smaller price, it makes the smaller price look like a real bargain. In the example below, if the subtotal $2997 were shown, it would make the final price of $1498.50 seem like less.Here's an example:
  3. Mobile Apps Status

    As a mobile developer myself, I think native > web app. Facebook recently came out and said they made a mistake using HTML5 for their mobile app, and are working on a native app. Web apps are slow and can't match the user experience of web apps.Personally, I would like a well-defined Internet API so that I can implement my own native app for mobile. You guys are not software developers, you are PHP scripters. Just give us the API and let the software developers make the native apps.
  4. IP.Board 3.4 Dev Update: Bulk Mail with Mandrill

    I would like to be able to have pre-made emails set up that go out to a user at set intervals after they create their account, and when changing to a certain user group. I would have it set up so one week after ordering our product (and getting moved into the user group for paid customers) they receive an email reminding them of cool product benefits, etc., to minimize post-purchase dissonance. Another one would go out after six weeks to make sure we keep them as a customer.
  5. Bring back database callbacks

    I am satisfied with this solution. Thank you.
  6. Bring back database callbacks

    Please add database callbacks back in the next update of IP.Content. We had some stable reliable code we use that runs on this. With it removed, we now have to find and hire a programmer to rewrite our old code, and we're out an extra $500-$1000 (plus the time spent recruiting, reviewing, and testing) just because IPS decided this wasn't the "right" way to do things.
  7. I disabled our gallery upon upgrading to IPB 3.2

    Since there is no reply to this, I am going to commence with hiring someone to transfer all our member gallery images into a custom database, and we will create our own gallery application. This is terrible.
  8. IP.Content 2.3 Dev Update: Nexus Blocks

    Here's an idea: a wish list for each user, including IP.Downloads items. Steam has this: A lot of people end up buying each other games, especially around Christmas.
  9. This is a terrible idea. You should create a custom database for YouTube video IDs like I did, or IPB should create an IP.Videos product. The gallery needs fewer features, not more.
  10. IPB 3.2 feels much faster

    Is it faster? It feels like all the pages are loading much much faster than the previous version.
  11. This is so bad, I won't even let this out on our site. I'm looking into migrating all our gallery images into a custom database. IPB 3.2 is a very good upgrade, but what the hell happened with the Gallery? This is literally all you have to do. If the user has gallery categories, just display the most recent image in each category, like the old gallery did: Instead, what you have is so complicated, I'm not even going to unleash it on my users, because I can't even understand what's going on, and I'm a programmer.
  12. IP.Content 2.3 Dev Update: Improved Relational Fields

    I didn't even know this existed. That's pretty useful.
  13. I'm late to the 3.2 party because I run a large and complex site, and it took a while to design a new skin for IPB 3.2. The new gallery turned me off from 3.2, and I still think the gallery is bad, but the rest of the new design is actually quite nice. It's been cleaned up a lot, and seems much more consistent. The elimination of separate photos/avatars was good, as well as the uniform avatar size and the new tags feature. Overall, I think this was a big improvement to IPB that improves cohesiveness and usability of the system.
  14. Interesting. There are RSS feed aggregators that will combine and sort items, too. Still, I think we are going to use a single forum and rely on tags, since that is pretty well implemented.
  15. Let's say I have a forum that is only a category. Not a top-level category, but a forum that acts as a category, and cannot be posted to: Fruit And this category forum has four subforums: Oranges Bananas Apples Lemons When viewing the "Fruit" forum, it would display the four subforums at the top. However, it would also display the most recent 10 posts from all subforums in a feed below that.