I migrated my last active vb site to Xenforo a few months ago. Now considering what to do with my IPB site.
The IPB Forum isn't doing well, because of my lack of focus on it. However, I had thought that by now 4.0 would be closer to a reality.
My users actually liked IPB 3.x more than Xenforo, but their engagement/activity trends revealed the opposite. I've since come up with a way to reduce the initial delay on IPB3, that was the primary contributor to going with Xenforo; just wish that there was some indication if my custom process is still going to be necessary with IPB 4.
I'm all for good software, but throw us a bone :unsure:
IPB is a different animal compared to other community platforms, but believe they have been very supportive. My problem has been finding the right strategy for user adoption of IPB.
I run a infrastructure design/config derived from years of paranoid thinking :ph34r: It is restrictive enough that both IPB and myself have been delayed on trouble resolution to a few past tickets. It's a challenge sometimes, but allows me to concentrate on my normal life.
You have to plan for the unexpected and test the recovery strategy. I've lost several of my sites many times over, meaning they were unrecoverable due to either infrastructure failure or security breach, but the end-user impact has been no more than possibly a few hours worth of missing posts. When a unrecoverable event occurs, I note what is possible, bring the site (or server) back from a backup, and address what I found afterward.
I'm planning to put up a few of my strategies on my blog soon, but are all simple to implement.
This isn't meant to be a criticism, but if you're concerned about "broken" content on an upgrade to 3.8; then it is a likely concern with IPB. I've never converted a vb3 site to IPB, but have been using it enough to realize that the two systems are not as similar as one would initially realize. My vb3 site uses cmps in a way that can't easily be converted to IPB and function exactly the same way, but it is still possible to do with some planning if an immediate need arose.
You might consider making a list of the issues you are aware of and sharing them with IPB Pre-Sales. They may be able to offer a solution.
I agree that it can add to the server's load, but would like to see this feature provided as an option. vbSEO's version not only takes out the unnecessary whitespace, but removes unnecessary comments (and inserts a few when strategically beneficial).
There is an auto-tag plugin I use on my R3Owners.Net vbulletin site that automatically creates a few tags based on the forum topic (unless the user adds them manually).
The problem with riders (at least on my sites) is that they find tags useful and click on them, but they don't like taking the time to add them. It may not be the perfect tag cloud, but it's not bad for a set of info that has been auto-generated:
I upgraded to Gallery 4.02, and admit that it has been a bit "rocky". However, the new interface is appealing to me. The use of whitespace is an issue, but the potential for increased disk storage isn't.
Regarding IP.Content, my initial attempt at using it was futile. When the latest update came out, I submitted a support ticket and worked with them over a few days. I was advised to uninstall and reinstall IP.Content. After some tinkering it does exactly what I want, and any user can submit new articles just like they were forum posts. If I need a completely separate page, it's not a big deal to do and I'll handle those on my own if the need ever arises.
I think the original approach of encouraging customers to learn the flexibility was too much take in. Now that I understand the basic Articles features, and have done a few customizations around it, creating custom/separate pages isn't complicated.