Console output

This topic contains 7 replies, has 3 voices, and was last updated by  Stiofan O’Connor 6 years, 1 month ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
  • Author
    Posts
  • March 24, 2018 at 12:16 pm #423119

    Dirk
    Full Member
    Post count: 390

    Hi,

    you still have a lot of console prints that should not be there for a beta.

    Best,
    Dirk

    March 25, 2018 at 6:42 pm #423228

    Alex Rollin
    Moderator
    Post count: 27815

    Thanks, noted; feel free to add specifics.

    March 26, 2018 at 7:32 am #423308

    Dirk
    Full Member
    Post count: 390

    Remove all.

    March 26, 2018 at 9:28 am #423322

    Stiofan O’Connor
    Site Admin
    Post count: 22956

    you still have a lot of console prints that should not be there for a beta.

    A beta is for testing and debugging, which is exactly why you would output to the console…

    This will not be removed until after the beta.

    Thanks,

    Stiofan

    March 26, 2018 at 5:20 pm #423465

    Dirk
    Full Member
    Post count: 390

    Can you explain what the “ready!” is helping you in debugging and testing?

    Thanks,
    Dirk

    March 26, 2018 at 5:31 pm #423467

    Stiofan O’Connor
    Site Admin
    Post count: 22956

    That is being used to let us know the add listing functions are being reached with no problems.

    It can tell us if JS problems occur before or after this action.

    Stiofan

    March 26, 2018 at 7:26 pm #423493

    Dirk
    Full Member
    Post count: 390

    ??? But this is not coming only when “Add listing” is called!

    Dirk

    March 27, 2018 at 8:36 am #423589

    Stiofan O’Connor
    Site Admin
    Post count: 22956

    Then there is the exact reason it was needed 🙂

  • Author
    Posts
Viewing 8 posts - 1 through 8 (of 8 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket