> For the complete documentation index, see [llms.txt](https://docs.gmetri.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gmetri.com/features/release-notes/2023/01-10-jan-update.md).

# 01-10 Jan Update

v0.5.3734 / 01 Jan 2023

### :rocket: Major Features

* WooCommerce integration. There is now a WooCommerce plugin in GMetri. You can bring your existing stores built on WooCommerce easily into the Metaverse.
* A **Brand new Editor UI** [🥳](https://emojipedia.org/partying-face/) 🎉

  We have removed the left bar, and moved a lot of the functionality to a new bar, paving way for a sleeker UX and faster improvements

<figure><img src="https://2186043722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mgll1jjQMRTVj7p6n7g%2Fuploads%2FjSNUsPvXU8vb1Xm99Hcm%2FNew%20Editor%20UI.png?alt=media&amp;token=230303fa-7b43-45aa-89f1-02bda0a3426f" alt=""><figcaption><p>New Editor UI</p></figcaption></figure>

* Improved Avatar System

### :arrow\_double\_up: Minor Improvements

* A lot more ready to use "My Metaverse Rooms" added

### :bug: Bug Fixes

* Fixed issue with EmbedHTML and EmbedSCORM element where it makes a unnecessary request to server.&#x20;
* Fixed issue where screen gets locked in mobile phones
* My Metaverse Rooms use organization cname if present
* Fixed search in Resources Panel
* Fixed duplication of deployment for My Metaverse Rooms
* Fixed jittery transform control while dragging elements. Sometimes while dragging elements the controls used to disappear
* Fixed loading issue for V4 editor


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.gmetri.com/features/release-notes/2023/01-10-jan-update.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.