in reply to YAML problem

Well, the filename doesn't change, but its a relative filename ... so try an absolute filename

Replies are listed 'Best First'.
Re^2: YAML problem
by Anonymous Monk on May 26, 2015 at 11:26 UTC
    No, this is not the case. Ive use unique file ne, file name with full path, or just put yaml file to the screen - results are alwsys wrong.

      I find no documentation in YAML::Syck how the library behaves in the case that DumpFile cannot write the file, for example due to missing permissions etc. . It may likely be that the new output is not written because the permissions between web server user are not sufficient.

        Once again. Even screen output loose data.
        Sorry for previous anonymous replies. The problem is in the YAML, because the content of variables can be printed on the screen, or dumped by other tools like Dump or write directly to the file without any problems. But the content of variables passed from one script to another not working with YAML, which is a very strange, like these variables start to have some kind of bad flag or mark.