Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • That’s all i can think of at the moment, if you want i can maybe help you debug this further.

    This sounds like the menu is saved, but the editor isn’t loading the nested items back correctly.

    Since the submenu still appears on the frontend, I’d first check whether this is only a Navigation block/editor issue rather than the menu data being lost.

    A quick test would be creating the same menu from Appearance → Editor / Navigation, then inserting that saved menu into the page instead of building it inline.

    If that behaves differently, it tells you the issue is with the block instance, not the menu itself. I can suggest the next check if that helps.

    For one specific category, this usually isn’t a normal settings toggle. The cleaner way is usually filtering the Yoast breadcrumb links and removing that category when it appears.

    CF7 doesn’t really work like a webhook-first form tool out of the box.

    For Airtable/Zapier/Make, I’d usually handle this after a successful form submit: collect the posted fields, format the payload, then send it to the webhook URL.

    The important bit is not just “send data,” but making sure failed webhook calls are logged somewhere so leads don’t silently disappear.

    It sounds like the images are uploaded correctly since they’re showing in the editor, but something is preventing them from rendering on the live site. A few common things you can check:

    • Right-click the missing image on the frontend → Inspect → see if the image URL actually loads when opened directly.
    • Sometimes caching/CDN (like Cloudflare or a plugin) serves broken paths or older versions of the page. Try clearing your cache to confirm.
    • In Divi specifically, if the image was set as a background vs. an inline module, it can behave differently depending on how it’s optimized or loaded.

    If none of those fix it, the issue might be related to how the media files are being referenced in your database or how your hosting environment serves them. That part can get a bit tricky, but the quick checks above should narrow down the cause.

    Let me know what you find when you try those steps — we can dig deeper from there.

Viewing 5 replies - 1 through 5 (of 5 total)