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
Jon Mountjoy_Jon Mountjoy_ 

Rich Text Editor in Visualforce in Spring '10

Hi

 

I tried to use the Spring '10 rich text editor field in one of my own Visualforce forms, but it didn't seem to work (online editor complained about the field).  Am I doing something wrong, or is that by design?

 

Thanks,
Jon

Best Answer chosen by Admin (Salesforce Developers) 
prageethprageeth

Hello Jon;

I didn't see any problem of using richText fileld in VF pages. If your Opportunity has a richText field 

named "myField__c", you can use following syntax to display it in the VF page.

 

<apex:page standardController="Opportunity">

<apex:form>

<apex:inputField value="{!opportunity.myField__c}"/>

</apex:form>

</apex:page> 

 OR

<apex:outputField value="{!opportunity.myField__c}"/>

 

Could you please post your code here?

 

 

 

 

 

 

 

All Answers

prageethprageeth

In order to use this field, you have to create a pre-release account.

Did you try it in a pre-release account (or in your normal developper accout)?

 

 

To create a pre-release account:

https://www.salesforce.com/form/trial/prerelease_spring10.jsp 

Jon Mountjoy_Jon Mountjoy_

Yep, I am on a pre-release org. 

 

The rich text editor fields work fine in the standard UI, but not in my Visualforce pages. 

prageethprageeth

Hello Jon;

I didn't see any problem of using richText fileld in VF pages. If your Opportunity has a richText field 

named "myField__c", you can use following syntax to display it in the VF page.

 

<apex:page standardController="Opportunity">

<apex:form>

<apex:inputField value="{!opportunity.myField__c}"/>

</apex:form>

</apex:page> 

 OR

<apex:outputField value="{!opportunity.myField__c}"/>

 

Could you please post your code here?

 

 

 

 

 

 

 

This was selected as the best answer
Jon Mountjoy_Jon Mountjoy_

prageeth, you are absolutely correct.  It works just fine in my Visualforce page now. I could have sworn the editor was complaining, but I cannot reproduce.  I must have made a mistake.

 

So now I have a page with a gorgeous rich text editor!  Awesome.

 

Thanks!

Jon