Aimogen ProDocumentation
Product page Support

Legacy Aiomatic identifiers

Every technical identifier in Aimogen Pro that still uses the Aiomatic name, why it does, and what it maps to.

The plugin was renamed from Aiomatic to Aimogen in version 2.6.3. Technical identifiers were deliberately not renamed, because doing so would break every existing site, every custom snippet and every third-party integration.

This page is the complete list of what you will encounter.

Why they were kept#

Renaming an option key orphans your settings. Renaming a shortcode breaks existing content. Renaming a hook breaks custom code. Renaming a table loses data. None of that buys anything except tidiness.

So the surface changed and the plumbing did not.

Text domain#

aiomatic-automatic-ai-content-writer

Used for every translated string. Translations keyed to it continue to work.

Options#

Every option keeps the aiomatic_ prefix:

aiomatic_Main_Settings          aiomatic_Chatbot_Settings
aiomatic_Spinner_Settings       aiomatic_Limit_Settings
aiomatic_Limit_Rules            aiomatic_Menu_Rules
aiomatic_Editor_Rules           aiomatic_mcp_settings
aiomatic_rules_list             aiomatic_youtube_list
aiomatic_amazon_list            aiomatic_review_list
aiomatic_csv_list               aiomatic_listicle_list
aiomatic_forum_list             aiomatic_reply_list
aiomatic_omni_list              aiomatic_running_list

Two exceptions use the new prefix, because they were added after the rename:

aimogen_snippets_db_version
aimogen_agents_db_version

The full list is in Data model.

Database tables#

{prefix}aiomatic_logs
{prefix}aiomatic_logmeta
{prefix}aiomatic_agent_runs
{prefix}aiomatict_shortcode_rez
{prefix}aimogen_snippets

Shortcodes#

Most are registered twice, once under each name, pointing at the same callback:

[aimogen-chat-form]     [aiomatic-chat-form]
[aimogen-article]       [aiomatic-article]
[aimogen-image]         [aiomatic-image]
[aimogen_charts]        [aiomatic_charts]

Both work. Existing content keeps rendering.

Three exist only under the aimogen name, having been added after the rename:

[aimogen_post_creator]
[aimogen_user_remote_chatbot]
[aimogen_demo_description]

And one has only ever had one name:

[aicontent]

The complete list is in Shortcode reference.

Hooks#

Filters and actions predating the rename keep aiomatic_:

aiomatic_modify_ai_query        aiomatic_modify_ai_reply
aiomatic_ai_functions           aiomatic_model_selection
aiomatic_ai_allowed             aiomatic_get_ip

Hooks added after use aimogen_:

aimogen_api_ready
aimogen_reliability_failover
aimogen_smart_key_state_changed
aimogen_smart_key_recovered
aimogen_super_page_components

The API key filters exist in both forms, and the order matters:

php
$token = apply_filters( 'aimogen_openai_api_key',  $token );
$token = apply_filters( 'aiomatic_openai_api_key', $token );

The aiomatic_ filter runs second, so a legacy filter still has the final word. See Filter reference.

Capability#

access_aiomatic_menu

One capability, unchanged.

Post types#

All seventeen keep the prefix:

aiomatic_agent          aiomatic_assistants     aiomatic_personas
aiomatic_forms          aiomatic_embeddings     aiomatic_batches
aiomatic_file           aiomatic_convert        aiomatic_finetune
aiomatic_video          aiomatic_remote_chat    aiomatic_omni_temp
aiomatic_editor_temp    aiomatic_omni_file      aiomatic_themes
aiomatic_user_data      aiomatic_lead

Taxonomies#

ai_template_categories
ai_file_type
coderevolution_post_source

The last is the marker identifying posts the plugin created, and predates both names.

Cron events#

aiomaticaction              aiomaticeditaction
aiomaticactionclear         aiomatic_new_post_cron
aiomatic_index_single_post  aiomatic_agent_run_single
aiomatic_agent_recover      aiomatic_agents_watchdog
aiomatic_expired_post_delete
aiomatic_license_recheck
aiomatic_wp_ai_connectors_warm_cache

Custom intervals: aiomatic_cron, aiomatic_cron_ten, aiomatic_cron_sfert, aiomatic_cron_half.

See Cron events.

REST namespaces#

/wp-json/aiomatic/v1/text
/wp-json/aiomatic/v1/image
/wp-json/aiomatic/v1/embeddings
/wp-json/aiomatic/v1/models
/wp-json/aiomatic/v1/assistants
/wp-json/aiomatic/v1/rules
/wp-json/aiomatic/v1/chart-image
/wp-json/omniblock/v1/webhook
/wp-json/aiomatic-mcp/v1/*

Firewall allowlists must use these paths. See Plugin and server conflicts.

Gutenberg block namespace#

aiomatic-automatic-ai-content-writer/aiomatic-chat
aiomatic-automatic-ai-content-writer/aiomatic-article
...

Kept so existing block content does not fail validation. The block category is aiomatic, displayed as "Aimogen Blocks".

Extension plugin folders#

aiomatic-extension-amazon-api
aiomatic-extension-mcp-server
aiomatic-extension-pdf-files
aiomatic-extension-wpforo
aiomatic-extension-toubiz-api
aiomatic-extension-amazon-s3-images

See Official extensions.

PHP files and classes#

The plugin file is aimogen-pro.php, and the folder is aimogen-pro, but most internal files and functions keep the aiomatic prefix:

aiomatic-generators.php     aiomatic-helpers.php
aiomatic-rules.php          aiomatic-chatbot.php
Aiomatic_Embeddings         Aiomatic_Query_Function
Aiomatic_Query_Parameter    Aiomatic_Agent

New components use the new name: Aimogen_API, Aimogen_Response, Aimogen_Thread, Aimogen_Snippets_Engine.

AIOMATIC_PLUGIN_FILE is defined alongside AIMOGEN_MAJOR_VERSION and AIMOGEN_IS_PRO.

Support and documentation URLs#

The support destination keeps the legacy path:

https://coderevolution.ro/support/tickets/aiomatic-support/

That is correct and current — it is where Aimogen Pro support tickets go.

What to use when writing about it#

Use "Aimogen Pro" in prose, in documentation and when talking to customers.

Use the exact identifier in code, settings references, firewall rules and support tickets — and say why, briefly, so nobody thinks it is a mistake.

Still stuck? Open a support ticket and include the diagnostics from Aimogen Pro › System & Logs › System Info.