[Rich]

I realize this thread is that old, lol. I posted in this thread hoping it would get someones attention. The issue with php5 and vb4 was reported like a year and half ago or longer. It has been an issue for me now for over a year and yet the issue hasn't been fixed. We have been told for over a year that it is being worked on and would be corrected. That is clearly not what is happening and I want to ensure as many people realize that vBulletin has simply said "fu#$ it" in regards to vb4 and this issue. They have released many fixes and even new versions for vb5 since this issue had first been reported but still we sit here waiting for our fix. I will never buy another vb product again and am telling everyone i know what this company has done in relation to this issue. If they don't give a ++++ about their customers who have held licenses for 12 years, then they sure as hell won't be seeing another penny of mine. vBulletin was awesome when it was owned by jelsoft and has turned into a circus event since these new assclowns acquired it. vBulletin is now a friggen joke!