{"id":51494,"date":"2026-04-08T07:55:58","date_gmt":"2026-04-08T07:55:58","guid":{"rendered":"https:\/\/crocoblock.com\/knowledge-base\/?post_type=troubleshooting&p=51494"},"modified":"2026-04-08T07:56:01","modified_gmt":"2026-04-08T07:56:01","slug":"jetplugins-not-working-after-domain-change-or-migration","status":"publish","type":"troubleshooting","link":"https:\/\/crocoblock.com\/knowledge-base\/troubleshooting\/jetplugins-not-working-after-domain-change-or-migration\/","title":{"rendered":"JetPlugins Not Working After Domain Change or Migration"},"content":{"rendered":"\n

After migrating a WordPress site to a new domain or hosting, JetPlugins <\/em>may stop working due to a combination of issues: outdated URLs stored in the database, a license tied to the old domain, and misconfigured post type or filter settings that reference the previous environment.<\/p>\n\n\n\n

This issue typically appears when moving from staging to live, changing a domain name, or switching hosting providers \u2014 and manifests as missing license updates, 404 errors on CPT <\/strong>pages, non-responsive filters, or broken form submissions.<\/p>\n\n\n\n

This is a common JetPlugins <\/em>not working after migration issue, and can also appear as a Crocoblock not working after domain change problem on WordPress websites.<\/p>\n\n\n\n

It affects all JetPlugins <\/em>\u2014 JetEngine<\/em><\/a>, JetSmartFilters<\/em><\/a>, JetFormBuilder<\/em><\/a> <\/em>\u2014 on WordPress sites built with Elementor, Gutenberg, or Bricks Builder.<\/p>\n\n\n\n

Before proceeding with the reading, check our JetPlugins Staging to Live: Checklist <\/strong><\/a>tutorial.<\/p>\n\n\n\n

Replace Old Domain URLs in the Database<\/h2>\n\n\n\n
\n

One of the most common reasons for non-working JetPlugins <\/em>after migration is that the old domain is still stored in the database.<\/p>\n\n\n\n

It often affects the plugin settings, so if the old domain is still present in the database, some JetPlugins <\/em>may continue pointing to invalid URLs or outdated objects.<\/p>\n\n\n\n

Use a proper search and replace tool to update all old URLs to the new domain.<\/p>\n\n\n\n

For example, you can use the Better Search Replace <\/em>plugin or WP-CLI<\/em> search-replace commands.<\/p>\n\n\n

<\/svg><\/div>
Warning<\/div>

A regular manual database edit may break serialized data, so it is recommended to use tools designed specifically for WordPress search and replace operations.<\/p><\/div><\/div>\n\n\n\n

\"replace<\/a><\/div>\n<\/div><\/div>\n\n\n\n

Check wp-config.php URL Constants<\/h2>\n\n\n\n
\n

If the old domain is hardcoded in the wp-config.php <\/strong>file via the WP_HOME <\/strong>and WP_SITEURL <\/strong>constants, WordPress may keep redirecting requests to the previous domain even after the database migration.<\/p>\n\n\n\n

Open the wp-config.php <\/strong>file and check whether the following constants are set:<\/p>\n\n\n\n

define( 'WP_HOME', 'https:\/\/your-old-domain.com' );\ndefine( 'WP_SITEURL', 'https:\/\/your-old-domain.com' );\n<\/code><\/pre>\n\n\n\n
If they still point to the old domain, update them or remove them if they are no longer needed.<\/p>\n<\/div><\/div>\n\n\n\n
Check SSL and Mixed Content Issues<\/h2>\n\n\n\n
\n
If the website was moved from HTTP to HTTPS, some frontend functionality may stop working because of mixed content issues. This may affect AJAX requests of the smart filters.<\/p>\n\n\n\n
Make sure all website URLs use HTTPS and that the SSL certificate is configured correctly.<\/p>\n\n\n\n
If necessary, you can:<\/p>\n\n\n\n