bfarber

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.

I'm seeing an increase in profile spam on IPB forums. I think there need to be a lot more solutions to combat that.

A lot of times these people just register and don't make any posts, so the profiles go unnoticed with website links and signatures that are inappropriate.

Maybe a minimum post count to set a signature and website link? at least it will get rid of the basic spammers. just thinking out loud

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

Quick question.

During the upgrade phase from 2.3 to 3.0 final, will the past subscriptions be remembered along with existing packages? I installed ipb 3 beta 5 on a test board and upon registration page the packages weren't available. I suppose this was done intentionally since subscription manager hasn't been released.

Data should be retained, yes :)

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)?

You gotta be kidding me! Isn't there a way to downgrade to 2.3.6 now anyway? Restoring an older DB from when my forum was 2.3.6 is something that simply cannot happen... After the upgrade to 3b4 there have been posted about 200 posts...

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.

What about those impatient ones who have already upgraded their live boards to a beta version of IPB3? How can they upgrade to the final version once released?

I am asking this because I'm one of those guys... :P

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.

Will there be support provided for upgrading from 2.3.6 to IPB 3 RC 1?

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.

Huh what? Where did you hear this? Pretty sure the people reporting bugs in B5 now are just the staff/QA team and will eventually be released to customers when they feel it's time ;)

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.

1) This was reported as a bug, and should be fixed for #3

2) The issue only crops up when you import the *same feed* more than once - you can import multiple separate feeds, but we never really planned for someone to import one feed multiple times into their forums.

Please report bugs to the bug tracker.

My understanding is bfarber means, they want to iron out all the current bugs and skin issues, get the RC out and then for next versions of 3.x.x consider adding new common ideas that members request...

I could be incorrect but would only make sense in order to not delay the RC build more than needed.

bfarber, do you think we are going to see a beta 5 or would it be possible with an extended delay to release RC soon? Just curious.

Exactly. We will look at feature suggestions when we begin work on 3.1 or whatever.

We will see a beta 5, yes. That is the plan right now at least.

IPB generally try and keep there features different from VB, cool feature though I agree.

We don't try to keep the features different or similar to any other specific product. We try to keep the features in line with what is requested by the majority of our customers.

However, we are at a beta 4 stage and are not introducing new functionality where possible, so I'm afraid any new features will have to wait until the next version.