# Special characters breaking blueprint content in the panel

**URL:** <https://forum.getkirby.com/t/special-characters-breaking-blueprint-content-in-the-panel/3748>\
**Category:** Questions\
**Tags:** v2\
**Created:** [April 4, 2016, 11:00am UTC](https://forum.getkirby.com/t/special-characters-breaking-blueprint-content-in-the-panel/3748 "2016-04-04T11:00:37Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![jenstornell](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/jenstornell/32/546_2.png) [@jenstornell](https://forum.getkirby.com/u/jenstornell)\
**Post date:** [April 4, 2016, 11:00am UTC](https://forum.getkirby.com/t/special-characters-breaking-blueprint-content-in-the-panel/3748/1 "2016-04-04T11:00:37Z")

</div>

In a field I’m building I save data like this:

```yaml
-
  seo-title: Some title
  seo-description: Some description

```

It works fine in most cases. Sometimes I got an error with \> (larger than) and adding : (colon) does not go so well.

Because this content is generated by javascript I can escape some characters before they are saved.

My question is… Are there any other characters that I should escape to prevent errors? If you have another approach, let’s hear that as well.

---

<div class="post-metadata">

**Author:** ![jenstornell](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/jenstornell/32/546_2.png) [@jenstornell](https://forum.getkirby.com/u/jenstornell)\
**Post date:** [April 4, 2016, 11:15am UTC](https://forum.getkirby.com/t/special-characters-breaking-blueprint-content-in-the-panel/3748/2 "2016-04-04T11:15:30Z")

</div>

Just tested some cases with [http://yaml-online-parser.appspot.com/](http://yaml-online-parser.appspot.com/) and this seems to work:

```auto
-
  seo-title: >-
    Seo title with : colon
  seo-description: >-
    Seo description with "some" cite 'and' > larger characters

```

Pitfalls or alternatives are still helpful.

---

<div class="post-metadata">

**Author:** ![jenstornell](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/jenstornell/32/546_2.png) [@jenstornell](https://forum.getkirby.com/u/jenstornell)\
**Post date:** [April 4, 2016, 12:38pm UTC](https://forum.getkirby.com/t/special-characters-breaking-blueprint-content-in-the-panel/3748/3 "2016-04-04T12:38:10Z")

</div>

With [http://yaml-online-parser.appspot.com/](http://yaml-online-parser.appspot.com/) it validates perfectly fine.

In a blueprint it trows a notice:

> Notice: Undefined offset: 5 in C:\wamp\www\seo\kirby\toolkit\vendors\yaml\yaml.php on line 508

```yaml
Seo: 

-
  seo-title: >-
    åäö llasdas
  seo-description: >-
    rwerwe wer ewrerte : fsd >

```

Is it a Kirby bug? It’s the last “larger than” character that causes it. It seems like the problem only appear when the “larger than” character is last in the row.

---

<div class="post-metadata">

**Author:** ![lukasbestle](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/lukasbestle/32/11437_2.png) [@lukasbestle](https://forum.getkirby.com/u/lukasbestle)\
**Post date:** [April 4, 2016, 1:44pm UTC](https://forum.getkirby.com/t/special-characters-breaking-blueprint-content-in-the-panel/3748/4 "2016-04-04T13:44:07Z")

</div>

Well, even easier: Always wrap the result in quotes and escape any quotes you have in the values:

```auto
-
  seo-title: "Some title with \"Quotes\""
  seo-description: "Some description"

```

You won’t need to escape any other characters.

---

<div class="post-metadata">

**Author:** ![jenstornell](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/jenstornell/32/546_2.png) [@jenstornell](https://forum.getkirby.com/u/jenstornell)\
**Post date:** [April 4, 2016, 2:18pm UTC](https://forum.getkirby.com/t/special-characters-breaking-blueprint-content-in-the-panel/3748/5 "2016-04-04T14:18:04Z")

</div>

I’ll probably go for that one. Shorter and looks better.

---

<div class="post-metadata">

**Author:** ![lukasbestle](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/lukasbestle/32/11437_2.png) [@lukasbestle](https://forum.getkirby.com/u/lukasbestle)\
**Post date:** [April 4, 2016, 2:38pm UTC](https://forum.getkirby.com/t/special-characters-breaking-blueprint-content-in-the-panel/3748/6 "2016-04-04T14:38:15Z")

</div>

…and is more robust. 😉

---

<div class="post-metadata">

**Author:** ![jenstornell](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/jenstornell/32/546_2.png) [@jenstornell](https://forum.getkirby.com/u/jenstornell)\
**Post date:** [April 4, 2016, 2:40pm UTC](https://forum.getkirby.com/t/special-characters-breaking-blueprint-content-in-the-panel/3748/7 "2016-04-04T14:40:36Z")

</div>

Yes. That’s the most important thing. Forgot to mension it. 🙂

---

<div class="post-metadata">

**Author:** ![noplans](https://avatars.discourse-cdn.com/v4/letter/n/d07c76/32.png) [@noplans](https://forum.getkirby.com/u/noplans)\
**Post date:** [July 29, 2016, 6:12pm UTC](https://forum.getkirby.com/t/special-characters-breaking-blueprint-content-in-the-panel/3748/8 "2016-07-29T18:12:53Z")

</div>

Hi,  
using this topic since I have a similar issue. Suddenly on every panel page appears an error notice:  
`Notice: Undefined offset: 63 in /kirby/toolkit/vendors/yaml/yaml.php on line 508`

It could be a special character issue because it didn’t appear until now and I didn’t change anything in the vendors or kirby files, but how can I know what produces the error?

Thanks,

---

<div class="post-metadata">

**Author:** ![Thiousi](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/thiousi/32/13656_2.png) [@Thiousi](https://forum.getkirby.com/u/Thiousi)\
**Post date:** [July 29, 2016, 6:32pm UTC](https://forum.getkirby.com/t/special-characters-breaking-blueprint-content-in-the-panel/3748/9 "2016-07-29T18:32:44Z")

</div>

Are you using the same blueprint on every page?  
Could you share that blueprint ?

I don’t know what else could cause this but some issues with spacing in your yaml files. Maybe somebody has got a better idea ?

---

<div class="post-metadata">

**Author:** ![noplans](https://avatars.discourse-cdn.com/v4/letter/n/d07c76/32.png) [@noplans](https://forum.getkirby.com/u/noplans)\
**Post date:** [July 29, 2016, 7:02pm UTC](https://forum.getkirby.com/t/special-characters-breaking-blueprint-content-in-the-panel/3748/10 "2016-07-29T19:02:53Z")

</div>

Ok, I didn’t know it was related to the blueprint. I re-wrote it and the error disappeared, must have been a spacing issue indeed. Thanks!

---

<div class="post-metadata">

**Author:** ![Thiousi](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/thiousi/32/13656_2.png) [@Thiousi](https://forum.getkirby.com/u/Thiousi)\
**Post date:** [July 29, 2016, 7:05pm UTC](https://forum.getkirby.com/t/special-characters-breaking-blueprint-content-in-the-panel/3748/11 "2016-07-29T19:05:22Z")

</div>

Yeah YAML can be pesky when it come to spacing.

Best tip: don’t use tabs, use actual spaces.  
If your text editor allows it, show spaces when editing the file so you can see errors as you go 😉

---

<div class="post-metadata">

**Author:** ![distantnative](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/distantnative/32/11319_2.png) [@distantnative](https://forum.getkirby.com/u/distantnative)\
**Post date:** [February 6, 2025, 4:57pm UTC](https://forum.getkirby.com/t/special-characters-breaking-blueprint-content-in-the-panel/3748/12 "2025-02-06T16:57:25Z")

</div>


