• Resolved mcroyworg

    (@mcroyworg)


    Hello,

    A big issue for me. when I insert the popoup widget, i can’t able to salve the page. it show an error “500 Internal Server Error”. I try to change php version, to clear all caches and disable all other plugin, but it doesn’t work. when I disable the plugin, everything come back “normal”.

Viewing 1 replies (of 1 total)
  • Plugin Author Veelo

    (@veelo)

    Hi! Sorry you’re hitting this.

    A 500 during save usually means a server-side PHP fatal when Elementor tries to process the document that contains the widget. To help us fix it fast, could you please:

    1. Enable WordPress debug log
      Edit wp-config.php and add (above the line “/* That’s all, stop editing! */”):

    define('WP_DEBUG', true); define('WP_DEBUG_LOG', true); define('WP_DEBUG_DISPLAY', false); @ini_set('display_errors', 0);

    Then try to save the page again (with the popup widget on it). After it fails, send us the last ~50 lines of /wp-content/debug.log.

    1. Grab the failing request from DevTools
    • Open Chrome DevTools → Network.
    • Click Update/Publish in Elementor.
    • Select the request to /wp-json/elementor/v1/save (or similar) that returns 500.
    • Send us a screenshot of the Response tab and the Headers (especially Response and Status).
    1. Environment details
    • WordPress version
    • Elementor version
    • Popup for Elementor version
    • PHP version
    • Active theme
    1. (If possible) Quick server checks
      Ask your host if ModSecurity blocked the request (common with JSON payloads). If there’s a hit, please whitelist the rule for this endpoint. Also confirm:
    • memory_limit ≥ 256M
    • max_input_vars ≥ 5000
    • post_max_size and upload_max_filesize ≥ 32M

    Meanwhile, as a workaround, try Elementor → Tools → Safe Mode and switch temporarily to the Hello theme; then try saving.

    Thanks! Once we have the error line from debug.log, we’ll ship a fix or provide a patch right away.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.