{"id":2554,"date":"2018-04-18T19:37:59","date_gmt":"2018-04-19T02:37:59","guid":{"rendered":"https:\/\/www.elegantthemes.com\/documentation\/?p=2554"},"modified":"2018-04-19T18:18:58","modified_gmt":"2018-04-20T01:18:58","slug":"compatibility-levels","status":"publish","type":"post","link":"https:\/\/www.elegantthemes.com\/documentation\/developers\/divi-module\/compatibility-levels\/","title":{"rendered":"Compatibility Levels"},"content":{"rendered":"

Note:<\/strong> This tutorial series is intended for advanced users. At least a basic understanding of coding in PHP and JavaScript is required.<\/p><\/blockquote>\n

How a custom module looks and behaves inside the builder depends on its level of compatibility with the builder.\u00a0There are three levels of compatibility available to custom modules:\u00a0off<\/code>\u00a0(this is the default), partial<\/code>, and on<\/code>. Custom modules can declare their level of compatibility using the vb_support<\/code>\u00a0property in their PHP class definition.<\/p>\n

No Compatibility<\/h2>\n

This is the default setting for all custom modules. Live previews are not shown for modules with no support for the latest version of the Divi Builder. Instead, a generic block will be shown. The module’s settings can still be edited and it can still be moved around on the page.<\/p>\n

\"\"<\/p>\n

Partial Compatibility<\/h2>\n

The builder will attempt to render a live preview via AJAX for custom modules that declare partial support. AJAX rendering is not ideal as it’s much slower than normal rendering and it won’t be suitable in all cases. For that reason, its important that developers test their modules and only declare partial support for modules that can actually be successfully rendered via AJAX.<\/p>\n

Declaring Partial Compatibility Example<\/h3>\n