• Resolved deothemes

    (@deothemes)


    Not sure why, but it does not work for me. I tried to insert a shortcode in Elementor and got critical error. Tried to add it as a block and no result. When entering plugin slug and saving the page after page refresh plugin slug is empty and nothing is showing.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Nick Diego

    (@ndiego)

    Hi @deothemes,

    Thanks for reaching out and I apologize for the issues you are experiencing. I just tested a shortcode in Elementor and was unable to replicate. Would you be able to share the critical error that you are getting (this might be stored in your sites PHP logs) as well as the version of WordPress you are running. That will help be further diagnose the issue.

    Thanks,
    Nick

    Plugin Author Nick Diego

    (@ndiego)

    Just following up on my previous comment.  Would you be able to share the critical error that you are getting (this might be stored in your sites PHP logs) as well as the version of WordPress you are running. That will help be further diagnose the issue.

    Thanks,
    Nick

    Thread Starter deothemes

    (@deothemes)

    There you go:

    Warning: Undefined array key "”single”" in /home/.../wp-content/plugins/easy-plugin-stats/includes/shortcode.php on line 74

    Thread Starter deothemes

    (@deothemes)

    By the way, I copied the code directly from the How do I use the shortcode? FAQ section. After retyping the type=”single” with proper quotation marks, which is probably the cause of the ciritical error I got an empty div. Here is my shortcode code example:

    [eps type="single" slug=”nocturne-dark-mode” field=”active_installs” cache=”43200″ before=”” after=””]

    Thread Starter deothemes

    (@deothemes)

    Update: I retyped all the quotations and finally got the result on the front-end 🙂

    Plugin Author Nick Diego

    (@ndiego)

    Thanks for the additional info. WordPress likes to convert straight quotes to curly quotes when you copy and paste. That said, this should not have caused a critical error on the frontend. I just pushed up v2.0.1 that patches that bug.

    Let me know if you run into any further issues. 🙏

    Best,
    Nick

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