[solved] XML>EDIT NODE component makes VC crashed - VisualCron - Forum

Community forum

RogerBoes
2013-03-21T16:29:39Z
Dear,

I would like to mention the following to you:

The input box of FILE NAME within the EDIT NODE component is to mention the xml file, which is grey as color on default. And variable usage to enter is impossible in this box as well. When I go to a location to point to the correct xml file via the browser on the right side next to the box, the program CRASHES!!
I tried it multiple times already, but every time with the same result.

The goal I would like is the following:
I would like to change the #package# string within the XML file attached when using the EDIT NODE from the XML Task menu.
Although the file is originally a XSLT- file, I am not sure if this component is the correct one.
And after this I presume there should be a WRITE XML component. When using a WRITE FILE component I will miss the XPATH part of the new xml file
I have created a work-around already for this problem, but just to mention this issue should be fixed I presume
Could you let me know if the failure is fixed and how I should use it?

Kind regards
Roger
File Attachment(s):
publishFM.zip (1kb) downloaded 37 time(s).
Support
2013-03-22T09:05:15Z
We could not reproduce the crash - maybe you are running an older version? We built a new version where this field is enabled but you probably have to enter xpath query manually.

http://neteject.com/down...Cron/VisualCron6.2.1.exe 
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
RogerBoes
2013-03-22T10:38:26Z
Hi,

I am currently using version 6.2.0, as I just mention almost the latest.
Anyway, I receive the gray field when I use the Client location as well on the server location. (see pic: VC_EditNode.png)

The only difference when using the client session on the server, doesn't crash indeed. But still the field of FileName is grey.(VCServer_EditNode_with_Filename.png)

Only on the client side (different machine) I got the crash after selecting the file.
Or even when I want to open the created EditNode on the server side and reopen it on the Client, it appears with the Error Handler window to register this. Which I have just send to you guys.

Roger
RogerBoes attached the following image(s):
Support
2013-03-22T14:17:26Z
If you download this now both problems should be solved:

http://neteject.com/down...Cron/VisualCron6.2.1.exe 
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
RogerBoes
2013-03-28T10:18:22Z
After installing the new version, I could detect indeed a difference within the field FileName as well the browser was working perfectly now. 😁

Great work and thanks for the quick respons.

The only question for me left is, could you explain a little how the component works?😕
And as I am using the XLST model instead, can I use the same EDIT XML component or should I just read each line as a normal file?

Thanks so far for Support!

Originally Posted by: Support 

If you download this now both problems should be solved:

http://neteject.com/down...Cron/VisualCron6.2.1.exe 



Support
2013-03-28T10:22:48Z
I think this should work just fine with XLST files too. I would first try with hardcoding the path to the file and then use the XPATH browser to find out which query to use to find the node you want to replace. Then when it is working you replace with Variable or similar and keep the query.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top