One of the frequent questions we come across is \u2013<\/h5>\n
\u201cI\u2019m using some popular theme which came with with Visual Composer built in. One of the features of Ultimate Addons isn\u2019t working with that theme.\u201d<\/p>\n
Some theme developers edit into the core files & code of Visual Composer<\/strong> for various purpose such as \u2013 adding extra functionality, removing things they don\u2019t like or simply with a purpose with making Visual Composer better in their themes.<\/p>\n Considering Visual Composer is already very developer friendly platform that provides ways to extend itself in an appropriate manner using standard APIs \u2013 this isn\u2019t really a good approach<\/strong>. Doing so usually removes the hooks \/ APIs<\/strong> which Visual Composer provides inbuilt that addons rely on<\/strong>. And as a result, part of the functionality that addons provide, doesn\u2019t work as it normally should. Moreover when theme developers edit into the core files & code of Visual Composer, it becomes difficult for them to provide updates of the plugin and users are left with the older versions.<\/p>\n How to fix this?<\/strong><\/p>\n Usually, this is simple.<\/p>\n