EDGE got stuck at 50% updating the forum width

[GuestGuest]

Whelp! EDGE got stuck at 50% when changing the forum width from 100% to 90%. Quickly making the cap below, the founder was logged out automatically after an hour and nothing changed! What now?




After logging in again:

[Ange TuteurAdministrator]

@Samantha NL try updating the width again, but open the console before clicking the button to save the changes. You can open the console by doing the following :
1. F12 > Console tab
2. Right click > inspect element > Console tab

Once the console is open, save the changes. If any errors occur it should pop up in the console. Also note : Depending on the size of the stylesheet and latency with Forumotion's servers, it might take a few seconds ( or minutes ) to update.

If there are any errors, let me know.

[GuestGuest]

Ofc... it worked 100% now, because FAE's creator went online



So what was causing it? Or did you fiddle with something in the bg to make it work and then told us to try again?


By the way, it said : "Click here to reload the page". That's something we didn't see in the translation...

[Ange TuteurAdministrator]

That's good, it may have been a latency issue then. When updating the stylesheet it has to send a large packet of data to the server, this can take awhile depending on your connection and Forumotion itself. The best thing to do is be patient and let it do its thing. If an error does occur it usually displays red text in the log saying where the error occurred.

That's something outside of the translatable range at the moment, but it's definitely possible that'll need an alias eventually.

[GuestGuest]

That's good, it may have been a latency issue then. When updating the stylesheet it has to send a large packet of data to the server, this can take awhile depending on your connection and Forumotion itself. The best thing to do is be patient and let it do its thing. If an error does occur it usually displays red text in the log saying where the error occurred.

That's something outside of the translatable range at the moment, but it's definitely possible that'll need an alias eventually.

Yeah. I just told him. Because when he retried it just took a sec or so. We had been patient, for like an hour or so this afternoon. I told him I wanted to take a cap just before he logged off and so... well, that told the story alright, yk. We got scared some JS or whatever got (half-)edited and we reported it before logging in again.

So, it's solved now. Thanks for your time and explaining.

Lemme know about any updates in the translational parts. I'm doing the translations here, the best I (or rather: we are doing) can

[Sponsored content]