Quote:
Originally Posted by KirbyDE
The Templates are compatible variable-wise, so you don't have to redo them.
The Database Schema also ahsn't changed.
|
I don't think that this is correct.
At least one table made a problem while upgrade 3.0.x to 3.5.
vBulletin is now using a table field which has the same name than the one AWS uses.
I tried an upgrade of my 3.0.8 board with AWS to vb 3.5 RC1 which brought up an error with a table. This was used from AWS and I had to delete it before the update went well.
I recommended weeks ago to change the AWS tables by adding them a prefix like
aws_
and the field names also
aws_
For future vB releases and other hacks I think this would be a good idea.