Thread

I imagine I’m simply missing something here, but I can’t seem to figure out how to really dig into this search.

We’re interested in storing per-entry notes (think weblog entry meta-info); something like the Template Notes which you can keep when Template Versioning is turned on.  Actually, it wouldn’t need to to be for each version (even if Entry Versioning is turned on), but should be kept with the entry.  I’d considered adding a field to each field group, but would really like something that will _never_ be available in templates so that content editors can keep whatever info they’d like there.

If anybody has ideas (or a dope slap and a pointer to how simple this is already!), I’ll be glad to hear them.

Thanks,
Scott

Any custom fields that you create for an entry don’t have to go into your templates 😉

Other than that not really come across anything for doing this. I think that a custom field would be your best bet in this instance though I stand to be corrected if there is a better way as would like to know if there is myself too.

Best wishes,

Mark

I’ve set up a number of sites with a “notes” custom field, and have never run into trouble doing it that way. If you’re concerned about someone accidentally adding that field in a template, you can always give it a short name like “notes_do_not_use_in_templates”.

The short name could always be gibberish, too.  The label for the field doesn’t have to match the short name at all, and the short names are case sensitive as well, making it even less likely that a field would be accidentally output in a public template.

OK, thanks everybody!  I’m glad for all the ideas, and especially the gibberish short name.  That will keep those hooligan designers at bay….

OK, thanks everybody!  I’m glad for all the ideas, and especially the gibberish short name.  That will keep those hooligan designers at bay….

They’ll rue the day that they place {Fhqwhgads} in a template!  Rue!