SandraS

We need a toggle button to switch between visual (RTE) editor, which should be placed directly directly on the Fast Reply box, and Full Editor mode box. Right now, the only way to switch between modes is by going to settings --> Posting Settings --> Enable visual (RTE) editor

I know someone also brought this up, but I will emphasize it. We need expiring redirects (and the user can set the specified time in hours, days, months, or a custom time) for moved threads. Also, we need a way to manage and set existing "moved threads" in the ACP. For example, with the new update, existing moved threads will not have this expiring redirect applied. In the ACP, please add a section where the admin can view all moved threads, and set expiring redirects as desired.

Thanks! :)

Agreed. After reading this thread, and then wasting three and one-half minutes of my life watching that video, I am thinking about removing them from my forum - completely.



No doubt. We should focus on other, more important things... like watching the paint dry on the wall. :rolleyes: :rolleyes: You guys do a great job! I love the software and the mods many of you come up with.

When a member makes a post that is subject to moderator approval - it would be nice if this post appeared to the user, but stayed hidden to all other groups that cannot see such a post.

That way the user would know it has been made and secondly could edit the post prior to it's approval (subject to his editing rights on the forum)

It could then be marked as awaiting approval.

When I want to PM someone, I usually click their name or visit their profile page. Upon visiting either one I click the little PM icon, in which pops up the quick PM. In almost every case I'm sending a member a PM to include something he/she ordered, which requires a PM attachment upload.

However, the quick PM has no way to upload or go to the full editor. So I must then remember their username, go to the Messenger, compose a new message, type it out.

Is it too difficult to add a simple "Go Advance", "Use Full Editor" or something along those lines in the quick PM pop up, that can send the current data in the textbox, or skip it into the main large PM editor box.

All confusing analogies aside:

Improving performance is an ongoing process which we continue to work on. Don't forget that we host thousands of IPBs so performance is extremely important to us as well :)

Version 3.0.2 is faster than 3.0.1 which was faster than 3.0.0. We will continue to improve performance as we release each version, get feedback, do more research and testing, release new version, repeat. We have already received great feedback from users saying that 3.0.2/3.0.1 was a huge improvement from 3.0.0.

Yes this is definetly right....


Count me in

Agreed with AndyMillne.

The previous AJAX editing of descriptions was very handy and my moderators used it all the time.

I guess it is probably quite hard to program into the new IPB 3 version, but it'd be great if it could.

Thanks, Can we get a mouse-over button like the one for editing topic title please? Editing description now takes three clicks and three full page loads. when it used to only take one mouse hold.

I'm not sure if this is a bug, an omitted feature in 3 or just me being stupid but the ajax edit topic description doesn't seem to work when listing topics. There also doesn't seem to be a way of editing it from within the topic itself. Am I missing a fundamental change with IPB3?

Yes, we added that in. I wrote a function called IPSLib::wait( $seconds ). We felt that life was moving too fast and wanted to slow it down a bit. We think that huge delays in serving up webpages will be a popular feature. Even Google will do the same one day. Just imagine, having to wait for 5 seconds for your search results. I know, it's a crazy concept but I think many will appreciate it.

We suggest you think about a loved one or task to do in that 5 seconds. Maybe take a peek out of the nearest window. Your choice, really. We're giving you the gift of time, it's up to you how you spend it.

While we may test some things in beta releases of browsers, we can never properly support a browser beta release. They have their own bugs which we shouldn't be attempting to correct for.

When FF 3.1 or 3.5 or whatever version they decide to slap on it is released final, we will of course correct any problems within IPB that affect functionality in the new release. Until then, we have to code for Firefox 3.0, as it's the current stable release.

As for why skin bugs aren't worked through as quickly as others - there are several reasons

1) There's one designer and 3 backend developers
2) A lot of the remaining skin bugs are much more challenging to correct than earlier bug reports. Sometimes one bug can take several hours to correct, or requires huge amounts of code to be refactored to correct.
3) Rikki has other work to attend to simultaneously (such as the lofi skin) which may not be listed in the bug tracker, but still needs to be done and takes time.

Exactly. killswitch - I see you telling someone else not to skim your posts, but perhaps take some of your own advice and not skim mine. :) I never said release would be in June. In fact, if we released tomorrow (which we're not) it would be before June, and my statement would be perfectly accurate.

We don't know exactly when we will release. Contrary to what some here believe, we also do not base our release dates on our competition. We are setting goals for ourselves to release the software in a stable, working, reliable and secure way for our customers. If that means holding back the release for "6 months" from our original plan to ensure that everything is fully functional, stable and secure - so be it. This is a huge release, a big rewrite from the 2.3 series, and we are aiming to do it right, not "fast".

Uh, you misread my post. I said before June, not in June.

Additionally, we absolutely cannot release the forum upgrade without the components. Customers have purchased these components from us and it is our responsibility to ensure there are compatible versions available for the new version of the forums.