Page 1 of 1

"External Source" warning dialog when open in batch mode

Posted: Sun Jul 01, 2012 7:33 pm
by kujo_adal
I am launching Helium with the following example command line:
"....\Helium Scraper.exe" "C:\Users\me\Desktop\project.hsp?--auto-close=true&--starting-url=http://google.com&param1=value2&param2=value2"
And then the following dialog pops up (also attached as image):
The project you are opening seems to come from an external source. It could contain malicious code that could compromise your private information.
Would you like to continue opening this project?
I created project.hsp on my own computer, so I don't know why it says it comes from an external source.

Me & most other people looking to run Helium in batch/command-line mode, are looking to have the program function automatically, without having to mouse-click alerts and dialog boxes.
I am now going to investigate using a keyboard-press emulator to press the enter key to get past this dialog, but is a very hacky way to do this. :(

Can this dialog be made to not show up when in batch/command-line mode?

Re: "External Source" warning dialog when open in batch mode

Posted: Sun Jul 01, 2012 7:48 pm
by webmaster
This seems like a bug. Can you try saving your project and then opening it by double clicking it and see if you get the warning?

Re: "External Source" warning dialog when open in batch mode

Posted: Sun Jul 01, 2012 11:52 pm
by kujo_adal
When I open it by double clicking it I do not get the warning.

When launching via command line, I do get the warning.

Re: "External Source" warning dialog when open in batch mode

Posted: Tue Jul 03, 2012 1:59 am
by webmaster
Hi,

I'm pretty sure the problem here is that you're using the path to the .exe file instead of using the .appref-ms one. Some configuration files might not being properly read when the .exe is launched directly.

Re: "External Source" warning dialog when open in batch mode

Posted: Tue Jul 03, 2012 2:46 am
by kujo_adal
I was indeed using the exe by itself.

Using appref-ms fixes the issue. I can use appref-ms for now.



Other users have reported that appref-ms's occasional updates break their automation, so that's why I was considering just using the EXE itself.