Hi guys,
the updater is finished!
The updater makes it possible for AUS-user to update their chv2.x to chv.3 without losing userdata.
Note: All passwords get lost, so inform your users to use password-forgotten to set a new one.
Functions:
I noticed some strange bugs while testing the updater, the mysql-process used a lot of memory (between 1gb an 5gb).
You have to take a look after step 3 and 4 , if everything is right in your db.
I only tested "connect images to user" with 5300 records, so more could take a lot of time.
Please use "import users" only one-time, or could get duplicate entrys.
Step 4 (connect images) after finishing the process, reload the site and click the button once more, if the success window tells you 0, everything is right->proceed with step 5.
Step 5 will take a while (tested with 5300 records).
Last step: get rid of AUS, if you want to keep the data don't click the button (It won't affect your chv3 system).
_____________
Setup the updater:
in chv2.x paste the whole folder (aus_update) into your directory index (user/public_html/www/chevereto/).
edit sql.php in aus_update (use the database of your chv2.x).
Then type in your browser: http://mysite/aus_update
The updater should appear.
Follow step one.
Update chevereto to chv3 (at least 3.2.5).
aus_update should now be in the same directory-level as index.php and install.php of chv3.x.
return to http://mysite/aus_update and follow the next steps.
If everything was right, welcome to CHV3!
_____________
Do you have problems to update chevereto?
I had some problems to update chv2.x to chv3, now i'll provide some solutions:
Initial release: Version 1.0
Update: Version 1.1 translated comments to english
Update: Version 1.2 set inactive AUS-accounts to "awaiting-confirmation"
the updater is finished!
What does the updater do?
The updater makes it possible for AUS-user to update their chv2.x to chv.3 without losing userdata.
Note: All passwords get lost, so inform your users to use password-forgotten to set a new one.
Functions:
- Copies important data as backup
- Edits the chv3 tables (update purpose)
- Imports AUS-users to chv3-users (generates random user_usernames for accounts without a username)
- Connects images to their uploader (User gets them listed in his/her account)
- Necessary count of images, to set the right amount in the user-table
- Deletes all AUS-data (DB-only!)
I noticed some strange bugs while testing the updater, the mysql-process used a lot of memory (between 1gb an 5gb).
You have to take a look after step 3 and 4 , if everything is right in your db.
I only tested "connect images to user" with 5300 records, so more could take a lot of time.
Please use "import users" only one-time, or could get duplicate entrys.
Step 4 (connect images) after finishing the process, reload the site and click the button once more, if the success window tells you 0, everything is right->proceed with step 5.
Step 5 will take a while (tested with 5300 records).
Last step: get rid of AUS, if you want to keep the data don't click the button (It won't affect your chv3 system).
_____________
Setup the updater:
in chv2.x paste the whole folder (aus_update) into your directory index (user/public_html/www/chevereto/).
edit sql.php in aus_update (use the database of your chv2.x).
Then type in your browser: http://mysite/aus_update
The updater should appear.
Follow step one.
Update chevereto to chv3 (at least 3.2.5).
aus_update should now be in the same directory-level as index.php and install.php of chv3.x.
return to http://mysite/aus_update and follow the next steps.
If everything was right, welcome to CHV3!
_____________
Do you have problems to update chevereto?
I had some problems to update chv2.x to chv3, now i'll provide some solutions:
- G\ app/settings.php not found -> just create an empty settings.php in chevereto/app/
- Could not create admin-account -> all needed sql-statements are in chevereto/app/install/sql copy and run users.sql
- If you get more errors like that, open the specific sql file and run the query manually (DO NOT RUN THE CODE OF images.sql)
- run the following querys for chv_images (
ALTER TABLE `chv_images`
MODIFY `image_id` bigint(32) NOT NULL AUTO_INCREMENT,
MODIFY `image_name` varchar(255),
MODIFY `image_date` DATETIME,
CHANGE `image_type` `image_extension` varchar(255),
CHANGE `uploader_ip` `image_uploader_ip` varchar(255),
CHANGE `storage_id` `image_storage_id` bigint(32),
DROP `image_delete_hash`,
ADD `image_date_gmt` datetime NOT NULL AFTER `image_date`,
ADD `image_description` text,
ADD `image_nsfw` tinyint(1) NOT NULL DEFAULT '0',
ADD `image_user_id` bigint(32) DEFAULT NULL,
ADD `image_album_id` bigint(32) DEFAULT NULL,
ADD `image_md5` varchar(32) NOT NULL,
ADD `image_storage` enum('external','direct','datefolder','old') NOT NULL DEFAULT 'datefolder',
ADD `image_original_filename` text NOT NULL,
ADD `image_original_exifdata` text,
ADD `image_views` bigint(32) NOT NULL DEFAULT '0';
UPDATE `chv_images`
SET `image_date_gmt` = `image_date`,
`image_storage` = CASE
WHEN `image_storage_id` IS NULL THEN 'datefolder'
WHEN `image_storage_id` = 0 THEN 'datefolder'
WHEN `image_storage_id` = 1 THEN 'old'
WHEN `image_storage_id` = 2 THEN 'direct'
END,
`image_storage_id` = NULL;
RENAME TABLE `chv_info` to `_chv_info`;
RENAME TABLE `chv_options` to `_chv_options`;
RENAME TABLE `chv_storages` to `_chv_storages`
Initial release: Version 1.0
Update: Version 1.1 translated comments to english
Update: Version 1.2 set inactive AUS-accounts to "awaiting-confirmation"
Attachments
Last edited: