Divi global modules can disappear, lose their editing controls, or break surrounding layouts when a Divi Library item saves only a placeholder instead of valid module shortcode. In this case, the affected global module contained [et_pb_module_placeholder selected_tabs="all"] rather than a real et_pb_text module body. Creating a clean replacement from valid existing module content restored normal editing and saving without changing the live page during testing.
Issue background
A new year-based toggle was being added to a Divi page using an established Divi Library workflow. Instead of behaving like the existing global toggle modules, the imported item appeared as a section and did not provide the expected settings gear or delete controls.
Dragging or reordering the item made the problem worse. After saving, the existing toggles disappeared, leaving an empty row and only the newly imported item.
The issue could be reproduced on a duplicated page, in Divi Safe Mode, and inside a newly created Divi Library row. Updating Divi, rolling it back, and installing a fresh current build did not change the behavior.
Diagnosis
The page shortcode structure was inspected first and appeared valid. The working year modules referenced normal global_module IDs, while the new item had been created through Divi’s standard Library workflow.
Browser debugging did not reveal a clear JavaScript or network save failure. The only notable console message was:
MaxListenersExceededWarning (EventEmitter scroll_end_event)Because the behavior persisted in Safe Mode and after Divi version changes, the investigation shifted from theme conflicts to the stored Divi Library content itself.
The malformed global module had normal Divi taxonomy and metadata:
layout_type=modulemodule_width=regularscope=global
However, its entire content body was only:
[et_pb_module_placeholder selected_tabs="all"]This confirmed that the problem was not missing taxonomy, a PHP fatal error, or a network-level save failure. Divi’s placeholder-first creation process had failed to replace the temporary placeholder with real module shortcode.
Resolution steps
- Reproduce the issue away from the live page. Duplicate the affected page or create an isolated Divi Library test layout. Confirm that importing and saving the global module produces the same disappearing or broken-module behavior.
- Inspect the stored Library item. Query the affected
et_pb_layoutitem and review itspost_content. A module that contains only[et_pb_module_placeholder selected_tabs="all"]is malformed. - Verify Divi metadata and taxonomy. Confirm that the item still has the expected
scope=global,layout_type=module,module_width=regular, and module type metadata. This separates a malformed content body from a missing-meta problem. - Do not overwrite the broken item immediately. Leave the original Library item and live-page references untouched while creating and testing a replacement. This provides a clean rollback path.
- Start from valid module content. Create a new global module using a known-good existing module body as the starting point rather than relying on the failing placeholder-first workflow. In this case, the replacement was created as a real
et_pb_textglobal module from the beginning. - Confirm the replacement content. Verify that the new item contains a real Divi module shortcode, has the expected global scope and taxonomy, and does not contain
et_pb_module_placeholder. - Update only the isolated test layout. Replace the malformed
global_modulereference in the duplicated page or test layout. Save the layout and confirm that the module remains visible and editable. - Test repeated saves and editing. Open the module settings, modify content, reorder the item, save several times, and reload the builder. Confirm that other global modules remain intact.
- Replace the live reference after verification. Once the clean global module behaves normally, import or reference it on the production page and perform another complete editing and frontend check.
Programmatically duplicating a Divi Library item can also fail if the item’s taxonomy terms and module metadata are not preserved. Cloning only the shortcode content is not sufficient. Always verify the new item’s Divi layout type, width, global scope, and module type before using it.
Final outcome
The clean replacement global module imported normally, displayed the expected Divi controls, and continued to work after the page was saved. The existing global modules no longer disappeared, and the production page could be updated with the new toggle without modifying or deleting the broken legacy Library items during diagnosis.
The key diagnostic signal was the placeholder shortcode stored as the complete module body. When Divi Library items behave like empty sections, lose controls, or vanish after saving, inspecting the underlying et_pb_layout content can reveal a malformed placeholder that standard theme rollbacks and Safe Mode testing will not resolve.
For help troubleshooting Divi global modules, malformed Divi Library items, or WordPress builder data issues, contact Freshy.
