has anyone else ran into this issue?

developer console page is failing to load on database.com

 

url loaded when clicking on "developer console"

https://saas-momentum-***.database.com/_ui/common/apex/debug/ApexCSIPage

 

error message: 

content: Started (2437720569, https://saas-momentum-***.database.com/_ui/common/apex/debug/ApexCSIPage) chrome-extension://dhdgffkkebhmkfjojejmpbldmpobfkfo/content.js:268

content: disable event processing for 2437720569 chrome-extension://dhdgffkkebhmkfjojejmpbldmpobfkfo/content.js:273

Loading config... ApexIDEBase_Ext4.js:93

Loaded config... ApexIDEBase_Ext4.js:93

Querying for trace flags... ApexIDEBase_Ext4.js:93

Failed to load resource: the server responded with a status of 400 (Bad Request) https://saas-momentum-***.database.com/services/data/v26.0/tooling/query/?q=SELECT%20Id%2C%20Visualforce%2C%20System%2C%20Database%2C%20Callout%2C%20ApexCode%2C%20ApexProfiling%2C%20Workflow%2C%20Validation%20FROM%20TraceFlag%20WHERE%20TracedEntityId%3D'005E0000001jeZ4IAI'%20AND%20ScopeId%3D'005E0000001jeZ4IAI'&_dc=1356739350887

 

I have tried a number of different browsers to the same effect.

Hi all,

I've posted before on Twitter about the browser-based developer console, and hinted at some of the issues I've had (overall though, I do like it), but not put them down in any meaningful fashion.

One of my dev orgs was updated to summer 12 this weekend and I've encountered an issue that's a real nusiance, so it's prompted me to post here to explain it in full. I'll also use this thread to list some of the other issues/areas for improvement.

Anyway, the main issue I'm having at the moment: before the update, the console was pretty good at working out when I had done something stupid and preventing the save, which allowed me to fix and save again once correct. After the update however, I get notified of the problem after I try to save, and worse, when I make changes, I can't save the file. I have to close the developer console window and open it again, re-do my changes and then save.

Previously I think this is how it worked:

1. User made changes to code in the console
2. As user made changes, either javascript on the page ran checks on the code, or sent the changes to the server - but did not commit them
3. When the user clicked save, the file was committed. The user could only save if the console thought the code was valid i.e. if the code passed step 2.

Now, it's as if the following is happening:

1. User makes changes to code in the console.
2. User clicks save - it is only at this point that the code goes to the server.
3. If there are errors in the code, the user is told there is an error. Internally, the console notes the code is invalid because the server has told it so.
4. User fixes the error, but cannot save the code as the console believes the code is invalid, because the server told it. The console should try to save the file again and await the new result.

Hope that makes sense - any one else experiencing the same? I'm using Chrome, haven't tried other browsers as yet.

Other issues I've been meaning to post about:

• No asterix on tab names - OK, this is a Summer 12 change. Previously, when you had multiple files open in the console, ones you'd changed but not saved were shown with an asterix against their name in the tab. This was useful but has been removed.
• Refresh - Every now and again you'll get a message about having to refresh logs manually, even when there are no logs open. You get one of these messages for every class/page you have open.
• Attribute suggestions - The editor can be a bit keen to suggest attributes for VF tags as you move around code. Actually this looks like it may have been fixed :)

Those are the only ones I spring to mind right now. I'll bookmark this thread and add more as I think of them.

I don't want to sound overly negative about the developer console - niggles aside, I was really quite happy with the last release's version, so much so that I made it my first choice for development over the Force.com IDE, and I really like the look of some of the things in the latest release. And it's all a long, long way away from the options we had, even as little as a year ago, so please keep up the great work :)