17452 Posts in 4473 Topics by 1971 members
Page: 1 2
|Go to End||Next >|
24 July 2007 at 12:11pm
Just working on our first website for SilverStripe. Is there a way to incorporate the ZoomIn API on our website? We want to include a map to the location for visitors.
24 July 2007 at 6:24pm
You might want to look at using the template tags inside a script tag to load data from the database
<% control Places %>
<% end_control %>
24 July 2007 at 6:30pm
I am warming up to this again... I presume that I create a Maps type and use a template to format this and pass parameters from the page definition in the CMS.
Is this correct?
27 July 2007 at 12:07pm
Has anyone else encountered such an issue?
30 July 2007 at 11:39am
I have contacted the ZoomIn developers regarding the issue where a static page containing the HTML generated by SilverStripe works but the dynamically generated GTML does not. This was the reply:
Hmmm, tricky. I don't know much about how SilverStripe works, but there are
two differences between the page source of the SilverStripe version and the
static version you pasted: the former starts with an XML tag (<?xml
version="1.0" encoding="UTF-8"?>), and the html tag include xml namespace
attributes (<html xmlns="http://www.w3.org/1999/xhtml lang="en" >).
Looking at the way the syntax is highlighted in the two versions by
Firefox's source viewer, I'd surmise that those changes are causing Firefox
to parse the CDATA block (containing our script) in a different way, which
causes an error (not a very meaningful one: "An invalid or illegal string
was specified"). Is there any way that you can configure SilverStripe to not
make those XML settings?
Can anyone assist with this?
Google Summer of Code Hacker
30 July 2007 at 10:01pm
Thanks for the reply. I removed the code from the default template as indicared by ZoomIn and this addressed the issue. Is this an issue that I should address with ProjectX and what would I tell them they should change?
I guess by removing this code, the generated code is no longer fully compliant.
31 July 2007 at 4:16pm
It's still compliant, but it's compliant HTML 4.01 instead of compliant XHTML. Strictly speaking, IE doesn't support XHTML and most browsers interpret XHTML provided to them as HTML 4.01.
Page: 1 2
|Go to Top||Next >|