Get_white_screen_when_send_feedback_or_send_message_and_send_message_…

serge-web / serge

Serious Gaming, Evolved - web interface

https://sites.google.com/deepbluec.com/serge/

Apache License 2.0

14 stars 4 forks source link

Get_white_screen_when_send_feedback_or_send_message_and_send_message_… #2925

Closed lilitkarapetyan closed 4 months ago

lilitkarapetyan commented 4 months ago

…from_admin

Fixes #2921

🧰 Issue

🚀 Overview:

🔗 Link to preview

🤔 Reason:

🔨Work carried out:

[x] Tests pass

🖥️ Screenshot

Confirmations

[ ] I have chosen reviewers for my PR.
[ ] I have assigned myself to this PR.
[ ] I have chosen an appropriate label for the PR.
[ ] I have completed the mandatory sections of this document.
[ ] I have deleted any unused sections.
[ ] I confirm that I have checked for required README updates and acted accordingly.

📝 Developer Notes:

IanMayo commented 4 months ago

Hello @lilitkarapetyan - can you explain how this fix works please? Surely we don't have a database called _global_changes?

lilitkarapetyan commented 4 months ago

Hello @lilitkarapetyan - can you explain how this fix works please? Surely we don't have a database called _global_changes? The _global_changes" database is automatically generated by CouchDB by default. It's part of CouchDB's built-in functionality to track changes across all databases within the instance. it's just that its structure doesn't match the new messages we're receving, that's why we get an erro. ![Uploading Screenshot (286).png…]()

IanMayo commented 4 months ago

I don't remember this feature. Can you remind me please @lilitkarapetyan ?

Update: sorry I missed the CouchDb part of the message. Got it.

lilitkarapetyan commented 4 months ago

I've updated it so that the updates from _global_changes aren't sent to tthe client through socket anymore I think it is not necessary for us in the client section