W3TC Error With Divi Theme

Hi thanks.

There are actually two issues here.

1. Here is the background:
– We are using the Divi theme.
– We are committed to the Divi solution because we are using its Library modules to build pages programmatically using the WordPress API.
– We create two different ‘page constructs’ using this method A) ‘bat-12-project’ pages and B) ‘bat-12-after-hammer’ pages.
– These two page constructs use the almost all of the same Divi library modules and our process to create them using the WordPress API is identical. The only difference between the two is the WordPress User who is designated are the ‘Author’.

2. The first problem is that if W3 Total Cache and the AffiliateWP plugin are activated it is causing a critical error when you select to view the ‘Pages > All Pages’ or ‘Pages >Add Page’ from the Admin Dashboard. This is the error: ‘There has been a critical error on this website. Please check your site admin email inbox for instructions. If you continue to have problems, please try the support forums.’
– If you disable all cache setting (as far we can tell) in W3 Total Cache there is still an error with AffiliateWP activated.
– If you deactivate W3 Total Cache with AffiliateWP activated there is no error.
– If you deactivate AffiliateWP with W3 Total Cache activated there is no error.
– If you change the theme to Twenty Twenty-Five with W3 Total Cache and AffiliateWP plugins activated there is no error.

The immediate solution has been to deactivate W3 Total Cache – however this is causing the second problem which has more impact on us than the first problem.

3. The second problem is that the ‘bat-12-project’ page construct created using the Divi theme will not display the Divi modules when W3 Total Cache is deactivated.
– This problem only affects the ‘bat-12-project’ page constructs and it does not affect the ‘bat-12-after-hammer’ page constructs.
– If you activate W3 Total Cache it will display the Divi modules.
– If you disable all cache settings (as far we can tell) in W3 Total Cache it will display the Divi modules.
– If you deactivate W3 Total Cache it will not display the Divi modules.
– If you delete W3 Total Cache and remove all traces (we can find using phpMyAdmin etc.) it will not display the Divi modules.
– If you change the theme to Twenty Twenty-Five with W3 Total Cache deactivated it displays one of the Divi modules (a template) but not all of the Divi libary modules.
– We tried creating pages programmatically with W3 Total Cache deactivated and it makes no difference so this does not appear to be something related to the page create process.

4. We have been in contact with AffiliateWP and Elegant Themes (Divi) support.
– The common issue appears to be W3 Total Cache operating with the Divi theme.
– AffiliateWP identifies the first problem (pages critical error) as related to W3 Total Cache because it only occurs with W3 Total Cache activated (we have not tried a different Cache solution). The same could be said about AffiliateWP though. Not sure where the plugin conflict lives.
– Divi identifies the both problems as related to W3 Total Cache, particularly the second problem because activating and deactivating W3 Total Cache directly triggers the viewing problem. We cannot display the subject pages without W3 Total Cache activated.

In sum our immediate solution is to deactivate W3 Total Cache but if we do that it is corrupting the ability to view Divi library modules. So W3 Total Cache remains activated until we can resolve how to deactivate it and to still be able to display all Divi modules in the ‘bat-12-project’ page construct.

Please let us know what we can do to help resolve this.

Thanks, Mark