136Views23Replies

Author Options:

Parser error Answered

Almost finishing a long instructable I got repeteadly the following error message:

There's been a problem updating your
                        Instructable
                        parsererror
       SyntaxError: JSON.parse: bad
             character in string literal


I am using Windows XP
Navigator: Firefox 12.0

I can not edit the instructable to finish and publish it.

Discussions

0
None
mikeasaurus

6 years ago

Thanks for reporting this, I've filed a bug report.

0
None
kelseymhmikeasaurus

Reply 6 years ago

See my note above. I think the server side code needs to do filtering of I'ble and step titles to make sure they are URL-compliant (i.e., only the US ASCII character set).

0
None
rimar2000kelseymh

Reply 6 years ago

Are both you the same person?

Thanks for your concern.

0
None
Jayefuurimar2000

Reply 6 years ago

No, they're just both called Mike :D

0
None
rimar2000mikeasaurus

Reply 6 years ago

Michael, I understand that the problem is not prioritary, but (almost?) all programation languajes have a function to translate a list of characters into another list:

In example

url_address = translate(title_string,"áéíóúüñÁÉÍÓÚÜÑ¡¿","aeiouunAEIOUUN--")

Add all US ASCII characters not allowed for urls, and it is all. That so simple code line would solve the problem forever.

Thanks for your concern!

0
None
rimar2000mikeasaurus

Reply 6 years ago

Thanks for the response, Mike. The problem was fixed some minutes after my post.

0
None
ClareBS

6 years ago

I'm having the same problem. I think it's because I used proper quotation marks instead of foot and inch marks. Is there someone who can delete the instructable so I can start over? It's the one on the Micro mini garden shed. Very simple, only three steps and three pictures.

0
None
rimar2000ClareBS

Reply 6 years ago

Maybe you should put a new bug (you -> Create -> Bug report). Otherwise your comment can last unnoticed.

0
None
ClareBSrimar2000

Reply 6 years ago

Thanks, since it was exactly the same report, but on a Mac, I thought I'd just leave a message here first. I opened it in Safari, was able to delete the steps and start over in Firefox. All is well now.

0
None
pfred2

6 years ago

Why you keep breaking this site?

0
None
rimar2000pfred2

Reply 6 years ago

I insist to use those awful spanish characters!

I am like peronistas, incorrigible (Jorge Luis Borges said "peronistas aren't bad, are incorrigible")

0
None
pfred2rimar2000

Reply 6 years ago

I was thinking you should have made your doors double doors, that way your fire wouldn't fall out when you were feeding it.

0
None
rimar2000pfred2

Reply 6 years ago

???

I don't understand. Maybe this comment refers to salamander stove?

0
None
rimar2000pfred2

Reply 6 years ago

About the door of the salamander, I thought about making it divided horizontally in the middle, but then I decided to try first in one piece. I will leave as is, because the smoke does not escape to the open, that was my main concern.

About comments, when I am replying, specially, sometimes the editor duplicates my previous comment instead of which I am trying to put.

0
None
rimar2000

6 years ago

The error appears only when I attempt edit step 15.

I need to do it in order to finish and publish.

0
None
rimar2000rimar2000

Reply 6 years ago

In step 14 was a spanish character ¡ (opening the exclamation mark).

By the way, would be nice if someone technic staff study the issue of the Spanish character, which appear well in the texts but not in the titles. They are:

á é í ó ú ü ñ Á É Í Ó Ú Ü Ñ ¡ ¿

0
None
kelseymhrimar2000

Reply 6 years ago

Hola, Rimar. The problem is that the step titles are used to generate URLs, and the URL specification only allows for basic US ASCII characters, and not even all of those. Extended ISO Latin-1 characters (let alone mention Unicode), don't have any consistent mapping for URLs.

In principle, I'bles could write special code to convert those characters to something in ASCII (e.g., by mapping the Latin-1 alphabetic characters to their unaccented equivalents), but it would be awkward to maintain over time. And given their clearly limited software resources, probably is not as high on their priority list as other things.

0
None
rimar2000kelseymh

Reply 6 years ago

Michael, I understand that the problem is not prioritary, but (almost?) all programation languajes have a function to translate a list of characters into another list:

In example

url_address = translate(title_string,"áéíóúüñÁÉÍÓÚÜÑ¡¿","aeiouunAEIOUUN--")

Add all US ASCII characters not allowed for urls, and it is all. That so simple code line would solve the problem forever.

Thanks for your concern!

0
None
Reed_Sky_Born

6 years ago

have you tried starting it again?

0
None
rimar2000Reed_Sky_Born

Reply 6 years ago

Thanks for the response, Reed_Sky_Born. The problem was fixed some minutes after my post.

0
None
Mastros

6 years ago

As you are now posting comments, you are of course logged in to Instructables.

Were you logged in when the problem arose? Perhaps, if you try again now, things will be oll-killed (i.e.: ok).

I had a similar message a few days ago, when I was posting a new post to my blog. The problem was that, for security reasons, google unsubscribes me every few days (two weeks?) and asks for my password.
-.

0
None
rimar2000Mastros

Reply 6 years ago

Thanks for the response. The problem was fixed some minutes after my post.