@MainrtNr5 Hello again:
Similar to your previous question on re-configuring, it’s an uninstall - re-install Rock-on thing. This helps us to keep the UI simple and works well as the Rock-on then gets re-established from the get-go. baring the existing config with the common shares used during the re-install of course.
Although I think I may not have quite grasped your actual question here.
Could you elaborate on your UI issue here. Also @Flox is more up on the internals of the Rock-ons currently so you may get a more authoritative answer in time.
Sketch out the path taken in the Web-UI and where it seemingly took a turn you didn’t agree with. Adding a share to a Rock-on does stop and start the rock-on but it doesn’t re-set it’s other shares. But it may be that your particular mapping caused that by overriding some config element with the new path established to map the new share.
Apologies for not quite getting your meaning on this one.
Full details on how our existing Rock-ons work internally has been excellently documented by @Flox in our technical wiki entry here:
and
That may help with what’s going on differently to what you are expecting. Unless we have a bug and in which case great: we can narrow that down and sort it to be as intended.
Hope that helps.