|
alainiala Posts: 5
02/03/2017
|
Hello,
We use Symenu in portable mode on the network for technicians to have a quick access to our tools. SyMenu is perfect for that! We are 3 administrators who can modify the menu items and we know that we must reload Symenu before making any changes. But I'm the only one who can make configuration changes. The problem is that if I make a configuration change and backup, it will be replaced by the next user who will exit SyMenu because SyMenu automatically saves the configuration when it is closed. My question is this: How do you prevent SyMenu from saving its config when you leave it? Thank you in advance!
edited by alainiala on 02/03/2017
|
|
|
link
|
|
Gianluca Administrator Posts: 1274
03/03/2017
|
Even if you don't touch the program options, SyMenu changes the Config\SyMenuConfig.zip file the same because it needs to store the last position and size for its various components. This is the reason for the saving during closing time.
SyMenu is not able to manage this mixed requirements. You need to have a part of the program configuration enabled for writing (the items part) and the other in read only mode for certain users and fully changeable for one other.
My suggestion: try using the Windows security. As I told you the file to protect is Config\SyMenuConfig.zip. Disable the write permission for the other two admins. The program should not complain and, just in case, I can fix the behavior.
Let me know if this solution is suitable for you.
|
|
|
-1
link
|
|
alainiala Posts: 5
03/03/2017
|
Thanks for your quick reply,  it was the option I had considered but the network manager did not like the idea. He preferred that the program itself handle this problem. I will ask him to restrict the rights of the config file as you suggest. I will keep you informed if it works or not.
Thanks again for your quick reply. By the way, you do a great job with SyMenu!
Alain, Canada
|
|
|
link
|
|
alainiala Posts: 5
03/03/2017
|
Sorry, I clicked "thumbs down" by mistake and I'm not able to undo my click!
|
|
|
link
|
|
Gianluca Administrator Posts: 1274
03/03/2017
|
Since I'm not the author of the software I'm using for the forum, I've no idea what the hell these thumb up and down serve... So thumb down as much as you want 
|
|
|
link
|
|
alainiala Posts: 5
03/03/2017
|
Gianluca wrote:
My suggestion: try using the Windows security. As I told you the file to protect is Config\SyMenuConfig.zip. Disable the write permission for the other two admins. The program should not complain and, just in case, I can fix the behavior.
Let me know if this solution is suitable for you.
Hello,
unfortunately the solution is not suitable because if I put the SyMenuConfig.zip file read-only for the other administrators of the menu items, they can no longer enter the management of the menu items that is actually part of the configuration. The message "This function is not available because the Symenu directory is read-only".
I come back with the same problem.
Thank you in advance!
Merci d'avance!
|
|
|
link
|
|
Gianluca Administrator Posts: 1274
03/03/2017
|
You are right. I forgot how it works... SyMenu is almost too big for me
Usually when a user suggests a special feature I put it in the forum to test the community reaction. We already are in the forum so let's wait for the community feedback.
In the meanwhile my opinion is that this feature is useless for the great majority of users.
SyMenu doesn't implement any user manager because it's a file system based program, so the file system security is enough for almost every needs.
Your need instead is very peculiar.
You have three admins but two of them have a minor power.... it's strange.
Can't you synchronize among you?
IMHO the program options modification is a really rare activity and once you choose the theme, the events, the general structure and a few other things you've done.
The items modification instead happens very frequently and you could have collision problems here too. So the synchronization is essential to avoid the risk to loose configured items. And this scenario is much more serious than the one you are trying to avoid.
|
|
|
link
|