I wanted to migrate from Divi 4 to Divi 5, but I keep getting the message “The plugins listed below are using the Divi 4 framework and are not fully compatible with Divi 5. These plugins will continue to function; however, as they use the Divi 4 framework, the parts of your website that use these plugins will not benefit from Divi 5’s performance improvements” – but only when using the Calculated Fields form. ”
I’ve already had a look around the forum and, as I’m not the first person to ask about this, I’d like to know when full support for Divi 5 is planned.
What version of the CFF plugin are you currently using?
CFF has supported Divi 5 for approximately a year and includes two dedicated modules: one for Divi 4 and another for Divi 5.
If your forms were originally inserted using the Divi 4 module, they will retain the Divi 4 module structure even after you upgrade your website to Divi 5. In this case, you simply need to run Divi’s Divi 5 Migrator to convert the existing CFF modules to their Divi 5 equivalents.
In your WordPress dashboard, go to Divi → Divi 5 Migrator. Divi will automatically run a Compatibility Check to scan your pages, posts, templates, and widgets for content that needs to be migrated.
After reviewing the compatibility report, click Migrate This Site to Divi 5. During the migration, Divi will recognize the migration structure provided by the CFF plugin and use it to automatically transform your existing CFF Divi 4 modules into their corresponding Divi 5 modules.
Therefore, you should not need to manually remove and reinsert your CFF forms after migrating to Divi 5.
Thank you, @codepeople2, for your quick reply, and I’d like to apologise straight away for omitting what was probably the most important piece of information. I’m currently using the latest version of the plugin, v5.5.0.8.
However, I now have a question to clarify: the message stating that the plugin is incompatible appears just before the migration process begins. You say, that the Divi 4 module is currently in use, which is declared as incompatible. During the migration process, this is migrated to Divi 5 and is therefore compatible again once the migration is complete. Is that correct?
If so, I do wonder why the migration process doesn’t recognise this? If a Divi 5 module is indeed present and is essentially just waiting to be used, why doesn’t the migration process recognise this and instead display a success message?
Unfortunately, the migration process requires the user to click the “Migrate This Site to Divi 5” option in the Divi Migrator screen. Please note that this step is required by Divi as part of its own migration process.
Correct! But I’m referring here to the process that takes place before I even carry out the migration. That’s when the plugin is evaluated to determine if it’s incompatible. Even if you tell me that a module for Divi 5 already exists and should therefore be compatible?
I’ll take a look at what is happening with the Divi detector. However, once you execute the migration process, Divi automatically transforms the structure of the CFF Divi 4 integration into the corresponding Divi 5 structures.
Could you please let me know if I can send you a version of the plugin that modifies the Divi integration module, so you can check whether the issue persists before we upload it to the WordPress directory?
We have tested it on our servers, and the issue does not occur there.
Thank you very much for participating in the testing process.
We have installed this plugin version in different environments, and in all of them, Calculated Fields Form has been identified correctly.
For example, in the following screenshot, we inserted the form using Divi 4:
And in this video, we ran the Divi 5 Migrator process. As you can see, Calculated Fields Form was correctly identified as a module with Divi 5 support:
