A tester reported that the latest version of my project cannot be imported. I can reproduce the problem. There is no error message. The project just does not appear in My Projects.
A version created a few days earlier can be imported no problem. The only difference is that more LUA code has been added. Just now, I tried importing the old version and pasting in the LUA from the new version. Saving that revised project and reimporting it did not fix the problem.
Perhaps given the extreme number of changes in the new web editor to support the Mini, the old one should be put up as well with a link we can access so we can continue mk2 development without running into beta testing issues?
I’ve tried reducing the size of the Lua file in the project that cannot be imported to below its size in the project that can be imported. That did not help.
Thanks @martin. Yes, that works for me on the beta site. Please let us know when the fix is in production, and/or announce it on the Releasing a new version of the web editor thread, which I’m watching.
The major part of this change is not the editor’s front end, but the underlying data structures in the database. When work on this project—adding support for a different controller—began, we considered two possible approaches:
Create a replica of the existing database that would serve as the backend for the new editor, while keeping the original editor running on the original database.
Migrate the database in several steps while making corresponding changes to the editor.
A considerable amount of effort was invested in exploring both options. The first approach, although it initially felt safer, required synchronizing all user changes in both directions: old → new and new → old. Without this, work on presets would be split across multiple databases. The synchronization logic proved to be quite complex and would have required ongoing effort and maintenance of two independent applications (the old frontend and the new frontend). After seeing this in action in our development environment, we decided to proceed with the second approach.
I know this has caused some inconvenience, and all our efforts are focused on resolving it. I am finalizing the v4.1.3 firmware update for both Mini and mk2, as well as the final adjustments to the web editor. I do believe that things will settle down.
There is no easy way to run the old version of the editor, as the database has changed. Even if we had chosen the multi-replica synchronized database approach, issues would have arisen as well. This is simply a major change, and we felt it was necessary. Many aspects of the system had remained unchanged since 2019, and it was time to move forward. Not only does this update add support for a second type of controller (and potentially more in the future), but it also enables work on new features that users have requested and that were previously difficult or impossible to implement.
Once again, I am sorry for the inconvenience, and I am doing my best to keep it to a minimum.