Why don't you fix "go to new post" here on vb.com?

[Ramsesx]

It's just a work of max. 5 minutes, vb germany did it already why can't this done here?

[Mike Anime]

It's just a work of max. 5 minutes, vb germany did it already why can't this done here?

they said it will be fixed in 4.0.2

[Paul M]

Thats not the question that was asked.

There is no reason they could not fix it here, before 4.0.2 is released, and tbh, I really wish they would, its very annoying.

[feldon23]

Is vBulletin.com no longer in the CVS loop?

[Colin F]

We actually switched to SVN about two years ago

This does not have anything to do with that though. The forum still uses files from SVN, it is simply not updated as often as it was previously.

[Carnage-]

Seriously off topic but since you don't want pms:

How do you deal with plugins products and templates with SVN? I've wanted to get my plugins/products into svn for ages but havn't really got a good way to go about it.

[AlexanderT]

The forum still uses files from SVN, it is simply not updated as often as it was previously.

And that is... why?

[feldon23]

We actually switched to SVN about two years ago

This does not have anything to do with that though. The forum still uses files from SVN, it is simply not updated as often as it was previously.

I don't want to get into the picky details, but it just seems like instead of how vBulletin was before where bugs were fixed within hours on vBulletin.com, so vBulletin.com always had its "best foot forward" with the least bug free version, now vBulletin.com seems frozen like a deer in headlights on 4.0.1.

I thought the point of CVS, SVN, Git, etc. was the ability to commit a change and pick which branches to apply that change to.

Do you see how when you add up all these little things, like vBulletin no longer having an actively updated documentation repository, vBulletin.com no longer running current software, most forum questions simply being ignored by vBulletin staff, and then Bob Brisco posting space cadety type marketing drivel from his Blog, that we are all really starting to wonder what the heck is going on here?

[Colin F]

Seriously off topic but since you don't want pms:

How do you deal with plugins products and templates with SVN? I've wanted to get my plugins/products into SVN for ages but haven't really got a good way to go about it.

The blog and CMS plugins are part of the codebase, so they're in the same repository. We have a very few other plugins, but the ones we have (like to display the license status to staff) aren't in SVN. Templates for the product are handled by exporting the style XML file, which is then committed to the repository.

And that is... why?

The workflow has changed. Development and bug-fixing of vBulletin has a higher priority to updating our forum say once a week. One could argue the advantages of either method, we've chosen to update less regularly for now. Possibly this will change in the future.

I don't want to get into the picky details, but it just seems like instead of how vBulletin was before where bugs were fixed within hours on vBulletin.com, so vBulletin.com always had its "best foot forward" with the least bug free version, now vBulletin.com seems frozen like a deer in headlights on 4.0.1.

I thought the point of CVS, SVN, Git, etc. was the ability to commit a change and pick which branches to apply that change to.

Do you see how when you add up all these little things, like vBulletin no longer having an actively updated documentation repository, vBulletin.com no longer running current software, most forum questions simply being ignored by vBulletin staff, and then Bob Brisco posting space cadety type marketing drivel from his Blog, that we are all really starting to wonder what the heck is going on here?

The technical details regarding SVN have absolutely no relevance. How it is used has not changed at all, and upgrading our forums wouldn't be much different if we didn't use a versioning system.

[s0lidgr0und]

In the time to type that post, it could have been fixed.

[Paul M]

In the time to type that post, it could have been fixed.

I was thinking that - it took me all of about a minute to fix my test forum, and most of that was opening the file in an editor, and locating the correct area to add the fix.

[Mike Anime]

i am glad they fix things here at the same time they fix it for the end users so the end users can see how things act in real time.

yes it would be nice to see it live here for about a week before it goes to us to iron out and big bugs but failing that my first sentence will have to do.

[Ramsesx]

The workflow has changed. Development and bug-fixing of vBulletin has a higher priority to updating our forum say once a week. One could argue the advantages of either method, we've chosen to update less regularly for now. Possibly this will change in the future.

Colin, it is a pain to use this forum now with this bug. But it makes it even more worse to see how the customers are treated or better said ignored. Nobody of vbulletiin staff seems to care about anything here in this times. We just can hope on vb 4.02 they don't forget the reply button if it need that long to fix things.

[Loco.M]

Thats not the question that was asked.

There is no reason they could not fix it here, before 4.0.2 is released, and tbh, I really wish they would, its very annoying.

my exact thoughts on this bug that's been annoying us for at least 10 days

[feldon23]

And will for another 7.