Joomla Templates Club 406,261 posts

[pressmar Friend pressmarJoin date: March 2008Posts: 119Downloads:14Uploads:51 Thanks: 25 Thanked: 4 times in 1 posts]

#207710

Hello Joomlart,

i know this isn’t your problem, but i posted the same issue in the joomla forum as well but got no answer. I got the job to do an upgrade from joomla 2.5 to 3.4. I did this maybe 20 times and just had minor problems. But this one is getting very tricky. To be honest i don’t have any clue to migrate the site to 3.4 correctly without errors.

Of course i did an backup and tried to upgrade the site in me testing area. First i did an update of joomla to the latest 2.5.28 and of all plugins, extensions and so one. I checked the database in administration. cleared cache. Than I used the integrated update procedure. This ends up with a 1214 error ” The used table type doesn’t support FULLTEXT indexes SQL=ALTER TABLE ‘jos-session’ ENGINE=InnoDB”. I can see a very limited administration an no webfront.I checked the Database in phpmyadmin. but found no problems and differences to other running joomla 3.4.1 sites.

I reloaded the 2.5.28 site in the test area disabled akeeba and every other plugin larger the >700. Automatic Upgrade and same result. Back to start. Than i tried to upgrade it with a manual upload of the upgrade. Same result. I tried to upgrade to 3.3.6 manually with same results. I checked many forums but got no real point to solve it.

Maybe you have some idea to get it working.
Thanks in advance
Oliver

[Phill Moderator PhillJoin date: February 2014Posts: 7013Downloads:40Uploads:77 Thanks: 917 Thanked: 2206 times in 1818 posts]

#575015

You’re using the wrong type of table. Mysql supports a few different types of tables, but the most commonly used are MyISAM and InnoDB. MyISAM (in MySQL 5.6+also InnoDB tables) are the types of tables that Mysql supports for Full-text indexes here.

[PHP]SHOW TABLE STATUS[/PHP]

Looking at the result returned by the query, find your table and corresponding value in the Engine column. If this value is anything except MyISAM or InnoDB then Mysql will throw an error if your trying to add FULLTEXT indexes.

To correct this, you can use the sql query below to change the engine type:

[PHP]ALTER TABLE <table name> ENGINE = [MYISAM | INNODB][/PHP]

Additional information (thought it might be useful): Mysql using different engine storage types to optimize for the needed functionality of specific tables. Example MyISAM is the default type for operating systems (besides windows), preforms SELECTs and INSERTs quickly; but does not handle transactions. InnoDB is the default for windows, can be used for transactions. But InnoDB does require more disk space on the server.

[pressmar Friend pressmarJoin date: March 2008Posts: 119Downloads:14Uploads:51 Thanks: 25 Thanked: 4 times in 1 posts]

#575044

Hey Phil,

thanks for you help. I found my way to solve it. I took the sql-changes from administration/componets/com_admin/sql/updates/mysql and entered each of them manually via phpmyadmin. With some work all changes worked – now it looks good.

thanks oliver

1 user says Thank You to pressmar for this useful post

1. Phill

[Author]

Posts