4.0.13.1 Utf8Converter

[GaryJames]

I have a problem trying to convert my current database to utf8 in preparation for the upgrade to 4.0.13.1.

I am aware that some of the modules that I have installed "Custom Side Blocks" for example are not supported in version 4, so to reduce the likelihood of these causing problems, I have uninstalled all the hooks and modules that are not supported. As part of this process the tables have been removed from the database and everything has been re-cached.

Now when I run the utf8 converter, it gives me an error saying the table custom side blocks cannot be found even though everything has been removed.

Is there something that the converter is reading that tells it what tables to look for?

Many thanks in anticipation.

Gary.

[David..]

You can reinstall Custom Side Blocks as IPS4 will disable it once you upgrade.

[GaryJames]

Many thanks for your reply David, I realise this when I completed a test install, but I really wanted to clean everything that was not compatible with version 4  before I run the live upgrade.

I really would like to know why the utf8 converter is looking for modules and hooks that are no longer installed?

With all the knowledge on this forum, I would of thought that someone would know how the process works and why it looks for tables and modules that are no longer installed.

Many thanks,

Gary. 

 

[Stuart Silvester]

Many thanks for your reply David, I realise this when I completed a test install, but I really wanted to clean everything that was not compatible with version 4  before I run the live upgrade.

I really would like to know why the utf8 converter is looking for modules and hooks that are no longer installed?

With all the knowledge on this forum, I would of thought that someone would know how the process works and why it looks for tables and modules that are no longer installed.

Many thanks,

Gary.

 

The UTF8 converter checks the database first and then stores a copy of the schema for the conversion process, You should just be able to remove the tables starting with x_utf_ and start the conversion again.

[GaryJames]

Many thanks for your reply Stuart and I am grateful for the help.

So if I am reading this correctly, when the conversion stops because it cannot find the table "Custom side blocks" it will have created a table called x_utf_custom_side_blocks.

I would then log into the database find the x_utf table, delete it, restart the conversion and the process will bypass the deleted table.

Many thanks,

Gary.

 

[GaryJames]

I've managed to resolve this problem, although I still don't understand why the converter is looking for tables modules that have been removed.

I left everything as it was with all the tables in tact, then I ran the converter and it updated everything to UTF8.

After running the update I now have another issue which I will post in a new topic.

Many thanks to those that posted.

Gary.