Login get's me back at the login screen + Error loading forum category

[PET]

As I have said. I'm working on my localhost. As I have said I already did a fresh install of a vB5 and did not had this problems.

Those problems are strictly with my upgraded 4.2.0 forum.

[PET]

Just did an upgrade on my localhost to Beta 27. I still have the problem.

I can not view any forum or topic. I just get this:
An internal error has occurred and the module cannot be displayed.

This is the screenshot with the topic module when I try to edit it.

[Lynne]

This is a fresh upgrade of 4.2.0 to beta 27?

[PET]

This is a fresh upgrade of 4.2.0 to beta 27?

This is an upgrade from Beta 26 to Beta 27.

4.2.0 was done to Beta 25.

[Trevor Hannant]

Do you see anything in your PHP error logs?

[PET]

I activated this in the config file:

$config['debug'] = true;

The module now displays this:

An internal error has occurred and the module cannot be displayed. Template: widget_conversationdisplay => conversation_toolbar Controller: prefix Method: fetch Arguments: Array ( [0] => 49747 ) Errors:

Array
(
[0] => Array
(
[0] => unexpected_error
[1] =>
Database error in vBulletin 5.0.0 Beta 27:

Invalid SQL:

SELECT prefix.*, prefixpermission.usergroupid AS restriction
FROM channelprefixset AS channelprefixset
INNER JOIN prefixset AS prefixset ON (prefixset.prefixsetid = channelprefixset.prefixsetid)
INNER JOIN prefix AS prefix ON (prefix.prefixsetid = prefixset.prefixsetid)
LEFT JOIN prefixpermission AS prefixpermission ON (prefix.prefixid = prefixpermission.prefixid)
WHERE channelprefixset.nodeid = 49747
ORDER BY prefixset.displayorder, prefix.displayorder;

MySQL Error : Illegal mix of collations (latin1_general_ci,IMPLICIT) and (latin1_swedish_ci,IMPLICIT) for operation '='
Error Number : 1267
Request Date : Friday, February 1st 2013 @ 05:38:26 AM
Error Date : Friday, February 1st 2013 @ 05:38:26 AM
Script : http:///vB/forum/about-this-forum/hy...=1359697050552
Referrer : http://localhost/vB/auth/login
IP Address : 127.0.0.1
Username : PET
Classname : vB_Database_MySQL
MySQL Version : 5.5.24-log

)

)

HUUUUUGE PROGRESS

Now how to fix it?

[Trevor Hannant]

When vBulletin creates a new table in the upgrade process, it asks MySQL what the default collation for the database is and then uses that. Most MySQL installations default to latin1_swedish_ci. If you have changed collations for any reason on tables in the past then you should change the database to use that as the default to prevent this issue from happening in the future.

You will find more information in the MySQL manual here:

http://dev.mysql.com/doc/refman/5.1/en/charset.html

You will need to use phpMyAdmin and make sure that all tables and fields within them have the same collation. Make sure your database collations are appropriate and consistent throughout the entire database. You need to use program like phpmyadmin to view your collations:

http://www.phpmyadmin.net/home_page/index.php

When you click your database name in phpmyadmin it will list all tables, their collations, as well as the collation of the database itself at the bottom. And when you click the name of a table on the left it will list the collations of individual fields within that table.

1) To edit the collation of the database itself you need to click the database name on the left and then click "Operations" on the top.

2) To edit the collation of an individual table you need to click its name on the left and then click "Operations" on the top.

3) To edit the collation of an individual field within a table you need to click the table name on the left and then click the edit image (a little pencil icon) for that field.

For more information please see: http://www.vbulletin.com/forum/showt...ight=collation

Note: It is very very very important to make full database backups before proceeding if you are ever manually making any changes to your database, let it be issuing queries, or editing it via phpMyAdmin or any other interface. If done incorrectly, manually modifying the database can potentially cause irreversible damage to your database, and there is no way to perform a "partial restore" to restore just the part you may break.

[PET]

Uggh... all tables already have latin1_Swedish_ci

[Lynne]

Clear your System Cache (under Maintenance).

[PET]

I did that. No luck.

The thing is that I have no prefixes set. So I tried to add a new prefix and I got this:

Debug: Error
Database error in vBulletin 5.0.0 Beta 27: Invalid SQL: SELECT channelprefixset.* FROM channelprefixset AS channelprefixset INNER JOIN prefixset AS prefixset ON (prefixset.prefixsetid = channelprefixset.prefixsetid) ORDER BY prefixset.displayorder; MySQL Error : Illegal mix of collations (latin1_general_ci,IMPLICIT) and (latin1_swedish_ci,IMPLICIT) for operation '=' Error Number : 1267 Request Date : Friday, February 1st 2013 @ 10:50:42 PM Error Date : Friday, February 1st 2013 @ 10:50:42 PM Script : http:///vB/admincp/prefix.php?do=insertset Referrer : http://localhost/vB/admincp/prefix.php?do=addset& IP Address : 127.0.0.1 Username : PET Classname : vB_Database_MySQL MySQL Version : 5.5.24-log
occurred in file C:\wamp\www\vB\core\vb\database.php on line 1113
Trace
Function halt in file C:\wamp\www\vB\core\vb\database.php line 412
Function execute_query in file C:\wamp\www\vB\core\vb\database.php line 446
Function query_read in file C:\wamp\www\vB\core\includes\adminfunctions_prefix.php line 163
Function build_prefix_datastore in file C:\wamp\www\vB\core\vb\datamanager\prefixset.php line 171
Function post_save_each in file C:\wamp\www\vB\core\vb\datamanager.php line 1112
Function save in file C:\wamp\www\vB\core\admincp\prefix.php line 773
Function require_once in file C:\wamp\www\vB\includes\api\interface\collapsed.php line 109
Function relay in file C:\wamp\www\vB\includes\vb5\frontend\controller\relay.php line 29
Function admincp in file line
Function call_user_func_array in file C:\wamp\www\vB\index.php line 141

The only difference between the channelprefixset table and the others is the storage type. Some are set to InnoDB and some are set to MyISAM.

[Lynne]

The problem in that error is here:
MySQL Error : Illegal mix of collations (latin1_general_ci,IMPLICIT) and (latin1_swedish_ci,IMPLICIT) for operation

Some fields are latin1_general_ci and others are latin1_swedish_ci. They need to all be one or the other.

[PET]

Ah I see. Cells can have collations to. Everything works....for now

- - - Updated - - -

I'm trying to edit a post. I get a popup with this:

HTTP 200 - SyntaxError: Unexpected token <

[Wayne Luke]

Uggh... all tables already have latin1_Swedish_ci

You need to check every field in those tables as well. Fields can actually have a different collation and character set than the table does. It is a pain but it is how MySQL sets it up.

Sorry.. didn't see the last page. I've created a JIRA for a tool that will test this in vBulletin. See here:

http://tracker.vbulletin.com/browse/VBV-7197

The syntax error looks like there is an extra < in your config.php files and it is sending out a notice. We have a JIRA to not send a 200 status OK on errors. Check your files and see if you can turn off Notice display in PHP. While the goal is to have vBulletin 5 Notice Free, there may be a few spots where it pops up still.