Skip to main content
Topic: EARLY Beta version of 2.0  (Read 6021 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: EARLY Beta version of 2.0

Reply #15

Ah yes, I see the code overflow when I narrow the browser .. solution, don't do that :laughing: 

Re: EARLY Beta version of 2.0

Reply #16

I'm in !
Thank's


Re: EARLY Beta version of 2.0

Reply #18

I made a CSS change which should have fixed that grid blowout issue.


Re: EARLY Beta version of 2.0

Reply #20

Glad to see Elkarte online :cool:

--- edit ---
seems that inline attachments are not visible, here an example https://www.elkarte.net/community/index.php?topic=6037.msg42918#msg42918
Last Edit: January 05, 2022, 05:41:21 pm by radu81
sorry for my bad english


Re: EARLY Beta version of 2.0

Reply #22

I put in a temporary fix for the attachment not showing and likely a few other issues here and there (same root cause)

The final fix will likely be a bit more involved, assuming I make up my mind what I want to do:confounded:
Last Edit: January 08, 2022, 09:25:58 pm by Spuds

Re: EARLY Beta version of 2.0

Reply #23

When I click on the "mark all messages as read" button, there is an endless looping.
Shown in the screenshot.

Re: EARLY Beta version of 2.0

Reply #24

I had something similar, I was not able to quote a message, but after cleaning the cache files in my browser the problem was solved.
sorry for my bad english

Re: EARLY Beta version of 2.0

Reply #25

Quote from: radu81 – I had something similar, I was not able to quote a message, but after cleaning the cache files in my browser the problem was solved.

after clearing the cache in the browser Chrome, the problem is not solved

Re: EARLY Beta version of 2.0

Reply #26

I'll log it so it can be looked into

Re: EARLY Beta version of 2.0

Reply #27

When you have a multi page topic, reply counting restarts each page, so on page 2 you get no mention of the first post, then it’s reply #1, reply #2 etc. And again on page 3.


Re: EARLY Beta version of 2.0

Reply #29

And it should be fixed now