The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#11
|
|||
|
|||
You must upgrade. There is no other option. Going to PHP3 is not a step backward but a step backward, tripping on a tree root, and falling off a cliff.
|
#12
|
||||
|
||||
@Areku: vb2.2.x x < 6 has problems with phpversions 4.2.x
you should really upgrade, you'll get more problems if you don't. also do you know that i could hack a vb220 board in about 10 minutes if i want? upgrading is really needed, it's just for your security.. |
#13
|
|||
|
|||
Then i'm sooo afraid of the upgrade because of the vast amount of hacks installed, that i don't even know if it will work later (the site I mean).
Moreover, wouldn't be more logic to first manage to get this version working and later do the upgrade? What if I upgrade and then I still have the same problems? As I said, 2.2.0 has been working fine with php4.0.6 so... why shouldn't it work now? |
#14
|
||||
|
||||
TECK wrote a tutorial on how to do this
Basically araxis merge is what you need It took me about 2 hours on my first go but now upgrading takes me about 30 mins - miSt |
#15
|
||||
|
||||
we all have hacked bords and do the upgrades
also believe my, fixing the bugs manually and upgrade later is much more work for you... also, you might overread something. vb220 has worked good on php406 but it's not secure, there are a lot of security bugs in it. when you won't upgrade you risk to get a new admin to delete your posts, and that would then mean real work for you... |
#16
|
|||
|
|||
THen i'm only afraid that after the upgrade the site still won't work... But I'll try to, thanks for all your support!
|
#17
|
||||
|
||||
you're welcome
if you'd have further problems, just post here |
#18
|
|||
|
|||
I realize this is an old thread, but i'm having the exact same problems as described in the first post. I'm on a hacked 2.3.0 and this is happening on a new server i'm trying to move to because the old one got hacked (rootkits up the wazoo). New box runs PHP 5.0.4 and mysql 4.0.20. Since the old server is still working as the production site right now, i'm using the new server with a second domainname i registered. Moved all the files over, updated the config, copied the databases over and updated the vb settings directly in the database. Site appears to work fine, but i can't go into forums or threads, and the articles hack i have installed that refers to an articleid=x also just keeps me on the same page.
Could this be a cookie issue or are there known problems with vb 2.3 and the mysql or php versions the new box has? I believe php safe mode is enabled on the new box. Would that have anything to do with it? Thanks for your time.. |
#19
|
|||
|
|||
I seriously doubt that 2.x will work on PHP5.x
I suggest upgrading to 3.6.1 which runs on PHP5 fine. |
#20
|
|||
|
|||
that's what i'm afraid of..
Overall it seems to work though. It's just bits here and there that don't, and those bits are pretty important. I don't really know vb3.x though and there's so many hacks to the 2.3 i run that i'd basically have to start over, which the users won't appreciate what about a downgrade to php 4? is that worth a shot, or too much effort? |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|