All posts in the topic Problem with viewing xml files (Short link)
Summary
- There are 6 posts — by 4 authors — in this topic.
- Latest post made by Richard Waid at 2007 May 03 20:46 UTC
Hi.
I have installed zope2.9 on debian, created an instance and it seems
functional (can login to zmi OK). I unpacked groupserver .9 to the Products
directory of the instance, restarted zope, created the groupserver site and so
far looks OK.
Apache rewrite seems to be working OK. However, pointing the browser at the
instance produces no errors but a blank screen. I returned to the zmi and
navigated to the instance/content/index-real.xml. If I click on the test tab i
also get a blank screen. I assume I should see the welcome/registration screen.
Any help would be greatly appreciated.
Regards jb
Richard is the better person for answering questions about installing
GroupServer, but I will give it a go!
On Fri, 2006-10-06 at 01:04 +1300, John wrote:
> Apache rewrite seems to be working OK. However, pointing the browser
> at the instance produces no errors but a blank screen. I returned to
> the zmi and navigated to the instance/content/index-real.xml. If I
> click on the test tab i also get a blank screen. I assume I should see
> the welcome/registration screen. Any help would be greatly
> appreciated.
In my experience, the Test tab (in the ZMI) never works. Try using
another Browser window to view GroupServer (remembering to keep your
site-admin and ZMI users separate when you log in!)
On Fri, 2006-10-06 at 01:04 +1300, John wrote:
> Hi.
>
> I have installed zope2.9 on debian, created an instance and it seems
> functional (can login to zmi OK). I unpacked groupserver .9 to the
> Products directory of the instance, restarted zope, created the
> groupserver site and so far looks OK.
>
> Apache rewrite seems to be working OK. However, pointing the browser
> at the instance produces no errors but a blank screen. I returned to
> the zmi and navigated to the instance/content/index-real.xml. If I
> click on the test tab i also get a blank screen. I assume I should
> see the welcome/registration screen. Any help would be greatly appreciated.
Sounds like you're missing the XSLT plugin. If you look in the
log/event.log of the zope instance, and restart Zope, you should see
reports of the XSLT plugins that successfully loaded or didn't. If the
libxslt plugin hasn't loaded, that is your problem.
In that case you'll need to double check the libxslt requirements in the
install documentation.
Hope that helps!
Hi, I had a similar problem (running on Windows), installing the plugin fixed
the "not loaded" error but now I'm getting character encoding errors:
PTRuntimeError: Page Template news_headlines.xml has errors: ['Compilation
failed', "exceptions.UnicodeEncodeError: 'ascii' codec can't encode character
u'\\u2026' in position 1043: ordinal not in range(128)"]
ZMI shows red exclamation marks in front of that file, as well as the following
files, and refuses to even open them (throwing "UnicodeEncodeError"s in
window):
/templates/output/groups_index
/templates/output/latest_topics.xml
Could this be caused by an incompatible locale setting e.g. in Windows?
Zope.conf seems to have some directives for overriding defaults.
Further to my previous message, I managed to fix this by downloading and adding "sitecustomise.py". However, after adding the first post I am now getting the following error on most pages: XML Parsing Error: junk after document element Location: http://masiina.com/example_division/index.xml? Line Number 2, Column 3: <p>An error was encountered while publishing this resource.
Pauli wrote: > Further to my previous message, I managed to fix this by downloading and adding "sitecustomise.py". > > However, after adding the first post I am now getting the following error on most pages: > > XML Parsing Error: junk after document element > Location: http://masiina.com/example_division/index.xml? > Line Number 2, Column 3: <p>An error was encountered while publishing this resource. > --^ > > Looks as if there's still something wrong with the XML parser? > Hi Paul. That's actually a browser message, look at the source of the page for the real error message (the brower thinks it is XML, and so tries interpreting it as such).