• Resolved Daniel

    (@damen02)


    Hi, Thank you for this amazing plugin!

    I am using your plugin on a website.
    I placed a shortcode to see “Top Cities” on one page.

    In “WP admin > Slimstat > Audience > Top Cities”, several cities are listed correctly, but no data is visible on the front-end. Instead, dev tools shows this line:

    <!-- Slimstat Shortcode Error: invalid parameter for w -->

    I am using Version 5.2.4 of the plugin.

    In Slimstat > Settings > Tracker > Third-party Libraries, I chose JsDeliver.

    How can I solve this problem?
    Thank you!

    The page I need help with: [log in to see the link]

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

    (@amirfallah)

    Hi @damen02

    Please provide the short code you have written so that we can review it and assist you.

    Regards,

    Thread Starter Daniel

    (@damen02)

    Hi @amirfallah, thanks for your answer.

    The shortcode I used is [slimstat f=’widget’ w=’slim_p2_23′][/slimstat]

    I took it from the panel Slimstat > Audience > Top cities > (?) icon.

    The panel “Top cities” in the admin shows detailed info, but is empty on front-end.

    In the previous post I forgot make public the page, now is online.

    https://www.forodelsectorsocial.org.ar/osc/trafico/

    Thread Starter Daniel

    (@damen02)

    Hi everybody!

    I’m still waiting for some answer for this problem:

    Shortcode [slimstat f=’widget’ w=’slim_p2_23′][/slimstat] shows an empty box on front-end.

    I’m looking to display “Top Cities”, that works very fine on back-end!

    Any clue? Thanks

    Plugin Support Amir

    (@amirfallah)

    Hi @damen02

    We apologize for the delay.

    We are currently investigating the reason for the widget not displaying, and we will inform you of the results soon.

    Thank you for your patience.

    Plugin Support Amir

    (@amirfallah)

    Hi @damen02

    We have fixed the issue with the Shortcode Top Cities widget not displaying in the development version with this commit, and it will be completely resolved in the next release

    Thank you for your patience.

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