Post Reply
Louis
Posts: 0
Joined: Wed Nov 05, 2014 2:03 pm

Error logic changed since update

Hi,

Before the update, I had a few errors messages that would enable (visible) when a service would fail (Data Error: Set property and on Success show what ever was being pulled). All working fine. It also worked if the content wasn't XML or JSON compatible. For example: If a feed no longer exists and the page has thrown a 404 redirect, it would treat it like an error and the messages would be enabled.

Since the update, error is now only thrown if the connection is a complete fail. If the actual page isn't correct, it just ignores it and acts as no error occurred.

Do you suggest anything to get it back to how it worked before?

Regards,
Louis

Evgene Karachevtsev
Posts: 12
Joined: Mon Apr 28, 2014 1:12 pm

Error logic changed since update

Hello Louis,

Unfortunately (or fortunately) we can't reproduce it. The logic works the same as for me. Could you please provide us with more info of what do you get in response?

Louis
Posts: 0
Joined: Wed Nov 05, 2014 2:03 pm

Error logic changed since update

No worries - It's not a big deal. I was just wondering if you were aware of any changes that might of done this.

Scenario:

  • Error message that has visible set to false on load / page show of page.

  • The rest service is then called, if success show content, if error message visible becomes enabled and the content stays disabled.

  • Before the update, the error would be called either if the connection failed or if the page isn't the correct language i.e. loading html 404 when the rest service expected JSON or XML.

  • After update, the error handler is only called if the connection failed. If the document is not what the rest service expected, it still counts as a success. So the error handler is never called.

    This might not be an error and made this way, but I was just making sure that you were aware of this change since the update.

    Regards,
    Louis

Yurii Orishchuk
Posts: 0
Joined: Fri Feb 14, 2014 8:20 am

Error logic changed since update

Hi Louis,

I've tried to do the same but i can not reproduce this issue.

Here is what is tried:

1.That's my service settings.
http://prntscr.com/574ub3/direct

  1. That's my events for this service.
    http://prntscr.com/574upl/direct

  2. That's result, when invoked on the page:
    http://prntscr.com/574vic/direct

    So please try to do the same from scratch. And please provide us screen shots with your testings if you will have this problem again.

    Regards.

Post Reply

Return to “Issues”