Thread

I am having a issue with the custom fields.

When I try and add a new custom field and select default text formatting to “none” it doesn’t work.  When I edit the new custom field the default text formatting is still set to XHTML.

Any ideas how to resolve this?  I am using Chrome on mac, and EE Version 2.1.3 Build 20101220

Are you using any extensions? Have you tried with other browsers?

I am using some plugins:

Structure
Blueprints
Matrix
FreeForm
MX Google Map
SEO Lite
CP Analytics
ImageSizer
Splitter

Yes I tired it in multiple browsers, chrome and firefox.  I reviewed the db entry and can see it doesn’t update the field.  So I am pretty confident it isn’t a browser issue.

I am also running into another issue.  The “Save Revision” button isn’t showing up.  I don’t think these issues are related, but wanted to mention it.

mz91184,

Are you saving any Custom Publish Layouts?

Yes, I am trying to utilize custom publish layouts.

I figured out a work around for now.  I am using the strip_html plugin to remove all html in the fields that shouldn’t have any formatting.  It would be great not to have to use a workaround though.

mz91184,

When I try and add a new custom field and select default text formatting to “none” it doesn’t work.  When I edit the new custom field the default text formatting is still set to XHTML.

Can I confirm here that it is when you go back to edit the actual custom field settings again it hasn’t stuck or is it the case when you goto your publish page and edit/add content to it there the text formatting is still XHTML?

Was this a fresh install or and upgrade from a previous version or build?

@John

Sorry for the bad wording before. I will try and write it better.

1)  Create a new custom text field with the text format as “none”.
2)  Edit the custom field settings and the text format is set to “xhtml” even though I selected “none” while creating it.
3)  If I add or edit content with this custom field, the output is in “xhtml”.

I am using a “Default EE” setup that I created last month.  This is the first time I used it in a project but I don’t think the “Default EE” setup is causing the issue.  It is just a mixture of pre-installed plugins and a modified config to speed up development.  I committed it to a SVN so I could export it whenever I started a new project.

I started this project using the “Default EE” setup with a previous build.  I noticed the custom field formatting issue and thought it was just a bug.  So I decided to upgrade to the latest build to see if it would be resolved.  It wasn’t resolved when I upgraded.

Here is the article I about the Dry EE install, (http://net.tutsplus.com/tutorials/php/apply-the-dry-principle-to-build-websites-with-expressionengine-2/).

Hi Mz91184,

I tried to replicate your issue as described above. When I set the new field to null and return to edit, it is still null.  This was a known issue with 2.1.2 and below. It was fixed with 2.1.3.

It seems like the upgrade to 2.1.3 didn’t take.  Did you commit it to the SVN or did you just try a clean install to test with first?

Do you have a version of 2.1.3 with no third party add-ons of any kind? If so can you try your three steps again in a clean install?

If you do not have a clean install, you can disable extensions to perform the test.

It is possible that SVN’s caching is interfering with this as well. It wouldn’t hurt to clear that cache.

The “Save Revision” button issue is a known bug we are working on 😊

Please let us know how it goes.

I’m having the same issue where the default text formatting changes back to XHTML. Disabled all extensions and it still did not work. Using the latest EE version (2.1.3)

RD
What extensions are you running?

Mz91184,
Did you have a chance to try our suggestions?

Barry,

I was out snowboarding all weekend; it was snowing all weekend here in MT.  Today I finally got a chance to try you suggestions.

1)  I tired clearing the cache but it didn’t fix the bug.

2)  I also tired disabling all the extensions, this didn’t have any effect either.

Thanks for the help and following up.

Barry,

I’m using Calendar, Deviant, Geotagger, Low Seg2Cat, Matrix, MX Title Control, and Super Search. I tried disabling them and had no luck. I’m running a few third party modules as well but I’m not sure if that has any effect on this.

Thanks for the help, Barry!

We’re still looking in this, thanks for your patience.

Thanks for all the help, guys.  If it is any help at all I didn’t start noticing it until I created around 6-7 custom field groups. Not sure if it was happening before but that is when I noticed the issue. May be of some help or none at all. 😊

Hi, guys. This is a problem with EE 2.1.3, but fixed in EE 2.1.4 beta.

I ran into this one myself and had to fix things up by doing the following:

Change the formatting to XTML - update the other entries. Save. Set to None, update the other entries.

Rinse, repeat.

I tested this with EE 2.1.4 and didn’t run into the same issue.

Does that help?