Helpful Information
 
 
Category: vBulletin 4 Discussion
help after upgrade vBulletin 4.0.0 Beta 3

http://domainyou.com/login.php?do=login

any can help me what wrong??

Warning: fetch_template() calls should be replaced by the vB_Template class in [path]/includes/functions.php on line 3780

Warning: array_merge() [function.array-merge]: Argument #1 is not an array in [path]/includes/class_bootstrap.php(1111) : eval()'d code on line 24

Warning: array_merge() [function.array-merge]: Argument #1 is not an array in [path]/includes/class_bootstrap.php(1111) : eval()'d code on line 34

Warning: array_merge() [function.array-merge]: Argument #1 is not an array in [path]/includes/class_bootstrap.php(1111) : eval()'d code on line 52

Warning: fetch_template() calls should be replaced by the vB_Template class in [path]/includes/functions.php on line 3780

Warning: fetch_template() calls should be replaced by the vB_Template class in [path]/includes/functions.php on line 3780

Warning: fetch_template() calls should be replaced by the vB_Template class in [path]/includes/functions.php on line 3780

but on my index i have warning
Database error in vBulletin 4.0.0 Beta 3:

Invalid SQL:

(SELECT 'package' AS classtype, package.packageid AS typeid, package.packageid AS packageid,
package.productid AS productid, if(package.productid = 'vbulletin', 1, product.active) AS enabled,
package.class AS class, -1 as isaggregator
FROM XXXX_forumer_package AS package
LEFT JOIN XXXX_forumer_product AS product
ON product.productid = package.productid
WHERE product.active = 1
OR package.productid = 'vbulletin'
)

UNION

(SELECT 'contenttype' AS classtype, contenttypeid AS typeid, contenttype.packageid AS packageid,
1, 1, contenttype.class AS class , contenttype.isaggregator
FROM XXXX_forumer_contenttype AS contenttype
INNER JOIN XXXX_forumer_package AS package ON package.packageid = contenttype.packageid
LEFT JOIN XXXX_forumer_product AS product ON product.productid = package.productid
WHERE product.active = 1
OR package.productid = 'vbulletin' );

MySQL Error : Illegal mix of collations (latin1_general_ci,IMPLICIT) and (latin1_swedish_ci,IMPLICIT) for operation '='
Error Number : 1267
Request Date : Monday, November 16th 2009 @ 01:20:31 AM
Error Date : Monday, November 16th 2009 @ 01:20:31 AM
Script : http://www.domainyou.com/
Referrer :
IP Address : 125.XXX.XXX.X
Username : XXXX
Classname : vB_Database
MySQL Version : 5.0.85-community-log

You should be posting this over on vb.com. Actually, first you should search over there because I've seen this posted before. And, I'll further add that you should read the announcement prior to installing. It very clearly says to disable your plugins which you have not done.

Can we run Beta 3 in production?

The official answer is that you may run this beta release on public sites, but we don't recommend it. If you put it in production, make sure to back up all of your data and files before upgrading.

Please remember that there is no official support for vB4 until the Gold release, so if you decide to put it in production, you're taking all of the usual risks of using beta-stage software. This means that there are still known bugs, some of which might be significant to your members, depending on how they use the software.

Is there anything we should be especially careful of?

New, fresh installations have been relatively predictable, but we have experienced some potentially serious issues upgrading existing vBulletin installations, depending on customization, configuration and certain aspects your database. In particular, disable all of your plugins before attempting upgrades.

http://www.vbulletin.com/forum/showthread.php?325409-How-to-Backup-before-Upgrading-to-4-0

Step #3

And who taught me step #3 ?? ^^ Lynne :D a long time agon in a galaxy far, far away ;)

http://www.vbulletin.com/forum/showthread.php?325409-How-to-Backup-before-Upgrading-to-4-0

Step #3

And who taught me step #3 ?? ^^ Lynne :D a long time agon in a galaxy far, far away ;)
hehe. And I learned from Steve or Wayne or one of the vb gurus over there.










privacy (GDPR)