V 2.0.0 not working

  • Resolved Tim Reeves

    (@tim-reeves)


    5 years, 7 months ago

    Found this plugin in the WP Repo yesterday and it seemed like just what I wanted – Multisite and minimalistic re-use of the basic tag cloud widget.

    Sadly, it does not work:

    • I really like the MultiSite section allowing to set the same params for all sites. The backend shows and I can set all the values I want. But on “Submit” I get a 404 error for “/wp-admin/network/admin-post.php”. Indeed, there is no such file.
    • So I used the individual settings for one site, these could be saved successfully. For example, I set the size range from 1 to 2 em, but I still see the standard “pt” sizes.

    Would be great if you could fix these teething problems, as I really like the concept. Thanks in advance!

    Tim

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author azurecurve

    (@azurecurve)

    5 years, 7 months ago

    Hi Tim,

    I’ve fixed the first issue with the multisite settings, but I can’t reproduce your second.

    When I change the unit to em and set smallest 1 and largest 10, I get a much changed tag cloud showing with very large test for the most used tag.

    Ian

    Thread Starter Tim Reeves

    (@tim-reeves)

    5 years, 7 months ago

    Hi Ian,

    wow that was quick! How can I get the new version?

    Re the settings not working – OMG my mistake, I had used the standard widget, not yours. My thinking was, that if you set parameters to the standard widget, then obviously I need to use the standard widget. Perhaps this point could be made clear in the description?

    Thanks!

    Tim

    Plugin Author azurecurve

    (@azurecurve)

    5 years, 7 months ago

    You happened to catch me at the computer 🙂

    The new version should show up in the WordPress Updates section soon.

    I’ll update the plugin to explicitly mention on the settings page that the widget has to be used.

    Thanks for the suggestion.

    Ian

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘V 2.0.0 not working’ is closed to new replies.