We were recently made aware of a potentially serious issue with the way Beaver Builder loads in modules and how it can affect those building third party modules. If you’re only overriding core modules in your theme and not creating modules in a separate plugin, you don’t need to worry about this issue.
The issue is that modules with the same relative path (e.g. button/button.php) will conflict with each other and one of them won’t be loaded (core modules take precedence over custom modules). For instance, if you create a custom module with the relative path table/table.php and we later come out with a module that has the same relative path, ours will override yours.
To solve this problem we are recommending that developers namespace their custom modules with a prefix (e.g. my-button/my-button.php) to avoid conflicts with core modules or other developers.
We realize that some of you may have already created modules without namespaces, which is totally fine. Just let us know what the relative paths are in this thread so we can be sure not to create a module with the same one.
At some point in the future we’ll look at fixing this so modules can have the same relative path, but right now that’s a bigger rewrite than we want to take on.
Please let me know if you have any questions and thanks for understanding!
Justin