Cloning modules in BeaverBuilder results in mismatched keys
-
It seems like there can be times when the pointers to BeaverBuilder modules gets corrupted if duplicated with Duplicate Post. I have noticed times when a module is selected and then inserted into a page, but the module that was selected is not the one that actually gets inserted.
Here is a screencast of the issue: Screencast of BeaverBuilder — Duplicate Post issue
BeaverBuilder has replicated the problem and here is their reply:
Hey Norm,
Sure enough, I was able to recreate the issue on my local install using the Duplicate Posts plugin via the Clone link within the templates page, and the same issue occurs even on regular templates. It seems like the cloned template takes over the existing template when applied to a page. Weirdly enough, visiting the actual page template works fine. By the way, I published the test page you were working on but set it to Private so only logged in users can see it.
I then tried duplicating the template manually and it works just fine, i.e., I simply applied the global module to a page and duplicated it. The duplicated instance is a standard module, not a global template. I then modified the contents so it’s easily recognizable, saved it as a template and it works just fine when applied to a page.
It most likely has to do with how the Duplicate Posts plugin is duplicating the post.
BeaverBuilder is willing to help out if needed to resolve this issue.
- The topic ‘Cloning modules in BeaverBuilder results in mismatched keys’ is closed to new replies.