This morning i woke up rather early, around 9am.. so.. today’s plan is to prepare a necessary backup for both of the site content and database table. I’ve been following the instruction for 1.0.12–>1.5.0 migration, but after spending 2-3 hours tinkering the shit, well… it’s still.. no apparent solution until i forced to give up… (take a break and eat some lunch first i mean)..
I’ve compressed the site’s content into one single zip file, but handling the database, on the other hand, was quite tricky. I’m quite shocked when i saw the backup .sql file.. it’s 12Mb! damn.. wondered for a few mins and i figured out that i think it’s because the statistics.. and prediction was right.. and uh.. i think it’s time to eliminate the gathered data.. (btw joomlastats gathered all kinds of useful stats). after purging its table, the size immediately reduced to just friggin 3Mb..
ok after mounted the site on a testing server (which is my xampp), populated, imported the dbase, and changed its configuration.php file, it work’d like charm. ok so i’ve now got a mirror site on my localhost, and i’m goin to test the official migration tool that i’ve downloaded earlier. (com_migration stable v.1 release — download link HERE). i installed it without problem, configured here and there, it comes out as a table structure that’s specially modified for version 1.5.. so after the dbase table structure has been changed from previous 1.0.12 to version 1.5, i created a new directory, downloaded 1.5.3 (newest stable version of the Joomla! CMS), mounted on my server, and here comes the trouble.
It appears that the table unsuccessfully populated with the old content. shit. i’ve tried several times tweaking here and there, searching some solutions in the Internet and it seems most of the people also experiencing the same error. (btw the data migration is only for the core joomla table, i think i’ll need to export and import the other tables manually.. FB, expose, shit load of them..
Ok that’s 2 hours. the 3rd hours i’ve managed to see some of the useful extensions out there, and it seems this mtwMigrator won’t solve the problem either. I’ve installed this component on the v.1.5.3, and it works and succesfully migrated some of the tables, but some of them are not migrated due to duplicated key.. .. hmmm…
Hopefully it’s not a dead end and i’ll hope i’ll find the answers sooner… erm.. some ppl might ask, why do i want to migrate?.. this is mainly because the old ones are … maybe … suck… first time installing it and lots of stupid experimentation ends up screwing the core content, and some of the stupid component table can’t be eliminated (zoom ftl), corrupted dbase table, unstable and stuff idk… besides that, killing my time perhaps..
the domain name and the webhost gonna expires soon.. i better hurry up searching local webhost company to rent.. erm.. local webhost most likely to be more reliable, fast and cheap.. well… since i can’t choose all three, perhaps i’ll sacrifice on the price.. this time, i’ll focus on the quality instead… anyone have recommendations?