Error In Import Plugin - Importing For Blesta 2.5 Db

[bdnetworks]

Hi guys - I'm finally getting around to upgrading from 2.5 to the newer 3.x versions. I downloaded the latest version (3.4.2) today and have it installed. I followed the instructions from the Blesta Docs website to install the Import Plugin and migrate my data over from the 2.5 database. I can open the Import tool, enter my database information and AES key, then select the "Automatically create any necessary packages during import" option, but as soon as I click on the final "Import" button, I get the following error (pasted below and screenshot attached).

 

SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '* FROM (SELECT `p_id` AS `id`, `p_instantact` AS `instantact`, `p_modrow` AS `mo' at line 1

 

The script was definitely able to connect to the MySQL database, because the packages and clients were migrated over. No invoices or services were copied though....not sure what else wasn't moved.

 

My system specs:

• Linux (Debian)
• MySQL 5.0.67
• Apache 2.4.12
• PHP 5.5.22 (Yes, I installed the 5.5 patch from the Blesta zip file)
• ionCube 4.7.5

 

Any suggestions as to what I should do? Thanks in advance -BD

 

[Paul]

Are you migrating from Blesta 2.5.4? If it's something less than 2.5.4 (ie 2.5.0-2.5.3) then it wouldn't work.

 

The error seems to indicate an issue with the query, but I've never seen this reported before and it's hard to say without the full query. It appears to be fetching module row information.

 

Are you importing to Blesta 3.4.2, using the Import Manager that ships with that version?

 

MySQL 5.0.67 is fairly old, and it should work, but curious why MySQL is so much older than your PHP. Upgrading MySQL might be a good idea, but I'm not confident it would result in a better outcome.

[bdnetworks]

I came back to post that I figured it out, and then realized you had responded with what the actual issue was...guess my spam filter ate the message notification. The problem was: I wasn't on 2.5 - I was still using 2.1.0...hadn't realized I was so far behind. I upgraded to 2.5, and then was able to successfully migrate to 3.4.2.

 

Thank you for responding quickly; and I'll heed your advice about MySQL as well. -Aaron