HZGN.COM
welcome to my space

NAVIGATION -

HOME

vBulletin 2.3.2 Released - Discuss

Published by: admin 2009-01-09

Discuss away!

If you are having a specific problem, please post in the appropriate forum rather than using this thread.

In any way Iam new here...
and I don't know any thing here...

can you people help?
what I do first?

1-download VBulletin?
2-ba an member?

The post that you are referring to was deleted by its author.

The answer is to upgrade to 2.3.2 and apply the fix if it is necessary on your site. You can find posted fixes in the vBulletin 2 Bugs forum.

A question:

If you didn't bother to upgrade to 2.3.2 from 2.3.0, can you upgrade to vB3 from 2.3.0 when the time comes, or will you have to upgrade to 2.3.2 first?:)

Satan

Shall we expect 2.3.3 tomorrow?
teehee...I could not help myself.

I installed 2.3.2 without any problems or after affects.
I will install 2.3.2 now.

Just really wanted to say "Hello",and a Hi at Martin,
wonder if he remembers me?

:);):)

So...will we have to rehack or what? lol

to jelsoft: please continue releasing the bug fixes for 2.3.2 in the same format. (manual code-changing instructions as opposed to automated upgrade.php scripts) it was a big hassle for me to re-hack everything after the upgrade, and i don't want to go through it all again just to achieve a stable version. thanks.
That would be outstanding if possible
:)

Well, vb 2.3.2 seemed to be relatively stable for the past 24 hours so I upgraded from 2.3.0
All I can say is thankyou araxis merge !
Twenty minutes of comparison / changing and all is done.
:)

Probably like a lot of other users,I never bothered to install 2.3.1 because of the bugs, so is it possible to have a list of the changes from 2.3.0 ?

http://www.vbulletin.com/forum/showthread.php?t=79486

That was my fault. I meant to edit and then deleted.

I'll say that I think that I understand from someone who has already upgraded to the 2.3.2 would gladly be okay with listed detailed fixes for founded bugs.
I also would like to say that for those who have not yet upgraded to 2.3.2 would love having all the currently noted fixes within the members area....with a date of course so they could add the fixes as need be from the date on.
To me this sounds easier then collecting fixes and creating a next version number till you hit 3 ugg, I hope this makes some kinda sense...I re-read my thoughts and it always sounds confusing after the fact.
To make it clear from my particular perspective...
I am using 2.3.0...no problems...but would like to keep current and secure....so I would like to upgrade to 2.3.2...but should I? What am I missing should I wait because not all bug fixes have been applied because they are being compiled till the 2.3.3.....
As a not installed yet person, I'm fine with upgrade knowing what I need to apply after such date of last fix to member area download.
As a person who already updated ...I'm fine with a "here's a bug fix" and a date to follow so I know if I personally need to apply it.
:o

Will all the 2.3.0 hacks work because i just fixed some majpr DB erorrs and dont wanna have to rehacks and have everyone re register? other than that good job ^_^

Hi n9ne, I did try that already though, thanks.. no luck on either update thread.

Sorry I realize that there is a reason details of security issues are not published~

I didn't notice anything saying "If you're downloading the upgrade scripts after this date ####, all fixes have already been incorporated." If we download now, are the manual fixes still needed?

Apparently, the Subscribed Threads (http://www.vbulletin.com/forum/showpost.php?p=509590&postcount=1) bug fix didn't work. :(

No they are not. This is standard procedure. Fixes are not added until a new version is released.

very strange with jelsoft in the moment!
I downloaded vb2.3.2 5min ago and I see some fixes are done and some not..
These fixes are integrated in current download:
http://www.vbulletin.com/forum/showpost.php?p=509590&postcount=1
http://www.vbulletin.com/forum/showpost.php?p=510053&postcount=2

This fix is not integrated in current download:
http://www.vbulletin.com/forum/showpost.php?p=511001&postcount=3

any statement from jelsoft?
vB2.3.2 is buggy, vB3 is buggy, vB2.3.0 ist the last stable-version for me

I still have a fresh copy of 2.3.0 sitting here if anyone needs it. post here with your email address if you need it.

P.s. do not ask for it if you do not have a license, I am not giving stuff away here.
You CANNOT distribute any vB files. Doing so is against the license agreement and may result in your license being revoked.

wish i had never upgraded :(

2.3.2 has a very bad bug causing it to not let anyone edit thier profile, it keeps asking for their location saying it has to be filled in, but in the edit profile there is no place to enter a location

very bad

any word on 2.3.3?
This is not a bug in vB 2.3.2. Please start a new thread about your problem so we can troubleshoot the issue.

Alright, I'm not gonna complain, nice work guys! I won't be installing for about a week, to let the rest of you find the other bugs, and by then I should be ready to install 2.3.8! :D

Just kidding around, but nice work guys. Glad to see you're checking your own work, and showing us how to upgrade without going back to an unhacked board. Thanks! :D

Upgrade was a breeze. Thanks guys :)

Apparently, the Subscribed Threads (http://www.vbulletin.com/forum/showpost.php?p=509590&postcount=1) bug fix didn't work. :(
Can you elaborate on this please?

Can we go straight from 2.3.0 to 2.3.2?
Yes, you will need to upload all the files and run upgrade24, then upgrade25.php.

Yes, you will need to upload all the files and run upgrade24, then upgrade25.php.

Ok, thanks for the quick response Kier. It's appreciated. :)

You need to purchase a license in order to have access to the Members Area and download vB. You can do this here:

http://www.vbulletin.com/order.php

You explained the code changes from 2.3.1 -> 2.3.2 Please. please, please do the same for 2.3.0 -> 2.3.2. Alot of people would thank you, including me. :)i already asked that Nex http://www.vbulletin.com/forum/showpost.php?p=508984&postcount=3 but apparently a changelog from 2.3.0 > 2.3.2 is not available.

Probably like a lot of other users,I never bothered to install 2.3.1 because of the bugs, so is it possible to have a list of the changes from 2.3.0 ?

Scott and Steve,
Are the last two fixes you both added to the announcement forum already applied to the members area download for 2.3.2 also?--this was not stated anywhere that I've seen---my apologies should I have missed it--kier mentioned that his fix was updated in the latest download...
Should we assume that all the fixes added in the announcement are applied to the download?
Thanks
:)

@Kier
it�s ok
but now, noone knows what fix is integrated!

Fix1 is ok, your wrote: I have updated the members' area with this fix
Fix2 no message, but member-area is update
Fix3 member-area isn�t updated, also no info

So I think it is the best release vb2.3.3 with all fixes and also fix current bugs! (subscribed threads...)

In this post:

http://www.vbulletin.com/forum/showpost.php?p=508909&postcount=2

You explained the code changes from 2.3.1 -> 2.3.2 Please. please, please do the same for 2.3.0 -> 2.3.2. Alot of people would thank you, including me. :)

I would hate to have to rehack the board for such a minor upgrade..... 2.3.0 to 2.3.1/2 is not a minor upgrade, a lot of files have changed between 2.3.0 and 2.3.2.

Do not confuse the fact that there is very little difference between 2.3.1 and 2.3.2 with the differences between 2.3.0 and 2.3.2.

In short:

2.3.0 => major change => 2.3.1
2.3.1 => tiny change => 2.3.2
2.3.0 => major change => tiny change => 2.3.2

May I ask why 2.3.1 RC wasn't released? If it was, then this would all have been picked up and then 2.3.2 would be 2.3.1 final....... and the subscribed threads bug could be fixed in RC2...

Hey,

Are you running any hacks, such as the hack to remove redirects such as this specific one below?

http://www.vbulletin.org/forum/showthread.php?s=&threadid=53762

Also, try replacing your functions.php file with one directly from the zip. (backup your old one of course). If the problem goes away, then your problem is in your functions file.

BTW, real nice website you have there.

-Jason

I am now waiting to see how vb3.0 work sout on my board http://www.echarcha.com/ which has a customised first page with templates made by querying different tables in the database.

I saw a site which was upgraded from 2.3.x to 3.0 beta and the templates on the first customised page all broke down.

I think I need to first install it locally and then get my live db records copied into it and then painstakingly make a first page again.

I wish Jelsoft comes up with a front page which has things like active threads, popular posts, etc. (Like Yahoo has MyYahoo where you can customise your content and layout)

*bump*
where are the devs?

Look below, is it meant to be "iif" in the solution as well as the text you are replacing? This is the bug fix on the announcements page.

bug in functions.php can cause problems if you allow dynamic URL for tags.

In functions.php, replace:

if($dobbimagecode and ($bbuserinfo[userid]==0 or $bbuserinfo[showimages])) {
// do [img]xxx
$bbcode = preg_replace("/(rnrn)*((httphttps)://([^;<>()"".iif($allowdynimg,"","!?&")."]+)[a-z0-9/\._- ]+)[/img]/siU", "

", $bbcode);
}
$bbcode = preg_replace("/[img](rnrn)*((httphttps)://([^;<>*()"]+)[a-z0-9/\._- ]+)[/img]/siU", "\2", $bbcode);

with:

if($dobbimagecode and ($bbuserinfo[userid]==0 or $bbuserinfo[showimages])) {
// do [img]xxx
$bbcode = preg_replace("/[img](rnrn)*((httphttps)://([^<>()"".iif($allowdynimg,"","!?&")."]+)[a-z0-9/\._- ]+)[/img]/siU", "

Google Maps 2.3.09 Released - With Street View. - Page 2 - xda ::
10 posts2.3.2 means you're reading it wrong, or it's not the same thing. Sure you're not looking at the Java version or . Powered by vBulletin® Version 3.7.4
http://forum.xda-developers.com/showthread.php?p=3087847HOME

[Release] Illidan's 2.3.2 Custom Weapons::
6 posts - Last post: Feb 3, 2008This is a discussion on [Release] Illidan's 2.3.2 Custom Weapons within the WoW Emulator Server Discussion forum part of the WoW forum
http://www.d3scene.com/forum/wow-emulator-server-discussion/10431-release-illidans-2-3-2-custom-weapons.htmlHOME

", $bbcode);
}
$bbcode = preg_replace("/[img](rnrn)*((httphttps)://([^<>*()"]+)[a-z0-9/\._- ]+)[/img]/siU", "\2", $bbcode);

To paraphrase:
vBulletin releases are like busses.
There's never one around when you want one then, all of a sudden, three come along in as many days.

Can we go straight from 2.3.0 to 2.3.2?

No they are not. This is standard procedure. Fixes are not added until a new version is released.

Just to get things straight: Does that mean, that 2.3.2 was the last 2.3.X release?
So far.

I'm waiting for 2.3.3 or at least a fix to this very serious problem http://www.vbulletin.com/forum/showthread.php?threadid=69803 which several of us are experiencing. I know this is attributed to the newest SQL version but many of us have no control over that and I would think that JelSoft could at least do something with their software so that this problem wouldn't be exasterbated. I don't get this error with my Invision Boards that I run.

Thats a problem with your server and not vBulletin. Make sure you complie PHP with MySQL 4.x support.

I *JUST* paid for and recently setup 2.3.0 and it hasn't even gone live yet, but i made a bunch of templates and made the 'default' one totally different than the default that's shipped.

My question is, in upgrading it says to upload *all* files, that surely means templates will be overwritten or is that not the case?

any tips on how to make sure your templates aren't overwritten or do you just have to save the templates and redo them? can you upgrade by only uploading listed files that were changed?

thx in advance.... i BARELY got it and already an upgrade :/

HI,

I have a customized template created by myself, if I were to upgrade to 2.3.0 to 2.3.2 do I have to re-edit and re-modify my templates? I don't have any other hacks installed, just a theme.

P.S. I also get a CRC error when unzipping thread.php in the admin folder, what can I do about this?

Thanks

Where is the "minor XSS fix" ??

It is mentioned in the first paragraph but then never spoken of again with details. I don't want to do the upgrade, but I need the security fix.. and I honestly don't have time to go through all the posts. Can't search for XSS because it is under the 4 char limit... please give details on this security issue.

I�m wait for vB2.3.3
vB2.3.2 is very bad, some fixes are done, some not...
one mod say new fixes are done in next release, another mod say some new fixes done in current release, it�s very unprofessional at the moment
As far as I am aware today, there are no plans to release a 2.3.3 package.

Yes, the upgrade script states you can run this on 2.2.9 or above

After the recent events over the past few days, I would normally jump to the defence of Jelsoft, but on this ocassion, even though I am now a vb3 beta user, Jelsoft why suddenly the dropping of the ball? I know you are putting most of your efforts into vb3, but don't make mistakes for those still using vb2. Why the rush to apparently "ditch" vb2 as soon as possible and not put some effort into making sure these mistakes don't keep on creeping through.

Is this down to the CVS problems you have been having?

woOoOoOoOoOow :d

Scott, Kier, etc...

Thanks for putting up the changes (minor bug-fixes) to code done since 2.3.2 was released in the Announcements forum. Can we please keep this up throughout the release life of a version so everyone can find the incremental fixes/changes easily?

Much appreciated - thanks. :cool:

I have to say, this is one of the poorest releases Ive ever seen from Jelsoft.
There has been 2 version release over the past few days, each requiring bug fixes.
It kinda reminds me of another companies forum software...

If it is required to release vb 2.3.3, please take a bit more time and perhaps use 1, maybey 2, release candidates before a final release.

Small things like this really give companies a bad reputation based on perception.

I agree. Basically 2.3.0 was working fine for me. I'm glad I didn't spend the time to "upgrade" to a version which has more bugs. It takes me a lot of time to perform upgrades on several sites and I don't like doing it 2 or 3 times in a week.

Are we up to 2.3.4 yet? :)

Is it possible to upgrade from 2.2.9 straight to 2.3.2?
As with any vBulletin upgrade, you can upgrade from any version to the latest version by uploading the latest files and then running the appropriate upgrade scripts in order.

In your case, you would need to run upgrade23, upgrade24 and then upgrade25.php.

Is there a way to get 2.3.0? I have only this post to go on but there seems to be some dissatisfaction with 2.3.2. This is my dilemma. I'm going to restart my board (currently using 2.2.6) hack it up to bit and change the template. I don't want to have to redo all this later and don't plan on upgrading to v3 for this forum.

So is 2.3.2 stable enough to go ahead and rely on having it for the next year or two if my board happens to stay up that long =PFor me vB2.3.0 the best stable version.
vB2.3.2 have to much new unfixed bugs and jelsoft don�t update to new version, also there is no stable vB3 until the next weeks...
To get vB2.3.0 is not easy, if you can�t get it from jelsoft I think you must look in some fileshari...

Is it possible to upgrade from 2.2.9 straight to 2.3.2?

Correct, you can skip the image files if you want.

Since I have translated all my templates into German, I wonder if I can use the new php Files with &-recoding but leave the templates as they are, all using the &-character with non-HTML encoding as &.
Otherweise it would be quite an effort for me so I would edit the character-encoding out of the new php-files.

Thanks a lot for your answers.
Bj�rn

This is in regard to the email announcements we receive when new versions are ready and also in light of the other announcement regarding fake PM's asking for user information...

Why is it important to have both my member number and password included on the email announcements? Isn't this unnecessary and a potential security issue?

Just a thought.

Steve K.

I'm hoping by the time I get home it will be safe to install this version. Last time I read the support and saw that everyone was having issues.

I have 2.3.0, Do I just upload the files with the changes listed in the annoucement or do I upload everything? I have a bunch of hacks. What's the best way for me?

Yes, you can upgrade from 2.3.0 to 3.0.0 directly.
Will upgrading from 2.2.9 to 3.0.0 still be supported now that 2.3.2 is out?

Strange!!
the last post in this thread is deleted, where is it and where is the answer???

here the post from Littlebit in my cache:

( I didn't get an auto e-mail stating that there was a reply to this thread. No auto subsciption to thread after posting? I'll check my settings...I'm still not used to vB3 yet :o )

So should I upgrade to 2.3.2 and then only apply 'fix number 3' or should I wait for an official new version ?

:confused:

Roody, please do not use this thread for troubleshooting. Start a new thread instead.

So when can we expect 2.3.3 :D (Only joking), thanks for the quick fix guys.

Hmmm...one of the Developers will need to comment on this. The normal procedure is that bug fixes found after a release are added to the next release.

I'm having some serious issues on my forums when it comes to amperstands.

Alot of the URL's are coming out like such:

http://www.ewplanet.org/e/showthread.php?s=&threadid=14887

http://www.ewplanet.org/e/search.php?s=&action=showresults&getnew=true&searc hid=21726

I knew should've waited to upgrade but I thought there were some serious bug fixes, 2.3.0 was running perfect as far as I could tell and now my forums are screwed.

Ah, hopefully you guys are able to fix this, otherwise I'll have to close the forums down and figure out what's wrong myself... and tha'ts not a good thing.

Off topic posts removed.

You shoudn't need to. There should have been a RC where all these bugs were picked up and then we were given a final which we could hack.

I don't understand why a note hasn't been posted saying this is not a stable release and should only be used on test boards till they get all the bugs out.

You CANNOT distribute any vB files. Doing so is against the license agreement and may result in your license being revoked.

It 's cool I was just trying to help. I'm not trying to break any rules around here. Disregaurd my last post.

Probably like a lot of other users,I never bothered to install 2.3.1 because of the bugs, so is it possible to have a list of the changes from 2.3.0 ?
You would find that in the vBulletin 2.3.1 release thread.

Yes, you can upgrade from 2.3.0 to 3.0.0 directly.

After reading all this I don't feel like updating from 2.3.0 to 2.3.1 anymore because I think that it doesn't worth the hassle if V. 3.0.0 is coming out soon/next.

Q: If I'm not going to update now, will I have a problems, trouble updating V. 2.3.0 directly to V.3.0.0 when it comes out? Or should I update now to V. 2.3.1 so I can directly update to V. 3.0.0 later?

Is what I already asked in the other thread ...

A question:

If you didn't bother to upgrade to 2.3.2 from 2.3.0, can you upgrade to vB3 from 2.3.0 when the time comes, or will you have to upgrade to 2.3.2 first?:)

Satan

Could somebody please answer this since it really doesn't worth updating for me with all the stuff I have installed. I would rather like to wait for V. 3.0.0!

Here the question again:

Q:
Will we be able to update from 2.3.0 to 3.0.0 directly? Because if not then I will have to update to 2.3.1 and then to 2.3.2 and so on anyways, so this is very important to me ...

I helped a friend upgrade to the newest version on his site, after the newest 2.3.2 issue occurred and had been updated with a fix, yet members are complaining that they arent receiving emails for subscribed threads.

Any word on this?

I'm waiting for 2.3.3 or at least a fix to this very serious problem http://www.vbulletin.com/forum/showthread.php?threadid=69803 which several of us are experiencing. I know this is attributed to the newest SQL version but many of us have no control over that and I would think that JelSoft could at least do something with their software so that this problem wouldn't be exasterbated. I don't get this error with my Invision Boards that I run.
This is not a problem we can fix and it has nothing to do with vBulletin.

You will need to recompile PHP to use the MySQL 4.X client libraries or downgrade to MySQL 3.23.XX to resolve this issue.

May I ask why 2.3.1 RC wasn't released? If it was, then this would all have been picked up and then 2.3.2 would be 2.3.1 final...

After downloading 2.3.2 i get a CRC-error.

The file /admin/thread.php seems to be corrupt.

I downloaded it for a few times extracted it to different dirs with differnet zip-programmes but no luck :(

joergh

question has been answered thank you!

joergh
When downloading, make sure that you turn off any download accelerators and ad-blocking software such as Norton Internet Security.

The problem has been tracked to a shared memory issue in 4.0.13 and below. It is fixed in 4.0.14 though.

For me vB2.3.0 the best stable version.
vB2.3.2 have to much new unfixed bugs and jelsoft don�t update to new version, also there is no stable vB3 until the next weeks...
To get vB2.3.0 is not easy, if you can�t get it from jelsoft I think you must look in some fileshari...
Thanks for the info. I'd be wary of d/ling anything that i didn't personally get from jelsoft. And i don't plan on getting vb3 for a while since when adding hacks i rely on the -well- documented hacks to install. Something i can guess vb3 won't have alot of for a while now :)

vb3 looks amazing though. Playing with the admin area was a real blast.

OK - dumb question alert...

You say you need to upload all files - what about image files? I've changed all my images and I don't particularly fancy having to go through all that again. I presume the image files haven't changed and therefore I don't need to upload them?

Michael.

I agree that since there were 2-3 thousand edits that we should have had a release candidate to save a little trouble because something would have gotten missed...

Anyways, at least the upgrade went successfully on my end, we're now running at 2.3.2 and ran into very few snags along the way (and mostly due just to conflicting hacks). ;)

It was just very tedious and time consuming to do at my site lol, at least if there's a 2.3.3 it'll be minor!

-Jason

As far as I am aware today, there are no plans to release a 2.3.3 package.

Just to get things straight: Does that mean, that 2.3.2 was the last 2.3.X release?

Good work guys! http://www.vbulletin.com/forum/images/icons/icon14.gif

Hey,

Are you running any hacks, such as the hack to remove redirects such as this specific one below?

http://www.vbulletin.org/forum/showthread.php?s=&threadid=53762

Also, try replacing your functions.php file with one directly from the zip. (backup your old one of course). If the problem goes away, then your problem is in your functions file.

BTW, real nice website you have there.

-Jason

http://www.vbulletin.org/hacks/index.php?s=&action=showhack&hackid=1250

I am using the User selectable redirects hack. There was a fix for the problem at the end of the thread, oddly enough I didn't check to see if there were problems with other users, my fault entirely.

And thanks for the comments on the website. I would say, "Hey... how about vB of the month" but my forum looks little odd right due to the upgrade.

Steve is right. Our normal procedure is to post fixes but not to update the package in the members' area unless the bug is found within 24 hours of a new release. We have found that if we update the members' area with every fix that is posted during the lifetime of a version, many people become confused as to which fixes are already integrated into the package they have downloaded, and which they must apply themselves.

You will notice that this fix (http://www.vbulletin.com/forum/showthread.php?p=509590&postcount=1) notes that the members' area package has been updated with the fix, although Scott's post below it omitted to mention that it had been updated again. We apologise for this inconvenience.

Well, from 2.3.0 to 2.3.2, many files changed, so I would definitely recommend uploading all of them.

Templates are stored in the database, so uploading the new files won't overwrite them. Basically, whenever you upgrade, if you've customized a template, your customized version will remain. If it's uncustomized, you'll get the new version.

If you've customized any of the templates in the 2.3.1/2.3.2 announcements, you may want to consider reverting+recustomizing or making the changes mentioned.

Just curious...

My footer template was edited prior to the 2.3.0 -> 2.3.1 -> 2.3.2 upgrade. The upgrade seems to have applied changes to my already modified footer template, making the version number a variable.

Was it only the announcement template that should have been reverted to original, and that upgrade changes to other templates are applied regardless of whether the templates were modified prior to upgrading?

I agree. Basically 2.3.0 was working fine for me. I'm glad I didn't spend the time to "upgrade" to a version which has more bugs. It takes me a lot of time to perform upgrades on several sites and I don't like doing it 2 or 3 times in a week.

Hate to be a "Lemming" but I have to agree on this.

The 2.3.0 scenerio was perfect. This had a couple of RC's before going "gold". I personally never upgrade straight away and let other people find the problems. However if things like the previous two versions continue this way, perhaps other people will be less then likely to upgrade as well.

I'd sooner wait for a stable "gold" version then have numerous updates. I personally feel that it looks like Jelsoft are so wrapped up in 3.0.0 that this was hurried out. Please think of the membership here and don't rush things.

I'd rather wait a few days longer and have something that is going to work that I can install.

Hate to say, but I am so glad to be running 2.3.0.

The balance between holding a release up until it is tested/stable and getting fixes out to the users as quickly as possible has been thrown off for 2.3.x it seems. :(

I respect that people needed the fixes provided by vB2.3.2.