After few minutes of checking I already found several issues when migrating from Editor to Editor X.
Property events are not migrated e.g., If I coded in JS a button click event, it won’t work. This mean that I need to go trough all buttons. set the property, copy ad paste the JS code to the new generated button event JS code.
It’s not possible to connect collection data to the header (I believe the same problem occur in the footer)
The horizontal sub menu are not working.
All hidden menus are displayed (I believe that the hidden setup were not migrated).
The migration added back to the menu, the blog, the account, the sign on and some others.
Not all elements were migrated in several pages.
The Auto save of/on is not available in editor x, which is a big issue, because it’s not always safe to save the changes immediately.
I hope somebody will read my post and these issues will be fixed before the deadline of 1st March 2023
Migrating from one version of a software to another can sometimes be a challenging process, as you have experienced with your migration from Editor to Editor X. It is not uncommon for there to be some issues or differences in functionality between the two versions, and it can take some time and effort to resolve these issues and get everything working as desired. Some of the issues you mentioned, such as the missing property events and problems with collection data and horizontal submenus, may be due to differences in the way these features are implemented in the two versions of the software. It may be necessary to modify your code or set up these features differently in order to get them to work properly in Editor X. The fact that some hidden menus are being displayed and that not all elements were migrated to the new version could also be related to differences in the way these features are implemented. It may be necessary to manually adjust these settings or recreate any hidden elements in order to get them to work as desired in Editor X. I can only recommend you to wait until new updates and features are added and your website works better on Editor X.
Hello,
I am not an expert but I just want to say that I understand that you’re facing several issues while migrating from Editor to Editor X in coding with Velo. Migrations can sometimes introduce unexpected challenges. While I can’t directly fix the issues for you, I can offer some suggestions on how to approach and potentially resolve them:
Property events: Since the button click events are not migrated automatically, you’ll need to manually set the properties and copy/paste the JS code to the new generated button event in Editor X. It might be helpful to create a checklist of all the buttons and their corresponding events to ensure nothing is missed during the migration.
Connecting collection data to the header/footer: If you’re unable to connect collection data to the header or footer in Editor X, you might need to explore alternative approaches. This could involve adjusting your data structure, using different components, or finding workarounds specific to the Editor X platform. Review the Editor X documentation or reach out to their support team for guidance on how to accomplish this.
Issues with horizontal submenus: If the horizontal submenus are not working correctly after the migration, you may need to inspect and debug the code responsible for the submenus. Check for any discrepancies between the original code and the migrated code, and make any necessary adjustments to ensure the submenus function as intended in Editor X.
Displaying hidden menus: If hidden menus are now being displayed after the migration, it’s likely that the hidden setup was not properly migrated. You’ll need to review the configuration of the hidden menus and make the necessary adjustments in Editor X to restore their intended behavior.
Unwanted elements added back: If certain elements like the blog, account, sign-on, or others were added back during the migration, it could be due to differences in the default setup between Editor and Editor X. You’ll need to remove or reconfigure these elements manually according to your desired setup.
Missing elements in pages: If not all elements were properly migrated in several pages, you might need to carefully review each page’s content and compare it with the original Editor version. Manually add any missing elements and adjust their properties as needed in Editor X.
Auto save functionality: If Editor X doesn’t provide an auto-save feature, you may need to adjust your workflow and save changes manually at regular intervals. It’s important to be mindful of saving your work frequently to avoid potential data loss. Consider making a habit of saving before making significant changes or taking breaks.
Thank for your detaiiled answer, but as a veteran of informatic system, I can tell you that this time Wix did a very poor job. Wix is a great product, but the automatic migration is a failure to my opinion.
It took me motre than 3 months men days to migrate one moderate site. The new editor doesn’t support tables and the repeater feature has signicantly less functiality than tables and has also several bugs. They also didn’t migrate datepickers.
By the way, the migration module is not available at the moment. they claim they are making some improvements, but there is no expected date.
Thank you anyway,
