Visual error in "create task" gui

[Tom Elliott]

That is supposed to be like that.

[Tom Elliott]

WOL doesn’t boot to init’s at all, so the debug options are not available to it.

When you schedule debug, you can’t shutdown the system and scheduling delayed or CRON style wouldn’t be any good either as you cannot maintain control over the taskings when they are in debug mode.

[bmaster001]

Don’t think so. When you check “wake on lan” by clicking on the checkbox, every other item stays the same. But when you click on the label “wake on lan”, the checkbox keeps the same state (checked/unchecked) but the other items dissapear.

[Quazz]

@bmaster001 This happens because clicking on the WOL label activates Debug task which causes the other options to disappear as Tom explained.

[Tom Elliott]

Wake on Lan Tasking is a separate thing from the “Wake on lan” checkbox.

The Wake on lan checkbox enables you to disable/enable WOL for the host about to take on the tasking. The wake on lan tasking only sends a WOL packet to the host. They are NOT the same thing.

[bmaster001]

I’ve never used much of the more advanced fog-settings, so for me as a “new” user, this is a confusing UI.
As I understand it, the WOL-checkbox means that you want to “wake” the host by WOL, instead of having to power it up manually. Clicking on the label next to the checkbox should simply toggle the checkbox-value. That’s how it works everywhere in Windows at least (and that happens with the “schedule schutdown” and “schedule debug task” as well)

Not sure what you mean by your explanation Tom, sorry…

[Tom Elliott]

@bmaster001 I don’t know what you mean. The check box is working fine when I select it or not select it. It shows the check or no check depending on the state it was previously.

[bmaster001]

See screenshots. First one is “before”, then I click on “Wake on lan” (the label, not the checkbox!), and I get the second situation (wake on lan still checked).

[george1421]

@bmaster001 The Advanced Settings dialog box is dynamic and hides incompatible settings (keeping the IT admin from making dumb mistakes).

With Debug task enabled delayed deployment, cron deployment, and shutdown are no longer appropriate, since you will be in the debug console.

Unless I missed something in your post. The WOL should have no impact on the debug task.

[Quazz]

@george1421 I think his complaint is that when you click on the Wake on LAN label it enables Debug task (which it probably shouldn’t?)

[george1421]

@Quazz said in Visual error in "create task" gui:

@george1421 I think his complaint is that when you click on the Wake on LAN label it enables Debug task (which it probably shouldn’t?)

Gotcha, let me update my dev environment is on 8157 right now. I can confirm that 8157 does not change anything when WOL is turned on or off.

[bmaster001]

This post is deleted!

[Tom Elliott]

@bmaster001 Fixed in latest.

[george1421]

@Tom-Elliott said in Visual error in "create task" gui:

@bmaster001 Fixed in latest.

Hey not fair, let me at least prove its was broken to begin with!!

[Tom Elliott]

@george1421 Once I know what it is, I fix it fast. Lol.

[bmaster001]

Seems like the hardest part here was to explain what was wrong…
And fighting over who gets to fix something… that’s called motivation