ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Site Migration to New Host - MySQL Character Issues?

May 08, 2012 2:36pm

Subscribe [1]
  • #1 / May 08, 2012 2:36pm

    mmcgeeCC

    17 posts

    I’m migrating my site from one server to another, but there seems to be an issue with the exported MySQL database. At the end of all my links it is adding a variable, which in turn breaks the front end of my site.

    For example, in a template, this…

    <a href="{site_url}">

    Displays as this…

    <a href="{site_url}?phpMyAdmin=93c4fa92b93t4ca84294">

    This is the case for all templates as well as entries. If I open the sql file, that I exported, its in there too. The old server is running MySQL 5.0.22 / phpMyAdmin 2.8.2.4. The new server is running MySQL 5.0.95 / phpMyAdmin 3.4.5. I selected “drop table”, all character format that I come across is set to UTF-8. Everything seems to work fine except for this issue.

    I followed the migration instructions found here. I’m running EE v2.2.2.

    Any suggestions or is this a question for a MySQL forum?

     

  • #2 / May 09, 2012 3:18pm

    Dan Decker

    7338 posts

    Hi mmcgeeCC,

    Thanks for posting to the Forums!

    That really looks like an issue with the export or import of your database from PHPMyAdmin. If you inspect the dump before importing it, do you see the errant value anywhere?

    That would let us know if the error is being input by the export or by the import process.

    Do you have the option to connect to the database using any other means? Perhaps a GUI based MySQL tool that can import/export?

    Cheers,

  • #3 / May 10, 2012 10:16am

    mmcgeeCC

    17 posts

    I’m certain its on the export. The errant values are NOT there when I view the original database content, but ARE there when I view the exported sql file.

    My export process is selecting the database, then selecting export, selecting all of the tables, selecting “Add DROP TABLE”, selecting “Save as file” with no compression, then GO.

    Regarding another connection option, I’m definitely a novice in regard to MySQL, so I have no other option at the moment.

  • #4 / May 14, 2012 4:05pm

    mmcgeeCC

    17 posts

    So I’m still not sure what is causing this issue, but it is resolved if I export the database as gzipped instead of no compression.

  • #5 / May 15, 2012 11:25am

    Dan Decker

    7338 posts

    Hi mmcgeeCC,

    Odd, indeed.

    My experience has always been the opposite. That compression *causes* problems.

    I’m glad you were able to work around the error in PHPMyAdmin.

    If you need anything else with ExpressionEngine, please let us know in a new thread.

    Cheers!

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases