I believe you, the current code is ancient.

Our challenge is, that in order to fundamentally change this code we need development capacity. Most of us do not have the skills to make these changes (I know I don't). I suspect @tino would be able to do it, but I doubt if he has time to do that.

let's wait for him to chime in though...

I still lose 1-2 chars every 10 (N) seconds though, still annoying.

In tpshout.js, async is set to false:
   $.ajax({
      type : "POST",
      dataType: "html",
      cache: false,
        async: false,

is there any reason for this ?

Chatgpt also suggested to detect keystrokes in js, and delay the update interval by 500ms each time it detects typing. This might not be a perfect fix though, if you happen to make a ~500ms pause when typing.

Best solution would be to use websockets.

I just checked the installers from TP3.0.0 and up and in none of the codes is there any mention of the creation of tp_blocks table with the fields access2 and editgroups.

These columns were last used in Tinyportal in version 2.2.0 and dropped 5 years ago.

The only explanation I have for those columns being in your table is that, after you did a clean install of TP 3.0.0 you imported the table into the database from an old install (with TP version 2.2.0). If that is indeed the case then you can simply drop the columns access2 and editgroups from the tp_blocks table, because they are no longer used.
After that the install should run without errors (at least if there are no othet tables affected).

I understand why you would do such a thing to restore settings after the issue you had in November, but the result would be that the table is in an incorrect state.

I am really trying to help you, but once again you are not answering my questions.

Let me try again:
I need to know the contents of those columns in tp_blocks table. You are sharing the tablestructure and not the tablecontents.

You cannot view this attachment.

Based on the structure I already saw that the table contains two columns that should not really be there: 'access2' and 'editgroups' are not supposed to be there.
(How they got there when installing a clean 3.0.0 install beats me, but that is next.)

The upgrader is now trying to rename column access2 to display, which fails because 'display' is already there.
If you show me the contents of the table I can see what you can try next.

You cannot view this attachment.

Either column 'display' is empty  (no values) or it has the same values as column 'access2'. When we know that, we can determine a path forward.

Note: the screenshots are samples from a functioning 3.0.2 install: I need to same the same information from your forum.

whoa nellie! hope you aren't irritated cause I can get that way too.

I just told you that the db shows the column of display as being the names of the forum areas [matching what the forum has]
colum of access 2 is the names of the blocks

this is from the db of the tables:



if this still is not what you want I am so sorry

I KNOW what the contents of the columns means.

What I want you to tell me is, if both columns in the table have the same values for the blocks. This would indicate that the rename action has only partially completed. As long as you do not provide the actual content of the table I cannot help you...

aha, no the contents of the display column are the "ingredients " of all the boards and places in the forum where the one I sent you is the items of the tables in the TP area

That is not an answer to the question

I just checked the install.php for 3.0.2 and on line 983 access2 is mentioned

Seems the 2.0 .0 installer for TP installed access2