Getting the following error on node view:
Juicebox Error: Config XML file not found.
Used Chrome console and was able to see that the XML was being returned - however, with an empty first line:
<?xml version="1.0" encoding="UTF-8"?>
<juicebox gallerywidth="100%" galleryheight="400px" backgroundcolor="#222222" textcolor="rgba(255,255,255,1)" thumbframecolor="rgba(255,255,255,.5)" showopenbutton="TRUE" showexpandbutton="TRUE" showthumbsbutton="TRUE" usethumbdots="FALSE" usefullscreenexpand="FALSE">
<image imageURL="http://x/sites/default/files/products/071105US.jpg" thumbURL="http://x/sites/default/files/products/071105US.jpg" linkURL="http://x/sites/default/files/products/071105US.jpg" linkTarget="_blank">
<title><![CDATA[]]></title>
<caption><![CDATA[]]></caption>
</image>
</juicebox>
I replaced the domain with "x" since it's internal for testing. Do you think that maybe the issue? If so, any suggestions on what could be causing this?
Thanks in advance!
Comments
Comment #1
pdesai commentedComment #2
pdesai commentedComment #3
pdesai commentedThis is resolved. After spending little over an hour - (ugh) - it ended up being in our settings.php which we had error_reporting code at the top with a closed ?> and a blank line after it
Comment #4
pdesai commentedComment #5
rjacobs commentedYeah, if anything is printed to the screen before the normal page headers, such as whitespace, this can cause problems. It often goes undetected until something using XML is involved (such as this module), as the XML parsers in most browsers will not gracefully ignore that whitespace. This comes up form time-to-time and unfortunately there is not much that can be done to avoid or detect it (that I know of). More info here: https://drupal.org/comment/7977753#comment-7977753
Comment #7
Road Kill commentedI am sorry to open this issue again but I am a little confused. I have juicebox working just fine when using the formatter in the content type full display but if I use it in a views attachment as a formatter on an image field I get Juicebox Error: Config XML file not found.
If this is a white space problem why is it only affecting the views field formatter and not the content type full display field formatter?
Comment #8
rjacobs commented@Road Kill, if you are seeing inconsistent errors such that the field formatter behaves differently than the views plugin then it's most likely that something else is going on. Though the whitespace issue is a common explanation for the "Config XML not found" error, it's certainly not the only one. If the problem persists I suggest opening-up a separate issue thread and try to post as many details as you can about your case there. One of the best things that you can do as part of that will be to share a link to a public page that demonstrates the problem (if possible).
Comment #9
rjacobs commentedI'll go ahead and toggle the status back on this issue since it sounds like the points from #7 are likely not directly related. @Road Kill, please feel free to open-up a separate thread regarding your issue if you are still having problems.