I would recommend running the either switching to the master branch to obtain Emoncms V10.0.0-beta or switching to the stable branch of App to run App V1.2.1.
I would recommend switching to Emoncms master to run V10, it’s currently proving to be stable and will hopefully be released to stable branch in the next week or so.
I think this partial release of sidebar is going to cause all sorts of problems. I’d suggest we really do not want folk move to master branch unless they really understand the longer term implications.
However if you installed any other modules, you need to be on the master branch for them all.
The issue is that
Not all modules (i.e. folders within the emoncms/Modules folder structure) are installed with the ‘core’ emoncms.
Some additional Modules, that reside in separate repositories, are actually required to make everything work (for instance graph).
Not all modules/repos have a ‘stable’ (or release) branch so when changes are merged into those master branches, that conflict with the emoncms stable branch, you get these issues.
It seems you are on a self install so moving to master for all repos should be OK.
BTW, your install is not quite right as it seems you had the App module installed twice (in 2 different folders under the Modules folder).
It does not make sense to me to publish modules which depend on a emoncms-version that is not available yet and thus ‘breaking’ it. I ran into the same issue and had to undo my 'git pull’s of the modules. Working now again.
Apologies for the confusion. If running the stable branch of emoncms core we recommend running the stable branch for each module. We have ensured that users running stable branches of all modules (e.g emonSD, emonPi , emonBase default branch) will not be effected by this change.
I see… I used (except for Emoncms) the master-branch…
Unfortunately switching to stable-branch did not work for all Modules I have installed. The device-module has no stable-branch.
