Object-level settings

This article covers functionality available to customers on the Pro version.

Local fields are settings for one specific object: this post, this page, this category, this author. They live where you edit the object, not in a settings panel.

#The one rule

A global setting decides how the whole site behaves. A local field overrides it for one object. That is the whole model, and it is the same for every object type.

An empty local field means "follow the site." So clearing a field is how you return to the global value; there is no reset button because emptying the field is the reset.

This is behind the most common confusion with Verba: "I changed it globally and this one post did not change." That post has its own value. Open it, clear the field, and it will follow the site again.

#Each type has its own fields

The set of fields depends on what the object can meaningfully configure. A tag has almost none. A post has the most. There is no single grid with exceptions, so read the page for the type you are working with:

Categories
Tags
Users and authors
Posts
Pages

#Questions

Do local fields survive a theme or plugin update?

Yes. They are stored as metadata on the object, in the database, so an update does not touch them.

What happens to them if I deactivate Pro?

The fields disappear from the editor and stop affecting the front end. The values stay in the database and come back with the plugin.

Can I set a local field for a whole category of posts at once?

Not through these fields, since each one belongs to one object. What you can do is set the global value the way most posts want it and override only the exceptions, which is usually less work anyway.

Last updated 9 Sep 2026

Was this article helpful?

Resources

On this page

#The one rule

#Each type has its own fields

#Questions

FIND THE ONE THAT FITS YOUR PROJECT