Turbine and UI issues with 1.7.5.3

[stimon]

Hi!

We would like to use the plugin with our updated 1.7.5.3 instance. I have cloned and built from scratch and the functionality seems to work fine except for UI integration and turbine errors (which are not further explained in the logs).

When it loads the page displays the following info message $turbineUtils.getBannerMessage($data)
And the warning XNAT System Path Verification Failure: Contact your system administrator. The "what is this message?" also brings a turbine error

Here are a couple of screenshots.
https://www.dropbox.com/s/p3g0ky5ntu6s96a/Screenshot%202019-05-28%20at%2016.14.05.png?dl=0
https://www.dropbox.com/s/w8d44we8sic4ult/Screenshot%202019-05-28%20at%2016.13.59.png?dl=0

Since this repo hasn't been updated for a while, I'm guessing some changes in the latest XNAT build broke the proper UI integration?

Thanks,
Santi

[rherrick]

The XNAT System Path Verification Failure is probably related to the siteConfig.pathErrorWarning issue but separate from the $turbineUtils.getBannerMessage($data) issue. That said, they're both fairly strange.

Are there any messages appearing in the XNAT logs on the back-end? There should be something logged in tasks.log if there really is an error with the system paths. Otherwise something strange is happening to make XNAT think that there's an error with those paths but nothing is actually getting set.

Also, you're correct that this repo hasn't been updated in a while. The developer who was working on it is no longer in our lab and we haven't had any resources to devote to it. We hope to get back to it at some point, but that's just dependent on funding, developer resources, etc.

[stimon]

That is the odd thing, there is nothing in the back-end logs. Only velocity.log complains about 2019-05-29 09:40:30,518 [http-bio-8080-exec-3] ERROR velocity - Left side ($sessionCount) of '>' operation has null value at navigations//DefaultTop.vm[line 152, column 41]

We are testing the plugin in 2 different old (recently upgraded to latest) 1.6.4 virtualbox images, experiencing the same issue. Maybe we missed some config? 🤔

Is there any way I can trace this?
Thanks!