Today I was faced with a new theme editor that is much slower and harder to read than the original, it also doesn’t give you warnings for unclosed “body” and “html” tags.
Is there anyway to revert to the old version?
Here is what it looks like:
1 Like
The new version was previously opt-in and could be enabled by adding ?vs=1 to the URL. Try adding ?vs=0 to your URL instead - this might revert you back to the old editor.
1 Like
Hey folks - Adding ?vs=0 to the URL does not seem to work, checking internally if it’s possible to re-activate the previous version.
2 Likes
Merchants are complaining on the regular forums too.
Slower is putting it lightly it’s a MAGNITUDE of difference in poor performance.
The good editor loaded in seconds.
VScode is an entire developers IDE that’s so bloat it can take MINUTES to load.
3x in boot time, load size, and memory usage.
Not everyone is running around with souped up hardware.
and that’s not counting virtual environs requirements going up.
When you want to make even the most minor edit online there is now A BOOT TIME.
And then’s there is all the bugs.
Try editing a file on small screens / mobile that’s just ONE problem of many Many MANY MANY problems with this.
We are NOT getting a reasonable replacement here.
But more importantly merchants are the ones getting a really unreasonable replacement.
Merchants/staff non-dev non-techies shouldn’t be forced to use complex developers IDE’s just because developers are used to self inflicted growing complexity and so therefore think EVERYONE else should be subject to the same experience and should just get used to it.
What’s next if a merchant want’s to crop an image there gonna be forced to bootup photoshop because the art teams are used to that tool??
1 Like
Hello @Liam-Shopify 
Any news on the topic ? I got multiple merchants asking me for a way to re-activate the previous version.
As a follow-up question, is the legacy editor discontinued or there is a plan to keep both versions alive ?
Thanks in advance and good day to you and the team !
Hi again folks - just to confirm, there’s currently no way to revert back to the old theme code editor, or opt out of this update.
I have highlighted the feedback shared here internally though, and I know we’re currently shipping performance improvements so you’ll see the loading speed up, and I expect other bugs will be addressed asap.
1 Like
Personally, I think the new editor is far better than the previous version.
Just the fact you can search for keyword, class name, function name and you get all files is mind-blowing. You couldn’t do this on the previous version.
CTRL/CMD+SHIFT+P allows you to open any snippet in a second.
Theme upgrades/migrations are far easier too.
Github has a similar editor. Probably if they would add more themes and dark mode it will be much easier to graps: https://github.dev/Shopify/function-examples
A better liquid syntax highlighting, parsing and better validations would improve the VSCode editor. Also, getting some feedback when the file is saved would be nice.
In the future, I think the new VSCode editor integration will be linked with AI that brings the entire store context and make it easier to build new functionality, sections and so on.
1 Like
Thanks for the news Liam
@app Do you have examples where any of these are not working in the new editor? I would love to share them with the team.
They are working for me, but I’m working with VSCode for more than 5 years and it feels native. For a new user, maybe is too much, but they don’t know the power of VSCode.
I was referring to the closing tags validations and syntax highlight as @David_Arbias mentioned in the first post. The previous Shopify code editor was giving some validations errors if some of the liquid tags were not closed, or missing.
It would be nice to see more clearly what tag was not closed and prevent saving the file if the validation fails.
These light theme colors are ok for me as I’m used this light theme, howver, for other users probably it will be easier for others to if they change VSCode themes to (Dark+, Monokai, Github Light, GitLab style) and so on.
A short learning video designed for merchants so they understand and learn how to use this new editor and what was changed would be a great idea. They need to understand why this editor is better than the previous. For example, How, CMD+S (hotkey) will save the changes without much effort. How CMD+Shift+P allows them to search through snippets..
One of our merchant had several CSS issues as they added some new CSS code and removed the the “}” when they added their custom code. There was new indication that something was wrong and the parsing was only added to the @media query.
Without looking at the minified/compiled CSS file, there was no way to know the file was broken because they removed the “}”.
There were some just some ideas and random thoughts.
Personally, I’m very happy with the new editor