Matt

I sincerely don't wish to antagonize but I would like to respond to the points raised here. Firstly, we do not ignore anyone. Our ticket system generally sorts by the oldest first. It's not like we see tickets and deliberately ignore them. We just work them in order. I think that a 17 hour turnaround on a conversion query is acceptable given the nature of the request. As mentioned above, you can call us if your site is down and this pages our hosting team. That's 24/7. You can also mark tickets as "Critical" if they genuinely are. This ensures that vital issues are taken care of ASAP. It's one click to remove the critical flag and another to remove that ability from a customer if it is abused. There is no way you can have "cheap", "fast" and "good". With all due respect I think that you are getting good service for the $0.66/day you're paying for your hosting account.

I'm sorry you feel that way. As stated in our standards of service page, we ask that you allow a 48 hour window for a reply. Of course, if it is urgent then you can make use of the 'Critical Issue' flag in the client center. This is for people who have a critical issue like their board is down, etc. I have looked up your ticket and I see that it was a general question regarding conversion that you chose to send into the Conversions and Transfers department. Ideally, that would have gone to sales as the C&T department is manned by fewer staff members than the technical support and sales departments. I realise that it's not abundantly clear but generally unless it is a matter dealing with an ongoing conversion or you are scheduling a conversion then you shouldn't need to send a ticket directly to it. If you would like faster guaranteed response times then you could consider purchasing a business license.

I'm actually currently implementing it with a default value of 365 but I'm doing it like this: It'll grab the user's last post (ibf_members.last_post) and then go back X days (last_post - ( 86400 * setting ). If there is no last post stored, it just uses the current timestamp to fire off the most efficient query. As expected, it didn't make any different locally. Will be interesting to see what it does on the company forums. This will be in 3.0.4

You mean the subscriptions manager you can download from your client center? Or another one we're not aware of? ;)

Just tested, and it's fine here.

Yes, we'll do that within the next few days as part of the beta testing.

Hello, The blog is an application that plugs-into IP.Board. There is no way to run the blog without an installed IP.Board. It was never designed to be a standalone product. :)

We are very much tied to MySQL's fulltext search. We have no control over that. However, boolean searching *is* broken in 3.0.2 (by boolean, I mean when you search for "hello +there"). This is fixed in 3.0.3.

And I finished it.

Indeed, this reinforces the need to ensure you are only handing out moderation privileges to those who can be fully trusted and who take reasonable measures to secure their own accounts.

I have been thinking about this a lot, actually. Nothing will be changed for 3.0.3 as we're close to wrapping that up but I do have a few ideas. My first one was to set a flag to note that a skin needs recaching instead of actually recaching it. This would mean that when the skin is loaded, it would check to see if it needs recaching first and if so, then recache it. This effectively distributes the caching over several page loads. The downside is that there may be times where an instant recache of one skin is required. I'll have to look into it more before committing code changes. Most likely we'll introduce the flag system along side the instant recache system.

I would suggest that you send in a ticket via your client center. If your support has expired, you'll need to renew that first.

Started to add this in. Means I have to finish it ;)

Ah, that's a good idea to add an option to "Flag as spam" when managing the validating queue. I'll try and get this in for 3.0.3

There's no need to forward a copy anymore, you can just invite them into the conversation. Is there a legitimate need to forward a copy? I ask without sarcasm. If there's a genuine need then we can consider adding it.

Bear! How are you? PM me! :D

Regarding the very first post: You have options now to allow a grace period for renewals. This means you can allow, say, 2 days for a renew to take place before demoting the member. You can also allow one to renew a package earlier than their expiration date. With regards to RC2: I'm working on it today. I'm hoping to have it wrapped up this week and final out soon after. RC 2 will be considered stable and we'll support it.

It's a fine line. Some people see an alpha product and judge it completely there and then even though it most likely has an unfinished interface and missing functionality. Typically we perform closed alpha testing and open it up to customers when most of the bigger issues have been fixed.

Yeah. I've thought about this a few times. After a few months the 'ip_address' is almost pointless for most users. Although the posts show the IP Address used for that post, if that helps and we have an IP look up tool that canl list all recorded IP addresses attached to a particular member.

The only issue with deleting PMs and Posts is that deleting posts is incredibly expensive. You'd certainly have to loop via refreshes in batches of 100 posts or so, I'd say due to the attachments check, topic and forum rebuilds. One thing the report center does currently lack is data on the person who created the item that was reported. It would be lovely to have their details to hand with links to "Flag as spammer" and "Warn Member". But then, the report center is a recent addition and its bound to mature over time.

Yeah, it's on our list. In the top half, I'd say. No firm idea when it will be added as we're still handling bigger issues.

It depends on the product, really. We don't have anything in alpha testing right now so it's hard to give a definitive answer. In the case of IP.Board 3, we opened up a preview board and invited all our members and customers to visit it, find bugs in the public interfaces and give us feedback. Typically we start with a small group and work outwards as development progresses. In the very early days there are bound to be numerous bugs and having more than a handful of people just makes it difficult to track issues.

The XML skin is one huge API, really. It's great for syndicating content and completely transforming how you display data.

Kind of. Once in the report center, you can click on the topic link at the top of the report center's page. Once the topic has loaded, click the mini-profile pop-up button () and click the mark as spammer icon (it's the first one; it has a red flag). Assuming you've set up your ACP's settings for spam management to unapprove their recent posts, this is all you need to do. Routinely, say every day or so on a busy board, you can then log into the ACP, click on 'Manage Spammers' under the 'Members' tab and delete or ban the members and remove their posts in one go.

Yes, sorry. We froze the download while we double checked everything was set. It's now been re-enabled.