bfarber

We have never promised it with 3.0.3 so please be careful spreading assumptions or starting rumors. I HAVE said I/we would LIKE it to be available with 3.0.3, but that is certainly not a promise.

I think you can tell that my estimate was sarcastic. Nevertheless, it's been reported already, more than once. :P

To gain access to the peer to peer areas you just need to log out and back in now that your order has been approved.

If you do not use MySQL Fulltext you can use shorter search words (instead of doing a fulltext query, a LIKE '%keyword%' query is used, which is much less efficient). If you use Sphinx, you can configure the word lengths in the conf file. Using Sphinx generally requires you to have root access to your server, so you will likely only see this used on larger sites.

You can return results as threads by checking an option in the advanced search page, but there's no way presently to make it the default. This could perhaps be added to the usercp default search options I suppose. I prefer returning posts personally, but that's me.

Please PLEASE do not report this to the tracker. It has been reported 973492834783274 times already. It is indeed already fixed for the next version.

Your analogys are off. Mac OSX is more resource intensive than Mac OS9 HOWEVER, through out the 10 series, they continually work at improving resource usage and efficiency so that by the time you reach the end of the 10 series, it is as efficient as possible (and 9/10 more so than the first iteration of the series). As I've said before, Windows 7 is what Vista should have been. Really it's just an update to Vista, however Microsoft doesn't generally do releases in the same fashion. They release patches, or an entirely new version, and not much in between. To that extent, since Windows 7 is building and improving upon Vista, my analogy above still stands. Same with Firefox or Opera or Safari. Firefox 3 uses WAYYY more resources than Firefox 2. HOWEVER, Firefox 3.0.1 improved upon 3.0.0, and 3.0.2 improved upon 3.0.1. It's the same way here. IPB3 uses more resources than IPB 2 (as a blatant general statement - this largely depends upon the features you enable). However, 3.0.1 uses less resources than 3.0.0 did, and 3.0.2 improved greatly upon 3.0.1. It's probable that you will see improvements with 3.0.3 over 3.0.2. And this is what we've said all along in this topic. Over the lifetime of the 3 series, we will continuously improve the software so that it becomes as efficient as possible. You have to use analogies that match up here. :)

We will not be adding it back in. It inevitably leads to the "how can I reindex member numbers sequentially" and "how can I change my member number" topics from users who don't understand the technicalities behind it.

When you delete a post or topic, if you aren't using the trash can, we do not keep a record of the original post or topic content, so this is not possible. This suggestion has been made in the past, and honestly this is something that would be both challenging to implement in a stable fashion, but also in a resource efficient manner.

For the record, I added (in 3.0.3) ability to edit about me and status text when editing a member from the front end. It was annoying me that I had to login to the ACP to do this, since most profile spammers are now using the about me area. Signature and "website" fields are already editable from the edit member screen presently.

Generally at that point we call it a beta and put it in the client area. :)

Yes it does. It's managed through a hook. Submit a ticket if you're having trouble with that feature.

No problem. You're not the first, and won't be the last. ;)

Documentation is forthcoming.

I'm afraid we don't have the resources to do that sort of thing. When a fix is simple we sometimes post a patch. When it's not so simple, it would be an extreme waste of our time to try to post instructions for every patch and then have our support department have access to every patch. Further to that, the patches have not yet undergone QA testing, so it's possible they could break other things. While I'm sure when you are affected by an issue you want it fixed as soon as possible, we have to stick to some sort of organization that will benefit all of our customers in the most efficient manner. Fixing reported issues and then releasing an update to address those issues is pretty much the norm in this industry.

When you view a member in the ACP you can view all rep they have given and all rep they have received.

Why? Say you have a member who is really knowledgeable about a subject, but has surgery and he's out for 6 months, not visiting your site, etc. In the mean time, users sign up and ask questions, and other users try to answer them. Say one member responds to a question and, perhaps while trying to be helpful, gives really really bad advice, something that could cause a lot of problems. The original "good" member comes back, and sees this. I would say it's reasonable for him to give the user who gave bad advice a "thumbs down" for his post, and then post the correct answer. Random theoretical scenario and all, but you get the idea. To me, it's a better idea to just issue warnings to users who can't behave themselves, and tell them to stop acting up on the forums.

Everytime we start working towards the next version a topic like this pops up. As usual, it will be released when it's ready to be released. We cannot tell you when that will be, because we simply don't know at this point. Whenever we give estimates, if we don't meet those estimates we're met with a lot of feedback, so it's easier to just say, it's coming and will be available when it's done.

Bah, that was my mistake. I meant to say "XP". Edited my post. If your board does not give out of memory errors at 24MB, there is no benefit in increasing the limit. Mainly, the limit is included in php.ini as a way to shut down a php script that starts consuming too much memory. Changing it does not optimize your scripts in any way.

My guess is that guy searched google for an issue similar to what you were posting about/answering, came across the topic, and thought the answer was good enough to register and reply to the topic. Personally, I could care less how old a topic is when someone replies. That's just me though. I know different people, for some reason, dislike older topics resurfacing.

Because the RTE cannot accept any HTML, so you would be otherwise forced to only use the formatting the RTE allows. Many users complained about this, so we reverted back to a textarea so that they can use raw HTML properly without the system forcing the RTE formatting.

There are a lot of improvements we can work towards in the report center, but honestly it *is* more than a glorified PM inbox as is now. :) All reports of any content throughout the site can be centralized into one single repository. The report center features RSS feeds if you need to keep abreast of stuff reported while not actually logged onto the forums. Moderators can discuss the reported content, assign statuses as the report is being worked, and ultimately mark the report resolved. It prevents overlap with multiple moderators working separately on a single issue. :)

Why not? What if I did a search for a topic on this site and found a post that clearly and accurately addresses an issue, but it was posted 6 months ago? It may be the first time I've seen the post, and the author truly deserves reputation points for the post, but based on some arbitrary date cut-off they won't get the points?

I actually did respond to your question earlier. We always look to improve performance with each release (it is actually a specific release step that we take a certain amount of time out and focus solely on improving performance with each update). I would be surprised if we found a magic bullet though. Like "just remove this unnecessary line of code and everything's as fast as 1.3!", that sort of thing. :) As for your Windows analogy....Windows 7 is what Vista should have been. :P In that case it would be ... Windows XP uses more resources than Win2K Windows 7 uses more resources than XP :whistle:

People marked as spammers can't create new posts