⚠️ SCHEDULED MAINTENANCE taking longer than expected

Announcements
1

SCHEDULED MAINTENANCE taking longer than expected :warning:

Hi everyone :wave:

As you know, the WeWeb editor is undergoing scheduled maintenance.

Unfortunately, the migration is taking longer than expected. Instead of going back live at 7:00 AM US Eastern Time, we expect to be back online around 10 or 11:00 AM 3 PM.

UPDATE: For more context, there are no issues with the release itself, but the migration is taking MUCH longer than we had anticipated. We always test in our development environment before and the timing of the migration is usually similar when we push to production but not this time around. We will investigate after the release to see if there’s something that explains this discrepancy.

Your live apps remain unaffected during this time.

Really sorry for the inconvenience. The team is doing its best to get everything back up and running asap.

Best,
Joyce

11 Likes
4

Alright! We’re back!

FYI, the WeWeb editor is a bit slow at the moment but should be back to normal in a few hours :slight_smile:

1 Like
6

Screenshot 2024-09-25 at 17.45.42
Screenshot 2024-09-25 at 17.45.42876×1038 115 KB

Sadly some elements still get the CSS applied to the wrapper instead of the element and they still have wrappers. But big kudos for the divs :slight_smile:

1 Like
7

We have two differents inputs now, one advanced supporting placeholder material style (which need a wrapper), and the basic one.
We have a migration to move most of the previous one to the simplier one, but we decide to not handle some corner cases and may have left some of them untouched (so still the “advanced” version, with a wrapper)

8

Do I get a price for reporting the first bug? :smiley: It seems like the modals are overlapping, you might wanna have a look. (Logs and Library)

Screenshot 2024-09-25 at 18.02.18
Screenshot 2024-09-25 at 18.02.18934×2326 104 KB

1 Like
9

I can’t sign-in. Getting a 504 Gateway Time-out error.

1 Like
10

Yes, some users are experiencing this on and off. The team is investigating. For now we don’t have answers but will communicate as soon as we do!

11

I hesitate to ask but figure being explicit is best. Is there any risk to making edits to our projects while the migration irons itself out? In other words, if I go and put in a bunch of work right now, is there a chance that the changes won’t persist?

12

With the new update, some of the overwrites in custom CSS for elements, go cleared.

Some places with transition property set got cleared as well.

Additionally, empty divs don’t show up in many cases. Use case - dividers.

13

Looks like the Gateway timeout is resolved for me now.

14

Is it possible that the HTML attributes are no longer working since the update?

1 Like
15

I’m noticing the same issue on my end - both with existing elements and a couple I was working on post-update.

16

Additionally Justify left and right are not working properly. In some places in order to justify flex children to the right you have to select left - strange…

1 Like
19

Hi all :wave:

Can you check that the change you see hasn’t been listed in the possible breaking changes here?

If it hasn’t, please open a support ticket with info about your project so the team can look into it.

20

Hi, I got suddenly 504 errors
image

21

Same, Editor stopped saving and upon reload it died.

23

Ah yes, sorry about this. It was the last scheduled downtime :slight_smile: We needed to restart the servers to allow a migration. Editor was down for 2-3 minutes.

1 Like
24

Also input for email code is not snapping to horizontal as well, just thought I’d share.