500 Internal Server Error

Sébastien Vercammen

March 10, 2021 21:21
Edited

Hey there,

I'm getting 500 Internal Server Error in the Cloud editor, and a lot of settings aren't working/saving.

Second issue: For a Text block, the "line height" setting is also broken - it's empty, in the HTML the value is set to "NaN" (and changing it by hand doesn't fix it), and the up/down buttons don't work. The field stays empty, with a "NaN" value in HTML.

Comments

11 comments

Sandra Prunici

March 11, 2021 14:26
Hi,

Yesterday we release a Cloud update and for this reason for 10-15 minutes, the Brizy Cloud wasn't available. Now, all should work fine. Could you please check the Brizy Cloud dashboard now?

About the second issue - in what conditions did you found it? Did you change the font and then added it back and then you receive this problem with empty "line-height"? We know about this behaviour and issue and our team are working to investigate and fix this problem. I'm sorry for this problem. We are doing our best to solve it as soon as possible.

Thanks!

Best regards,
Sandra
0

Sébastien Vercammen

March 11, 2021 14:38

Hi Sandra,

I created a new popup from a template, project ID 5661652, and its default background is still causing a 500 Internal Server Error on the URL https://apricot5661652.brizy.site/

Trying to set the popup to Global also doesn't work - it shows the loading icon permanently no matter how long you wait (tested waiting 1h+ yesterday).

The following error can be seen in console:

editor.js:133 Uncaught (in promise) TypeError: Cannot read property 'id' of undefined
    at O (editor.js:133)
    at editor.js:133

The code is obfuscated so there's not much more I can tell you, but when I pretty-print the file to get better code presentation, editor.js:133 refers to the following lines (with the error on line 3, e.collectionType.id):

    const O = (e=Object(i.B)(Object(r.b)().getState()))=>{
        let t = p
          , o = l.c ? e.collectionType.id : "page";
        if (l.l) {
            const {ruleMatches: e} = a.a.get("wp");
            c.g ? (t = m,
            o = h) : e && "post" === e[0].entityType && (t = p,
            o = "post")
        }
        return {
            group: t,
            type: o,
            id: e.id
        }
    }

Sébastien Vercammen

March 11, 2021 14:39
Where the line-height issue is concerned, it was indeed while changing the font, and this error is less critical than the popup.

Not being able to publish the popup is the last thing holding me back from publishing a website.
0
Sébastien Vercammen

March 11, 2021 16:43
Just tested with Firefox, to make sure it's not my Chrome, and getting the same error:
```
Uncaught (in promise) TypeError: e.collectionType is undefined
    O https://www.brizy.cloud/editor-build/free/172-cloud/editor/js/editor.js:133
```
No plugins are installed on Firefox.

The 500 Internal Server Error also still happens.

Creating a new Popup also did not fix the problem - trying to set it to Global still triggers this error.
0
Sandra Prunici

March 12, 2021 09:17
Hi,

Thank you for all these details and reports. We are aware of these problems you encounter with external pop-up and empty line-height while changing the font in the Brizy Cloud. For both of them, we created an issue and informed our developers. They are already working on it and investigating them to find the best solution. In the next Brizy Cloud updates we will release the fix and all will work fine. I'm sorry for these problems.

Thank you in advance for your understanding and patience!

Best regards,
Sandra
0
Sébastien Vercammen

March 13, 2021 14:17
Hi Sandra,

Do you have an ETA on the release cycle?

As mentioned before, this is a critical bug for us because it's blocking our launch, and having an ETA - even if not perfectly accurate - helps us plan for it.
0
Sandra Prunici

March 15, 2021 13:49
Hi Sebastien,

I would like to provide an ETA for this feature but unfortunately, we can provide it. We are doing our best to release this fix and we are striving to release it as soon as possible.

Thanks!

Best regards,
Sandra
0
Sébastien Vercammen

April 13, 2021 15:41
Hi Sandra,

It's been over a month and the same Brizy Cloud error is still blocking our business.

Has it been fixed yet, or is it time for us to move on from Brizy?
0
Sandra Prunici

April 14, 2021 09:09
Hi,

The problem with line-height and letter spacing is on the testing stage and improvements, therefore, we suppose that in the next updates we will release the fix.

The problem with external pop-ups added as embed on external sites is already fixed. Could you please check it again and inform us if you receive the same problem? Where did you embed the pop-up? Is it a WP site or a non-WP site?

Thank you!

Best regards,
Sandra
0
Sébastien Vercammen

April 14, 2021 18:21

Edited
Hi Sandra,

Brizy Cloud > Edit Popup > top right corner, click the left icon for the popup's settings > enable "Make Global".

This causes an error, and has been causing an error as described in my message a month ago. The "loading" spinner won't disappear either after clicking "Make Global" due to the bug.

It's not even being used/embedded yet. It's purely in the popup's cloud editor, to make it global.
0
Sandra Prunici

April 15, 2021 09:57
Hi Sebastien,

I'm sorry, I missed that you asked about making global or save an external pop-up. Yes, we know about this problem and our developers are almost finished fixing this problem. In one of the future updates for Brizy Cloud, we will release the fix for this issue too.

Best regards,
Sandra
0

Please sign in to leave a comment.

Comments

Didn't find what you were looking for?