Ah Ok I had missed that. There is a line in the update script to force a new link, but I suspect the logic is not quite right to make it run.
Or that this new script does not have the ‘f’ to force it (can’t immediately tell which script is being run on update - it’s a bit of a maze right now).
I also couldn’t work out where the config file was generated from. Rather than it being the module install script (which would be logical) it is in the install script for all modules (above).
It has always been a maze, now it’s like a 3D maze as not only do the scripts go here there and everywhere (as before) but there is also the live, redundant and not yet rolled out timeline aspect, plus the stable vs master versions of the emoncms repo’s to boot.
[edit]
On a new install, there is no need to force as there is no symlink to replace. I’m pretty sure the issue is the use of the -f on a folder, it follows the symlink and put’s the new symlink in the folder rather than overwriting the existing symlink.
[edit2] having said that (-n req’d) if the backup/backup folder no longer exists, then the symlink should get replaced with just -fas it cannot result in a nested symlink (can’t put a symlink in a folder that doesn’t exist!). IMO the -nf options should still be used together when re pointing a folder symlink, even if it should “work out” cause the link is dead because if things are done in the wrong order eg the backup module doesn’t pull first time due to local changes etc, the result not as expected.
Just wanted to provide some information, I hope not to confuse the issue. I have the Backup menu item but not the Post Process menu item. Running v9.9.9
the $ should be #. I fixed it and it worked great!
The config.cfg file was no-where to be found, and I don’t know WHERE
it went, but I used nano to create a new config.cfg file, copied and pasted the code in your response, fixed the $ #, and tested it out… worked great and I now have a sidebar import/export menu when I select backup under SETUP.
Thanks again!