function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
dkraun123dkraun123 

Site wide visualforce failures

Hi,

A week or so ago, I became unable to submit any visualforce forms that access custom objects/fields. Just in case my code could have been the problem, I made a very simple test page, and it shows the same problem. The test page is (I took out the
apex:page controller="testController"
apex:pageMessages id="pageMessages"
apex:form
apex:pageBlock
apex:pageBlockButtons
apex:commandButton value="Test" action="{!test}" rerender="pageMessages"
apex:pageBlockButtons

apex:pageBlockSection
apex:inputField value="{!testContact.Type__c}"
apex:pageBlockSection
apex:pageBlock
apex:form
apex:page

and the controller is:

public class testController
{
CRM_Contacts__c testContact = new CRM_Contacts__c();
public CRM_Contacts__c getTestContact()
{
return testContact;
}

public void test()
{
ApexPages.addMessage(new ApexPages.Message(ApexPages.Severity.INFO, testContact.Name));
}
}


Type__c is a picklist and when I first pull up the page, the picklist displays just fine with all of its values. The problem occurs when I click on the "Test" button to submit the form. I get the following visualforce error:

Could not resolve field 'Type__c' from <apex:inputField> value binding '{!testContact.Type__c}'


This same type of error occurs on every visualforce page, even pages that used to work and that I have not changed. Salesforce support said that they are unable to help with visualforce problems, so I was just wondering if anyone has seen anything like this before.

Thanks,
David

Message Edited by dkraun123 on 09-25-2008 11:33 PM

Message Edited by dkraun123 on 09-25-2008 11:35 PM

Message Edited by dkraun123 on 09-25-2008 11:39 PM
dchasmandchasman
There is a problem with namespacing and Developer Mode interaction that will be corrected in the next patch (fix has already been submitted for deployment). The workaround is to disable Developer Mode in your user settings.

BTW "The test page is (I took out the <>'s because they are causing problems with the post):" Use the SRC toolbar button to post source please.