Any way to import v3 SQL backup to v4 fresh installation?

[Skotina]

Hello all,

Long story short - I messed up with backups and ended up with broken chevereto v3 installation with several problems.

1. High CPU consumption by DB - big queries just hang up DB and consume 100% of CPU time.
Example below:

SELECT
        *,
NULL AS image_original_exifdata
FROM
(SELECT
            *
FROM
            chv_images
LEFT JOIN
            chv_users
ON chv_images.image_user_id = chv_users.user_id
LEFT JOIN
            chv_albums
ON chv_images.image_album_id = chv_albums.album_id
WHERE
chv_images.image_is_approved = 1
AND (
image_views > 0
            )
AND (
chv_users.user_status IS NULL
OR chv_users.user_status <> 'banned'
            )
AND image_size > 0
AND (
chv_albums.album_privacy NOT IN (
'private', 'private_but_link', 'custom', 'password'
                )
OR chv_albums.album_privacy IS NULL
            )
AND (
                (
image_views < '6260'
                )
OR (
image_views = '6260'
AND image_id <= '2278'
                )
            )
ORDER BY
chv_images.image_views DESC,
chv_images.image_id DESC LIMIT 51) chv_images
LEFT JOIN
        chv_storages
ON chv_images.image_storage_id = chv_storages.storage_id
LEFT JOIN
        chv_categories
ON chv_images.image_category_id = chv_categories.category_id
ORDER BY
chv_images.image_views DESC,
chv_images.image_id DESC

2. Impossible to upgrade because of the above problem - the server ends with error when trying to load anything.

So the big question is - does anybody know how I can import existing albums/images data from sql to new v4 installation? Tried several queries but ended up with 404 error when clicking on the image in album.

Or any way to inject the SQL queries to fresh v3 installation and make it work like before and then upgrade to v4?

Any help is appreciated.

 

[blackjack]

I would update your old instance to the latest version 3.20.XY. Then move to V4 and run the database migration command or go to /update url.

 

[Skotina]

I would update your old instance to the latest version 3.20.XY. Then move to V4 and run the database migration command or go to /update url.

Thanks for your thoughts but it's impossible at the moment can't run the backup (moved to another server and can't trace the error that prevents the app from loading). Guess it is a fresh start then