• Resolved wpress2010

    (@wpress2010)


    I am working on an Elementor site with PPWP (free version). I protected a page, and it works as expected. However, if I go in and try to Edit the page with Elementor, it does not go to the editor, and generates this message: “Sorry the content area was not found in your page. You must call ‘the_content’ function in the current template, in order for Elementor to work on this page.” The page displays normally.

    I created a new identical page from scratch, leaving out any protection. It displays normally, AND I can Edit with Elementor as usual. BUT – if I then add PPWP protection to the new page, it generates the same error message and won’t let me edit it with Elementor. Just FYI.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Quinnie

    (@quinniewpfolio)

    Hi @wpress2010 ,

    Thank you for reaching out.

    This issue is a known conflict between PPWP and Elementor. To resolve it, please try one of the following options:

    1. Enable Elementor Safe Mode:
      • Go to Elementor > Tools > Safe Mode and activate it.
      • Then, try editing the protected page again.
    2. Use the Following Snippet Code:
      You can add this snippet via the Code Snippets plugin or in your theme’s functions.php file:
    add_filter('the_content', 'custom_ppwp_elementor_fix', 20);

    function custom_ppwp_elementor_fix($content) {
    // Check if Elementor is active or if we are editing with Elementor
    if ( defined('ELEMENTOR_VERSION') || isset($_GET['elementor-preview']) ) {
    return $content;
    }

    // Run the default PPWP content protection
    if ( function_exists('ppwp_protect_content') ) {
    return ppwp_protect_content($content);
    }

    return $content;
    }

    This snippet will ensure that the content remains accessible for editing with Elementor while still applying PPWP protection on the frontend.

    Please let me know how it goes or if further assistance is needed.

    Best regards,

    Thread Starter wpress2010

    (@wpress2010)

    Thanks. Adding the snippet to the child theme’s functions.php does not fix the issue. The Safe Mode tactic is just too clunky for me to use.

    • This reply was modified 2 months ago by wpress2010.
    Plugin Support Muhammad

    (@muhammadwpfolio)

    Hi @wpress2010,

    Thanks for the update, and I appreciate you testing that out.

    Since the snippet didn’t resolve the issue and Safe Mode isn’t a good fit, a practical workaround for now would be to temporarily disable protection while editing the page with Elementor, then re-enable it once your changes are complete. This avoids the conflict during editing while still keeping your content protected on the frontend.

    That said, I’ll pass this along to our dev team to further investigate if there’s a more seamless way to handle this in the free version.

    Thanks again for your patience, and feel free to reach out if anything else comes up.

    Thread Starter wpress2010

    (@wpress2010)

    That’s what I’m going to do. Easier to toggle protection on and off – but of course, have to remember the status at all times.

    Plugin Support Muhammad

    (@muhammadwpfolio)

    Hi @wpress2010,

    That sounds like a solid approach for now. As mentioned earlier, we’ve looped in our development team to see if there’s a more seamless workaround or fix we can implement in a future update.

    In the meantime, feel free to toggle the protection as needed while editing — and if anything else comes up, don’t hesitate to reach out.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.