Version3 Preview 6 Database Editor wont shown

vradarserver / vrs

A .NET web server that can plot the positions of aircraft on a map

http://www.virtualradarserver.co.uk/

Other

269 stars 50 forks source link

Version3 Preview 6 Database Editor wont shown #44

Closed antonov124 closed 3 years ago

antonov124 commented 3 years ago

With the lastest Update Preview6 da Database Editor wont shown. Back to Preview 3 Database Editor is back... (Dont have Preview 4/5)

Bug or Feature?!

vradarserver commented 3 years ago

I've just run v3 preview 6 on both Windows and Ubuntu and the database editor is working fine.

Bear in mind that you will need to install preview 6 of both the server and the plugin. The preview 3 plugin might be relying on things that are no longer present in preview 6.

antonov124 commented 3 years ago

The Database Editor link is missing in the preview 6 , thats what i mean, in previous versions its still there...

vradarserver commented 3 years ago

The editor link is there for me in preview 6, both under Windows and Linux / Mono.

Windows preview 6:

and Mono preview 6 running on Ubuntu 18.04:

You are running custom content. Disable the custom content plugin and then refresh the page, if the link now appears then the custom content is the issue. Otherwise make sure that you have enabled the database editor plugin and installed the preview 6 version.

antonov124 commented 3 years ago

the custom content has the issue, with prev 3 its working, so do you have anything changed since prev3 to 6 in this section?

vradarserver commented 3 years ago

I have no control over your custom content, I have no way of knowing which change has broken it.

My guess - and it is only a guess - is that a custom script is expecting to see the airport data link and it is breaking when it's not there? It could be that that script runs before the database editor's script gets a chance to add its link to the page. When the custom script breaks it stops all scripts that run after it from initialising correctly.

I would start with having a look at the browser's console window for errors. Or alternatively disable each custom script one-by-one until the page loads correctly and then fix the script that you had to disable.