I attempted to pull up the Editor moments ago (12:58pm EDT) and it redirects to the Maintenance page. However, https://status.weweb.io/ indicated maintenance should have been completed. Is there anything more the team can share?
1 Like
Same here.
Is there a new expected time for the editor to come back to us? @Joyce 
Hey there 
Yeah, sorry about that. I just updated the maintenance page to reflect the fact itâs taking longer than expected.
The tech team is all-hands on restoring services as quickly as possible. ETA right now is 7:30pm UTC but I canât make any promises.
Iâll keep you posted as soon as I know more.
2 Likes
Thank you for the quick and honest reply. We look forward to it! 
2 Likes
Thanks so much for your support, we really appreciate it!
We really look forward to it too 
I honestly canât wait to put this monster release behind us and get back to shipping improvements on a weekly basis! 
4 Likes
Aaaand weâre live!!!
Thanks so much for your patience. We really hope you love this update and canât wait to get all your feedback on board to start shipping improvements
2 Likes
1 Like
WAHOO!! Looks awesome!
Just a heads up. flow logic in workflow goes off the screen though 
I just wanted to be first. lol. Still like the upgrades.
1 Like
haha keep them coming @esowers!
Iâll log it as well on my side. If you see any others, can you create a ticket here with a short image or screen recording?
Maybe I am overlooking something simple, however what is the difference between Integrations and Plugins? For example, we have Xano added as a Plugin, however it also shows it is not added as an integration, but can be added.
Hey Derek
The Plugins is the old way of doing things. You can continue to work with Plugins and Collections in the Interface tab (you can think of that tab as everything that existed when WeWeb was âjustâ a frontend builder).
We didnât want to do the migration for you because the risk of breaking production apps was too high.
You can use Integrations if you want to. Itâs completely optional. We recommend it because having the clear separation between all things front and all things back is a nicer building experience, but you donât have to 
If youâre migrating an app, you can have both the Plugin and Integration running at the same time and do the migration little by little.
Does that make sense?
Just to add on to what Joyce said above^
in the case of Xano, the big difference is that the Xano integration offers WeWeb backend capabilities that the plugin doesnât.
For example, with the Xano integration installed, you then have access to Xano actions inside WeWeb backend workflows. (So you could do something like using a âXano requestâ action inside an API endpoint in your WeWeb backend).
Or you could use a table in Xano as your source of data for a WeWeb table (which then lets you set up table views in WeWeb on top of your Xano table).
The Xano Auth system in the new backend also has some features that were not possible with the plugin, such as having control over handling refresh tokens.
2 Likes
Please when can we have variable aliasing???
1 Like
Where can we report bugs or make suggestions regarding the new update?
1 Like
Right here: https://support.weweb.io/
Hey Bellie
What do you mean? Youâd like to be able to bind the default value of a variable to another variable for example or did you have something different in mind?
I just submitted one. Maybe I am missing the verbose setting but the debug panel isnât showing workflow related returns / responses anymore. You now have to click into the workflow and open a tiny popup window that shows the raw json while the old UI displayed them in the debug side panel with nice collapsible objects.
1 Like
Ok, thanks for reporting this! The team will take a look and get back to you asap
