<\/p>\n
![\"Divi](\"https:\/\/digitalmarketstore.com\/wp-content\/uploads\/2026\/06\/Copilot_20260625_001304-1024x683.png\")
<\/p>\n
Introduction<\/h2>\n
Let me paint the picture.<\/p>\n
I built a simple Safelist Manager tool \u2014 something to keep my marketing organized. It worked flawlessly on Google Sites. But when I moved it over to my Divi 5 website, the buttons just sat there like props. They looked great, but clicking them did absolutely nothing.<\/p>\n
No errors.
\nNo warnings.
\nJust dead buttons.<\/p>\n
If you\u2019ve ever tried running JavaScript inside Divi 5, you already know this pain. This article breaks down what\u2019s actually happening, why Google Sites doesn\u2019t fight you, and the exact moment \u2014 literally right before I fell asleep \u2014 when I finally figured out the solution.<\/p>\n
Why I Built My Safelist Manager<\/h2>\n
I wanted a simple dashboard where I could:<\/p>\n
- \n
- Track safelist websites<\/li>\n
- Store usernames, passwords, and credits<\/li>\n
- Log last sent dates<\/li>\n
- Auto\u2011calculate next send dates<\/li>\n
- Keep notes<\/li>\n
- Upload and download CSV files<\/li>\n
- Save everything locally<\/li>\n<\/ul>\n
So I built it. And on Google Sites, it ran perfectly on the first try.<\/p>\n
Here\u2019s the working version:<\/strong>
\nhttps:\/\/sites.google.com\/view\/safelistmanager\/home<\/a><\/p>\nDivi 5 vs Google Sites: Two Completely Different Experiences<\/h2>\n
Google Sites: The Easy One<\/h3>\n
Google Sites doesn\u2019t interfere with your code. It lets you run:<\/p>\n
- \n
- Inline JavaScript<\/li>\n
- Event listeners<\/li>\n
- LocalStorage<\/li>\n
- Modals<\/li>\n
- Tables<\/li>\n
- CSV parsing<\/li>\n<\/ul>\n
Paste your code, publish, done.<\/p>\n
Divi 5: The Builder With Rules<\/h3>\n
Divi 5 is a different story. It uses:<\/p>\n
- \n
- A new rendering engine<\/li>\n
- Shadow DOM<\/li>\n
- Iframe\u2011based modules<\/li>\n
- JavaScript sanitization<\/li>\n
- Delayed loading<\/li>\n<\/ul>\n
Which leads to:<\/p>\n
- \n
- Inline onclick handlers get stripped out<\/li>\n
- Your script can\u2019t \u201csee\u201d inside Divi\u2019s iframe<\/li>\n
- Event listeners attach too early<\/li>\n
- Buttons look fine but do nothing<\/li>\n<\/ul>\n
That\u2019s the core of the Divi 5 JavaScript problem.<\/p>\n
Why Divi 5 Buttons Don\u2019t Work<\/h2>\n
Here\u2019s the simple explanation:<\/p>\n
Divi 5 puts your HTML inside an iframe.<\/strong>
\nYour JavaScript runs outside that iframe.<\/p>\nSo when your script tries:<\/p>\n
document.getElementById(\"addEntryBtn\");<\/code><\/pre>\nDivi basically says, \u201cThat element doesn\u2019t exist.\u201d<\/p>\n
That\u2019s why:<\/p>\n
- \n
- Add Entry doesn\u2019t work<\/li>\n
- Notes don\u2019t open<\/li>\n
- Delete doesn\u2019t fire<\/li>\n
- Sorting and filtering don\u2019t respond<\/li>\n<\/ul>\n
CSV upload works because file inputs behave differently, but everything else is blocked.<\/p>\n
What I Tried (And Why It Didn\u2019t Work)<\/h2>\n
Inline onclick<\/h3>\n
Divi strips them instantly.<\/p>\n
Event listeners<\/h3>\n
They attach before the module exists.<\/p>\n
Delays<\/h3>\n
Even with timeouts, Divi sometimes loads modules after the delay.<\/p>\n
Iframe targeting<\/h3>\n
Divi uses nested containers with changing class names.<\/p>\n
Theme Options JavaScript<\/h3>\n
Still runs outside the iframe.<\/p>\n
My Aha Moment: The Fix That Finally Worked<\/h2>\n
Here\u2019s the part you\u2019ll appreciate.<\/p>\n
After hours of testing, I finally gave up for the night. I went to bed frustrated. And right before I fell asleep, I had a sudden, crystal\u2011clear aha moment:<\/p>\n
I realized I was putting the code on a normal Divi 5 page \u2014 but I needed to switch to Classic View, add a module, then add an element inside that module, and choose the Code element. Once I did that, everything worked.<\/strong><\/p>\n
That was it.<\/p>\n
The moment I moved the code into:<\/p>\n
Classic View \u2192 Add Module \u2192 Add Element \u2192 Code<\/strong><\/p>\n
everything came to life:<\/p>\n
- \n
- Buttons fired<\/li>\n
- Notes opened<\/li>\n
- Event listeners attached correctly<\/li>\n
- The tool behaved exactly like it did on Google Sites<\/li>\n<\/ul>\n
It wasn\u2019t the code.
\nIt wasn\u2019t the logic.
\nIt wasn\u2019t the tool.<\/p>\nIt was the placement.<\/p>\n
Lesson Learned: Never Give Up When the Solution Is Near<\/h2>\n
This whole experience taught me something important \u2014 something we all forget when we\u2019re knee\u2011deep in a problem:<\/p>\n
Most problems aren\u2019t impossible. You just quit too early.<\/strong><\/p>\n
I was one tiny step away from the solution the entire time.
\nThe code wasn\u2019t broken.
\nMy logic wasn\u2019t wrong.
\nThe tool wasn\u2019t flawed.<\/p>\nI just wasn\u2019t placing the code in the one spot where Divi actually allows JavaScript to run.<\/p>\n
It\u2019s wild how often the answer shows up right after you decide to take a break. That late\u2011night \u201caha moment\u201d wasn\u2019t luck \u2014 it was persistence.<\/p>\n
Here\u2019s the takeaway:<\/p>\n
- \n
- Don\u2019t walk away when you\u2019re close.<\/li>\n
- Don\u2019t assume the platform is wrong \u2014 sometimes it\u2019s just picky.<\/li>\n
- Don\u2019t give up when the finish line is one small adjustment away.<\/li>\n<\/ul>\n
If I had quit earlier, I never would\u2019ve discovered the Classic View trick.<\/p>\n
Working Example: My Google Sites Version<\/h2>\n
https:\/\/sites.google.com\/view\/safelistmanager\/home<\/a><\/p>\n
Everything works there:<\/p>\n
- \n
- Add Entry<\/li>\n
- Delete<\/li>\n
- Notes<\/li>\n
- Sent Today<\/li>\n
- CSV Upload<\/li>\n
- CSV Download<\/li>\n
- JSON Backup<\/li>\n
- Templates<\/li>\n
- Filtering<\/li>\n
- Sorting<\/li>\n<\/ul>\n
My Two Divi 5 Pages (And Their Issues)<\/h2>\n
- \n
- https:\/\/digitalmarketstore.com\/safelist-manager\/<\/a><\/li>\n
- https:\/\/digitalmarketstore.com\/safelist-control-hub\/<\/a><\/li>\n<\/ul>\n
The UI loads.
\nThe inputs load.
\nThe table loads.
\nCSV upload works.<\/p>\nBut the buttons don\u2019t execute unless the code is placed inside Classic View \u2192 Code Module.<\/p>\n
Who This Is Best For<\/h2>\n
Beginners<\/h3>\n
Google Sites is perfect \u2014 no restrictions.<\/p>\n
Divi users building interactive tools<\/h3>\n
Use Classic View or wait for updates.<\/p>\n
Developers building dashboards<\/h3>\n
Google Sites, Webflow, or standalone HTML will save you time.<\/p>\n
Anyone who wants buttons to actually work<\/h3>\n
Right now, Google Sites wins.<\/p>\n
FAQ<\/h2>\n
Q: Why don\u2019t my JavaScript buttons work in Divi 5?<\/strong>
\nA: Divi 5 renders modules inside an iframe and strips inline JS.<\/p>\nQ: Why does the same code work in Google Sites?<\/strong>
\nA: Google Sites doesn\u2019t block JavaScript.<\/p>\nQ: Can Divi 5 run JavaScript?<\/strong>
\nA: Yes \u2014 but reliably only in Classic View \u2192 Code Module.<\/p>\nQ: Should I wait for Divi updates?<\/strong>
\nA: Yes. Divi 5 is still evolving.<\/p>\nQ: Should I move my tool to Google Sites?<\/strong>
\nA: If you need it working today, yes.<\/p>\nConclusion + CTA<\/h2>\n
After all the debugging and frustration, here\u2019s what I learned:<\/p>\n
- https:\/\/digitalmarketstore.com\/safelist-control-hub\/<\/a><\/li>\n<\/ul>\n
- https:\/\/digitalmarketstore.com\/safelist-manager\/<\/a><\/li>\n