Open ChrisVeigl opened 5 years ago
Great suggestions! Thanks a lot.
Alternatively, we could save the link, to the documentation, in the component collection in a dedicated entry. I think this way, the procedure is more robust (less error-prone) and not that susceptible to changes.
The fix works for most of the incosistent plugin names mentioned above, but there are two who still don't work:
Maybe there are still others. So I think in this case the simplest solution would really be to rename the help filename in the docs folder
So I think in this case the simplest solution would really be to rename the help filename in the docs folder
Yeah, why not 👍 Maybe this is even easier: https://stackoverflow.com/a/14814577/9219743
So I think in this case the simplest solution would really be to rename the help filename in the docs folder
Yeah, why not +1 Maybe this is even easier: https://stackoverflow.com/a/14814577/9219743
This would be the easiest solution indeed, but unfortunately, we don't have access to the webserver. In order for that we would have to move the hosting to another server, e.g. ionos.
I just found that the pressing "F1" in the modelSwitcher plugin results in a 404 error, although the page https://www.asterics.eu/plugins/actuators/ModelSwitcher.html exists.
The problem is that the ACS tries to access the page https://www.asterics.eu/plugins/actuators/modelSwitcher.html (small "m") and the filesystem is case-sensitive.
The same problem exists for plugins that do not follow the naming convention and start with a non-captial letter: serialSender, enocean, openHAB, openBCI, p2_parser.
I suggest to rename the help files for those plugins (or to refactor the plugin name in bundle descriptors and source files - but it should be verified that this does not cause problems with existing models)