- Support Forum
- Main Forum
- Joomla Extensions Support
- XML import failed | log file not written
XML import failed | log file not written
oh yes - I did exactly these settings - including field mapping. I did show all steps I did in several screenshots, but when I tried to post them (one screenshot per step) here, I got a message according to many links. So I decided to make one picture out of that. Unfortunally it is not shown - I don't know why. At first I tried with *.png format, now I did upload the picture again on my webspace in *.jpg format. Let's see:
[img size=313.809 Bytes]c-brand.design/files/2018-08-17_screenshots.jpg[/img]
If the image is not displayed - try the link directly: you will see the whole experience I made!
In addition I attach the image to this post.
Please check the following thread and see if you are doing the field mapping correctly on import screen.
because my problem still remains, I did make a minimalistic test with a *.xml file, containing only two items - just to figure out, if it works then. Maybe someone can give me a hint, what I did wrong.
The content of the *.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?><items><item>
[img size=322.896 Bytes]c-brand.design/files/2018-08-17_screenshots.png[/img]
Mmmmh: this is not what had been intended.
Is there anybody out there, having an idea?
I tried to import a *xml file with a profile set up to sychronize data, but the following error message occured:
PARSE_ERROR - expected '>' Import Failed
This happened with the vData version 2.9.23, so I did update to the latest version, but it too did not import the data.
Well, I did parse the *.xml with another tool www.w3schools.com/xml/xml_validator.asp and there was no error - the source file seems to be okay.
When I go to the "Log Details" page a filename of a log file is mentioned, but no link on it - what seems to be the consequence of the fact, that the log file does not exist. I did search it where in former versions of vData the log files had been saved (Joomla! root/log), but there is none. In version 2.9.23 the files had been created successfully.
Does anyone has an idea?