Applied "latest" and now unable to use Editor about vvveb HOT 3 OPEN

The first issue was missing tables in the database (fixed by applying various SQL scripts).

There are some recent changes to db schema mostly for ecommerce, the schema will be fixed after 1.0 release.

If some changes will be needed to schema after 1.0 release then they will be applied by the automatic update tool that will be enabled with 1.0.

loss of all changes to the main index.html page

Layout changes made in the page builder are saved directly to theme files, this complicates the theme update process.

Theme update will work by diff patching to keep custom changes.

the editor will not run at all - just a rotating circle of dots.

This might be caused by javascript files caching, it often happens after update, you can try clearing browser cache.

some guidance on how to methodically update my code or at least not break my home page

You should skip updating public/themes directly or manually update only folders like cart checkout etc where changes were not made.

Most recent changes to landing theme are done in the checkout area.

If you want to integrate some changes made on a page you have customized, you can use something like https://meldmerge.org until automatic theme update will be available.

Thank you!

from vvveb.

Interestingly, a copy in my Test area is working correctly ?
I have been playing catch up and note some additional changes in the last 2 hours that I will apply to my Test environement.
2 questions - it appears the </> Code Editor is now removed / disabled in the Admin module ( or I need to enable it ? )

and there seems to be a new DEBUG element at the bottom, but I cannot disable this by editing the env.php file (for Production) ?

from vvveb.

latest.zip has all the latest code changes before they are pushed to github and it's updated often.

The debug panel is from the debug plugin, you can disable it if you don't want to show the bottom debug panel.

The code editor is always enabled, there is no option to disable it.

Probably it is hidden behind the debug panel that displays at the bottom.

from vvveb.