Access to Studio Back-Office

[eisen]

Hi guys,

I'm new to developing in Board Game Arena Studios. I started developing a game, but I'm currently stuck. I'm trying to access the logs to debug my new game setup, but I can't find the logs anywhere I have access to.

According to this article: http://en.doc.boardgamearena.com/Studio_back-office, I should have a resources.html file on the root of my sftp account that provides this information. I don't have the file at all, just the folders for the game I'm developing and the demo games for learning.

I'm assuming at this point the logs are in the studio back-office. If this is correct, how can I get access to the back-office? If the logs aren't not in the back-office, how do I access the logs?

Thanks for your help,
Eisen

[Een]

Hi,

The studio back office is now obsolete, we need to update this wiki page.
All functionnality has been moved to the menu or to links at the bottom of the game area. For the logs, please see http://forum.boardgamearena.com/viewtop ... =12&t=3719

Cheers,
Een

[eisen]

Thank you Een for your response. The problem is that my game is crashing during new game setup and I never make it to the game table page. But you just gave me the idea to comment out the code and start uncommenting until it crashes.

Best regards,
Eisen

[sourisdudesert]

Hi,

We've updated the Studio so the crashes during game setup are now displayed as a "red error message" during the "Express start".

This way, there's no need of this log anymore: you get immediately the error message you need.

Eisen: if you want to try this you can reproduce your game setup error and see if it appears correclty during the "Express start".

Cheers,

[eisen]

Thank you sourisdudesert,

It is working fine. I appreciate your help.

Eisen

[coolpapa]

Can I ask also where the PHP trace functions (self::debug, self::log, etc.) send their messages? I've got several in my code and I don't see those messages anywhere....

[sourisdudesert]

Hi,

It is supposed to appear in the normal message log (request & SQL logs).

Cheers,

[coolpapa]

Hmmm. I'm really not seeing any of those debug messages anywhere. Any ideas on what might be causing that?

[Een]

Hello,

Last time I checked, messages were displayed correctly:
self::trace($msg) writes in the log displayed by the 'BGA request&SQL logs' link
self::error($msg) writes in the log displayed by the 'BGA unexpected exceptions logs' link.

Cheers,
Een