bfarber

1) Each user agent has to be mapped - we've only done blackberry and iphone so far 2) The lofi skin isn't done yet, so I wouldn't really try to test it yet

The lofi skin is going to be one of the last things we finish, because it's basically just a stripped down version of the main skin - and we want to ensure the main skin is "done" before we create the lofi skin based off of it (to prevent having to apply bug fixes to multiple skins and so forth).

Most likely because it only started happening since uploading some changes Thursday or Friday. We'll look into it. :)

The link is for debugging, and a link to the topic with more information has been posted. I think that answers your original questions. Topics about "swine flu" or other non-feedback topics should be kept to the general chat forums. ;)

SMF can be converted, yes. You should email sales, as suggested, to find out exactly what will or won't be preserved.

It's not a bug, so I wouldn't post it in the bug tracker. It's a simple enough suggestion, but right now we're simply concentrating on finishing up what we have now. Might be something to revisit in 3.0.1 or something.

For future reference, you can click "Tracker" at the top of the page to access the bug tracker. :)

Yes

Yes, that works for 3.0. It's how my localhost dev environment is setup.

So don't post such long titles :P

Hmm. Couldn't you just use the warn panel. Use the reason field for the admin notes, use the ban member feature, then elect to send them an email using the appropriate fields? Seems like all of this functionality is already there in the warn panel if you ask me.

You can already do this by 1) Don't let default members group edit profile 2) Auto promote to a new group that can edit profile after x posts

Yes, Matt posted some info in the customer lounge on it.

Done

Yes, it has been discussed and posted elsewhere already. :)

If you have mod_rewrite available you can get rid of index.php in the URL. If not, you can still use friendly urls but it will be formatted like so http://domain.com/forums/index.php/topic/12345-Topic-title

I won't promise one way or another just yet. Ideally the data will be retained...but I can't make any promises just yet until it's fully converted and the compatibility can be properly checked.

Are you looking for help modifying this for your own user, or making a feature suggestion (as this is not possible presently)?

I'm afraid we've stated over and over with every beta release NOT to update your live site. We said it would not be supported, and we've publicly stated that we did not expect to end up releasing an upgrade path from betas to final. The only reason the upgrader is available presently is purely for testing. I'm sorry that you are in this position, but it is not something we will likely be able to accommodate. Your work load may not be as big as it seems, hard to say. We do have a database checker int he ACP that will fix any database problems it can find - so long as you are able to access the ACP.

Umm...you might need to restore a backup. Or update manually somehow. I'm really not sure tbh - you'll be kind of on your own I'm afraid.

This isn't something that is feasible in a product such as ours, where it can be available in so many environments. You would really need to find someone to build you a custom modification to handle something like this.

We do not provide support for any beta or RC release.

I don't know if any of the RCs will be encoded. Last I heard - they wouldn't be. We have not promised an upgrade path from betas to RCs, and in fact have quite frequently stated it is very likely there *won't* be such an upgrade path. It is extremely likely that when RC1 is available, it will only allow you to upgrade from 2.3.6 or lower to RC1, and not from any 3.0 betas to RC1. We don't know for sure yet, but there have been many upgrader/installer bugs that as they get fixed can't be retroactive. Do not plan to use a beta and upgrade to an RC release. It may or may not be possible.

Exactly. With the first wave of betas we've kind of just been pushing them out there without full QA procedures being followed internally. They were early betas after all, and we knew there were bugs. As we approach finalizing the software we're just getting back into the habit of properly QA-ing the software before releasing it is all. Beta 5 will be made available to everyone.

Bashers...I'd recommend you just wait for final if you can't handle there being bugs in the software. Even then, I don't know that you'll be pleased, because I can guarantee that 3.0.0 final will have bugs in it. As will 3.0.1. As will 3.0.2. And 3.1.0. And every other release. We are putting in all our efforts to ensure that the 3.0.0 final release is as stable as humanly possible. There are more code changes in this release than virtually any other release we've ever put out (definitely more code changes than any release I've personally been involved with) so we've been taking our time to make sure we get things right. If this bothers you, and you'd really we just rushed it, then I can only recommend you step back and just wait for the final release. We will publicly announce it when final is available.