Over the last couple of months, across all orgs used by my development team, we have noticed that the Developer Console refuses to allow anybody to save changes made to Visualforce pages or components. Whenever you try to save, an issue with no problem description shows up in the Problems panel attached to line 1 of the page/component. This happens every single time, regardless of any actual changes being made (I can add and delete a whitespace, and it still won't allow me to save). We noticed this problem during Summer '13, and it is still happening after our upgrade to Winter '14.
Anybody else experiencing this issue, or know how to fix it?
Best Answer
I've experienced this too in the Developer's Console, and the errors I encounter mention that there is an issue with either the
ContainerIdor theDeploymentId.If it is the
DeploymentId, there is an easy fix. Copy your code (always make sure you copy your code if you are having trouble with the Dev Console...), then go to any Salesforce record and paste the badDeploymentId, then click Delete .Example:
You'll get a page that looks like this:
If the issue purely concerns a
ContainerId, then I don't know of an easy fix. When this has happened to me, the only fix I found was to edit my Class in the Class record itself.( Develop ➽ Apex Classes ➽ Your_Class)
As a side note, having different developers working on VF Page AND the Controller simultaneously can be a big headache because (many, many times) I've had my Controller's changes overwritten when the developer working on the VF page commits a change without making sure they had the up-to-date controller.
I highly recommend trying to nail down the Controller first before working on the VF Page, and if this is not possible, both developers need to have enough wherewithal to know which version of the controller they are working with (so not to overwrite the Controller with an old version resulting in lost work).