Migration service and script#123
Merged
Elfangor93 merged 121 commits intoJoomGalleryfriends:mainfrom Feb 21, 2024
Merged
Conversation
52ef1be to
0e626ce
Compare
|
I have prepared a test environment for this pull request. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
316ce30 to
0353915
Compare
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
2b89d1e to
4a9d1ec
Compare
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Member
Author
|
Yes, this is known. Im working on it. |
use new folder structure = no image usage != direct usage
If Use new folder structure=yes, compatibility mode has to be deactivated
Make the compatibility mode a sensitive parameter
When migrating the path of the category are not generated correctly when the compatibility mode is enabled and Use new folder struct = no.
More help for the case of incosistent category path in source database.
9b2139c to
84c4b23
Compare
Member
Author
|
Thank you everybody for helping! |
reilldesign
added a commit
to reilldesign/JG4-dev
that referenced
this pull request
Mar 20, 2024
This adds back the necessary information that was deleted in pull request JoomGalleryfriends#123.
Elfangor93
added a commit
that referenced
this pull request
Apr 2, 2024
fix masonry bug caused by #123
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds the migration service as well as a new MVC routine called
migration.A migration script called
Jg3ToJg4to migrate a JoomGallery v3.x to v4.x is already included. Additional migration scripts intended to be installed as an extension like in Jg3.The migration view can be requestid with the following url:
/administrator/index.php?option=com_joomgallery&view=migrationHow to test this PR
Attention!!
This PR is not compatible with Joomla v4.4.0, v4.4.1, v5.0.0, v5.0.1.
Older and newer versions of Joomla are fully compatible.
Prerequirements
There has to be a source (JG3 updated to JG4) and a destination (JG4) available.
There are two possibilities:
This way you end up having a source installation containing database tables looking something like
#__joomgallery_XX_old. And a JoomGallery administration folder containing an xml file calledjoomgallery_old.xml. The source needs to have some categories and images.Perform a migration
A migration consists of 4 steps.
You can go to the next step of the migration, if you successfully passed the prvious one.
Step 1: Configuration
Here you have to define where your source is located you want to use for the migration as well as how you want to write the records into the destination.
Source: JG3 updated to JG4
Destination: JG4
Step 2: Pre-Check
Your entire system and installation gets checked if everything is setted up correctly such that the migration will run without problems.
Step 3: Migration manager
Here you see a list of migration processes that have to be performed in a specific order. First the categories have to be migrated, then the images and at last the category thumbnails have to be reselected based on the new IDs created for the images during migration.
The start button starts the automatic execution of the migration process based on a queue. For each element in the queue an ajax request is started to execute the migration of this element. When the request returns from the server, the progress bar and the log output gets updated to inform you about the migration progress.
The automatic execution of the migration can be stopped at any time with the "Stop migration" button.
As soon as all the migration processes are performed the button on the bottom "Check and finish migration" becomes clickable.
Step 4: Post-Check & Finish
The results of the post check tells you how well the migration was done. It checks if all the queues are processed and if there were errors in the migration which might need to be resolved.
The button to remove the source data is not yet wokable. When you click it, you will always get a success message. But actually is not doing anything currently.