I was pulling my hair two years ago with these Fantastico database issues because some sites were in real trouble and some people even lost their sites when mysql dump file did not have all tables included but basicly if you have a full and tested (checked) backup file of your site and you can use tools like phpMyAdmin it does not matter if the first trial fails and shows question marks in the place of some unicode letters. The mysql dump file (backup file) can be utf8 or latin and the commands inside mysql backup file may try to restore data in certain collation or charset. Each field inside table can have different collation and character set. Each table can have different collation and character set. There are some tiny risks in taking backups if site is old (with some 3rd party activities) or big and it's good to check that saved backup sql file has all the tables included.ĭatabase itself has default collation and character set. I don't see this as a big problem in Fantastico installs IF sites are using only latin characters - but most sites do use unicode characters and other languages in addition to english. Most versions of phpMyAdmin and MySQL allow both moodle and `moodle` (or what ever the name is with or without backticks) but some old versions may requre even separate commands for character set and collation with backticks - these can all be given from SQL tab in phpMyAdmin - or you can change the collation of database from Operations tab in phpMyAdmin. Or if you want to continue with Fantastico install you could take full backup of tables (export tables with phpMyadmin) and restore the mysql dump file back using utf8 charset (import tables with phpMyAdmin).or alter each table separately if you want.Thanks Mauno And to the latest available stable version (current 1.9.7+), not any repaired Fantastico version. Even with CPanel or FTP you can delete old folders created with fantastico install (moodledata or uploaddata) and reinstall moodle in a way that can be later upgraded and modified without Fantastico. You could as well drop all current tables, make sure that collation is some unicode collation and charset is utf8 and install standard moodle package from to some folder inside your htdocs. If the start is correct all data that goes to database gets correct collation and charset automatically using default values. The easiest solution is usually to create a fresh database with correct collation and charset or alter collation and charset of empty database with sql (the other tab in phpMyAdmin) command likeĪLTER DATABASE moodle DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci ĪLTER DATABASE moodle DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci (Backup) The DEFAULT collation and char set of your whole database BEFORE you install anything - and the content of different tables that you try to change afterward. There are two different things that matter: It's amazing how these Fantastico installs still use latin charsets - and continue to mess all updates etc later.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |