deprecated tables

[sandrose]

Hello,

What are the deprecated tables in vbulletin 5.6, I used the tool to convert the tables to utf8mb4 and found those tables not converted:

Beginning conversion to charset utf8mb4
found new charset utf8
found new charset utf8mb4
skipping album- not a VB Table for prefix
skipping albumupdate- not a VB Table for prefix
skipping attachment- not a VB Table for prefix
skipping cacheevent_log- not a VB Table for prefix
skipping cms_article- not a VB Table for prefix
skipping cms_category- not a VB Table for prefix
skipping cms_grid- not a VB Table for prefix
skipping cms_layout- not a VB Table for prefix
skipping cms_layoutwidget- not a VB Table for prefix
skipping cms_navigation- not a VB Table for prefix
skipping cms_node- not a VB Table for prefix
skipping cms_nodecategory- not a VB Table for prefix
skipping cms_nodeconfig- not a VB Table for prefix
skipping cms_nodeinfo- not a VB Table for prefix
skipping cms_permissions- not a VB Table for prefix
skipping cms_rate- not a VB Table for prefix
skipping cms_sectionorder- not a VB Table for prefix
skipping cms_widget- not a VB Table for prefix
skipping cms_widgetconfig- not a VB Table for prefix
skipping cms_widgettype- not a VB Table for prefix
skipping eventhighlight- not a VB Table for prefix
skipping eventhighlightpermission- not a VB Table for prefix
skipping inactiveuserlog- not a VB Table for prefix
skipping ipdata- not a VB Table for prefix
skipping legacyevent- not a VB Table for prefix
found new charset latin1
skipping postindex- not a VB Table for prefix
skipping thread_serviceupdate- not a VB Table for prefix

IF those tables has be deprecated, what shall i do? Can I remove them?

Thanks

[Wayne Luke]

None of those tables are deprecated. They don't match the table_prefix you have defined. There is a big difference between the two issues.

Do you have a table prefix defined in /core/includes/config.php? if you do then the prefix defined in vbutl_config.php file must match exactly. If not, then you should not have a prefix defined in the vbutil_config.php file.

I am guessing that either you have two copies of a vBulletin database structure in your database or that you're not actually using a table prefix.

[sandrose]

Thank you for reply.

There is no prefix in config.php file

// ****** TABLE PREFIX ******
// Prefix that your vBulletin tables have in the database.
$config['Database']['tableprefix'] = '';

There is only one copy of each table in the database.

So, why it was skipped?

How can I solve this issue.

Thanks

[Wayne Luke]

The DB tools scripts have their own configuration file. You need to edit it to match your database information in your /core/includes/config.php file.

Having their own file allows you to place use these files outside the vBulletin directory for security. They should never be placed in a directory that can be accessed from the Web.

[sandrose]

In both config files there is no perfix. Can I change the tables and column collation manualy??

[Wayne Luke]

It runs a series of queries. However, if your data is not English, you need to cast the content into binary in order to try and maintain the content. Sometimes multiple variable casting is needed. That is why we have the scripts. I believe your site is in Arabic. I really don't recommend doing it manually. If you do, there are thousands of tutorials on how to do this on the web.

Without looking at the database, I don't know why you're having these problems.

[sandrose]

So, how can I proceed with conversion of the remaining tables?

Thanks

[Wayne Luke]

You can proceed by resolving the underlying problem. This isn't possible in a forum topic because there is no way to determine that that problem is. I have not even seen your problem before. It would require a proper support contract and support ticket.

[sandrose]

I submitted the support ticket.

Regards,