Recherche
Fermer
  1. Accueil
  2. Forum
  3. API users
  4. Urgent - REST API error on xml notification
Liste des forums Liste des messages

Urgent - REST API error on xml notification

  • comptoirdesmonnaies
    comptoirdesmonnaies 100% (11610x)
    PRO premium

    80 messages

    France

    Hello,
    When i deseserialize your xml on PHP/Symfony, i've the error xmlParseEntityRef: no name.
    After search, this error is trigger when i have a "&" in a title or description.

    To resolved it, can you modify the content of the markups from

    Allemagne, Jeton, Les frères Grimm - Blanche-Neige, Arts & Culture, FDC

    to


    ?

    And can you resend the Seller_Item_Close_Sold notifications since Sat 13 Mar 2021 at 00:00 ?

    Thank you,

    Julien from Numiscorner
  • comptoirdesmonnaies
    comptoirdesmonnaies 100% (11610x)
    PRO premium

    80 messages

    France

    Hello,
    When i deseserialize your xml on PHP/Symfony, i've the error xmlParseEntityRef: no name.
    After search, this error is trigger when i have a "&" in a title or description.

    To resolved it, can you modify the content of the markups from

    Allemagne, Jeton, Les frères Grimm - Blanche-Neige, Arts & Culture, FDC

    to


    ?

    And can you resend the Seller_Item_Close_Sold notifications since Sat 13 Mar 2021 at 00:00 ?

    Thank you,

    Julien from Numiscorner
    • Posté le 15 mars 2021 à 04:54
    • #1256551
    Allemagne, Jeton, Les frères Grimm - Blanche-Neige, Arts & Culture, FDC

    to

    Allemagne, Jeton, Les frères Grimm - Blanche-Neige, Arts & Culture, FDC

    in the markup title.

    (i mean, i can't write markup in the forum)
  • comptoirdesmonnaies
    comptoirdesmonnaies 100% (11610x)
    PRO premium

    80 messages

    France

    Allemagne, Jeton, Les frères Grimm - Blanche-Neige, Arts & Culture, FDC

    to

    Allemagne, Jeton, Les frères Grimm - Blanche-Neige, Arts & Culture, FDC

    in the markup title.

    (i mean, i can't write markup in the forum)
    • Posté le 15 mars 2021 à 05:44
    • #1256569
    Ok the CDATA doesn't work too.

    So put strings in a CDATA markup. The title with & will not be interpreted as XML markup but as string.

    Thanks you
  • comptoirdesmonnaies
    comptoirdesmonnaies 100% (11610x)
    PRO premium

    80 messages

    France

    Ok the CDATA doesn't work too.

    So put strings in a CDATA markup. The title with & will not be interpreted as XML markup but as string.

    Thanks you
    • Posté le 15 mars 2021 à 05:47
    • #1256575
    I have the same problem with <> characters (see image).

    Thank you
    Julien
    board
  • @thomas
    Administrateur
    @thomas

    348 messages

    Belgique

    Ok the CDATA doesn't work too.

    So put strings in a CDATA markup. The title with & will not be interpreted as XML markup but as string.

    Thanks you
    • Posté le 15 mars 2021 à 05:47
    • #1256575
    Hello Julien,

    The '&' character is replaced by '& amp ;'. (see attached image) So you have to decode the xml text when you try to read it.

    We cannot comply with your request to resend notifications but I can provide you with a list of your items sold since 13 March 2021 00:00 by email.

    Kind Regards,
    --
    Thomas
    Delcampe Team
    board
  • comptoirdesmonnaies
    comptoirdesmonnaies 100% (11610x)
    PRO premium

    80 messages

    France

    Hello Julien,

    The '&' character is replaced by '& amp ;'. (see attached image) So you have to decode the xml text when you try to read it.

    We cannot comply with your request to resend notifications but I can provide you with a list of your items sold since 13 March 2021 00:00 by email.

    Kind Regards,
    --
    Thomas
    Delcampe Team
    • Posté le 15 mars 2021 à 09:27
    • #1256659
    Hello Thomas,

    I already replaced the "&" character but this morning the caracters "<" and ">" (see the attached image) cause the same problem. But they are more difficult to encode because i risk to encode real markup too (and php didn't like that when we deserialized). For me that issue is major, i don't know if someone sended a post for it, but it impact all php implementation of your api :/

    Yes if you can send me by email the orders, it should be great.

    Kinds Regards
    Julien
    board
  • @thomas
    Administrateur
    @thomas

    348 messages

    Belgique

    Hello Thomas,

    I already replaced the "&" character but this morning the caracters "<" and ">" (see the attached image) cause the same problem. But they are more difficult to encode because i risk to encode real markup too (and php didn't like that when we deserialized). For me that issue is major, i don't know if someone sended a post for it, but it impact all php implementation of your api :/

    Yes if you can send me by email the orders, it should be great.

    Kinds Regards
    Julien
    • Posté le 15 mars 2021 à 11:50
    • #1256728
    I have sent you the email with your sold items.

    The characters "<" and ">" are also replaced by "& lt ;" and "& gt ;" respectively. The html_entity_decode can help you convert these characters: Lien (https)

    Kind Regards,
    --
    Thomas
    Delcampe Team
    board
  • comptoirdesmonnaies
    comptoirdesmonnaies 100% (11610x)
    PRO premium

    80 messages

    France

    I have sent you the email with your sold items.

    The characters "<" and ">" are also replaced by "& lt ;" and "& gt ;" respectively. The html_entity_decode can help you convert these characters: Lien (https)

    Kind Regards,
    --
    Thomas
    Delcampe Team
    • Posté le 15 mars 2021 à 12:18
    • #1256743
    Thank for the Email.

    In my case they aren't replaced when i received the notification (see the image).
    And i can't use html_entity_encode because i'll encode all the <> characters.

    Kind Regards,


    Julien
    board

Rejoignez la communauté des collectionneurs !

S'inscrire Se connecter