Skip to main content
All of Generatify’s settings live in a single WordPress option, generatify_settings, stored as an associative array.
Toggles are the strings on and off, not booleans. A key that has never been seeded is absent from the array, and absent counts as off.
Prefer the settings screen or the PUT /settings endpoint over writing the option directly. Both merge your values over the stored ones and fire the update hooks; a direct update_option with a partial array silently discards every setting you left out, including your API keys.
To change one value safely in code:

When keys are seeded

Free defaults are written on activation. Pro defaults are added when a licensed install first loads, and again after an update for any key that did not exist before. Your existing values are never overwritten. This means a free install has no connectorChatgptApiKey key at all rather than an empty one. Code that reads a Pro key on a free site should handle it being missing.

Free settings

Pro settings

These keys only exist on an install with an active license.

Renamed keys

Two migrations run automatically on update. You do not need to do anything, but if you have code referencing the old names, update it. The four editor toggles became a single feature. An install with any of them enabled keeps the capability under the new key.