<p>You need to use valid html/twig in your templates. Your “HTML Source Code” is not valid html. Removing the <code>.</code> from the beginning of your attributes i.e.: <code>&lt;span ex:content="genre"&gt;</code> should resolve the error, but it still wont be good html.</p>

<p>Best option, IMHO, is to start with a good solid foundation of valid html and work up from there.</p>

CC BY-SA 4.0
2018-05-22T12:29:17.907Z
2018-05-22T12:29:17.907Z
Seth Warburton
<p>ex) original HTML source code</p>

<pre><code>&lt;link rel="exhibit/data" type="application/jsonp" href="https://spreadsheets.google.com/feeds/list/~~~~/od6/public/basic?alt=json-in-script" ex:converter="googleSpreadsheets" /&gt;
</code></pre>

<p>~~~~~</p>

<pre><code>&lt;td valign="top" padding="0.5em"&gt;
    &lt;span style="text-alight:left;" ex:content=".label"&gt;&lt;/span&gt;&lt;br /&gt;
    &lt;b&gt;Aired: &lt;/b&gt;&lt;span ex:content=".start"&gt;&lt;/span&gt;&lt;br /&gt;
    &lt;b&gt;Genre: &lt;/b&gt;&lt;span ex:content=".genre"&gt;&lt;/span&gt;&lt;br /&gt;
&lt;/td&gt;
</code></pre>

<p>You can see .label, .start, and .genrem but on Craft CMS they are errors.</p>

<p>How do I create code with no errors?</p>

<p><strong>Error message is,</strong></p>

<p>Internal Server Error</p>

<p>Unexpected token "punctuation" of value ".".</p>

<p>*The error message displays like this on my PC's XAMPP
craft/templates/index,html
<a href="https://i.sstatic.net/OfidZ.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/OfidZ.jpg" alt="enter image description here"></a></p>

<p>Thanks in advance!</p>

<p><strong>ref image on google spreadsheet,</strong>
<a href="https://i.sstatic.net/lPkH5.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/lPkH5.jpg" alt="enter image description here"></a></p>

CC BY-SA 4.0
2018-05-21T00:08:31.357Z
Not sure I'm following... where are you getting the error?  Can you enabled devMode and share the full stack trace leading up to the error? Are you trying to get data into a format that Google Spreadsheet can recognize?
Brad Bell
CC BY-SA 4.0
2018-05-22T04:28:53.890Z
I edit and add the error message image. I already have a simile's timeline website like http://relationworld.com/adrama/timeline/drama/top_menu/adrama_title_all-timeline.html    I'd like to use simile's timeline on Craft CMS not using Google Spreadsheet. But I don't find the way of changing from spreadsheet to craft's fields. ex) .label to {{ entry.label }}, but doesn't work  or using spreadsheet then doesn't work
tetsujikenny
<error-message><error>
How to create any code from google spreadsheet like {.label} by Craft CMS
# How to create any code from google spreadsheet like {.label} by Craft CMS

(Asked by: username_0 on 2018-05-20)

ex) original HTML source code


~~~~~

    
    Aired: 
    Genre: 


You can see .label, .start, and .genrem but on Craft CMS they are errors.
How do I create code with no errors?
Error message is,
Internal Server Error
Unexpected token "punctuation" of value ".".
*The error message displays like this on my PC's XAMPP
craft/templates/index,html

Thanks in advance!
ref image on google spreadsheet,

**Tags:** error-message, error
> **Comments:**
> **username_1**: Not sure I'm following... where are you getting the error?  Can you enabled devMode and share the full stack trace leading up to the error? Are you trying to get data into a format that Google Spreadsheet can recognize?  
> **username_0**: I edit and add the error message image. I already have a simile's timeline website like http://relationworld.com/adrama/timeline/drama/top_menu/adrama_title_all-timeline.html    I'd like to use simile's timeline on Craft CMS not using Google Spreadsheet. But I don't find the way of changing from spreadsheet to craft's fields. ex) .label to {{ entry.label }}, but doesn't work  or using spreadsheet then doesn't work  

---

## 1 answers

### Answer by username_2 on 2018-05-22. Score: 1

You need to use valid html/twig in your templates. Your “HTML Source Code” is not valid html. Removing the `.` from the beginning of your attributes i.e.:  should resolve the error, but it still wont be good html.

Best option, IMHO, is to start with a good solid foundation of valid html and work up from there.


---

