Thread

I made a custom field for a weblog… it’s a field for meta keywords.  I got my template pulling this value for the entries, but my values are getting paragraph tags around them.  Yar. 

The field Type: Text Input
Default Formatting: None , with “Hide Formatting Menu” checked.

What did I miss?

Thanks.

Sorry, here’s another I posted in the community core tech support… (http://ellislab.com/forums/viewthread/102358/)

I made a custom field for a weblog… it’s a field for meta keywords.  I got my template pulling this value for the entries, but my values are getting paragraph tags around them.  Yar.

The field Type: Text Input
Default Formatting: None , with “Hide Formatting Menu” checked.

I can edit the value, and it changes when I view the page, but my text gets the tags around it, which isn’t what I want for meta keywords.

What did I miss?

Thanks.

Sounds like it’s still applying XTHML formatting. Try to change it to some value, then back to “None” and be sure to check the box that applies it to all existing entries.

I’m not seeing any check box for applying the change to existing entries.  I’m using ExpressionEngine v 1.6.3.  Is this a version issue, or am I simply in the wrong place?  I’m in
CP Home ›  Admin ›  Weblog Administration ›  Field Groups ›  Custom Fields

Thanks.

Although upgrading to 1.6.6 is highly recommended, this should work with 1.6.3 as well. When you chose a different formatting option, you get

Note: You have selected a different field formatting choice then what was previously saved.
Update all existing weblog entries with your new formatting choice?

at the bottom of the page, right above the “Update” button.

Nope.  No such button.  No such message.  Verified that it’s not there in Safari and Firefox.

Upgrading will require a full dev/qa/prod release… so I might just hit this with a SQL query and be done with it.  It’d be nice to know, however, if the source of the problem is in fact the version of EE that this site is running.

I’d recommend updating as well.  a.)  for the bug/security fixes to the code base and b.)  To blow the dust off of the code you are currently running, making sure nothing has been corrupted, etc.

If you feel comfortable hitting it with an SQL query, make sure to backup first.  😊

Will do.  Yeah, I’m more comfortable with MySQL than I am with EE, and that’s stating it mildly.  We put things through a dev—>qa—>prod release cycle, so I think we’ll be fine as far as catching bugs and such is concerned.  The only thing we have trouble with in this case is when we push from dev to prod, we only push the templates… users are involved with the site making comments and such affect other tables that we don’t want to overwrite.  Does anyone know if the update affects the DB in any way?  Or is it just the files in the filesystem?  If it’s just the file system, then that’s pretty simple… we test in dev, then do a Subversion update on prod and we’re done.

Yes, the updates affect the database.  See ./system/updates/

-greg