<p>Thanks to carlcs for pointing this out. If I edit the Standard.json file in craft/config/redactor/ as per these instructions (<a href="https://craftcms.com/help/redactor-ii-configs" rel="nofollow">https://craftcms.com/help/redactor-ii-configs</a>) it's fixed. </p>

<p>I find it odd that Craft 2.5 didn't come with this Redactor config fix included, rather than letting it break and leaving it up to developers to fix it. I can understand if you had custom configs, but the default Simple and Standard configs should come fixed with the install or upgrade, no?</p>

CC BY-SA 3.0
2015-12-04T02:46:47.793Z
Craft updates won't ever touch any file outside the craft/app/ folder. Download the manual update package from craftcms.com to get the updated config files.
carlcs
CC BY-SA 3.0
2015-12-04T20:29:20.943Z
Anyway to update the Default config? I only have two configs simple and standard, all of my fields have always used Default. So now I need to edit standard.json, then go change all my rich text fields to standard instead of default... or is there a way to update the default config?
Bowenac
CC BY-SA 3.0
2015-12-04T01:27:11.817Z
2015-12-04T01:27:11.817Z
Benek Lisefski
<p>After recently upgrading to Craft 2.5.x the HTML code view button is now missing from the "standard" Rich Text view, which means I can no longer edit all the custom HTML code I've added to those fields.</p>

<p>Do I have to create a custom Redactor config file to get HTML code view back, or should it still be included in the Standard config?</p>

CC BY-SA 3.0
2015-12-04T01:18:19.227Z
I don't have a custom redactor config file. I'm using the Craft standard view. Is the Craft standard view going to be updated with the change or is it now required that we create custom redactor configs to get source view back?
Benek Lisefski
CC BY-SA 3.0
2015-12-04T01:22:43.067Z
There's two config files in craft/config/redactor/ that are meant to be edited, Standard.js and Simple.js. Edit them to your needs and select a config from the Rich Text field settings.
carlcs
<redactor><richtext><upgrades>
HTML code button missing from Rich Text "standard" view after 2.5 upgrade
# HTML code button missing from Rich Text "standard" view after 2.5 upgrade

(Asked by: username_0 on 2015-12-04)

After recently upgrading to Craft 2.5.x the HTML code view button is now missing from the "standard" Rich Text view, which means I can no longer edit all the custom HTML code I've added to those fields.

Do I have to create a custom Redactor config file to get HTML code view back, or should it still be included in the Standard config?

**Tags:** redactor, richtext, upgrades

> **Comments:**
> **username_0**: I don't have a custom redactor config file. I'm using the Craft standard view. Is the Craft standard view going to be updated with the change or is it now required that we create custom redactor configs to get source view back?  
> **username_1**: There's two config files in craft/config/redactor/ that are meant to be edited, Standard.js and Simple.js. Edit them to your needs and select a config from the Rich Text field settings.  

---

## 1 answers

### Answer by username_0 on 2015-12-04. Score: 2

Thanks to username_1 for pointing this out. If I edit the Standard.json file in craft/config/redactor/ as per these instructions (<https://craftcms.com/help/redactor-ii-configs>) it's fixed.

I find it odd that Craft 2.5 didn't come with this Redactor config fix included, rather than letting it break and leaving it up to developers to fix it. I can understand if you had custom configs, but the default Simple and Standard configs should come fixed with the install or upgrade, no?

> **Comments:**
> **username_1**: Craft updates won't ever touch any file outside the craft/app/ folder. Download the manual update package from craftcms.com to get the updated config files.  
> **username_2**: Anyway to update the Default config? I only have two configs simple and standard, all of my fields have always used Default. So now I need to edit standard.json, then go change all my rich text fields to standard instead of default... or is there a way to update the default config?  

---

