Viewing 6 replies - 1 through 6 (of 6 total)
  • Hi,

    I tried to remove the avatar since i dont need it but it still gives me the parserror.

    I also made the replacement. But still gives me the error.
    It is not working with me

    Thread Starter 123hede

    (@123hede)

    in your liveblog post page, open firefox – open firebug extension (or install extension first), go to “Net” tab. Clear all data. After publish new liveblog post at the same page. what do you see in firebug net tab. click requested url in this tab. open response tab. copy all response data and write here.

    Hi 123hede,

    Thank you for your quick response.

    Here is a print screen link from the response tab.

    View post on imgur.com

    Thank you again for your help.

    Thread Starter 123hede

    (@123hede)

    Not header response, only response

    Headers, Post, –> Response <– here

    Sorry ??

    Here is the response

    {"entries":[{"id":"3794","type":"new","html":"<div
    id=\"liveblog-entry-3794\" class=\"liveblog byuser comment-author-merxhanemini even thread-even depth-1
     liveblog-entry\" data-timestamp=\"1433856803\">\r\n\t<header
    class=\"liveblog-meta\">\r\n\t\t<span
    class=\"liveblog-author-avatar\"><\/span>\r\n\t\t<span
    class=\"liveblog-author-name\"><\/span>\r\n\t\t<span
    class=\"liveblog-meta-time-- pull-right\"><a
    href=\"#liveblog-entry-3794\"><span
    class=\"date\"><\/span><span
    class=\"time\">15:33<\/span><\/a><\/span>\r\n\r\n\r\n\t<div
    class=\"liveblog-entry-text\" data-original-content=\"dsdada\">\r\n\t\t<p>dsdada<\/p>\n\t<\/div>\r\n
    \t<ul
    class=\"liveblog-entry-actions\">\r\n\t\t<li><button
    class=\"liveblog-entry-edit button-secondary\">Edit<\/button><button
    class=\"liveblog-entry-delete button-secondary\">Delete<\/button><\/li>\r\n\t<\/ul>\r\n<\/div>\r\n"}
    ],"latest_timestamp":null}

    Hi 123hede,

    Can you find the solution. Do you think if I totally delete the avatar function calls and vars the error will disappear.

    Thank you,
    Merxhan

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Error: parseerror bug fixing’ is closed to new replies.