Mark

That error means "Error returned from library trying to save comment" - as Andy says, you should report that to the bug tracker.

If your forum has a large amount of posts, you will be asked if you want to run queries manually. You will be also asked if you want to skip the PM conversion stage and use the command line tool which is in the 'Tools' directory of the IPB distribution.

It will be in the "My Apps" menu There's a bug report open about them... I assume they'll be removed.

When I first saw this thread, I thought Lee was joking... it's been 2 weeks and 4 days since we said '2 weeks'. RC 1 will be out very soon, I promise you. You can see the QA team have been submitting bugs for the past couple of days which should tell you that the release is imminent.

You might change your mind when you start getting bouncebacks ;)

Well the perl script will create the key parts that needed for any application - to add more sections you would just copy the files, or to add another module, copy a directory and update the xml. Applications house modules - the application folder has two directories 'modules_admin' and 'modules_public' - and the modules house sections, which are represented by a PHP file in the relevant modules folder. While it can be a bit daunting creating your first application, it's easy to pick up and once you get the hang of it, you'll find it much easier than the 2.x components system. There's no real need for Admin CP tools to create application structures or anything like that - I think it's more likely to confuse novice users, and really, the system can only hold a developer's hand so much.

1. The mark entire board as read? It was always at the bottom :blink: 2. Gone 3. That's a fair enough point... things are bigger. 4. Click your name and then "My Gallery"

We can understand that some people won't like the default skin - as said, it's impossible to please everyone, and for that reason, we will be shipping two skins with IPB 3 though, the second will be whichever skin wins the contest, so make sure you cast your vote for a skin that you do like ;) Of course, if you have any specific feedback on how we can make the current default skin better, we'd love to hear it :)

I think the only reason iPhone and Blackberry are the only ones on the list is because almost everyone at IPS has one of the other :P I'm sure agents like opera mini and IE mobile will be added to the user agent lists for the lofi skin once it's been finished and we can test it works on those... if not you can always add them yourself, it's done through the ACP ;)

In future, you should send in a ticket :)

Yes, but it's not an easy task. I'm actually changing the way the converter script works so in future it will be much simpler to do... But at the moment, one of our technicians would need to do it for you. If you send conversions@invisionpower.com and Email, mention whether you'll be buying an IPB license or one of our hosting packages and which license/package, and we can get you a price for that :)

I had to check, but yes it should :)

On 2.3? Add to conf_global.php $INFO['fake_mail'] = true; Instead of sending mails it will log them as to files in the /_mail folder (which should obviously be created)

:rolleyes: I like how we're at RC of 3.0, Alpha of 4.0 and beta of 12.0 all at the time time....

We just posted a development update :) Really, people keep suggesting weekly status updates - but what are you hoping to read? All you'd see is "well this week we fixed all the known bugs and released beta 5" - trust me, I read everyone's weekly reports, they're boring. No :)

[quote name='tera

Do you even have access to the betas? I thought you opted to not renew your license? In which case, are you just going by the count in the bug tracker? There are always bugs in the bug tracker - at the moment we're in QA stages so we have people whose job it is to look for bugs, of course bugs are going to be found - that doesn't mean the software is unusably buggy. And we know there's a big gap between beta 4 and beta 5, the reason is because we want everything ready for beta 5 before we move into RC - we don't want new things being added in the RC stages, obviously and so things like help files, final changes needed for the components, finishing the MSSQL driver, making sure we're XHTML valid etc are being done before beta 5 is released. Hence all the "4.1" and "4.2" - in the past these would have been new betas (they're new builds) but what we want to be beta 5 isn't ready.

Yes :)

:rolleyes: Brandon said "I'll simply say that our target release date is before June." - that is quite different to "Our target release date is in June." which is how it looks like some people read it. And people wonder why we don't like to mention dates.... That is the plan

We will continue providing tech support for 2.3.6 for the forseeable future, but there will be no more updates.

While obviously I haven't looked into this fully, nor do I have say over what features are added - I think it may be a little more complicated than you are thinking, this is just off the top of my head: 1) Searching - the search engine would probably need a bit of a rewrite to accommodate this 2) Permissions - what if they have permission for the alternate forum, but not the main one? Can they see the topic in the alternate forum? If no, it would be too resource intensive to work, if yes, well then, we have a bit of a permissions problem... 3) Moving - what if the thread is moved? Does it move from the forum it is moved from? Or both? What happens if you try to move the topic in the alternate forum to the main one? The move function would have to be rewritten a bit however that is decided. 4) Deleting - if you delete one, does the other delete? The delete function would have to be rewritten a bit. 5) What if someone wants to add an alternate forum after posting? We'd need something to accommodate that. 6) What if someone wants to remove the alternate forum after posting? Even worse, what if someone wants to remove the main forum and make the alternate forum the main forum? We'd need something to accommodate that. Personally, I think it would be a bit of hassle for a bit of strange feature - in what circumstance would you need this? There might be a better solution, such as allowing announcements to have replies, maybe?

Guys... relax. We're not going to get a team of lawyers to sue you and send repo men to your house to collect money for damages because you used "invisionpower" in your domain. If you want to use "invisionpower" in the domain, submit a ticket in the client area and we'll send it to the management who can discuss the situation further. Like Lindy said, creating resource sites is appreciated, and we're going to be working with you to defend our trademarks, not against you :)

We were actually talking something similar to this the other day. I'm not sure if it will actually happen - but I'll shift this over to the feedback forum so the right people see it.

Just because you would like it doesn't mean everyone does. In my opinion, AJAX is fantastic when it is done right. Not only is it good aesthetically, it has useful practical applications (such as the aforementioned video scenario). Unfortunately, it is rarely done right when there is a lot of information to process. There are so many different browsers which handle it slightly differently, it's a nightmare to code, confusing for the user when it doesn't work (but most likely submitted the content, just not returned it) and often done for little more than the sake of it. Even sometimes when I post a comment on YouTube, the submit button greys out and gets stuck on "Posting..." (or whatever it says) - then if I reload, sometimes its there, sometimes its not, maybe that's because the person posting the video has comment moderation enabled? Who knows? Not the user ;)