I ran into some troubles with the documentation / installation and wanted to let you know about it. The one I am referring to is hosted at: https://helpv4.mangoautomation.net/linux-installation and I am running a relatively clean and updated Opensuse 15.2
- The install script fails when trying to install Mango 4.0 (or any other version than the default 3.6.6 for that matter):
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of /tmp/tmp.5ikghN5F2T or
/tmp/tmp.5ikghN5F2T.zip, and cannot find /tmp/tmp.5ikghN5F2T.ZIP, period.
There is an error when trying to run "chown -R mango:mango /opt/mango" because there is no mango group yet.
The copy command fails because the unzipped mango archive does not have the overrides folder yet.
cp /opt/mango/classes/env.properties /opt/mango/overrides/properties/
- manually starting Mango complains that the file does not exist...
linux-wh13:/home/fl/SW # sudo -u mango /opt/mango/bin/start-mango.sh > /dev/null &
linux-wh13:/home/fl/SW # sudo: /opt/mango/bin/start-mango.sh: command not found
+ Exit 1 sudo -u mango /opt/mango/bin/start-mango.sh > /dev/null
... and hence does start.
- While installing the service file works, it does -- unsurprisingly -- not start Mango neither.
mango.service - Mango Automation
Loaded: loaded (/etc/systemd/system/mango.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2020-10-09 10:32:53 CEST; 2s ago
Process: 13198 ExecStart=/opt/mango/bin/start-mango.sh (code=exited, status=203/EXEC)
Oct 09 10:32:53 linux-wh13 systemd: Failed to start Mango Automation.
Oct 09 10:32:53 linux-wh13 systemd: mango.service: Unit entered failed state.
Oct 09 10:32:53 linux-wh13 systemd: mango.service: Failed with result 'exit-code'.
FWIW, v3.7.7 runs beautifully on this machine.
Thanks in advance for any comments and help,
@MattFox kindly developed a user module which extends the code of <ma-point-value> with two fields for "value-anchor" and "anchor-target". With this the popup and the link work properly. While there is a chance that this is feature creep, the modification is much better than the current behaviour which IMHO is a bug.
Anyway: All good now. Many thanks for your comments and help!
That is all more than alright; please enjoy your weekend as much as you can in these strange times! The main use is that the user can click on the data point and be led to a different page. Popup with data point details is already bonus functionality. Thinking about it this way, it would even be an option to disable the bubbles for "statistics", "chart", "value table", and "point events". My users would likely not miss them ... no overlays, no problem.
Have a nice weekend!
Having tried your suggestion -- thanks! -- I would like to be more specific: The datapoint popups which create an overlay are the troubling ones. "Data point details" opens the proper link (the data point details), but the other ones show the overlay and additionally open a new tab with the link.
Even after restructuring thrice the problem description sounds odd. Apologies for that. Maybe the code helps...
<a href="http://localhost:8080/ui/watch-list/" target="pointdata"> <ma-point-value style="position: absolute; left: 0px; top: 350px; width: 90px; height: 40px;" enable-popup="right" quick-info="false" point-xid="internal_mango_num_data_points"></ma-point-value> </a>
The solution you suggested still works great, @MattFox! There is just one flaw: We added the "enable popup" option but if one clicks on said popup it opens the link as well as the data point page. The link seems to gets surround the the popop as well. We tried all directions for the popups but only got mixed results. In, the majority of cases the link opens as well and not only the data point page. Would you mind sharing your thoughts on this?