Found the bug! No more nameless shared servers :)

Dev Community Apps & Creations
1

So I have been searching for this for quite some time and finally found it :) FAST FORWARD to 3min to see the error where they have no names:

 

https://www.youtube.com/watch?v=G8pHEDMtdaE

 

There is a single cut that is breaking the Library/List.xml, Library/Grid.xml & Library/Bookcase.xml for mega multiple shared libraries if you remove this simple cut from each xml it fixes the error from ever happening and you can then see all the names of all the shared or local library tabs no matter how many you may have ;)

 

Grid.xml (error):

 

{{VAL(name)}}{{VAL(local::0= <{{TEXT(remote)}}>|0 =)}}
{{CUT(@main/size:CUT:0=CUT|1=CUT|2=)}}         

 

Grid.xml (fixed):

 

{{VAL(name)}}{{VAL(local::0= <{{TEXT(remote)}}>|0 =)}}

 

List.xml (error):

 

header>


{{VAL(name)}}{{VAL(local::0= <{{TEXT(remote)}}>|0 =)}}

{{CUT(@main/size:CUT:0=CUT|1=CUT|2=)}}      

 

List.xml (fixed):

 

header>


{{VAL(name)}}{{VAL(local::0= <{{TEXT(remote)}}>|0 =)}}

 

Bookcase.xml (error):

 

{{VAL(name)}}{{VAL(local::0= <{{TEXT(remote)}}>|0 =)}}
{{CUT(@main/size:CUT:0=CUT|1=CUT|2=)}}    

 

Bookcase.xml (fixed):

 

{{VAL(name)}}{{VAL(local::0= <{{TEXT(remote)}}>|0 =)}}

2

Yeah... bad programming.

Trouble is, this will CUT server when their number is starting with "1", which happens with 10..19, 100..199, and so on (though I doubt you tested it in the higher orders).

Try that:

{{CUT(@main/size:CUT:0=CUT|1=CUT|1 =)}}  <= that  behind the second 1 is important!
3

This fixes it as well using the modified cut, thanks I will use it in my fork also. Finally I hope no more intermittetent random nameless servers from here on out :)

Hard to test due to the issue being intermittent but thankfully currently its still there to test the original/modified and removed CUT's.