change color of icon "upload"

[jc35]

Hello,
thank you for your very good job.
It’s not really a new functionality.
Can you change the color of icon “upload” ? (for example red for warning).
Because some users click on the “upload” icon by mistake and the master is destroyed.

[Jaymes Driver]

I find this funny

We changed the name of the icon from “upload” to “capture” to help alleviate the issues we see with this.
I don’t see any reason why changing the color would hurt anything!

@Developers Anyone disagree?

[Tom Elliott]

I don’t think changing the color should matter at all. If people are clicking the button, I don’t think the reasoning for the clicking is color based or not.

That said, what is the “warning” for? If you’re capturing an image, you’re capturing an image. if you don’t want user’s to accidentally overwrite an image, why not just set the image to “protected” and/or change the files so they’re immutable?

[Matthieu Jacquart]

I agree with that, better differentiation will be fine ! For example on hosts management page, icons are : first => deploy, seconde => capture. But on Tasks management - List all hosts it’s the opposite : first => capture, seconde => deploy

[Tom Elliott]

@Matthieu-Jacquart I’ve switched the “ordering” of the icons for tasks listhost element to display the task icons similar to how it is displayed on host listall/search now.

[Matthieu Jacquart]

@Tom-Elliott ok thanks, you made this on dev branch ? git pull and update in working branch but no change

[Tom Elliott]

@Matthieu-Jacquart Change is in working-1.3.5.

[x23piracy]

Hi all,

what about automatically setting the protection after creating an image, when now someone trys to upload the webif could ask for: “image is write protected do you really want to overwrite it” then presenting the delete protection dialog where i need to enter fog credentials to finally remove the protection and start uploading the image.

This would make a lot of sense to me.

• Out of the box any image is protected
• False overwriting never possible until user is very stupid
• No need to set the protection
• No need to remove it when wanting to overwrite because system will ask if you want to remove protection while trying to overwrite an existing image.

Regards X23

[Tom Elliott]

@x23piracy No. There’s too much in the system to try to handle somthing like this.

[x23piracy]

@Tom-Elliott it was just an idea, i don’t have any clue what’s hanging at the rat’s tail

Regards X23

[jc35]

Sorry for my very bad english.

@Tom-Elliott said in change color of icon "upload":

I don’t think changing the color should matter at all. If people are clicking the button, I don’t think the reasoning for the clicking is color based or not.

That said, what is the “warning” for? If you’re capturing an image, you’re capturing an image. if you don’t want user’s

Yes, It attracts user attention. I change color in red with other version, but I must do it after each update. actually we work on 1.2. It is true that with version 1.3, it is obsolete with the protected image.

to accidentally overwrite an image, why not just set the image to “protected” and/or change the files so they’re immutable?

Sorry I don’ty see this in 1.3.
We change version monday 20 febrary.

[Wayne Workman]

@Tom-Elliott said in change color of icon "upload":

if you don’t want user’s to accidentally overwrite an image, why not just set the image to “protected” and/or change the files so they’re immutable?

This is the proper answer. 1.3.0+ allows you to protect the image from accidental deletion and accidental rewrite.

In 1.3.0+ the terminology is much more clear. In 1.2.0 and below, it was “upload” & “download”. Myself, all of my co-workers, my cousin, and many people on the forums all found this very confusing. So for 1.3.0 and higher, it was changed to “Capture” & “Deploy” and now we see a whole lot less confusion about it.

@jc35 I would recommend you upgrade your FOG Server in the near future to take advantage of these features plus the many others that 1.3.0+ has to offer. You might want to look at this article if you don’t want to disturb the old server and want to start fresh: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG