Author Topic: Group Naming conflict  (Read 1545 times)

0 Members and 1 Guest are viewing this topic.

Mace

  • $upporter
  • Contributor
  • *****
  • Posts: 77
  • Karma: 1
    • View Profile
Group Naming conflict
« on: March 02, 2015, 09:57:16 PM »
Hello,

Would like to offer a little info for user friendliness.
Recently i was trying to use a Confirm.'Group Name' as an event in my group to trigger a command. I kept getting the error "invalid xml", when trying to drag and drop, after some frustration at sourcing why this was happening i eventually worked out it was because i had the special character ' & ' in the title of my group. Yes i know, pretty basic issue for those in the know, but in my defense it was 1am. 

However this got me thinking, if i didn't know anything about xml formatting i would seriously have the shits on.

On to the point of this discussion. Is it possible to add a better error explanation, like  'no special characters allow' or something like that?

jitterjames

  • Administrator
  • Hero Member
  • *****
  • Posts: 7713
  • Karma: 116
    • View Profile
    • VoxCommando
Re: Group Naming conflict
« Reply #1 on: March 03, 2015, 08:29:24 AM »
Were trying to recreate this problem but having some difficulty.

The problem with xml is there are about a thousand reasons why it could be invalid.  In this case it looks like I should be able to fix the code which drags events from the history window.

Thanks for the heads up. Seems like a fixable bug.

Mace

  • $upporter
  • Contributor
  • *****
  • Posts: 77
  • Karma: 1
    • View Profile
Re: Group Naming conflict
« Reply #2 on: March 03, 2015, 08:34:33 AM »
I think the group title i had was "Generate Payload & Reset"

The command required a confirmation
It was when i try and drag the history event 'Confirm:Generate Payload & Reset' to the command is when i have the error.

I changed nothing but removed the '&' symbol and everything worked sweetly.

jitterjames

  • Administrator
  • Hero Member
  • *****
  • Posts: 7713
  • Karma: 116
    • View Profile
    • VoxCommando
Re: Group Naming conflict
« Reply #3 on: March 03, 2015, 09:34:10 AM »
The part that confuses me is that you keep saying group when I think you mean command.

jitterjames

  • Administrator
  • Hero Member
  • *****
  • Posts: 7713
  • Karma: 116
    • View Profile
    • VoxCommando
Re: Group Naming conflict
« Reply #4 on: March 03, 2015, 09:37:21 AM »
Anyway I got it sorted out.  Thanks.

By the way "invalid XML" is the whole story in terms of the error exception generated by the .Net runtime or whatever it's called.  It does not say why the xml is invalid, I am actually passing the error exception text directly to the popup window.  the only other information provided is what line of code the error is generated on which would be of no help to the end user.

Mace

  • $upporter
  • Contributor
  • *****
  • Posts: 77
  • Karma: 1
    • View Profile
Re: Group Naming conflict
« Reply #5 on: March 03, 2015, 09:45:53 AM »
Ah yep that would be true, cause my group and command name was the same, I was thinking group when should of said command.

Yeh invalid XML really wasn't of much help to me. Lol

Cheers