+ Start a Discussion
ryyhryyh 

Old Console?

Is there anyway to get to the old developer console anymore?

 

The new one for simple things just straight up Blows Goats. It never works in Chrome for me have to goto Firefox, it's instanely slow and clumbsy. It's slowing down my development and I'm going to throw the monitor I keep it on out the window. 

 

Thanks!

Thomas DvornikThomas Dvornik
The system log (old developer console) has been removed, so there is no way to get to it.

What never works in Chrome? Maybe I can help you past some of those issues.

If all you want is the old capabilities, you can minimize the problems panel, and just use the Log tab with the Open Raw Log functionality. You can also set up a perspective just to show the log panel in the interactive view, so you can filter the log to see the data you want, while hiding all of the other panels.
gaisergaiser

I do not think so, but If you want to add an indea on ideas exchange I would vote for it.

 

Incodentally for me it works better in Chrome than FF. Although when I say "better", I do not mean good, it just means less unbearable.

 

I had to teach myself not to double-click or use "Open" on debug log and always use Raw Log.

Every time when I accidentaly double-click on on a log line in Log window it is quicker to close the console and start all over again than to wait while this thing loads all that stuff it wants to load.

ryyhryyh
In chrome

There is no execute buttons in the code box http://www.screencast.com/users/ryanmh/folders/Jing/media/1b195aa6-cbe4-4343-abd9-c1db5a0b020b
After executing code the log tab appears but shows no log info http://www.screencast.com/users/ryanmh/folders/Jing/media/520ed773-960f-425b-8ca0-d1e718269875
I get this error a lot http://www.screencast.com/users/ryanmh/folders/Jing/media/2c76c1ce-781c-4e18-a1d7-ece9486511f2

And that is just for starters. I'm on MAC OS X 10.8.2 and the latest Chrome
Thomas DvornikThomas Dvornik

Hey Ryyh,

 

Yes, that is a known with Chrome v25. We are still working with Sencha on a fix. Here is more information: http://salesforce.stackexchange.com/questions/9131/developer-console-issues-in-chrome-spring-13

 

Once the developer console gets in that state, nothing will render properly. Closing the logs, waiting 5 seconds, and refreshing the console will fix it, but it will most likely break again when you open another log in the interactive view.